Benefic
Edit Audio Metadata
Lossless tag editing for FLAC, MP3, WAV, DSF, Ogg, Opus, M4A, AAC, ALAC, and AIFF — ID3v2, Vorbis comments, and MP4 iTunes atoms all supported.
Files never leave your device. The editor runs entirely in the browser, so your tracks stay private and nothing is uploaded. Only the tag container is rewritten — the audio bitstream is untouched, so there is no quality loss.
Frequently asked questions
Everything you might wonder about editing audio metadata in Benefic.
What is audio metadata?
Audio metadata is descriptive information embedded inside an audio file — track title, artist, album, track number, disc number, year, genre, and cover art. It is stored in a tag container alongside the audio, so music players, DJ software, and libraries can display and organize your files without scanning the audio itself.
Which audio file formats does the metadata editor support?
Writable containers: FLAC, DSF, MP3, WAV, Ogg (Vorbis and Opus), AIFF, and MP4 (M4A). Writable codecs: FLAC, DSD, MP3, PCM, Vorbis, Opus, AAC, and ALAC.
Which tag formats can Benefic write?
ID3v2.4 for MP3, WAV, AIFF, and DSF; Vorbis Comments for FLAC, Ogg Vorbis, and Ogg Opus; and MP4 iTunes atoms (ilst) for M4A (AAC / ALAC). When your source file already has an older tag (ID3v2.2 or ID3v2.3), Benefic reads it and rewrites it as ID3v2.4 on save.
Which fields can I edit?
Track title, artist, album, track number, disc number, year, genre, and embedded cover art. Other frames or atoms in the source file (ReplayGain tags, MusicBrainz IDs, lyrics, custom text frames, and so on) are preserved on save for MP3, WAV, AIFF, DSF, FLAC, and Ogg — see the caveat about MP4 below.
Which ID3 versions are supported?
Benefic reads ID3v2.2, ID3v2.3, and ID3v2.4 tags and normalizes them to ID3v2.4 on save. ID3v1 (the 128-byte trailer at the end of some older MP3s) is not read or written — if your file has only an ID3v1 tag, it will import as having no tag, and saving will add a fresh ID3v2.4 tag at the head of the file.
Do my audio files get uploaded to a server?
No. The editor runs entirely in your browser as WebAssembly. Your audio files are read, decoded, and re-written locally — nothing is sent over the network. This makes it safe to use for private or unreleased tracks.
Does editing tags re-encode my audio?
No. Editing metadata only rewrites the tag container — the audio bitstream itself is untouched, so there is no quality loss and no perceptible wait even on large lossless files.
Can I add or replace cover art?
Yes. Drop an image onto the cover-art tile (or click it to pick a file). JPEG, PNG, and WebP are accepted. The new image is embedded into the tag container on save. Hit "Remove" on the preview to strip the embedded art instead.
Does Benefic preserve fields it doesn't expose?
For MP3, WAV, AIFF, DSF, FLAC, and Ogg, yes — the tag is read from the source, only the fields you edit are changed, and every other frame or comment is preserved on save. For MP4 (M4A), the ilst atom is rebuilt from scratch on save: the fields above plus existing cover art are preserved, but other atoms (composer, grouping, and similar ilst entries) are not currently carried through.
Is there a file-size limit?
There is no hard cap set by Benefic. Practical limits come from your browser's available memory — modern desktop browsers handle multi-gigabyte lossless files without trouble. Because the tool runs locally, there is no upload bandwidth or rate limiting to worry about.
Does it work offline?
Yes, once the page has loaded. The editor is a static page plus a WebAssembly module — after the first visit it will run without a network connection.
Why are some files not editable in place?
A few containers are recognized on import but not yet supported by the tag writer — Matroska (.mkv / .webm) and raw MP4 video files are the notable ones. When Benefic cannot write the container, the editor shows file info but the save button is disabled. We are actively expanding writer coverage.
Is the audio metadata editor free to use?
Yes. It is free, requires no account, and has no upload or usage limits. Because it runs client-side there is no infrastructure cost to pass on.