Audio Tag Viewer

See every metadata tag inside an audio file: ID3v1 and ID3v2.2 to 2.4 in MP3s, Vorbis comments in FLAC, Ogg and Opus, iTunes atoms in M4A, APEv2, and WAV INFO chunks, with the cover art and where each tag sits in the file. Nothing is uploaded or changed.

Viewer Media & Files Updated Oct 16, 2026
How to Use
  1. Drop an audio file: MP3, FLAC, Ogg, Opus, M4A/MP4, WAV, AIFF, or an APE, WavPack or Musepack file with an APE tag.
  2. Or press a sample to see each tag format: the tool assembles a small tagged test file in your browser.
  3. Read the table: every field, its value, and how it was stored (tag version, frame or atom ID and text encoding).
  4. Check the file map on the right: it shows where each tag block sits, such as an ID3v2 tag at the start and a 128-byte ID3v1 tag at the end.
  5. If names from an old MP3 look garbled, change “Legacy text read as” to the code page the file was tagged in, such as Windows-1251 for Cyrillic.
  6. Save the cover art, or copy every field as text. The Show Work section walks through the bytes of your file.
Input
Drop an audio file, or
MP3, FLAC, Ogg, Opus, M4A, WAV, AIFF, APE — read on your device, never uploaded
Samples
Tags and Where They Sit
Tag format
—
Fields
—
Cover art
—
Tag bytes
—

Worked Example

Reading an ID3v2 header. An MP3 starts with the ten bytes 49 44 33 03 00 00 00 00 21 76. The first three spell “ID3”, then version 3 (ID3v2.3), revision 0 and flags 0. The size bytes are syncsafe, 7 bits each: 0 × 2,097,152 + 0 × 16,384 + 33 × 128 + 118 = 4,342. So the tag is 10 + 4,342 = 4,352 bytes and the first MPEG audio frame starts at byte 4,352.

Frames inside it. A TIT2 (title) frame holding “Café Sunrise” in UTF-16 with a byte-order mark takes 1 encoding byte + 2 BOM bytes + 12 × 2 = 27 bytes of data, plus a 10-byte frame header. In ID3v2.3 that size is written as the plain number 00 00 00 1B; in ID3v2.4 it would be syncsafe, which for any size under 128 is the same four bytes. The difference appears at 128: a 300-byte frame is 00 00 01 2C in ID3v2.3 but 00 00 02 2C in ID3v2.4, because 300 = 2 × 128 + 44.

The common mistake: reading a syncsafe size as an ordinary number. The bytes 00 00 21 76 read as a plain 32-bit integer are 0x2176 = 8,566, almost twice the real 4,342. A parser that does this skips 4,224 bytes of audio, and one that applies syncsafe to ID3v2.3 frame sizes reads the 300-byte frame above as 172 bytes and loses its place. iTunes once wrote ID3v2.4 frame sizes as plain numbers, so this tool checks which reading lands on a valid next frame.

Show Work

Drop an audio file or press a sample to see each tag block, frame and byte offset it contains.

Formulas

Syncsafe size
n = b₀×2²¹ + b₁×2¹⁴ + b₂×2⁷ + b₃
Each byte holds 7 bits; the largest tag is 2²⁸ − 1 = 268,435,455 bytes
ID3v1 position
offset = file size − 128
“TAG”, title 30, artist 30, album 30, year 4, comment 30, genre 1 byte
MP3 frame length
bytes = ⌊144 × bitrate ÷ rate⌋ + padding
MPEG-1 Layer III: 128 kbps at 44.1 kHz is 417 bytes
MP3 length (constant bitrate)
seconds ≈ audio bytes × 8 ÷ bitrate
Tags are taken out first; a Xing/Info header gives the exact frame count instead
FLAC and Opus length
seconds = samples ÷ rate; (granule − pre-skip) ÷ 48,000
From STREAMINFO, or from the last Ogg page

From 128 Bytes to Hundreds of Frames

MPEG audio has no field for a song title, so in 1996 Eric Kemp’s program Studio3 appended a fixed 128-byte block to the end of the file: “TAG”, then 30 bytes each for title, artist and album, 4 for the year, 30 for a comment and one genre byte indexing a list of 80 genres (the ID3v2.3 document lists 126, counting Winamp’s additions). Michael Mutschler’s ID3v1.1 took the last two comment bytes for a zero and a track number. Putting the tag at the end meant old players ignored it, but also that a player streaming the file saw it last.

