Event Photo Metadata: What to Keep and What to Strip
TIME&SPACE · Photographer's Edge
Every file you deliver carries a hidden layer of data. Some of it protects your authorship. Some of it tells a stranger where a guest was at 23:14.
Event Photo Metadata: What to Keep and What to Strip
In short: Keep copyright and creator. Strip GPS. Most photographers do neither on purpose, which means they ship files that prove nothing about authorship and quietly disclose location.
Every photograph you deliver carries data you did not type. Camera settings, timestamps, serial numbers, often precise coordinates. It rides along invisibly, and almost nobody decides what should be in it.
The three layers
EXIF is what the camera wrote: exposure, lens, timestamp, and GPS if the camera or phone had it.
IPTC is what you write: creator, copyright, caption, keywords. This is the layer that carries your name.
XMP is what your editing software writes, including edit history.
They travel together in the file and most people never look at any of them.
Keep: copyright and creator
If a photograph of yours is used without permission, embedded creator and copyright fields are not conclusive proof, but they are evidence, and their absence is conspicuous. It is also the difference between a publication being able to credit you easily and not bothering.
Set this once as an import preset. Creator, copyright notice, and a contact URL. It applies to everything from then on and costs you nothing per job. The wider question of what rights you actually hold is in the event photography copyright guide.
Strip: GPS
This is the one that matters and the one that gets ignored.
A photograph geotagged to street level tells anyone who opens it exactly where a person was, on a specific date, at a specific minute. For a public festival that is unremarkable. For a private party, a corporate offsite, a wedding at someone's home, or an event with any safety dimension, it is a disclosure you had no intention of making.
Guests download these files and repost them. The coordinates go with them.
Unless there is a specific reason to keep location, strip it from guest-facing files. Keep it on your archive copies if it helps you organise.
The timestamp question
Timestamps are usually harmless and often useful. They let a gallery sort correctly and let you reconstruct a timeline.
The one thing worth doing is making sure all cameras on the job agree. Two photographers whose clocks differ by forty minutes produce a gallery that shuffles the evening out of order, and no amount of editing fixes it afterwards. Sync clocks before the first frame. It takes a minute and it is unrecoverable later.
What guests actually receive
Worth checking rather than assuming. Different delivery paths behave differently: some platforms strip everything on processing, which protects guests but also removes your copyright fields, and some pass the original through untouched, GPS included.
Take one delivered file, open its properties, and look. It is a two minute check and most photographers have never done it for their own delivery pipeline.
A working default
For guest-facing files:
- Keep: creator, copyright, contact, caption
- Keep: timestamp, with synced clocks
- Strip: GPS coordinates
- Strip: camera serial numbers, which serve no one downstream
- Consider stripping: full edit history, which occasionally reveals more about your process than you want a client to see
For your archive, keep everything. The archive is yours and the extra data is what makes it searchable years later.
The short version
Set an import preset that stamps your authorship, strip GPS from anything a guest will download, and sync your cameras before the event. Then check one delivered file to confirm your pipeline does what you think it does, because most do not.
TIME&SPACE
Your photos delivered. Earn a referral on every event you bring in.
See How It Works for Photographers
Founder, TIME&SPACE