EXIF Metadata Explained: What a Photo Can Contain

EXIF describes capture and image properties

Exif was developed for digital still cameras and related systems. Its fields are organized in directories and tags that can describe dimensions, orientation, date and time, exposure, aperture, focal length, sensitivity, flash, lens or camera identity, a preview thumbnail, and GPS measurements. Devices and editors choose which supported fields to write, so two photographs rarely contain identical tag sets.

A tag’s presence does not guarantee correctness. A camera clock may be wrong, coordinates can be edited, and software can copy stale values. Metadata is evidence supplied by a device or workflow, not cryptographic proof of who made an image or exactly where it was captured.

• Capture tags help photography and catalog workflows.
• Orientation can tell software how stored pixels should be displayed.
• GPS is optional and may be absent even when a photo app displays a place.

EXIF is not the whole metadata story

Image files can carry information outside EXIF. XMP can store extensible editing and rights data; IPTC-oriented fields can describe creators, captions, keywords, and licensing; ICC profiles describe color interpretation. File-system properties, sidecar files, cloud-library records, and platform database entries may exist outside the image bytes entirely.

That distinction matters when a tool says it removes EXIF. A selective tag editor may leave XMP or another container segment untouched. Tool Packer instead decodes the supported image into visible pixels and exports a fresh JPG, PNG, or WebP copy without deliberately copying the source metadata, but it does not certify every possible external record.

• Embedded metadata can travel with the file.
• Sidecars and catalogs travel separately.
• Visible watermarks and captions are pixels, not hidden tags.

Orientation and previews require special care

Some cameras store pixels in one orientation and rely on an EXIF orientation tag to rotate or mirror them for display. A cleaner that deletes the tag without transforming pixels can make the result appear sideways. A browser decode-and-export workflow normally renders the oriented view into new pixels before producing the derivative, but the downloaded copy should still be opened and checked.

Embedded thumbnails can be independent miniature images. A careful clean export should not copy that preview, while a narrowly selective editor needs to account for it. Compare the final composition, dimensions, transparency, color, and orientation rather than looking only at the file extension.

Choose preservation or removal by purpose

An archive master may benefit from capture time, authorship, rights, color, and camera information. A public sharing derivative often does not need precise coordinates, device identifiers, or editing history. Keep these purposes separate: retain the trusted original privately and publish a purpose-built copy.

Re-encoding is not a forensic erasure of every system that has handled an image, and it cannot retract a file already shared. It can also change compression, animation, resolution, or color behavior. Make the clean copy before disclosure, verify it, and keep the master out of the upload selection.

• Preserve the original when provenance matters.
• Minimize the derivative when privacy matters.
• Document the chosen workflow for repeatable publishing.