ID3v2, edited by Martin Nilsson, moved the tag to the front and made it a list of frames: version 2.3.0 is dated 3 February 1999 and 2.4.0 1 November 2000. Version 2.4 added UTF-8, syncsafe frame sizes and multiple values separated by a zero byte. Other formats chose simpler designs: Xiph’s Vorbis comments, used by Ogg Vorbis, Opus (RFC 7845) and FLAC (RFC 9639, December 2024), are plain UTF-8 “NAME=value” strings with little-endian lengths, and Apple’s iTunes stores MP4 tags as “ilst” atoms such as ©nam and ©ART inside moov › udta › meta.

About This Tool

This tool reads the tags in an audio file and shows how each one is stored: the tag version, the frame or atom ID, the text encoding, and the byte range of every block, so you can see why one player shows a title and another does not. It reads the formats people actually meet, from ID3v1 to ID3v2.4, APE, FLAC, Ogg, Opus, M4A, WAV and AIFF, and it shows embedded cover art with its real pixel size.

Everything runs in your browser. It reads only slices of the file, the start, the end and the tag blocks, so large files are quick, and nothing is uploaded or changed. The built-in samples are small test files assembled in your browser to show each format.

It is for music collectors, podcasters checking their episode tags, and developers writing tag code who want to see the bytes.

Related tools: Audio Converter, Metadata Scrubber, and File Inspector.

Frequently Asked Questions

Which tag formats does it read?

ID3v2.2, 2.3 and 2.4 (including unsynchronisation, extended headers and zlib-compressed frames), ID3v1 and v1.1 with the Enhanced TAG+ extension, APEv1/APEv2, FLAC Vorbis comments and PICTURE blocks, Ogg Vorbis and Opus comment packets with embedded pictures, iTunes-style MP4/M4A “ilst” atoms, WAV LIST/INFO and id3 chunks, and AIFF text chunks. Lyrics3 blocks are detected but not decoded.

Why does the title show strange characters?

ID3v1 has no way to say which character set it uses, and ID3v2’s “ISO-8859-1” fields were often filled with a local code page instead. A Russian title saved as Windows-1251 reads as accented Latin letters when treated as ISO-8859-1. Pick the right code page under “Legacy text read as”; UTF-8 and UTF-16 fields are not affected.

What is a syncsafe integer?

A number stored 7 bits per byte, with the top bit of every byte left at 0, so the tag can never contain the 11 set bits an MP3 player looks for at the start of an audio frame. The four size bytes 00 00 21 76 mean 33 × 128 + 118 = 4,342. ID3v2.4 uses them for frame sizes too; ID3v2.3 frame sizes are plain numbers.

Can it edit or remove tags?

No. It only reads; the file is never changed or saved. To strip metadata from a file before sharing it, use the Metadata Scrubber; to re-encode the audio into another format, use the Audio Converter.

Is my file uploaded?

No. The page reads small slices of the file in your browser: the first and last kilobytes, plus the tag blocks themselves. A 2 GB audiobook is as quick to read as a 3 MB song, and nothing leaves your device.

How do I use the Audio Tag Viewer?

Just type your numbers. The answer shows up right away — there is no button to press. Change anything and it updates by itself.

Is it free? Does it work without internet?

Yes to both. It is free with no sign-up, and once the page has loaded it keeps working even with no internet.

Where does my data go?

Nowhere — every calculation runs on your own device. Nothing you enter is uploaded, logged, or stored.

Common Use Cases

Check a tagger’s work

After a batch edit, confirm that 12 tracks really got TRCK 1/12 to 12/12 and a 500×500 front cover.

Find out why a player shows “Unknown artist”

See whether the artist is in an ID3v1 tag only (30 characters at most) or missing altogether.

Fix garbled song names

Find the code page an old MP3 was tagged with, such as Windows-1251 or Shift_JIS, before retagging it.

Measure the tag overhead

A 1.2 MB cover picture in a 3 MB song is 40% of the file; see exactly how many bytes each tag block takes.

Last updated: