Audio Metadata edits a music file's title, artist, album and year, and writes cover art into the containers that support it. The panel is called “Music tags”: a text field left empty is not written, and a cover can be dropped in as JPG or PNG; MP3, M4A and FLAC support cover art, and other formats are told plainly that only text tags can be written.

Nothing here recompresses the sound. The implementation uses ffmpeg stream copy (-c copy) to rewrite container metadata only; MP3 gets ID3v2.3. When no new cover is chosen, a file that supports cover art keeps the one it already has.

1. 01Select the audiochoose the file whose tags you want to change on the left of the workspace and open the “Music tags” tab.
2. 02Fill in the textenter “Title”, “Artist”, “Album” and “Year” as needed, leaving fields you do not want to change blank.
3. 03Add a coverMP3, M4A and FLAC accept a dropped JPG or PNG; other formats show text-tag editing only and suggest converting the format first.
4. 04Write the resultafter previewing the command, click “Write tags” or “Write cover and tags” and download the new audio file.

Cover format

only JPG, JPEG and PNG are accepted as uploads; the square-image advice is a hint in the interface, and nothing is cropped to a square automatically.

Audio that can carry a cover

the panel only offers cover art for MP3, M4A and FLAC; other formats can still take text tags but no embedded image.

Not a tag reader

the form does not prefill existing titles, artists and so on, so a blank field means “do not add this field” rather than being a full tag-management view.

No audio re-encoding

processing is fast, but the metadata abilities the container itself lacks do not appear just because of this tool.

What it does not do

it does not fetch cover art online, does not match against a song database and does not batch-edit a whole folder; convert the format first with “Audio Converter” when it does not fit.

The audio and the cover image are handed to ffmpeg.wasm locally in the browser and are never uploaded; the first use of the workbench downloads about 31–32 MB of ffmpeg core from the site's asset domain or jsDelivr.