Skip to content
checkaifree

Local image workflow

Photo metadata tasks: dates, orientation, thumbnails and batch handoffs

Start with the question your file needs to answer. A capture timestamp, a display rotation, an embedded preview and a batch inventory are different outputs; this center helps you choose and verify the one you need.

18 October 2026 · Check AI Free

Pick the result you need

Pick the result you need
QuestionPrimary toolKeep or check
Which stored date describes capture?Photo date viewerEach source, raw string, offset, subsecond digits and warning
Can this date be converted to UTC?Photo date viewerUnknown offsets stay unknown; a UTC day can differ from the stored local day
Why does this JPEG appear sideways?Photo orientation fixerEncoded dimensions, tag1–8 and the actual re-encoded display copy
Is there an older or different embedded preview?EXIF thumbnail extractorOriginal IFD1 JPEG bytes and dimensions, or an explicit empty/unreadable result
What does a collection contain?Batch metadata inspectorOne localID/result per selected file, including failures and same-name inputs
Can I hand off clean copies?Batch section of metadata removerVerified output files, policy, original-name choices and the per-file ZIP manifest

Three defined camera-workflow scenes

These are reproducible source definitions and variants of one self-authored corner chart. They are not independent camera captures or an accuracy benchmark. All date and camera fields are invented, and the separately encoded purple thumbnail deliberately differs from the main chart.

Three defined camera-workflow scenes
SceneObserved or expected task outputDecision
S-H02-CAMERA · date-offset.jpgKnown+05:30 capture, tag6, a separate48×32 thumbnailPreserve the source records; make a new display copy only if you want to accept re-encoding.
S-H02-MISSING · unknown/absent controlsUnknown capture timezone, empty thumbnail or no embedded dates depending on the selected fileKeep missing and unknown states; the browser clock supplies no replacement capture time.
S-H02-DIAGNOSTIC · conflict/broken controlsComparable date conflict or unreadable thumbnail rangeRetain the warning and obtain an intact or better documented source rather than inventing a repair.

Build a handoff that another person can check

  1. Step 1

    Keep the input role clear

    Record whether each file is the original, a download, an editor export or a generated copy. Use batch localIDs when filenames repeat, and keep a separate private mapping if you omit original names from reports.

  2. Step 2

    Separate reading from transformation

    Date reading and thumbnail extraction do not change the source. Orientation normalization re-encodes a new image and drops metadata. Metadata removal copies retained compressed image bytes under its chosen category policy. Pick the method whose effects you can accept.

  3. Step 3

    Verify the output you will actually send

    Reopen downloaded images or extracted ZIP entries, preserve partial/error rows in the report, and inspect warnings. A complete archive, a present camera field or a plausible date is not a certificate of image authenticity or private-data removal.

Follow the task-specific limits

The batch inspector supports JPEG/PNG/WebP; the dedicated date, orientation and thumbnail operations currently support JPEG only. Batch count and byte limits, bounded PNG text limits, orientation pixel limits and unsupported animation policies are shown in the respective tools. An unsupported or damaged component is not the same as a missing field.

If sharing privacy is the goal, use the privacy center to choose a removal policy and read the resulting file. Camera timestamps, thumbnails and other stored records may contain information you do not intend to distribute, while faces and signs visible in pixels need a separate visual review.

Sources and reproducible inputs

Continue with your file