An ID3 tag decoder reads the metadata frames embedded in an MP3 file — title, artist, album, track number, year, genre and artwork — from either the ID3v1 block at the end of the file or the ID3v2 frames at the beginning.
What is the ID3 Audio Tag Decoder?
MP3 has no metadata in its own format, so ID3 was bolted on. ID3v1 is a fixed 128-byte block at the very end of the file with rigid 30-character fields and a numeric genre — cramped enough that long titles are simply truncated. ID3v2 replaced it with variable-length frames at the start of the file, identified by four-character codes: TIT2 for title, TPE1 for artist, TALB for album, APIC for attached artwork.
Most files in the wild carry both, and the two can disagree — a common cause of a track showing one name in one player and a different one in another. Character encoding is the other frequent culprit: ID3v2.3 defaults to Latin-1 or UTF-16, while ID3v2.4 supports UTF-8, and mismatched assumptions produce the mojibake familiar to anyone with a large music library.
How to use the ID3 Audio Tag Decoder
- Upload the audio file — parsing happens locally in your browser.
- Read the tag version and the decoded frames.
- Compare the ID3v1 and ID3v2 values if players are showing different titles.
When to use it
- Diagnosing why a track shows the wrong artist in one player and not another.
- Auditing a music library's tagging before a bulk metadata cleanup.
- Checking what encoder and settings produced a given MP3.
ID3 Audio Tag Decoder at a glance
| ID3v1 | 128 bytes at end of file, fixed 30-char fields |
| ID3v2 | Variable-length frames at start of file |
| Key frames | TIT2 title · TPE1 artist · TALB album · APIC art |
| Encoding | v2.3 Latin-1/UTF-16 · v2.4 adds UTF-8 |
Frequently asked questions
Why do different players show different metadata?
Because the file has both ID3v1 and ID3v2 tags with conflicting values, and players disagree about which takes precedence. Most modern players prefer ID3v2.
Why is my track's title showing as garbled characters?
A text-encoding mismatch. ID3v2.3 tags written as Latin-1 but containing UTF-8 bytes (or vice versa) render as mojibake. Retagging with UTF-8 in ID3v2.4 usually fixes it.
Do other formats use ID3?
MP3 mainly. FLAC uses Vorbis comments, MP4/M4A uses its own atom-based metadata, and Ogg uses Vorbis comments too — different containers, same concept.
Last reviewed · found a mistake? contact@decoder.tools · view as markdown