How to Clean FLAC Metadata — Technical Walkthrough

TL;DR: A FLAC file stores its tags in metadata blocks that sit between the four-byte fLaC marker and the first audio frame, as defined by RFC 9639. The tag data lives in a VORBIS_COMMENT block (block type 4) — title, artist, album, ENCODER string, ReplayGain values, freeform TXXX-style fields — and embedded cover art lives in a separate PICTURE block (block type 6). To remove all of it, open the FLAC in Metadata Cleaner and click Clean: the tool drops the VORBIS_COMMENT and PICTURE blocks, leaves the mandatory STREAMINFO block in place, and copies the audio frames through unchanged. The audio is bit-identical after. What a tag strip does not remove: an audio watermark encoded into the waveform, or an acoustic fingerprint derived from the sound itself.

You ran your master through a FLAC encoder, named the file something neutral, and figured the lossless track was anonymous. It wasn't. The encoder wrote its version string into a VORBIS_COMMENT field, your DAW stamped your username into another, and a four-megabyte cover image was sitting in a PICTURE block — riding along to every recipient.

What's Actually Inside a FLAC File?

A FLAC file is two things stitched together: a chain of metadata blocks at the front, and the encoded audio frames that follow. RFC 9639 — the IETF spec published in December 2024 — defines both.

The file opens with the four-byte ASCII marker fLaC (66 4C 61 43). The metadata block chain follows. Each block has a 4-byte header — one bit flagging whether it's the last block, seven bits identifying the block type, and twenty-four bits coding the body length in big-endian — followed by the body itself. The 24-bit length field caps each block at 16 MB.

RFC 9639 defines seven block types: STREAMINFO (0) is mandatory and must come first — it holds sample rate, channel count, bit depth, total sample count, and an MD5 of the unencoded audio; strip it and decoders refuse the file. PADDING (1) reserves empty space for tag growth. APPLICATION (2) holds vendor-defined data keyed by a 32-bit ID. SEEKTABLE (3) indexes into the audio for fast scrubbing. VORBIS_COMMENT (4) is the FLAC tags — the block we care about most. CUESHEET (5) holds cue-sheet data. PICTURE (6) is where cover art lives.

The VORBIS_COMMENT block is the one that carries identifying text. It's a Vorbis comment packet embedded inside FLAC — uniquely, its length fields are little-endian, while everything else in FLAC is big-endian. The block opens with a vendor string (commonly reference libFLAC 1.4.3 20230623 — the encoder fingerprint), then a count, then a list of UTF-8 KEY=value strings: TITLE, ARTIST, ALBUM, DATE, GENRE, TRACKNUMBER, COMMENT, ENCODER, the four REPLAYGAIN_* loudness values, and any vendor-specific key a DAW or store wants to write.

Photo by Benjamin Lehman on Pexels.

Embedded cover art has two homes. The preferred one is a PICTURE block carrying a 32-bit picture type, a MIME type, a description, width and height, color depth, and the raw image bytes. The older convention stuffs a base64-encoded picture into the VORBIS_COMMENT block under the key METADATA_BLOCK_PICTURE. Some tagging tools still write both. A clean strip has to handle both paths.

None of this is the audio. The metadata blocks sit beside the FLAC frames, not inside them — which is exactly why they can be removed without re-encoding a sample. For the same idea worked through MP3, our walkthrough on removing MP3 metadata online compares ID3 tags to FLAC's block-based design.

Why Would You Want to Clean FLAC Metadata?

A handful of reasons, depending on who's getting the file.

Privacy. FLAC tags are freeform UTF-8, and software writes into them without asking. A DAW stamps your username; a ripping tool writes the device or account; a store download leaves a purchase identifier in a custom key. A renamed file with a cleared ARTIST looks anonymous and isn't. The Electronic Frontier Foundation has spent years documenting how the metadata people forget about is the metadata that identifies them.

The encoder fingerprint. Every FLAC carries a vendor string at the top of the VORBIS_COMMENT block — reference libFLAC with a version and build date for files from the reference encoder, something distinctive for other tools. Two FLACs carrying the same vendor string and ENCODER field can be linked back to the same source rig — a quiet correlation signal that survives renaming the file and clearing the visible fields.

Cover art weight. A PICTURE block holding a high-res front cover easily runs 2–5 MB on a 30 MB track. Dropping it is a 10–15 percent file size win.

AI music exports. Tools in the AI-audio space write their identity into the comment block — a Suno or Udio export names the tool in ENCODER or a vendor-specific key. We covered the AI-music side in our post on why AI music gets reach-throttled.

Clean handoff. Sending the file to a mastering engineer, sync library, or label? Stripping the block hands them a blank slate instead of whatever your converter and DAW left behind.

How to Clean FLAC Metadata Online

The removal runs locally in your browser tab. Metadata Cleaner reads the file into memory, walks the metadata block chain, drops the blocks we want gone, and hands the result back. The FLAC never uploads to a server.

1. Open Metadata Cleaner in any browser. Desktop or mobile both work; no install, no account.
2. Drag the FLAC into the drop zone, or tap to pick it on a phone. The file loads into the tab's memory.
3. Click Clean. The worker reads the fLaC marker, walks each metadata block by its 4-byte header until the last-block flag, drops every VORBIS_COMMENT and PICTURE block, leaves the mandatory STREAMINFO block in place (along with any SEEKTABLE for fast scrubbing), and writes a new file. The audio frames are copied through byte-for-byte.
4. Click Download. The cleaned FLAC lands back in your downloads. If it had embedded cover art, expect it noticeably smaller; the PICTURE block is usually most of the tag bulk.

