Image Metadata for Artists
Image metadata is the hidden data stored beside an image's pixels: EXIF technical fields from cameras and phones, IPTC descriptive and rights fields you fill in yourself, and the XMP container that carries them. For an artist the job is to set creator, copyright and source type once, remove location data, and test what each platform strips.
Every image file can carry information alongside its pixels: which app saved it, when, sometimes who made it and under what license, and for a phone photo, where you were standing. For artists this image metadata matters in two directions. It can help show a piece is yours, and it can leak information you did not mean to share. Most of it is also fragile, because many sites remove it on upload. This guide explains the three families of embedded data, the exact fields to fill, how to remove location data, and a ten minute test of what your platforms keep. It belongs to the process and provenance pillar.
EXIF, IPTC and XMP: the three families of image metadata
The names get used loosely, so separate what each holds, who writes it, and how it travels. A fourth row covers the signed provenance manifest, which is a different kind of record and is explained in Content Credentials and C2PA for artists.
| Family | What it holds | Who writes it | Survives upload? |
|---|---|---|---|
| EXIF | Capture data: device model, date and time, exposure, orientation, often GPS coordinates | Cameras and phones automatically; painting apps write little or none | Rarely on social feeds; test |
| IPTC (Core and Extension) | Descriptive and rights fields: creator, contact, copyright notice, credit, title, description, keywords, digital source type | You, through a file info panel or a metadata tool | Mixed; portfolio hosts and direct file sharing keep more than feeds do |
| XMP | A container, now an ISO standard, holding IPTC fields, edit history and app data | Creative apps on save or export | Same as the IPTC fields it carries; stripped when the file is re-encoded |
| C2PA manifest | A signed record of signer, actions, ingredients and a hash of the pixels | An app that supports Content Credentials, on export | Only if the platform copies it across or hosts it; any pixel edit breaks the hash |
The IPTC Photo Metadata Standard defines the Core and Extension field sets and notes that they are implemented through XMP, which is why a single file info panel can show both. The ExifTool XMP tag reference lists every namespace a container can hold, which is useful when a field in your app has a different label from the standard name.
The IPTC fields an artist should fill, with example values
Nine fields cover authorship, contact and rights for a working illustrator. Fill them once as a template in your editor and apply it on every export.
| IPTC field | Example value | Why |
|---|---|---|
| Creator | Mara Okafor | The name a viewer or editor should credit |
| Creator's Contact Info (website) | maraokafor.art | Lets someone reach you without guessing; use a site rather than a home address |
| Copyright Notice | Copyright 2026 Mara Okafor. All rights reserved. | The rights claim in plain words |
| Credit Line | Mara Okafor / maraokafor.art | What a publisher pastes under the image |
| Title | Harbor Girl | The name of the piece, matching your folder and session files |
| Description | Digital painting, Clip Studio Paint, 2026. Character study, harbor at dusk. | Tools and year in one line; doubles as a process note |
| Keywords | digital painting, character, harbor, dusk | Search and archive use, five to ten terms |
| Rights Usage Terms | Personal sharing with credit permitted. Commercial use by license only. | States what a viewer may do before they ask |
| Digital Source Type | digitalCreation | The IPTC value for media made by a person with digital tools |
The last row deserves care. The IPTC Digital Source Type vocabulary retired the older digitalArt value on 2024-09-17 and replaced it with digitalCreation. trainedAlgorithmicMedia marks media created with a generative model, and compositeWithTrainedAlgorithmicMedia marks a real image edited with one. Set the value honestly; an accurate label is worth more than a flattering one when a question comes up later.
Use the same spelling of your name, the same site and the same copyright wording on every file. A body of work that carries identical fields is far more convincing than any single file.
Removing location data before you post
Painting apps rarely write GPS, so the risk is photos of traditional work: a phone shot of a sketchbook page can carry the coordinates of your home and the exact time you took it. Check before posting. ExifTool is the free command line inspector that shows every field a file holds, and it can remove fields selectively. Most phone share sheets and desktop image viewers can also strip location, but the command line lets you see exactly what changed.
List everything the file carries
Run exiftool -a -G1 -s photo.jpg. The -G1 flag prints the group of each tag, so you can see which fields are EXIF, which are IPTC and which are XMP.
Remove the GPS block only
Run exiftool -gps:all= photo.jpg. This clears the EXIF GPS tags and leaves creator and copyright fields in place. ExifTool keeps a copy named photo.jpg_original unless you add -overwrite_original.
Strip everything when the file is only a snapshot
For a quick phone shot with no rights fields worth keeping, exiftool -all= photo.jpg removes all metadata. Do this on a copy, never on the archive file.
Check the result
Run the listing command again and confirm the GPS lines are gone. Then apply your IPTC template if the image is a finished piece.
Keep creator and rights fields. Remove location. Never rely on metadata alone as proof of authorship, because anyone can type into these fields.
How to test what a platform strips
Platforms treat metadata differently and change behavior without notice, so test rather than trust. The IPTC provides a reference image on its standard page with every field filled with its own name, so the value of Creator reads Creator (ref2025.1). It is the ideal test file, because a single glance at the download shows which fields survived.
Prepare two test files
Download the IPTC reference image, and export one of your own pieces with your template applied and, if your app supports it, a Content Credential attached.
Upload both everywhere you publish
Your portfolio host, each social platform, your shop, and any messaging app you send work through.
Download each copy back
Use the platform's own download or save option, never a screenshot, since a screenshot has no metadata by definition.
Inspect each download
Run exiftool -a -G1 -s on every file and note which of the nine fields, the GPS block and the manifest survived. A three column note per platform is enough: kept, stripped, changed.
Repeat after major platform updates
Behavior changes. A yearly re-test, or one after a platform redesign, keeps your notes honest.
Most artists find that portfolio hosts and direct file transfer keep the IPTC fields, while many feeds strip nearly everything, including the fields you most want to keep. That is exactly why embedded data should be one layer of your authorship record and never the only one.
What image metadata can and cannot prove
Metadata is text in a file. Anyone with a free tool can write your name into it, or a stranger's name into a copy of your work, so on its own it proves little. Its value is that it makes your claim legible to an honest editor, a stock site or a search engine, and it supports the harder evidence. A consistent set of fields across dozens of files, matching the folder names, session saves and replay described in how to document your art process, is a pattern that is expensive to fake.
The same logic applies in reverse. If you are checking an image before crediting it, treat its metadata as a lead rather than a verdict, and follow the full routine in how to check where an image came from. Our own handling of reader data is set out in the Bio Rust privacy policy.
Mistakes artists make with image metadata
| Mistake | Why it hurts | Fix |
|---|---|---|
| Posting a phone photo of a sketchbook with GPS intact | Reveals your home or studio location | Run the GPS removal step or the share sheet location toggle before posting |
| Filling fields differently on every file | Inconsistent names look like different people | One saved template, applied on every export |
| Setting the retired digitalArt value | Modern readers expect digitalCreation | Use the current vocabulary value |
| Assuming the platform kept your fields | Most feeds strip them silently | Run the upload test and keep notes per platform |
| Treating metadata as proof by itself | Any field can be edited by anyone | Pair it with a process archive and a credential |
| Stripping the archive master | Loses the only copy of your rights fields | Strip copies only |
Image metadata as the readable layer of your record
Set creator, contact, copyright, credit, description and source type once and apply them to every export. Remove location from anything shot on a phone. Test each platform with the IPTC reference image and note what it keeps. Image metadata then does the job it is good at: making your claim legible wherever the file lands, while the process archive behind it makes the claim hard to dispute.
Common questions
What is the metadata of an image?
Image metadata is the data stored inside a file beside its pixels: EXIF technical fields such as device, date and GPS written by cameras and phones; IPTC descriptive and rights fields such as creator, copyright and description that you fill in; and the XMP container that carries them. A signed C2PA manifest is a newer, separate layer.
How can I extract metadata from an image?
Open the file in a metadata viewer. ExifTool is the free command line standard: exiftool -a -G1 -s file.jpg lists every tag with its group. Most image editors also show the fields in a file info panel, and desktop file properties show basic EXIF. A screenshot of an image carries none of the original data.
Can you recover metadata from photos after a platform stripped it?
Not from the stripped copy; the fields are gone from that file. Recovery means going back to your original export or archive master, which is why the master should never be stripped or overwritten. If a Content Credential was attached, a verifier may re-find the manifest through a soft binding, but embedded IPTC fields do not come back.
How do I see iPhone photo metadata and remove the location?
The Photos app shows capture details and a map for a photo, and the share sheet has an options toggle that removes location from the copy you send. For a full view, transfer the file to a computer and run ExifTool, which lists every field and can clear the GPS block with exiftool -gps:all=.
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 and the reference test image.
- 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.
- ExifTool by Phil Harvey: reading every field in a file and removing location data.
This method is part of the process and provenance pillar. Pair it with How to Document Your Art Process and Content Credentials and C2PA for Artists.