Read the tags on any audio file and edit them for MP3, FLAC, and OGG — title, artist, album, artwork. Your audio bytes are never re-encoded.
The metadata editor shows the tags on any audio file — title, artist, album, artwork, and the rest — and lets you edit them on MP3, FLAC, and OGG. Everything else is deliberately view-only, because writing tags for a format properly is a different job from reading them, and a half-correct writer is how libraries get corrupted.
It's for fixing the track that shows up as "Unknown Artist", adding artwork before you share something, or cleaning up an inconsistent library. The important guarantee: your audio is never re-encoded. Tags live in a separate region of the file, so editing them leaves the audio bytes untouched and bit-identical — every save is checked against the original before it's written, and abandoned if anything doesn't match. How to edit audio metadata covers which formats can be written and why.
Those formats can be viewed but not written, deliberately. M4A/MP4 stores tags inside the MP4 container's atom structure, and rewriting that safely is a different class of problem than the tag blocks MP3, FLAC, and OGG use — so rather than risk corrupting your files, the editor is read-only there. Opus files (including .ogg files whose codec is Opus — the editor checks the actual codec, not the file extension) use OpusTags, which this editor can view but not write. Tag writing is currently supported for MP3, FLAC, and OGG (Vorbis).
No — the audio stream is never decoded, re-encoded, or touched in any way. Editing tags rewrites only the small metadata block at the head of the file; the audio bytes are copied through untouched. The editor actually proves this to itself on every save: it computes a SHA-256 fingerprint of the audio region before and after, and refuses to produce the file if they differ. It also re-reads the saved file from scratch to confirm it parses cleanly with the same duration, sample rate, and channels.
MP3 files get an ID3v2.3 tag — v2.3 rather than the newer v2.4 because Windows Explorer and a number of older players still don't read v2.4 correctly, so v2.3 is the compatibility-safe choice. FLAC and OGG files get standard Vorbis comments, which is the native tagging system for both. Any old ID3v1 block at the end of an MP3 is removed so stale values can't linger in old players.
JPEG or PNG, embedded as a front-cover image (the kind players and phones display). The editor shows the image's dimensions and file size before you save, and warns you above roughly 1 MB — oversized art bloats every copy of the file and most players display covers at small sizes anyway. Around 500–800 px square is the sweet spot. You can also remove existing art entirely.
Browsers can't overwrite a file on your disk — that's a browser security boundary, not a limitation of this tool. Saving produces a new file named like "song (tagged).mp3" so it's unambiguous which copy has your edits, and your original stays exactly as it was. Nothing is uploaded at any point; the rewrite happens entirely in your browser's memory.
It depends on the format, and the editor is honest about the difference. For FLAC and OGG, every field it doesn't display — ReplayGain values, MusicBrainz IDs, lyrics, custom fields — is preserved verbatim in the saved copy. For MP3, the ID3 tag is rebuilt from the fields shown, so uncommon frames (like embedded lyrics or podcast chapters) are not carried over — if your MP3s carry specialist frames you care about, check the saved copy before replacing anything.