ID3 Tag Editor
View and rewrite common ID3/tag fields (title, artist, album, genre) and export a new copy. Nothing is uploaded.
How this tool works without JavaScript
Copies the audio stream and writes updated metadata using FFmpeg, so the audio content is preserved. The output is a new file; the original is never modified.
Enable JavaScript to use the interactive tool. Processing happens locally in your browser; nothing is uploaded.
What it does
Copies the audio stream and writes updated metadata using FFmpeg, so the audio content is preserved. The output is a new file; the original is never modified.
Tool-specific detail
ID3 Tag Editor is scoped to Fix a mislabelled track: it accepts MP3, WAV and other supported formats, produces audio, and exposes only the controls that job needs. Stream copy preserves the audio bytes but may re-wrap the container.
How to use
- Add an MP3/M4A/FLAC file.
- Fill in the tags you want (empty fields are left as-is or cleared, as shown).
- Export the re-tagged copy and verify it in the metadata viewer.
Common use cases
- Fix a mislabelled track.
- Add artist and album to a rip.
Limits & considerations
Stream copy preserves the audio bytes but may re-wrap the container. Some players cache tags aggressively. Not all tag frames are editable in this build.
How your audio is processed
ID3 Tag Editor uses FFmpeg.wasm on this device to create audio. The engine is loaded from this site on first use and cached afterwards; no source audio is uploaded.
Privacy & security
ID3 Tag Editor reads MP3, WAV and other supported formats from local memory, creates audio with browser APIs, and keeps the result in a temporary object URL until you download it or leave the page. No audio bytes are uploaded, logged, or stored by Bench.
Frequently asked questions
ID3 Tag Editor keeps this job on your device. iD3 Tag Editor reads MP3, WAV and other supported formats from local memory, creates audio with browser APIs, and keeps the result in a temporary object URL until you download it or leave the page. No audio bytes are uploaded, logged, or stored by Bench.