A music library with wrong or missing metadata is a library that doesn't work. Tracks show up under the wrong artist in your DAW, your DJ software can't filter by genre, your streaming distributor rejects files for missing required fields. Fixing tags one file at a time is not a solution when you're dealing with hundreds of tracks.
This guide covers what ID3 tags are, why they matter, and how to use Audiobrain's Batch Tag Editor on Mac to fix the metadata of an entire folder of audio files in a single pass.
What Is an ID3 tag?
An ID3 tag is a metadata container embedded inside an audio file. It stores information about the track — title, artist, album, genre, year, BPM, comment — that music players, DAWs, streaming platforms, and DJ software all read to display and organize your library.
ID3 tags are separate from the audio data itself. Editing them does not touch the waveform, does not re-encode anything, and does not affect audio quality. It only changes the descriptive information stored alongside the audio.
The standard is ID3v2, which is what Audiobrain writes. ID3v2 tags are supported by every major music player and platform — iTunes, Spotify, Serato, Rekordbox, Ableton, Logic Pro, and all streaming distributors.
Why Metadata Matters More Than Most Producers Think
Clean metadata is infrastructure. It determines how your music behaves in every system it touches after it leaves your drive.
DAW & Plugin Organization
Ableton, Logic, and most DAWs index samples and loops by their ID3 tags. Missing or wrong tags break search, filtering, and smart folders.
DJ Software
Serato, Rekordbox, and Traktor all organize your library by metadata. Bad tags mean tracks land in the wrong place — or disappear from filters entirely.
Streaming Distribution
Distributors like DistroKid and TuneCore require correct artist and track metadata. Files with missing fields get flagged or rejected before they go live. Before uploading, also make sure your masters are normalised to the correct streaming LUFS target.
Sample Pack Releases
Every sample pack sold on Splice, Beatport, or your own store should have proper artist and genre tags. It is part of the standard for delivered packs. Before tagging, ensure all files are in a consistent format — batch converting your audio to WAV or MP3 first means you tag once and deliver in the right format.
Client Deliveries
When you deliver stems or a full session to a client, correctly tagged files look complete. Missing artist or album tags signal a rushed or careless delivery.
Music Libraries
Sync libraries and music supervisors use metadata to search and filter large catalogues. If your genre or BPM fields are empty, your tracks won't surface in relevant searches. For libraries moving toward AI-driven discovery, you can also complement manual tagging with AI genre classification to auto-tag large catalogues without manual effort.
How the Batch Tag Editor Works in Audiobrain
Audiobrain's Tag Editor takes a batch of audio files and applies the metadata fields you specify — artist, album, genre, year, comment — to every file in the batch simultaneously. The tags are written directly into each file using FFmpeg's ID3v2 implementation. All processing happens natively on your Mac with no internet connection required.
Editable metadata fields
| Field | ID3 Tag | Used by |
|---|---|---|
| Artist | TPE1 | All players, DAWs, distributors, streaming platforms |
| Album | TALB | iTunes, music players, DJ software library views |
| Album Artist | TPE2 | Compilations, VA releases, streaming platforms grouping |
| Genre | TCON | DJ software filters, streaming categories, sync libraries |
| Year | TDRC | Library sorting, distributor metadata, copyright records |
| Comment | COMM | Internal notes, licensing info, version identifiers |
How to Batch Edit Audio Tags on Mac — Step by Step
The entire workflow takes under a minute regardless of how many files you are processing.
Launch Audiobrain and select Tag Editor from the Audio Tools sidebar.
Drag individual audio files or an entire folder into the left drop zone. Audiobrain queues every supported file — MP3, WAV, FLAC, AIFF, M4A, AAC. Use the + button to add more files to an existing queue, or the × next to any file to remove it individually.
Enter the values you want to apply in the right panel. You only need to fill in the fields you want to change — any field left blank is skipped and the existing tag value is preserved.
Click Replace Tags In-Place. Audiobrain writes the new ID3v2 tags into each file sequentially. A confirmation prompt appears before any changes are made. When the progress bar completes, every file in the batch has been updated.
Important: tags are written in-place
Unlike most tools in Audiobrain that export to a new file, the Tag Editor writes directly into your source files. This is intentional — copying hundreds of audio files just to change metadata would be wasteful and disrupt your folder structure. Audiobrain warns you before any writes occur. If you want a backup, duplicate your folder before running the batch.
When to Use Batch Tag Editing
Fixing a Downloaded Sample Pack
Most downloaded packs have generic or missing tags. Drop the whole folder in, set your genre and a comment with the pack name, and every sample is tagged in one pass.
Preparing a Release for Distribution
Before uploading to DistroKid or CD Baby, run your master files through the Tag Editor to confirm artist, album, and year are consistent across every track on the release.
Cleaning Up an Old Library
If you have years of tracks with inconsistent artist names or missing album fields, batch editing by folder lets you fix an entire era of your library at once.
Tips for Batch Tag Editing Audio Files
- Leave fields blank to preserve existing tags. If you only want to set Genre, leave Artist and Album empty. Audiobrain will only write the fields you filled in.
- Use Album Artist for compilations. When tagging a VA release or a sample pack, set Album Artist to the pack or label name while leaving Artist blank — this keeps individual track credits intact.
- Use Comment for version or license notes. The Comment field is a useful place to embed internal info — a license code, a version number, or a client name — that travels with the file without affecting how it plays.
- Process by folder, not by individual file. Group your files by album, pack, or project before tagging. This lets you apply consistent metadata to a logical set in one operation.
- Back up before large batches. The Tag Editor writes in-place. For a batch of 500 files, duplicate the folder first. For a batch of 10, the confirm prompt is enough protection.