Clean audio metadata in your browser
Select Audio in the cleaner to inspect a WAV, MP3, native FLAC or supported M4A file of up to 50 MiB. Processing stays in your browser. The cleaner preserves the audio samples or encoded frames and checks the output again before offering a download.
AI provenance and ordinary descriptive tags appear separately. Ordinary titles, artists and comments stay unless you select private metadata removal. Selecting an AI finding removes its whole supported record, including any ordinary fields inside it.
What each format supports
| Format | Supported metadata | Preservation |
|---|---|---|
| WAV | RIFF C2PA and AIGC chunks, LIST/INFO entries, supported ID3 tags, BWF description and supported XML metadata | Selected chunks become empty padding; audio data and offsets stay unchanged |
| MP3 | Plain ID3v2.3/v2.4 descriptive frames, C2PA GEOB and recognized provenance private frames, ID3v1 tags | MPEG Layer III frames remain byte-identical |
| FLAC | Vorbis comments, vendor information, optional pictures and supported leading ID3 tags | STREAMINFO, seek information and encoded audio frames remain byte-identical |
| M4A | Recognized C2PA/XMP carriers and supported movie-level descriptive or keyed metadata, including AIGC, prompt, workflow and generator fields | Selected records are cleared in place; encoded AAC/ALAC audio and file offsets stay unchanged |
C2PA carriers and AIGC entries are metadata evidence. Their signatures are not validated by this cleaner. Unknown chunks, ID3 frames and FLAC application blocks remain unchanged; unsupported findings cannot be inferred absent.
Supported boundaries
Extended, unsynchronised, compressed, encrypted or flagged ID3 tags/frames are rejected. ID3v2.2, ID3v2.4 footers, RF64, segmented WAV, free-format MP3 and unsupported trailing MP3 tags are outside this workflow. This is native FLAC support, not Ogg FLAC. Raw AAC, OGG and Opus are not supported in the Audio tab.
M4A support requires an M4A major brand, audio-only AAC or ALAC tracks and self-contained media references. Encrypted audio entries, fragmented containers, external media references, other brands/codecs and mixed video/audio layouts are refused. Track-level or unsupported metadata locations can remain. A cleaned M4A may stay the same size because selected metadata space is replaced with cleared padding.
A browser may be unable to play a supported audio file. Preview support is separate from metadata processing. Open the download in a compatible player to check playback.
What cleaning does not establish
Metadata cleanup does not detect or remove SynthID or other watermarks embedded in the sound, establish human authorship or guarantee that a platform will stop showing an AI label. A file can contain AI-generated audio without any supported metadata findings.
Read the audio cleaning guide for the steps and a Gemini WAV example, or our metadata-cleaning test method for verification details.
Processing memory and cancellation
Supported M4A files are inspected through bounded file slices, skipping encoded audio payloads. Cleaning retains unchanged original ranges and verifies the metadata edits before download. M4A container metadata, including sample tables, is limited to 8 MiB and 10,000 root boxes; damaged or over-budget files are refused.
WAV and native FLAC now use bounded file slices too. WAV skips sample data and unknown chunk payloads; FLAC reads its leading tags and metadata blocks, then preserves the encoded audio through original file slices. MP3 checks every frame header using 64 KiB read windows, so it still scans the audio region but never buffers the whole file at once. Cleaning keeps unchanged original ranges and verifies the resulting metadata before download.
WAV/MP3/FLAC metadata is limited to 8 MiB in total. This includes loaded WAV format/LIST chunks and FLAC padding, pictures and application blocks. WAV and FLAC allow at most 100,000 chunks or blocks; supported leading ID3 tags are limited to 16. Damaged or over-budget files are refused without a partial result.
All audio formats retain the 50 MiB file limit. You can cancel audio processing and choose another file. Broader browser and mobile performance measurements are still pending.