Home Wi-Fi question

How do I import camera-card photos without creating a mess?

Questions with the same meaning and scope are grouped here; questions with different scope stay separate.

Quick answer

Current answer

Use a dedicated intake folder for each camera-card session, copy before sorting, and organize only after the copied batch has been checked. A clear session name, one destination rule, and a short review keep card imports from scattering files across your library.

Prepare a session folder

Before connecting a card, make an intake folder that identifies the shoot without relying on a camera-generated folder name. A pattern such as 2026-09-18_Garden-walk_camera-intake works well. Put every file from that card session in this one place first, including video clips and sidecar files that may hold adjustments or settings. If the card contains more than one outing, use separate intake folders after copying, based on the dates and subjects you can confirm. Avoid importing into a random desktop folder, because it is easy to lose track of what still needs review.

Copy, then check the transfer

Use your photo application’s import command or copy the card contents into the intake folder. Let the copy complete without disconnecting the card. Compare file and folder counts where practical, then open samples from the beginning, middle, and end of the session. Include a video or raw image if the camera creates them. This check is about confirming that the copied files open from the destination; it is not enough that filenames appear in a list. Leave the card unchanged while you organize the new copy.

Organize from the intake area

Review the session in chronological order and assign the keepers to your established year, month, and event folders, or import them into the relevant managed library. Preserve the camera capture date. Add a concise event name and a few search terms where your system supports them, especially when an event title would not be obvious later. If several files are near-duplicates, mark a preferred version instead of rushing to remove the others. Keeping an intake folder until review is finished gives you a safe place to compare them.

Close out the session safely

After organization, look at the destination folders or library view and confirm the session is represented across its date range. Confirm that the main library has its normal separate copies before considering the card ready for its next use. Keep a simple import log with the card session name, date imported, and destination; one line is enough. If an import was interrupted, begin a new intake folder and compare it with the first attempt rather than mixing partial and repeated copies together.

Sources

These official sources can help you check the next step for your equipment.

  1. National Archives: Digitizing family archives — National Archives: Digitizing family archives
  2. Library of Congress: Personal Digital Archiving — Library of Congress: Personal Digital Archiving

Before making disruptive changes

  • Do not format or erase a camera card until the copied files open from their intended library location and your usual backup process has run.
  • Camera folder names and sequential filenames can repeat across cards, so they are not safe unique identifiers by themselves.
  • Import tools may offer an automatic duplicate option; review its rules before allowing it to skip or combine files.
Scope & boundaries
Applies when
Personal digital photo organization and preservation question limited to: How do I import camera-card photos without creating a mess?
Does not apply when
Excluded when: account recovery device hardware repair photo copyright or ownership decisions irreversible deletion operations repairing damaged physical originals guaranteed data recovery legal, insurance, or professional custody conclusions.
Check first
  • Check first

    Does your situation match the recorded scope and exclusions?

    A scope or exclusion mismatch can mean that a different canonical question is needed.

Not the question you meant?

Find another question

This does not submit feedback or change this question.

Technical question record
Canonical question ID
920c2e5b-e02d-7e93-a600-fddae30e29b4
Identity revision
1
Source language
en