Image Metadata for Artists: What Survives an Upload

Every image file can carry hidden information alongside its pixels: which app saved it, when, sometimes who made it and under what license. For artists this data matters in two directions. It can help show a piece is yours, and it can quietly leak information you did not mean to share. Most of it is also fragile, because many websites remove it when you upload. This guide explains the main kinds of image metadata and gives you a quick test to see what actually survives.

The three families of embedded data

• EXIF. Technical data written mostly by cameras and phones: device, date, exposure, and sometimes GPS location. Painting apps write little or none, but a photo of a traditional piece can carry a lot.
• IPTC. Descriptive and rights data defined by the IPTC Photo Metadata Standard: creator name, copyright notice, credit line, description, and a digital source type that can state whether media was made by a person or a model.
• XMP. A flexible container that many creative apps use to store IPTC fields, editing history, and custom data inside the file.

Provenance manifests from the C2PA standard are a fourth, newer layer that is cryptographically signed. They are covered separately in Content Credentials explained.

Set your creator and rights fields once

Check what you are leaking

Photos of traditional work are the usual risk. A phone photo of a sketchbook page may carry the GPS location of your home and the exact time you took it. Before posting, view the metadata and remove location data. A free inspector such as ExifTool shows every field in a file, and most operating systems can show or strip basic EXIF from the file properties. Our own approach to reader data is set out in the Bio Rust privacy policy.

The upload survival test

Platforms treat metadata differently and change their behavior over time, so test rather than trust. It takes ten minutes and tells you exactly what your audience receives.

1. Export one test image with creator, copyright, description, and source type filled in, and a credential attached if your app supports it.
2. Upload it to each place you publish: your portfolio, each social platform, your shop.
3. Download the image back from each platform, using the platform's own download or save option.
4. Inspect each downloaded file and note which fields survived.
5. Repeat after major platform updates, because behavior changes.

Most artists find that portfolio hosts and direct file sharing keep more data, while many social feeds strip nearly everything. That is exactly why embedded data should be one layer of your authorship record, never the only one.

Build a layered authorship record

The strongest approach combines what is fragile with what is robust. Embedded creator and rights fields and a credential on the published file cover the cases where data survives. A visible caption or process note covers the cases where it does not. And a private archive of sketches, layered masters, and timelapse, as set out in how to document your art process, covers everything else. Metadata makes your claim easy to read; your process makes it hard to dispute.

Sources and further reading

Primary references for the facts and definitions in this piece, all from independent publishers:

• IPTC Photo Metadata Standard: creator, copyright and description fields.
• ExifTool: XMP tag names: what an XMP container can hold and how a viewer reads it.
• IPTC Digital Source Type vocabulary: the values for marking how media was made.