Add your file
Choose or drop a .flac file. You can paste the contents instead.
Choose a .flac file to see where its fLaC signature sits and every metadata block in order, with type, last-block flag, offset and length. The STREAMINFO panel shows block and frame sizes, sample rate, channels, bits per sample, total samples and an exact duration, also given as a fraction when the sample count does not divide evenly. Vorbis comments are listed in file order with duplicate fields kept as separate rows, and can be copied as FIELD=value lines or downloaded as a .txt file. Invalid UTF-8 bytes are shown as replacement characters (�). A comment in FIELD=value form with bad bytes is marked invalid UTF-8 in its status column; a comment with no = sign is marked only as malformed there, so its encoding problem shows through the replacement characters and in the findings list. Byte offsets of comment encoding errors appear only in the findings list, while the vendor string and picture descriptions show their offset right beside the value. Picture, seek table, cue sheet and application blocks are summarised, and ID3 tags attached before or after the FLAC data are pointed out.
or drop a file here
Choose or drop a .flac file. You can paste the contents instead.
The file is read and parsed in this browser — nothing is uploaded.
Look over what came back, then copy it, download it, or move on.
Want to know how files are handled? Read the privacy notice →
Choose the .flac file on this page and every Vorbis comment, such as ARTIST, ALBUM or TRACKNUMBER, is listed in the order it appears in the file. Repeated fields stay as separate rows, field names are shown as written and upper-cased, and the encoder's vendor string has its own panel.
Yes. Alongside the table, the comments appear as plain FIELD=value lines that you can copy or download as a UTF-8 .txt file named after your FLAC file. Both views cover exactly the same comments, in file order and with duplicates included.
No. The FLAC file is read by script inside your browser tab and its bytes are not sent to a server; reloading the page clears the result. Only the metadata blocks at the start are parsed, and the audio frames after them are skipped entirely.
Open this page in Safari, Chrome, Edge or Firefox and pick the file — nothing has to be installed on macOS or Windows 11. Beyond the common tags that system file properties tend to show, you also get the raw STREAMINFO values, picture blocks, seek tables and cue sheets.
That message means the fLaC signature was not found at the start, even after skipping any ID3v2 tags in front of it. The usual cause is a WAV, MP3 or M4A file renamed to .flac; renaming does not convert audio, so no stream fields are shown for it.
It means the file ran out of bytes before reaching a metadata block marked as the last one, which typically follows an incomplete download or a cut-off copy. The blocks read up to that point are still listed, and the finding describes byte layout only.
Usually the tag holds bytes that are not valid UTF-8, such as text saved in a legacy Windows code page. FLAC comments are UTF-8 by specification, so the viewer shows invalid bytes as � instead of guessing another encoding. Comments in FIELD=value form get an invalid UTF-8 status, and the exact byte offset is given in the findings list.
Files up to 256 MB (268,435,456 bytes) can be read; anything larger is refused before a single byte is examined. Inside a file, reading also stops at 4,096 metadata blocks, 5,000 Vorbis comments or 8 MiB of tag text, with a warning naming the limit.
No image is displayed: each PICTURE block is listed with its type code, MIME type, description, declared width and height, colour depth and image data size. The picture bytes are skipped while reading, so the cover cannot be previewed, extracted or saved with this tool.
No. The MD5 shown is the fingerprint the encoder wrote for the unencoded audio, and checking it would require decoding the audio, which this tool never does. An all-zero MD5 simply means the encoder did not set one; it is not a sign of damage.
The viewer only reads metadata bytes and never plays or decodes audio, but it gives no verdict on whether a FLAC file is safe, malware-free or properly licensed. Fields such as COPYRIGHT or LICENSE are self-declared text from the file and are shown exactly as written.
No. A file starting with OggS uses the Ogg container, and the tool stops with a clear message instead of misreading it as native FLAC. Only the container signature is checked, so the tool does not say whether the Ogg stream holds FLAC, Vorbis or Opus audio; native FLAC keeps its metadata blocks right after the fLaC signature.