Edit MP3 tags
Title, artist, album and cover art are edited without re-encoding a single sample of audio. The tag is a block at the start of the file, separate from the sound, so correcting it costs nothing in quality.
Fix the title, artist, album and the rest, without re-encoding a single frame of audio. The file is read and rewritten on your own device — which matters for music more than most things, because fixing tags usually means doing it to a great many files at once.
Nothing is uploaded, and nothing is re-encoded. The audio frames are copied across byte for byte.
The audio is not touched
This is the thing worth checking in any tag editor. Tags are not part of the audio — they sit alongside it in the same file — so changing them should never involve decoding or re-encoding anything. BriskFile rebuilds the tag block and copies the audio frames across unchanged, and the result is bit-identical where it counts. An editor that re-encodes takes a little quality every time you correct a typo, and you would never notice until the twentieth pass.
Why players disagree about the same file
ID3 is really two formats sharing a name. ID3v1 is a fixed 128-byte block stuck on the end of the file, limited to 30 characters a field and no accents at all. ID3v2 sits at the front, is variable length, and supports proper text encodings. A great many files carry both, saying different things, because different software wrote each one — and players pick whichever they prefer.
Both are read here, with the richer v2 tag winning where they disagree. Saving writes a single clean v2 tag, which is what ends the argument.
Accents, and why they were broken
If an artist's name has ever come back as mojibake, the file was tagged in Latin-1 — an encoding with no room for most accented characters, let alone anything non-European. Retyping the name and saving writes it as UTF-8, which every current player reads correctly, and it stays fixed.
What is left alone
Album artwork, lyrics and any frame this page does not show are carried through untouched rather than dropped. Editing the title does not quietly strip the cover art, which is a failure mode of more tag editors than it should be.
Questions
What are ID3 tags?
The block of text stored inside an MP3 that tells a player what the track is: title, artist, album, year, track number, genre and a comment. It is not part of the audio — it sits alongside it in the same file, which is why a badly tagged track plays perfectly and still shows up as "Unknown Artist".
Does editing tags re-encode the audio?
No, and this is the thing to check in any tag editor. BriskFile rebuilds the tag block and copies the audio frames across byte for byte, so the sound is bit-identical to what went in. An editor that re-encodes degrades a little more every time you correct a typo.
Why do my tags show up wrong in one player and right in another?
Almost always because the file carries two sets. ID3v1 is a fixed 128-byte block at the end of the file, ID3v2 is a richer block at the front, and plenty of files have both saying different things. Different players prefer different ones. Saving here writes a single clean ID3v2 tag, which resolves the disagreement.
Why are accented characters broken?
Because the file was tagged in Latin-1, which cannot represent them, so they were mangled when written. BriskFile writes UTF-8, which every current player reads — retyping the name correctly and saving fixes it permanently.
How do I remove a tag entirely?
Empty the field and save. An empty value drops the frame rather than writing a blank one, so the file stops carrying it at all.
Can I edit album artwork?
Not yet. Artwork is stored as an embedded image frame and is left exactly as it was — editing the text tags never disturbs it.
Are my files uploaded?
No. The file is read and rewritten by this page on your own device, which matters for a music library more than most things: fixing tags usually means doing it to hundreds of files, and no music collection should have to be uploaded to be sorted out.
What BriskFile will not do to you
-
Your files never leave your device
Every conversion runs in your browser. Open DevTools, watch the Network tab, and you will see no upload — because there is not one.
-
No account, no email, no watermark
Nothing to sign up for and nothing stamped on your images. There is no step between choosing a file and getting it back.
-
No limits at the download button
No daily cap, no file counter, no "upgrade to download". If the tool starts a job, it finishes it.
-
Checkable, not just claimed
Open the Network tab and convert something — nothing goes out. Or load the page, disconnect, and watch it keep working: the tool is already on your machine, and your file never leaves it.