On-device AI — professional-grade, fully private.

Audio Tag Editor

Edit audio tags and album art — the sound is never re-encoded.

  • Runs on your device
  • Audio copied, never re-encoded
  • 19 fields plus album art
  • One file free · 100 with Pro

Drop audio here

MP3, M4A, M4B, MP4, FLAC, OGG, Opus or WAV — one file at a time, up to 200 MB

Tag formatHow the tags are written into the file
ID3 version
ID3 version

v2.3 is read by the widest range of players. v2.4 stores full dates and non-Latin text.

128 bytes at the end of the file, for players that read nothing newer. Titles are cut to 30 characters there.

FilenamesFill tags from the name, or rename from the tags
Pattern

Use %artist%, %title%, %album%, %track% and %year%. A slash makes folders in the archive.

Off by default, so a save never changes a filename you did not ask it to change.

All filesActions across everything in the queue
Pro

Removes every tag and the artwork from every queued file, and leaves the audio untouched.

Add a file to see the tags it already carries.

The audio is copied, not re-encoded

Tags live in a block at a known place in the file, separate from the encoded audio. That means editing them is a splice: build a new tag block, then copy the audio straight through. This tool never decodes your audio, so there is nothing that could change it.

  • Nothing is decoded. No audio engine is loaded and no samples are read. The save reads a few kilobytes of tag block and writes a few kilobytes back.
  • The cost does not grow with the file. Measured on the reference machine, a 200 MB file saves in the same few milliseconds as a 10 MB one, because the amount of work is the same.
  • Every save is checked. The finished file is re-read, all nineteen fields are compared against what was asked for, and the audio is compared against your original. If anything differs you get an error instead of a file.
  • Untouched tags stay untouched. ReplayGain values, MusicBrainz identifiers, ratings and anything else the editor does not show are carried across rather than quietly dropped.

The practical consequence: you can retag a lossless master as many times as you like without it degrading, and a tagged file will still match a checksum of its own audio.

Album art, embedded properly

Every format stores cover images differently, and getting it wrong produces a file that looks tagged and shows no picture. Choose a JPEG or PNG and it is written the way each format actually expects.

  • MP3 and WAV. An APIC frame marked as the front cover, inside the ID3v2 tag.
  • FLAC. A real PICTURE metadata block, with the width, height and colour depth measured from the image rather than copied from whatever was there before.
  • M4A, M4B and MP4. A covr atom, tagged as JPEG or PNG by reading the image bytes rather than trusting the file extension — a picture typed as the wrong kind draws as nothing at all.
  • OGG and Opus. The standard picture block, encoded into the comment header.
  • Export and remove. The artwork already inside a file can be saved out as an image, or removed without touching the rest of the tags.

Nineteen fields, and what each is for

Most editors offer four or five. The fields below are the ones music players, podcast apps and DJ software actually read, grouped the way you fill them in.

  • Track. Title, artist and genre — the minimum for a track to be identifiable in any player.
  • Album. Album, album artist, release date and the compilation flag. Album artist is what stops a compilation splitting into twenty one-track albums.
  • Numbers. Track number and total, disc number and total, and BPM. Filling the totals is what makes an album sort correctly rather than alphabetically.
  • Credits. Composer, grouping, publisher, copyright and ISRC — the fields that matter for classical, library music and anything being delivered to a distributor.
  • Notes. Comment and lyrics. Lyrics are stored in the field players actually display, not in the comment.

Formats, and what happens to each

Five container families, each edited in its own native tag format rather than converted to a common one.

  • MP3. ID3v2.3 or ID3v2.4 at the head of the file. Tags written by older software as ID3v2.2 are read and upgraded, and any ID3v1 block at the end is replaced or removed to match.
  • M4A, M4B, M4R and MP4. iTunes-style atoms. When the tag block sits before the audio, the internal offsets that point at the audio are corrected as part of the save — miss that and the file plays silence with no error anywhere.
  • FLAC. Vorbis comments and a picture block. The seek table and cue sheet are kept, so instant seeking and album track boundaries survive.
  • OGG and Opus. The comment header is rebuilt and the stream repaged, with every page checksum recomputed. Where the new tags fit the original layout, not one audio page is touched.
  • WAV. Both a RIFF INFO list, which is what Windows and most editing software read, and a full ID3 block, which is where the artwork and the rest of the fields live.

Anything else — AAC streams, Matroska, WMA, AIFF — is refused at the file picker with the reason and a link to the converter, rather than accepted and failed later.

Filenames and tags, in both directions

The information you are about to type is usually already in the filename. A pattern such as %artist% - %title% reads it out, and the same pattern renames the file from the tags once you are done.

  • Filename to tags. Fills the matching fields from the name. A name that does not fit the pattern says so instead of filling the fields with nonsense.
  • Tags to filename. Renames the saved file. Track numbers are padded to two digits so a folder sorts correctly.
  • Folders in a batch. A pattern containing a slash produces real folders inside the downloaded archive, so an album comes out organised rather than as a flat list.
  • Safe by construction. Every part of a generated name is cleaned separately, so no file in the archive can be written outside the folder you extract it into.

