EveryMark documentation
Everything you need to run EveryMark against a real library — from the first folder you load to the backup that saves you when a batch goes sideways.
EveryMark is a desktop application for reading and writing the metadata stored inside media files: the capture date in a photograph, the coordinates in a video, the album artist in a FLAC. It runs on Windows, macOS, and Linux, does its work entirely on your machine, and uses ExifTool as its reading and writing engine.
These pages describe the application as it works today. EveryMark is in private beta while installers are packaged and signed — join the list to get the build.
Where to start
If you've never opened it, read the first two pages in order. If you're here for something specific, jump straight to it.
Installing & first launch
Install it, understand the three-panel layout, and get your first folder on screen.
Loading & organising
Three ways to add files, then sorting, filtering, grouping, and selecting the ones you actually want.
Editing metadata
Inline editing, which fields are editable, validation, and what happens when you edit several files at once.
Dates & locations
Absolute dates, bulk offsets, the interactive map, place search, and copying coordinates between files.
Saving, backups & export
Reviewing a change set, what happens during a write, where backups live, and exporting to CSV or JSON.
Supported formats
Every image, video, and audio extension EveryMark reads, plus the full editable field reference.
Keyboard shortcuts
The complete list, for Windows, macOS, and Linux.
Troubleshooting
Files that won't load, fields that won't edit, saves that fail, and maps that stay blank.
Three things worth knowing first
Metadata lives inside the file
This is the whole premise. A catalogue application stores your corrections in its own database; EveryMark writes them into the file itself. That means the fix travels with the file — through an export, a copy to another drive, a handoff to a client, or a migration to different software five years from now. It also means saving rewrites the file, which is why backups exist.
Nothing is written until you save
Edits accumulate as pending changes. They're highlighted in the metadata panel and counted in the toolbar, and they touch nothing on disk until you press Save. Discard throws the whole set away with no consequence.
Everything applies to the selection
Sorting, filtering, and grouping exist to help you build the right selection. Once files are selected, an edit applies to all of them — which is enormously useful and occasionally dangerous, so the selection count stays visible at all times and multi-file edits ask for confirmation.
If something goes wrong
Start with Troubleshooting, which covers the common failures. Every save creates a backup first, so a bad write is recoverable — see Backups for where those live and how to use them.