How to Export Your Event Photo Data as JSON
Your event's tags are useful outside the gallery too: for a results partner, your own records, or matching photos back to the photographer's folders. Photos to Data Export puts every processed photo in one JSON file, with the bibs and other fields you choose.
In short: open your event, go to Photo, then Tools, and choose Photos to Data Export. Tick the Fields to include, select Export, and download the JSON file when it shows Ready. Every processed photo gets one entry, including photos with no bibs.
What the export gives you
Photos to Data Export answers one question for every photo in your event: what do we know about it? The file has one entry per processed photo, keyed by the photo's ID, with the fields you picked.
It is the right export when you start from the photos:
- Matching tags back to originals. The file name and path tell you which file in the photographer's folder each entry is.
- Finding photos nobody can find. Photos with no bibs are in the file with an empty list, ready for a second look.
- Keeping your own record. A copy of the event's tags as they stood on a given day, for your archive or another system.
If you start from the runners instead, and want each bib with its photos, use Bib to Data Export.
Step 1: Open the tool
In the dashboard, open the event, go to Photo and select the Tools tab. Choose Photos to Data Export. It was called Photos to Bib Export before, and old links still open it.
The page has two columns. On the left are the fields and the Export button. On the right is the Latest export and a preview of its file. Before your first export, the right side shows an Example file so you can see the shape.
Step 2: Choose the fields
Bibs and Manual tags are ticked by default. Add any of the others you need. You need at least one.
| Field | What it holds |
|---|---|
| Bibs | The bibs participants find the photo by: detected bibs plus your manual tags, minus any you removed. |
| Manual tags | Bibs you added by hand in Manual Tagging. |
| Original file name | The photo's name when it was imported. |
| File path | Where the photo is in its source, including its name. For a 9Pic upload, the folder inside the upload. For Google Drive, Dropbox, OneDrive, Box or SharePoint, the path inside the shared folder. Empty for photos from a custom link. |
| Detected bibs | Bibs found on the photo, before any you removed. |
| Removed bibs | Detected bibs you removed in Manual Tagging. |
| Detected text | All text read on the photo, such as sponsor names and signs. |
Each extra field makes the file larger. Detected text adds the most, so leave it off unless you will use it.
The boxes start from your latest export's fields. If you change them, a note reminds you to export again so the file matches.
Step 3: Export and download
Select Export. The export runs in the background and shows how many photos it has read. You can leave the page and come back. A large event takes about a minute.
When it shows Ready, the Latest export box lists when it ran, the file size and three counts: Photos, Bibs and Photos without bibs. It also names the fields in the file. Select Download JSON to save it.
Each event keeps its latest export of each type, so a new export replaces the one shown on the page.
Step 4: Read the file
Every file starts with the same details: event_id, export_type, generated_at, options (the fields included) and counts. The photos are under data. Here is a file with file name, file path, bibs and manual tags:
{
"event_id": 6109,
"export_type": "photos_to_bib",
"generated_at": "2026-11-13T09:30:00+00:00",
"options": ["file_name", "file_path", "bibs", "manual_tags"],
"counts": {"photos": 30240, "bibs": 7374, "photos_without_bibs": 2086},
"data": {
"3f2a...c91e": {
"file_name": "IMG_4821.jpg",
"file_path": "Habit Run 2026/Finish line/IMG_4821.jpg",
"bibs": ["1024", "2210"],
"manual_tags": ["2210"]
},
"9d03...6b7f": {
"file_name": "IMG_4822.jpg",
"file_path": "Habit Run 2026/Finish line/IMG_4822.jpg",
"bibs": [],
"manual_tags": []
}
}
}
A few things to know when you read it:
- The key of each entry is the photo's ID in 9Pic AI. It is not the file name. Tick Original file name when you need that.
- Photos with no bibs are still listed, with an empty list. That is how
photos_without_bibsis counted. - A photo from a custom link has
nullas its file path, because it has no folder.
Check it before you download
Under the latest export, File preview shows the start of the file, laid out the same way. Select a key or its arrow to open or fold it, or use Expand all and Collapse all. Raw shows plain text with line numbers, and Copy copies the preview.
The preview holds the first 20 photos, and long lists are cut short with a line such as "… 5 more items in the download". Folded entries show how many keys or items they hold in the full file, so the counts are real even when the preview is short.
Three practical uses
Match tags to the photographer's originals
Tick Original file name and File path. Each entry now tells you which file in which folder it came from, so a photographer or editor can find the original for a bib without searching the gallery.
Find the photos with no bibs
Look for entries whose bibs list is empty. Many will be crowd shots, scenery or the start line. Others may be runners whose bib was hidden. Those are worth a pass in Manual Tagging; see how to tag bibs by hand after AI.
Check what was corrected
Tick Detected bibs and Removed bibs to see what bib reading found and what your team took out. It is a quick way to review a tagging pass, or to explain why a runner no longer finds a photo.
What counts as a bib
Only processed photos are in the file. The Bibs field follows the same rules as participant search:
- Bibs found with the event's bib detection settings. When the event uses its bib list, only listed bibs count.
- Minus detected bibs you removed.
- Plus your manual tags, even before they are published to participant search.
So the file matches what participants find, with your newest manual tags included early.
FAQ
Does the file update when I change tags?
No. A file shows the tags at the moment it ran. After tagging, select Export again.
Which plans include it?
Every plan. It also keeps working after a plan ends, so you can still take your data with you.
The export failed. What now?
Select Export again. If a download fails, try once more: each click prepares a fresh download link.
Can I open the file in a spreadsheet?
JSON is made for software, so the easiest path is to hand it to whoever runs your results or registration system. Most data tools and spreadsheet add-ons can import JSON too.
What to do next
Run a first export with the default fields and open the File preview to see your event's shape. Then add file name and path if you need to match originals. For a list of each bib with its photos, read how to export race photos by bib number. Bib reading itself is covered on the BibTrack page.