Which metadata fields can I actually edit?

Six: title, artist, album, year, genre and comment. They map to the TIT2, TPE1, TALB, TYER, TCON and COMM frames. Album art, track and disc numbers, lyrics and composer are not exposed, even if the original file contained them, so those frames are not carried into the rewritten tag.

What happens to the original file on my disk?

Nothing. The editor reads the file into memory, rewrites the tag in memory, and downloads a new copy named with a (tagged) or (no tags) suffix. Your original is never opened for writing, which means a bad edit is always recoverable by simply discarding the download.

Will editing a tag re-encode the audio?

No. The audio bytes are copied across untouched; only the tag block is rebuilt and prepended. That is why the operation is instant even on a long episode and why the sound is identical to the source. The tag is the only thing that changes.

Why did my ID3v2.4 file come back as v2.3?

Because the writer emits ID3v2.3 by design. It discards the old tag block entirely and builds a clean v2.3 tag, with the year going into the TYER frame that v2.3 expects. This makes the output widely compatible across players at the cost of not preserving a v2.4-only structure.

Can I tag several files at once?

No. The editor works on one file at a time and there is no queue, because it is built around inspecting and editing the fields of a single tag. If you need to process a batch, run the files through one after another; the per-file work is quick since no audio is decoded.

ID3 Tag Editor

You Might Also Need

Podcast Chapter Marker Tool

Add chapter markers to podcasts

Show Notes Timestamp Generator

Generate timestamps for show notes

Batch File Renamer

Rename audio files in batches

Podcast Cover Art Generator

Generate podcast cover images

ID3 Tag Editor reads the metadata block inside an MP3, lets you edit the common text fields, and writes a fresh ID3 tag back into the file. It also strips a tag entirely when you need a clean master before distribution.

What is ID3 Tag Editor?

Choose an MP3 and the editor parses its ID3 tags on load, showing the tag version and the number of frames alongside the current title, artist, album and year values. Six fields are editable, and each one maps to a specific text frame in the file: Title to TIT2, Artist to TPE1, Album to TALB, Year to TYER, Genre to TCON and Comment to COMM. Whatever was already present is pre-filled into the form, so editing an existing tag starts from its real values rather than a blank slate.

What the editor exposes:

Six editable MP3 metadata fields: title, artist, album, year, genre and comment.
A current-tags panel showing the detected tag version and frame count, plus a title, artist, album and year summary line.
A write action that rebuilds the tag as ID3v2.3 and downloads the audio as name (tagged).mp3.
A strip action that removes the entire ID3 block and downloads the audio as name (no tags).mp3.
An automatic download on completion, so there is no extra save step after the rewrite.
A clear-file control that resets the session without touching anything on disk.

All the parsing and serialisation lives in one library module, and the write path is a full rewrite rather than a patch. The writer finds the existing ID3 header, measures its size from the syncsafe length field, discards everything up to the start of the audio, and prepends a newly built tag. Text frames are emitted for whichever fields you filled in; an empty field is simply not written rather than written blank. The Comment frame is assembled with an English language code and Latin-1 text, and 512 bytes of padding are appended inside the tag so a future edit has room to rewrite in place without shifting the audio. Because the old tag is discarded first, an older or non-standard tag is normalised to a clean ID3v2.3 block as a side effect.

The real limitations to plan around:

MP3 only; the picker accepts MPEG audio and nothing else.
Only the six documented fields are editable, so there is no album art, track number, disc number, lyrics, composer or multi-value artist support.
Output is always written as ID3v2.3, so a file that arrived as v2.4 comes back as v2.3.
Genre is free text written straight into TCON, not the numeric ID3 genre list, so a player may show it verbatim rather than as a mapped name.
Text is encoded as Latin-1, which means non-Latin scripts can be mangled; keep metadata to Latin characters for reliable round-trips.
There is no batch mode and no undo; each file is handled one at a time and the original on disk is never modified, only a new download is produced.

The two buttons cover two different intents, and it helps to be deliberate about which you use. Write tags and download is for finishing an episode: fill the fields that matter, leave the rest blank, and let the writer normalise the tag. Strip tags and download is for producing a clean master when a distributor or a client wants an untagged file, since it removes the whole block in one step instead of blanking field by field.

How to use ID3 Tag Editor

Click Drop or choose an MP3 and select a file; the existing tag is parsed and the fields fill in with whatever was already there.
Edit the title, artist, album, year, genre and comment fields you want to change, leaving any field blank to omit it from the new tag.
Press Write tags and download to rebuild the tag as ID3v2.3 and save the audio with a (tagged) suffix.
If you need an untagged copy instead, press Strip tags and download to remove the ID3 block entirely.

When to use ID3 Tag Editor vs related tools

ID3 Tag Editor is the metadata tool for a finished MP3, while Podcast Chapter Marker Tool writes the chapter frames that sit alongside those fields in the same tag block. If you are preparing notes rather than the file, Show Notes Timestamp Generator produces the text-side timings. For tidying a folder of episode files in one pass, Batch File Renamer handles the filenames that sit next to the tags. When the artwork that goes into those fields does not exist yet, Podcast Cover Art Generator makes it before the tag is written.

Privacy & Security

This tool runs entirely in your browser — no data ever leaves your device. There is no server round-trip, no upload, no logging, and no account required. Your input is processed locally using client-side JavaScript and is never stored, transmitted, or accessible to anyone else. When you close the tab, everything disappears.