A backup that loses titles, tags, and dates is only half a backup. Photographers feel this the first time they open a folder of IMG_3847.jpg files with no story attached.
Here is how Flickr separates camera EXIF from Flickr metadata, what the official export does, and how FlickrVault keeps both next to your originals.
Two different kinds of “metadata”
1) EXIF (and related embedded data)
Captured by the camera or phone: shutter, aperture, ISO, lens, GPS (sometimes), and often date taken. Flickr can display EXIF on the site. Whether downloads keep it depends on the path—and Flickr notes that some export tools strip EXIF if misconfigured.
Flickr’s own FAQ: embedded EXIF on downloaded files typically reflects what was present at upload. See EXIF data FAQ.
2) Flickr metadata you add later
Titles, descriptions, tags, albums, licenses, and comments live in Flickr’s database. On a full Data request, much of that arrives in JSON, not magically rewritten into every JPEG.
So: file bytes ≠ the story you wrote on Flickr—unless your backup tool reunites them.
What official downloads give you
- Individual / Camera Roll downloads: originals when allowed; EXIF generally as uploaded.
- Request My Flickr Data: media files + separate JSON; titles/tags you added after upload are in the JSON side, not always embedded in the image.
That split is why “I downloaded everything” threads often continue with ExifTool scripts and archive rebuilders.
What to demand from a backup tool
A serious Flickr backup should:
- Fetch original media when Flickr exposes it
- Preserve or restore date taken on the filesystem (so Finder/Explorer sort works)
- Keep titles, tags, descriptions, licenses in a structured sidecar you can parse
- Optionally write EXIF back when the downloaded file is missing it but Flickr still has a copy
- Organize albums as folders so humans can navigate without a database
How FlickrVault stores metadata
When you back up with FlickrVault:
- Each album folder can include a
FlickrVault-metadata.jsonlisting per-photo title, description, tags, dates, license, owner, and EXIF records - File created/modified times are set to date taken where possible
- If a downloaded original already contains EXIF, FlickrVault can read it from the file; if not, it can use Flickr’s recorded EXIF and write it into the file (see recent changelog notes on fewer API calls and
exifSource)
You still own the JSON: open it in any editor, or feed it to your own scripts. You are not locked into a proprietary catalog.
Workflow tips
Before you back up
- Fix titles/tags on Flickr if you care about them—your backup will capture the current state
- Note which albums matter; “not in any set” is easy to forget and easy to lose track of later
After you back up
- Spot-check a few files’ dates in Finder/Explorer
- Open
FlickrVault-metadata.jsonand confirm tags you expect - Keep the backup disk unplugged or versioned if it is your only offline copy
If you already have Flickr’s ZIP export
You can still run a desktop backup for a clean album tree. Treat the official ZIP as a second freeze, not the only layout you will live with.
Competitors and CLI notes
Projects like flickr-exporter embed titles/tags via ExifTool. That is a solid engineer workflow. GUI users often prefer sidecars plus correct file dates without installing a Perl toolkit.
Older apps advertised EXIF preservation too—evaluate whether they still install cleanly on current macOS/Windows (Adobe AIR-based tools are a common pain point).
Privacy and trust
Metadata can include GPS. A local backup keeps that on your disk. Prefer tools that:
- Use Flickr OAuth (no password to the app vendor)
- Do not upload your photo bytes to intermediate servers
FlickrVault downloads Flickr → your folder and keeps tokens in the OS keychain.
FAQ
Will Lightroom see my tags?
Import the files, then either map from FlickrVault-metadata.json or use embedded fields if present. Sidecar-first is honest: not every field belongs inside every file format (especially video).
Do credits affect metadata?
Own-account backups include metadata the same way. Credits apply to public/search downloads; license and attribution fields matter more there—keep them.
Is JSON enough for long-term archive?
JSON + originals is a transparent pair. Pair it with disk redundancy (and optionally Flickr’s own Data request).
Bottom line
Keeping EXIF is necessary but not sufficient. You also need Flickr titles, tags, dates, and licenses living beside the files. Official takeout separates them; a dedicated downloader should reunite them in a folder layout you can open tomorrow.
Download FlickrVault and verify metadata on a small album first, then run the full library.