WOUTER.BLOG

    Blog · Workflow ·

    IPTC Metadata for Concert Photos: Captions Editors Can Use

    Which IPTC fields matter when you deliver concert photos to media, how Google Images uses your credit and copyright, and how to fill them all in once per job.

    A concert photo without a caption is half a delivery. The editor who opens it at midnight needs to know who is on stage, where, when, and whose name goes under it. If the file can't tell them, they guess, they mail you, or they use the photo that came with a caption.

    That information lives in the IPTC metadata: inside the file, or in the XMP sidecar next to a raw.

    The fields that matter

    You don't need all of IPTC. For concert and event work, these do the heavy lifting:

    FieldWhat goes inExample
    HeadlineOne line: who and whereArtist at Venue City
    CaptionThe full sentenceArtist, Venue, City, on 21-11-2026. Photo by Your Name
    Person shownWho is on stageArtist
    Event, Location, CityThe jobArtist, Venue, City
    KeywordsSearch termsartist; venue; city; concert
    CreatorYouYour Name
    Credit lineHow the credit should read© Your Name
    CopyrightYour notice© Your Name
    Usage termsWhat the client may doEditorial use only, credit required
    Web statementA link to your termsyour own terms page

    Why it's worth the effort

    Editors search. A caption with the artist and the venue can be found in a picture desk's system; IMG_3777.jpg can't. It's the same reason I name my files with the date, the artist, the venue and my name.

    Google reads it. Google Images shows the Creator, Credit Line and Copyright Notice from a photo's IPTC metadata, and a Web Statement can mark the image as licensable.

    It travels, sometimes. Many sites keep the metadata; social platforms usually strip it. A caption in the file won't stop misuse, but it makes the honest use easy and leaves no doubt whose photo it is. More on that side in finding out where your concert photos are published.

    Fill it in once per job

    The trick is to never type the same thing twice. In Snelkeus, every field can use tokens: {event}, {location}, {city}, {date}, or the name of any other field. The defaults:

    FieldDefault template
    Headline{event} at {location} {city}
    Caption{event}, {location}, {city}, on {date-dmy}. Photo by {creator}
    Keywords{event}; {location}; {city}; {creator}
    Credit line© {creator}
    Copyright© {creator}

    So per job you fill in three or four fields, event, location, city and maybe the person shown, and the headline, caption and keywords write themselves.

    Fields you pin keep their value for every job: your name, your copyright notice, your usage terms. Unpinned fields start empty for every new job, so last week's artist never ends up in this week's captions. A location you've used before fills in its city by itself.

    Snelkeus also checks your work. If a caption points at a field that's still empty, it asks before writing. And it won't build file names from a template with an empty field in it.

    Save the whole setup as a .snelkeus preset and double-click it on another Mac.

    Where it ends up

    Snelkeus writes XMP only: a sidecar next to a raw, inside the file for JPG, DNG and HEIC. Lightroom Classic reads the IPTC fields when you import, so the caption follows the photo into your catalog, and into your exports as long as your export settings include the metadata.

    A few habits

    • Write the caption for someone who wasn't there: full names, the venue, the city, the date.
    • Use the date format your clients use. {date} gives 2026-11-21, {date-dmy} gives 21-11-2026.
    • Put your name in both Creator and Credit line. Not every system shows both.
    • Keep the usage terms short and plain.

    Snelkeus is free and open source for macOS: get it here.