What Metadata Does a Photo Editing App Add or Remove?

Raw camera output is one metadata story. After Lightroom, Snapseed, VSCO, or Photoshop exports a JPEG, the file may tell a different story — sometimes less GPS, sometimes more software fingerprint. This is distinct from social re-compression (remove EXIF data social media path) and distinct from HEIC conversion (HEIC to JPG).

Platform baseline differences: metadata differences between iPhone and Android photos. Two-file confusion: why two copies of the same photo can have different metadata.

What editors typically preserve

Copyright, creator name, camera Make/Model, lens, exposure — when export preset says ‘keep all except GPS’ or similar. Professionals want lens data for portfolio; privacy users want GPS gone but artist credit kept.

What editors add

Software identity: ‘Adobe Lightroom Classic,’ ‘Snapseed,’ visible in EXIF/XMP.

Edit history XMP: Lightroom and Photoshop can record adjustment steps in XMP sidecars or embedded packets — revealing that a image was edited even if pixels look natural.

DerivedFrom / DocumentID: Ties exported JPEG to catalog UUID — useful for DAM, leaky if you thought export was anonymous.

Fresh timestamps: DateTime digitized shifts to export moment — can contradict ‘candid untouched’ claims.

What editors remove — intentionally or not

GPS IFDs when ‘Remove location info’ checked. MakerNotes may strip if re-encoded from pixels only. Thumbnails regenerated — old thumbnail GPS leak may disappear or move depending on rewrite depth.

‘Save for web’ low-quality exports may drop most metadata as side effect of recompress. ‘Save As copy’ from Photoshop with metadata toggle off is explicit removal.

Mobile filter apps

Often write minimal EXIF — Software tag with app name, sometimes strip GPS by default, sometimes retain everything from source HEIC. Behavior changes per app version without announcement.

Workflow recommendation

1. Know your editor’s export metadata preset before publishing.
2. Run final share JPEG through MetadataWipe for a consistent clean baseline.
3. Verify with metadata viewer — how to verify metadata was removed.
4. Keep RAW/catalog originals separate from public exports.

Non-destructive edits versus exported JPEG

Lightroom and Capture One keep adjustments in catalogs or sidecars — the exported JPEG is a new artifact with its own metadata story. Editing in Photoshop with ‘Maximize Compatibility’ can embed a flattened TIFF preview inside PSD that retains tags you thought you removed on export. Always inspect the attachment file, not the project file, before email or publication.

Batch export consistency

Teams exporting fifty portfolio JPEGs with mixed metadata presets ship inconsistent headers — some with GPS, some without. Standardize on one export preset plus MetadataWipe pass for client deliverables so every file matches the same privacy baseline regardless of which editor touched the RAW.

RAW versus exported JPEG metadata

RAW/DNG files carry extensive MakerNotes never meant for client JPEGs — but accidental ‘export with all metadata’ copies GPS into deliverables. Editors can strip location on export while keeping copyright. If unsure, run the JPEG through MetadataWipe as final gate — same habit as virus scan before send.

Collaborative edits multiply versions: photographer exports with GPS, retoucher re-exports without checking preset, social manager posts from the wrong folder. A final MetadataWipe pass on the canonical share JPEG reduces version roulette.

Preset naming in Lightroom — ‘Web strip GPS’ versus ‘Print keep all’ — prevents the wrong export when interns pick from a dropdown under deadline. Document presets in your studio wiki, not only in one senior editor’s head.

Capture One sessions synced to iPad for client review can export with different metadata toggles than the desktop default — verify the iPad export, not only the master RAW.

Freelancers billing by the hour should line-item ‘metadata strip pass’ on deliverables — it documents privacy work clients forget to ask for until something leaks.

JPEGmini and other recompressors may preserve XMP you thought Lightroom removed — re-inspect after any optimizer pass.

Export-for-web presets that downsize to 2048px still carry tags unless the preset explicitly clears them — size reduction is not metadata removal.

Related guides

See also:

• Metadata differences between iPhone and Android
• Why two copies can have different metadata