Photo by Tima Miroshnichenko on Pexels.

The audio is bit-identical after the clean. The STREAMINFO MD5 — the hash of the unencoded samples in the first block — matches the original, because the audio frames haven't changed. A 30 MB album track cleans in well under a second; a 24-bit/96 kHz session FLAC at a few hundred megabytes takes a couple of seconds.

One thing to flag: clearing fields inside a tag editor isn't the same as removing the block. Many editors blank an entry — overwriting ARTIST=My Name with ARTIST= — which leaves the block structure and the vendor string intact. A rewrite that drops the entire VORBIS_COMMENT and PICTURE blocks is what actually leaves you with the bare STREAMINFO and the audio.

How to Confirm the Tags Are Gone

Trusting a tool is fine; checking it is better. Three ways to confirm, in rising order of authority:

• Re-open it in Metadata Cleaner. Drop the cleaned FLAC back in. If the tool reports no comment fields and no embedded picture, the blocks are gone.
• metaflac --list. The reference metaflac tool ships with the FLAC reference encoder. metaflac --list cleaned.flac dumps every block in the chain. After a clean you should see exactly one STREAMINFO block (type 0) and nothing else aside from optional PADDING or SEEKTABLE blocks; no VORBIS_COMMENT, no PICTURE.
• ExifTool, or a hex check. Phil Harvey's exiftool -G1 -a cleaned.flac will list any remaining tags grouped by their source. For the truly thorough: the first four bytes of a FLAC are 66 4C 61 43 (fLaC); the very next byte's high bit is the last-block flag and the low seven bits are the block type. After a clean, that low seven bits should read 0 (STREAMINFO), and once you skip the 34-byte STREAMINFO body the next header should already have the last-block flag set — meaning STREAMINFO was the only block left before the audio frames.

What Stripping FLAC Metadata Doesn't Reach (Honest Limits)

Removing the comment block and the picture block is a real, verifiable change — but it's one layer, and it's worth being clear about what it doesn't touch. All three of these live in the audio samples themselves, not in the metadata, so dropping the blocks leaves them exactly where they were.

It doesn't remove an audio watermark. A watermark is encoded into the waveform — the audio samples FLAC compresses — either audibly or below the threshold of hearing. Dropping VORBIS_COMMENT and PICTURE blocks does nothing to it. Robust watermarks are engineered to survive metadata stripping and even lossy transcoding. We covered the full distinction in audio watermarks versus metadata.

It doesn't remove an acoustic fingerprint. Acoustic fingerprinting — AcoustID, Shazam-style recognition, platform Content ID — derives a signature from the audio itself. A fingerprint can identify a track that's been completely stripped of tags. Removing metadata blocks cannot change what the sound is, so it cannot change what the fingerprint computes.

It doesn't touch the STREAMINFO MD5. The MD5 stored inside STREAMINFO is a hash of the unencoded audio samples. After a clean strip, that hash stays the same. It's useful for integrity checks, and a thing to be aware of: the MD5 will match any other lossless copy of the same audio, including ones tagged with your name.

Photo by cottonbro studio on Pexels.

It doesn't touch records you don't hold. If a track was registered with a distributor, the DDEX flags and rights data live in the distributor's systems, not in your file. Same for any server-side record an AI tool kept when it generated the audio. Cleaning your copy does nothing to a database row on someone else's server.

Stripping VORBIS_COMMENT and PICTURE blocks reliably removes the title, artist, album, comments, cover art, ReplayGain values, and the encoder vendor string — which is what most people mean by "cleaning" a FLAC. A watermark in the waveform or a fingerprint to be matched is a separate problem.

FAQ

Does removing FLAC metadata change the audio quality?

No. The clean rewrites the metadata blocks only and copies the audio frames through unchanged. There's no re-encoding, and the STREAMINFO MD5 of the audio samples matches the original. FLAC is lossless, and a metadata strip preserves that exactly.

Will the FLAC still play after the strip?

Yes. A FLAC with only a STREAMINFO block is valid under RFC 9639. Every player, DAW, and decoder that handles FLAC opens it normally — it just shows empty tag fields and no cover art.

Does this remove embedded album art?

Yes. Cover art lives in PICTURE blocks, and the clean drops all of them. A base64 picture inside VORBIS_COMMENT under METADATA_BLOCK_PICTURE goes too.

Why does my music player still show tags after I "cleared" them in another tool?

Most editors blank entries inside the VORBIS_COMMENT block rather than remove the block itself, and some leave the encoder vendor string at the top untouched. A rewrite that drops the entire block is what leaves the file blank.

Can I clean FLAC metadata on my phone?

Yes. Metadata Cleaner runs in mobile Safari, Chrome on Android, and Firefox mobile. Drag-and-drop becomes tap-to-pick, and the cleaned file saves to Files or your Downloads.

Is removing FLAC metadata legal?

Yes. Vorbis comments are metadata in a file you own; no general law requires you to keep them. Narrow professional contexts — rights administration, mastering-house deliverable specs — may expect certain metadata to be preserved. Outside those, whether the tags travel is your call.

---

Got a FLAC carrying tags you'd rather not hand off — a DAW username, encoder fingerprint, cover art, AI-tool vendor string? Strip it before the file leaves your machine. Try Metadata Cleaner free — drop the track, hit Clean, download. The audio stays bit-identical; the paper trail doesn't have to come with it.