Skip to main content

MP3 tag editor online

Read and edit ID3 metadata tags in audio files directly in your browser.

Free & unlimited
Mode
All processing happens in your browser. No data is sent to any server.

Edit the metadata that music players read off your MP3 files. The page parses the existing ID3v2 block directly from the file's bytes — including the embedded cover image — shows you every field it found, and writes a fresh ID3v2.3 header in front of the untouched audio data when you save. Eleven fields are supported: title, artist, album, album artist, year, genre, track number, disc number, composer, BPM and comment. Cover art can be replaced with a JPEG, PNG or HEIC image, which is converted for you. A batch tab applies shared values — artist, album, year, genre — across up to twenty files at once, which is the fast way to fix a whole ripped album.

Key facts about MP3 tag editor online

Key facts about MP3 tag editor online
ReadsThe ID3v2 block at the head of the file, decoding ISO-8859-1, UTF-16 and UTF-8 text frames
WritesA fresh ID3v2.3 header placed in front of the original audio frames
FieldsTIT2 title, TPE1 artist, TALB album, TPE2 album artist, TYER year, TCON genre, TRCK track, TPOS disc, TCOM composer, TBPM and COMM comment
Cover artWritten as an APIC frame, picture type 3 (front cover); HEIC input is converted before embedding
Audio untouchedThe audio frames are copied byte for byte — nothing is decoded or re-encoded, so tagging is lossless and near-instant
Old tag handlingAn existing ID3v2 block is measured from its size header and skipped, so tags are replaced rather than stacked
BatchUp to 20 files per batch, applying shared artist, album, year and genre
Genre pickerA searchable list of standard genre names, or type your own
OutputThe same filename and MIME type, with the new tag block in front
Size limit500 MB per file

What happens to your file

Your music never leaves the tab. The file is read into an ArrayBuffer in your browser, the existing ID3 block is parsed by JavaScript on this page, and saving assembles a new byte array — a fresh 10-byte ID3v2.3 header, the frames you filled in, then the original audio bytes copied straight across — and hands it back as a blob. Nothing is uploaded, no lookup is made against any music database, and no processing engine is downloaded. Cover images you add are read the same way and embedded locally.

About this tool

  1. 1

    Load an MP3

    Drop a file in single-file mode. The existing ID3 tags are parsed and every populated field appears filled in, along with the embedded cover art if there is one.

  2. 2

    Edit the fields

    Title, artist, album, album artist, year, genre, track, disc, composer, BPM and comment are all editable. Empty fields are simply not written.

  3. 3

    Pick a genre

    Use the searchable genre list for a standard name that players will recognise, or type anything you like — the field is free text in the tag format.

  4. 4

    Replace the cover

    Drop in a JPEG, PNG, WebP or HEIC. It is embedded as the front-cover picture; HEIC files from an iPhone are converted first.

  5. 5

    Or switch to batch

    Drop up to twenty files and set the fields they share — artist, album, year, genre — to apply the same values across the whole set in one pass.

  6. 6

    Save

    The new tag block is written in front of the untouched audio and downloaded under the original filename.

Specs & compatibility
Tag version writtenID3v2.3, the version Windows Explorer, iTunes and most car stereos read most reliably
Tag versions readID3v2 with ISO-8859-1, UTF-16 with BOM, UTF-16BE and UTF-8 frame encodings
Best-supported inputMP3 — ID3v2 is an MP3 tagging standard and that is what the writer emits
Cover art formatsJPEG, PNG, WebP and HEIC (converted before embedding)
Batch cap20 files per batch
Maximum file size500 MB
SpeedInstant — the operation is a byte copy, not an audio process
BrowsersAny modern browser; no WebAssembly or Web Audio required for tagging itself
  • Tagging is lossless. The audio frames are copied byte for byte, so you can retag a file as many times as you like without any quality cost.
  • The album artist field is what most players group a compilation by. Filling artist alone leaves a various-artists album scattered across your library.
  • Cover art bloats the file. A 3000 x 3000 JPEG adds several megabytes to every track; 600 x 600 is plenty for a phone screen and a fraction of the size.
  • Batch mode is for the fields a whole album shares. Title and track number are per-file and still have to be set individually.
  • Existing tags are replaced, not merged — anything you leave blank in the form is dropped from the saved file. Check what was read before you save.
  • The genre field is free text in ID3v2.3, so a custom genre is valid even though some older players only display the numeric genre list.
  • If a player still shows the old tags after saving, it is almost certainly reading a cached library entry rather than the file. Re-import the track.
  • Reads existing ID3v2 tags including embedded cover art
  • Eleven editable fields covering the standard ID3v2.3 text frames
  • Cover art replacement with automatic HEIC conversion
  • Searchable genre picker
  • Batch mode for up to 20 files with shared fields
  • Lossless: audio frames are copied, never re-encoded
  • Saves under the original filename
  • Fixing artist and album fields on a ripped CD so it groups correctly in a music library
  • Adding cover art to tracks that show a blank square on a phone
  • Setting album artist across a compilation so it stops splitting into separate albums
  • Correcting the year and genre on files bought from an inconsistent download store
  • Stripping a comment field left behind by a download site
  • Renumbering tracks on an album that imported in the wrong order
No, and that is the point. ID3 tags live in a block at the front of the file, entirely separate from the audio frames. When you save, the tool measures the size of the old tag block from its header, skips past it, writes a fresh ID3v2.3 header plus your frames, and then copies the original audio bytes across unchanged. The audio is never decoded, so it cannot be degraded. You can retag the same file a hundred times and the sound is identical every time.
ID3v2.3. That is a deliberate choice: it is the version with the broadest real-world support, read reliably by Windows Explorer, iTunes, Android media scanners and virtually every car stereo and hardware player. ID3v2.4 is technically newer and handles text encoding more cleanly, but support for it is patchier in older hardware. On reading, the parser is more permissive and handles ISO-8859-1, UTF-16 with a byte-order mark, UTF-16BE and UTF-8 frames so it can open files written by other taggers.
Because the image is embedded in full inside the tag, not linked. A 3000 by 3000 pixel JPEG from a scan or a high-resolution download can easily be three or four megabytes, and that is added to every track you apply it to — across a twelve-track album that is forty megabytes of duplicated artwork. Resize the image to something like 600 by 600 before embedding. That is more than enough for any phone or car display and costs a few tens of kilobytes per file.
The reliable case is MP3. ID3v2 is an MP3 tagging convention, and the writer here emits an ID3v2.3 block followed by the original audio bytes — which is exactly right for MP3. Other formats use different tagging schemes: FLAC and OGG use Vorbis comments, M4A uses MPEG-4 atoms. If you need to tag those, use a dedicated desktop tagger. For MP3, which is what the great majority of untagged library files are, this handles the job losslessly.
No. Saving writes a complete new tag block and drops the previous one, so any field left empty in the form is simply not present in the saved file. This is why the tool fills the form with everything it found when you load a file — what you see is what will be written. If you only meant to change the genre, leave the other fields exactly as they were read. In batch mode, only the shared fields you fill in are applied.
No. There is no lookup, no fingerprinting and no music database query of any kind — the tool reads what is in your file and writes back what you type. That also means it cannot fill in tags automatically for an untagged file; you supply the values. Everything happens inside your browser tab: the file is read into memory, the tag block is parsed and rebuilt by JavaScript on this page, and the result is handed back as a blob. Nothing is uploaded.

Related tools

View all

Part of Audio tools that run in your browser

Updated

We use anonymous analytics to improve ToolChamp. No personal data is stored or sold. Privacy Policy