Engineering note

# How do shared photo copies lose location metadata?

Last reviewed 20 November 2026

Two fresh copies remove source metadata from shared photos; original exports keep their imported bytes.

## What happens on the phone?

Publishing an item page sends prepared copies, rather than the imported original files. The sharing path renders up to five photos in item order with a longest edge of 1440 pixels, draws each onto a fresh opaque white canvas and encodes it as JPEG. It reduces JPEG quality if needed and refuses a copy that cannot fit below the upload limit.

The app draws the image itself; it does not copy the original file’s EXIF location, camera details or other metadata into the shared copy. This happens whether you choose the original appearance or studio edits for the page.

## Why does the server save the pixels again?

The sharing service independently decodes each uploaded JPEG under size and memory bounds, then encodes a new JPEG using only its width, height and pixel data. It does not pass the uploaded file through to storage.

This drops source EXIF and GPS information, comments, colour profiles and payloads appended to the file. The small card image used for previews is also encoded from pixels, using the first gallery photo. The stored images are fresh JPEGs, not files with every kind of header removed.

## Do original exports change too?

No. Original-photo exports copy the imported bytes, including any metadata. Vinted exports use originals. Sharing an original file elsewhere is a different action from publishing a Keepmere item page.

The vault retains the originals separately from its edits and shared copies.

## Can the picture still reveal a location?

Yes. A street sign, address label or reflection is part of the picture, not hidden metadata. Review every photo and the public text before publishing. Anyone with a page link can view, save or forward it; removing a page cannot recall a saved copy.

## Which implementation was checked?

- `ListingBench/SharingClient.swift · sharedPhotos`

- `ListingBench/PhotoEngine.swift · prepared`

- `ListingBench/BenchStore.swift · photoURLs / exportItems`

- `server/src/content.ts · cleanPhoto / leadPhoto`

- `server/src/items.ts · publish`

Checked against the repository on 20 November 2026. This describes the implementation; it is not a separate audit of a deployed service.

## Keep reading

[Item pages without a script dependency](https://keepmere.app/notes/item-pages-without-javascript/) [Readable ten-character page codes](https://keepmere.app/notes/readable-page-codes/) [Photo rules and field order](https://keepmere.app/marketplace-photo-rules/) [Privacy and sharing](https://keepmere.app/privacy) [All engineering notes](https://keepmere.app/notes/)

Canonical: https://keepmere.app/notes/shared-photo-metadata/