How to edit audio tags

  1. Add your audio Drop in an MP3, M4A, FLAC, OGG or WAV. The tags already in the file are read and shown straight away, so you can see what is there before you change anything.
  2. Edit the fields Change any of the nineteen fields. Edited fields are marked, and clearing one removes that tag from the file rather than leaving it blank.
  3. Add album art Choose a JPEG or PNG to embed as the cover. You can also export the artwork already in the file, or remove it entirely.
  4. Save Only the tag block is rewritten. The encoded audio is copied through byte for byte, so the sound is identical and the save takes milliseconds however large the file is.

Getting a library to sort correctly

  • Fill album artist on anything with more than one artist on it — this is the single most common reason a compilation splits into twenty separate albums.
  • Fill the track total as well as the track number, or players fall back to sorting alphabetically.
  • Keep artist spelling identical across an album; a trailing space is enough to create a second artist.
  • Choose ID3v2.3 if the files are going to a car stereo, a DJ controller or older software; choose v2.4 if you need a full release date or non-Latin text.
  • Use square artwork of about 600 by 600 pixels — larger images make every copy of the file bigger without any player showing more detail.
  • Check the result in the player you actually use before retagging a whole library.

Common use cases

  • Fix a downloaded album. Read what is there, correct the artist and album, add the artwork, and keep the audio exactly as it was.
  • Prepare a release. Fill ISRC, publisher, copyright and composer before sending files to a distributor.
  • Tag a podcast episode. Set title, artist and comment so the episode shows correctly in podcast apps.
  • Clean a file before sharing. Remove every tag and the artwork in one action, leaving the audio untouched.
  • Rescue a badly named folder. Fill the tags from the filenames, then rename the files back from the tags in a consistent shape.
  • Retag a lossless master. Edit a 24-bit FLAC as often as you like — the samples are copied, never re-encoded.

Runs on your device, not our servers

The file is read where it sits and the finished file is assembled on your device. Nothing is uploaded, nothing is stored, and no part of your audio or your tags is sent anywhere — which is also why there is no online database lookup here: it could not work without sending your music somewhere else.

Tag blocks are read and rewritten in place, so the work does not grow with the size of the file.

Frequently asked questions

Does editing tags re-encode my audio or reduce the quality?

No, and not as a setting you can get wrong — as a property of how the tool works. A tag block sits at a known place in the file, so saving replaces those few kilobytes and copies the encoded audio through untouched. The audio is never decoded, so there is nothing to re-encode. The tool checks this on every save by comparing the audio in the file it produced against the audio in your original, and refuses to hand you the result if they differ.

Can I add album art or cover images?

Yes. Choose a JPEG or PNG and it is embedded as the front cover in the way each format expects: an APIC frame in MP3 and WAV, a PICTURE block in FLAC, a covr atom in M4A, and a base64 picture block in OGG and Opus. You can also export the artwork already inside a file, or remove it.

Which fields can I edit?

Nineteen: title, artist, album, album artist, composer, genre, date, track number and total, disc number and total, BPM, grouping, publisher, copyright, ISRC, the compilation flag, comment and lyrics. Anything else your file carries — ReplayGain values, MusicBrainz identifiers, a rating — is kept exactly as it was rather than being dropped.

What is the difference between ID3v2.3 and ID3v2.4?

Both are widely readable, and v2.3 is the safer default because some older car stereos and DJ software read nothing else. v2.4 stores text as UTF-8 and can hold a full release date rather than only a year. If you type a year and month, the tool tells you before you save that v2.3 can only keep the year, and offers v2.4 as the fix.

Why does clearing a field actually remove the tag?

Because an empty tag and an absent tag are different things, and a player shows them differently. Clearing a box removes that tag from the file, rather than writing a tag whose value is an empty string — which is what most editors do and why an album you thought you had cleared still shows as a blank album rather than an untagged track.

How large a file can I edit?

Up to 200 MB on the free plan, with no length limit at all, because nothing is decoded — a two-hour audiobook costs the same as a three-minute single. Pro removes the size limit up to what your device can handle and lets you queue up to 100 files at once.

Can it look up tags from an online music database?

No, and that is a deliberate choice rather than a missing feature. Looking a track up means sending its title, or a fingerprint of its audio, to somebody else's server — which is exactly the thing this site promises never to do. Instead you can fill the fields from the filename, which is where the information usually already is, and it all runs on your device, not our servers.

What happens to tags this editor does not show?

They are carried through untouched. A file arriving with ReplayGain values, MusicBrainz identifiers or a rating leaves with all of them intact — the only tags removed are the ones you clear yourself, or all of them if you use Remove all tags.

4.7out of 5

from 645 ratings

Rate this tool

Tap a star — it takes a second