The work is executed in the page through browser workers, WebAssembly, Web Audio, or WebGPU as stated.
TAGS / AVAILABLE NOW
Audio Metadata Editor
Fix tags without re-encoding audio. Read and update title, artist, album, date, track, genre, comment, and cover art locally.
TAGS / local workbenchmusic-metadata plus FFmpeg remux
NO COVER
JPEG, PNG, or WebP. Audio remains local.
GUIDE / audio metadata editor online
What does audio metadata editor do?
Audio metadata stores descriptive tags separately from encoded sound frames. SoundTools reads common tags with music-metadata, previews embedded artwork, and asks FFmpeg to copy the audio stream while writing updated fields and optional cover art, avoiding an unnecessary audio re-encode.
RELATED USES
- MP3 tag editor online
- edit FLAC metadata
- change album art
- M4A metadata editor
FIELD NOTES / 01
A real local processor, not a decorative upload box
music-metadata parser + FFmpeg stream copy runs after you choose a source and explicitly start the operation. The audio samples remain in browser memory; SoundTools does not send the selected media to an application endpoint.
Inspect the existing fields, change only the tags you intend to replace, optionally select JPEG, PNG, or WebP artwork, and save a new file rather than overwriting the source. Results remain available for preview and download only in the current tab. Closing or refreshing the page releases those temporary objects.
PROCESS / THREE STEPS
How to use audio metadata editor
- 01
Choose the local source
Open a compatible file in the dedicated workbench at the top of this page. The browser validates and decodes it without an upload step.
- 02
Set the useful controls
Inspect the existing fields, change only the tags you intend to replace, optionally select JPEG, PNG, or WebP artwork, and save a new file rather than overwriting the source.
- 03
Process, check, and export
Run the local processor, inspect the status and preview, then save Tagged source-format copy when the result is ready.
SIGNAL NOTES / VERIFIED BEHAVIOR
What this tool actually does
Clear limits are part of a useful tool. These values describe the processor currently running in this page.
Runtime and model assets may be downloaded, but the selected file is not attached to those requests.
The dedicated workbench exposes only formats it can actually produce in the current browser.
USE CASES / 02
Useful reasons to open audio metadata editor
- Library cleanup
Correct a title, artist, album, year, track number, or genre.
- Cover replacement
Embed an image into a supported local audio container.
- Private cataloging
Inspect tags without sending a music collection to a web API.
QUESTIONS / PRACTICAL ANSWERS
Questions about this tool
Answers based on the current browser processor—not promises about a future version.
01Is my audio uploaded for processing?
No. Audio samples stay in browser memory. The page may download a codec or model asset, but it does not send the selected file with that request.
02Why can the first run take longer?
This tool uses music-metadata parser + FFmpeg stream copy. A browser may need to download and initialize that runtime before the first operation; later runs can reuse cached assets.
03Can I preview the result before saving?
Yes. Audio-producing tools expose local result players, while analysis and transcription tools show their detected data before download.
04What happens when the browser is unsupported?
The workbench reports the missing capability instead of uploading the media or pretending that processing is still running.
05Do I need an account or install?
No. The tool opens directly in a compatible browser, requires no SoundTools account, and creates its temporary working state on the current device.
06Does editing tags reduce audio quality?
The save command copies the audio stream instead of re-encoding it when the container accepts the requested metadata.
07Does this overwrite my original file?
No. The browser creates a separate download with “updated” in its filename.