Streaming & Digital

ID3v2

Reviewed by

The dominant version of the ID3 tagging standard for MP3 files, stored at the start of the file and supporting a wide range of metadata fields including embedded artwork.

ID3v2 is a metadata container prepended to the beginning of an MP3 file, allowing fields such as title, artist, album, BPM, key, genre, comments, and embedded album art to be stored alongside the audio. It superseded the older ID3v1 standard, which was limited to 30-character fields stored at the end of the file, and is now the universal tagging format for MP3 across all major DJ software.

Why it matters

Because the ID3v2 block sits at the head of the file, DJ software can read all track metadata instantly without scanning the entire audio stream, which matters when loading a large library. Corrupted or missing ID3v2 data leaves the DJ without BPM, key, or artist information in their software.

In practice

Use a dedicated tag editor (such as Mp3tag on Windows or Kid3 on macOS/Linux) to inspect and clean ID3v2 frames if a track displays incorrectly in your DJ software. Pay attention to which version of ID3v2 you write: versions 2.3 and 2.4 are both common, and some older hardware reads only 2.3.

Frequently asked questions

ID3v1 is a simple 128-byte block appended to the end of an MP3 file, limited to fixed-length fields of 30 characters each and a small list of predefined genres. ID3v2 is placed at the start of the file, uses variable-length frames, supports Unicode text, embedded artwork, and an essentially unlimited number of fields. Almost all modern DJ software ignores ID3v1 and reads only ID3v2.
Different DJ applications read different ID3v2 frame identifiers. For example, BPM may be stored in the TBPM frame, but an older app might look for a custom frame or a different tag entirely. Embedded artwork can also conflict between ID3v2 versions 2.3 and 2.4. Re-tagging the file with a tool set to write ID3v2 version 2.3 (the most widely compatible version) and clearing duplicate or conflicting frames usually resolves the discrepancy.
WAV files have their own native metadata system via the RIFF INFO chunk, and AIFF files have native text chunks (NAME, AUTH, ANNO, and Copyright). However, many DJ applications also write or read ID3v2 blocks embedded inside WAV and AIFF files, stored in a dedicated chunk within the container. Because this embedding is non-standard for WAV, compatibility between different software can be inconsistent, which is one reason many DJs prefer FLAC with Vorbis Comments or AIFF with ID3v2 for lossless files.
Ben Modigell

Hey, it's Ben Modigell 👋

I DJ and produce as so I so — downtempo, minimal, dub house, tech house, and techno (releases on Spotify and SoundCloud, links above). Everything I write here comes from my own gigs, studio sessions, and library cleanups: the rules I follow, the failure modes I've actually hit, and the workflow I use when nobody's watching. If a technique didn't earn its place in my own sets, it doesn't make it into a tutorial.

DJingMusic ProductionTech HouseMinimal HouseDub HouseTechnoDowntempoLibrary Organization