Music Tags: The Afternoon Checklist for Your Library

Most guides to music tags cover the same ground: title, artist, album, ISRC, genre. That's release metadata, and it matters for royalties and distribution. But if you manage a catalog, a sample pack, a sync library or a DJ crate, you need a different set of tags: the ones that let you find, filter and pitch a track without opening it. This checklist covers both, but it's built for the second job, and you can work through it in an afternoon.

What counts as a music tag (and what doesn't)

Release metadata identifies a recording: title, artist, ISRC, UPC, credits, artwork. It's administrative, and distributors like DistroKid or CD Baby collect it during upload. Descriptive tags are different: they describe what the track sounds like, so someone (or some algorithm) can find it later. That's BPM, key, genre, subgenre, mood, instrumentation, vocals, structure and use case.

Most personal libraries have plenty of the first kind and almost none of the second. A folder of 800 WAV files might have correct artist and album fields and zero BPM, key or mood data. That gap is what actually breaks discovery, because nobody searches their catalog by album name when they need "a 90 BPM minor key track with sparse instrumentation for a montage scene."

Step 1: audit before you tag anything (15 minutes)

Don't start renaming or re-tagging files blind. First find out what's actually missing. Connect your local folder to a library view that separates tagged files from untagged ones, with sortable columns and folder aliases so nested subfolders don't get lost. TrackTag's My Library view does this by scanning file names and sizes locally, on your own machine, so nothing uploads until you explicitly choose to analyze a track. Browser folder access for this kind of scan works in Chrome, Edge and Brave; Safari and Firefox don't support it, which is one reason a desktop app exists for Mac and Windows, where connected folders stay linked permanently without repeated permission prompts.

Once the scan finishes, you'll have a real number instead of a guess: "340 of 800 tracks untagged" is a much more useful starting point than "I should probably tag my library sometime."

Step 2: decide how deep you need to go

Not every track needs the same level of detail. A useful split:

• Findable tags: BPM, key, genre, subgenre, moods, and keyword tags. Enough to file a track and search for it later.
• Pitchable tags: everything above plus emotions, themes, occasions, instruments, vocals, song structure, production notes and a written description. Enough to send to a music supervisor or drop into a sync brief without writing a paragraph yourself.

This is the actual difference between the two analysis levels in TrackTag Studio: Core returns the nine fields that file and find a track, keyword tags included, at one credit each. Ultra returns all 35 fields, description included, at two credits. Both run the same analysis engine on the same audio, so accuracy doesn't change between them, only how much of the answer you get back. If a track only needed filing today but you're pitching it for sync next month, you can re-analyze it at Ultra later for just the one-credit difference, no need to start over.

For catalogs headed toward supervisors or licensing platforms specifically, it's worth reading through what a sync-ready tag set actually needs before you commit to a level for the whole batch.

Step 3: get BPM and key right, not guessed

BPM and key are the two tags that get used programmatically, for playlist ordering, harmonic mixing, sync search filters, so they need to be measured, not estimated from genre averages. TrackTag's Precision Mode reads tempo and key directly from the audio signal on-device, and it's benchmarked at 15 out of 15 tempo agreement against the leading industry analyzer. If you're curious how that measurement actually works under the hood, the BPM and key detection breakdown covers the method.

Step 4: batch tag the backlog, don't do it one file at a time

Once you know what's untagged and what level you need, the actual tagging should take minutes per hundred tracks, not per track. Drop the batch into TrackTag Studio, or use the "Analyze untagged" action from My Library to send only the backlog, and let it run. If the batch is large, run it from the desktop app so it keeps going in its own window instead of tying up a browser tab. The batch tagging guide covers timing and file-prep tips if you're working through a folder in the thousands.

If your workflow already lives somewhere else, TrackTag connects rather than requiring you to change tools. The public API lets a marketplace or delivery pipeline POST a track and get the same JSON analysis back automatically. The MCP server lets an assistant like Claude Desktop or Cursor analyze a track, search your local files by name, and check your credit balance from inside a chat, running on your own machine. And the Zapier integration adds an "Analysis Finished" trigger and an "Analyze Track" action, so a new track landing in Dropbox can get tagged and logged into a Google Sheet or Airtable base with no code involved.

Step 5: export in the format the next step needs

Tags are only useful once they leave the analyzer. Export the batch, a hand-picked subset, or a file per track as TXT, CSV, XML, JSON (including schema.org JSON-LD for web catalogs), Markdown or PDF, matching whatever your DAW, DAM or licensing platform expects to ingest. If the destination is a submission portal, run through the catalog submission checklist before export so you're not re-exporting twice.

Where TrackTag fits next to enterprise tools

If you've looked at Cyanite or AIMS, both do real work: Cyanite's similarity search is genuinely useful at catalog scale, and AIMS integrates well into existing label delivery pipelines. Where they differ from a self-serve tool is access and transparency. Cyanite's plans have historically carried a high monthly floor that only makes sense at enterprise volume, and AIMS pricing sits in a similar bracket, both a step up from what an independent catalog owner needs to just get a library tagged this week. TrackTag starts with free credits, then packs from $20 for 50 tracks, or an Unlimited plan at $49/month with your own Google AI key, no enterprise floor required. See the honest side-by-side breakdowns at TrackTag vs Cyanite and the pricing comparison guide if cost is the deciding factor for your catalog.

The actual afternoon plan

Audit your library (15 minutes), decide Core or Ultra per section of the catalog (10 minutes), run the batch through TrackTag Studio or the desktop app while you do something else (30 to 90 minutes depending on volume), then export into whatever system holds your catalog going forward. That's a full library of music tags, done, searchable and ready to pitch, in one sitting instead of spread across a month of one-off edits.