CartVisual
Sign inCreate account

Assets & tasks / PRACTICAL ANSWER

How Do I Avoid Mixing RAW Files From One Memory Card With JPEG Previews From Another Shooting Session?

A RAW file and JPEG with the same basename are not necessarily a valid capture pair. Cameras can reuse file numbers, and separate cards or sessions may contain colliding names. Preserve each card's original folder and compare capture metadata, camera identity and visible content before linking previews to editable originals.

01 / HOW DO I AVOID MIXING RAW FILES FROM ONE MEMORY CARD WITH JPEG PREVIEWS FROM ANOTHER SHOOTING SESSION?

Treat filenames as labels, not unique capture identifiers

Start with an untouched copy of each card. Keep the original directory structure and record the card or session from which every file was transferred.

Inspect the candidate RAW and JPEG pair's camera model, available serial number, capture time and exposure settings. Lightroom Classic supports metadata-based organization, while ExifTool documents detailed EXIF and composite timestamp fields.

A basename such as IMG_0042 may appear in multiple sessions. A matching name is therefore useful only when it is supported by the capture context. Similarly, a matching timestamp without sufficient precision may be ambiguous during rapid shooting.

02 / HOW DO I AVOID MIXING RAW FILES FROM ONE MEMORY CARD WITH JPEG PREVIEWS FROM ANOTHER SHOOTING SESSION?

Check the actual image relationship

Compare product orientation, hand position, reflections, label text and background landmarks. A camera-produced JPEG may apply picture styles, sharpening and tone mapping that differ from the RAW editor's initial interpretation, so pixel-identical appearance is not required.

The relevant question is whether both files represent the same exposure event. If one image shows a closed lid and the other an open lid, the pair is incorrect regardless of filename.

Where the camera records subsecond timestamps, include them. ExifTool's SubSecDateTimeOriginal composite can combine available date, subsecond and time-zone information. Do not invent precision absent from the source metadata.

03 / HOW DO I AVOID MIXING RAW FILES FROM ONE MEMORY CARD WITH JPEG PREVIEWS FROM ANOTHER SHOOTING SESSION?

Hypothetical two-card collision

Hypothetical illustration—not an inspected camera archive: card A contains RAW file DSC_0042 captured at 09:15:02 during a blue-bottle session. Card B contains JPEG DSC_0042 captured at 16:40:18 during a red-bottle session.

Pairing by basename would attach the red preview to the blue RAW. The different capture times and product colors reveal the conflict.

A second JPEG named DSC_0042 from the morning session may be a better candidate, but the editor still checks its camera identity, timestamp and scene content before accepting it.

No actual memory cards or image metadata were examined for this example.

04 / HOW DO I AVOID MIXING RAW FILES FROM ONE MEMORY CARD WITH JPEG PREVIEWS FROM ANOTHER SHOOTING SESSION?

Create a durable pairing manifest

Assign each capture a stable internal identifier that includes its session and source location. Record the RAW path, JPEG path, original filenames, capture time and verification status.

Do not rename or overwrite the originals until the mapping is established. If the camera stores RAW and JPEG on separate cards, verify that both cards cover the same capture interval and that no images were omitted during transfer.

If a pair remains ambiguous, keep it unpaired and use the confirmed RAW source for editing. A wrong preview can cause a merchant to approve the wrong color or packaging revision.

After pairing, check a representative set at the beginning, middle and end of each session, plus every collision. The completed manifest should make the relationship reproducible without relying on the original operator's memory.

05 / HOW DO I AVOID MIXING RAW FILES FROM ONE MEMORY CARD WITH JPEG PREVIEWS FROM ANOTHER SHOOTING SESSION?

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Hypothetical sourceFilenameCapture timeVisible productPairing status
Card A RAWDSC_004209:15:02Blue bottleOriginal to identify
Card B JPEGDSC_004216:40:18Red bottleReject basename-only pairing
Morning JPEG candidateDSC_004209:15:02Blue bottleVerify camera and exposure

Download the editable CSV worksheet

06 / HOW DO I AVOID MIXING RAW FILES FROM ONE MEMORY CARD WITH JPEG PREVIEWS FROM ANOTHER SHOOTING SESSION?

What the references establish

Published by CartVisualPublished Updated Evidence and editorial policy
SOURCES & SCOPE

Sources and further reading

Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.

QUESTIONS, ANSWERED

Frequently asked questions

Does matching IMG_0042 across two cards prove the files are paired?

No. File numbers can recur. Verify capture context, timestamps, camera identity and image content.

Must the JPEG look exactly like the RAW editor's preview?

No. Camera processing and RAW interpretation can differ. The files must represent the same capture, not necessarily the same rendered colors.

PREPARE ASSETS FOR YOUR NEXT STEP

Create supporting product assets in CartVisual.

Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.

Create account and open this workspace Check pricing and credits

Start with free concept and copy planning after sign-in. Image and video generation require available credits; review the quote before starting.

Already have an account? Open the workspace.