All tools

FLAC Metadata Reader

Data

Read sample rate, channels, bit depth, total samples, and duration from a FLAC file's STREAMINFO block, plus Vorbis comment tags like artist, title, and album, without decoding any audio

Drop in a FLAC file and get its sample rate, channel count, bit depth, total sample count, and duration back immediately, read straight from the STREAMINFO metadata block that every valid FLAC file starts with. If the file also carries a VORBIS_COMMENT block, the tool pulls out the encoder vendor string plus common tags like artist, title, album, date, genre, and track number, along with the full raw tag list for anything less common. None of this touches the actual compressed audio frames, so it works even on a very large file and stays fast regardless of bit depth or channel count. Files with no VORBIS_COMMENT block simply come back without tag fields rather than erroring, since tags are optional in the format.

audioflacmetadataformatdurationvorbis-comment

How to use FLAC Metadata Reader

  • 1.Drop a .flac file (or click to browse) to read its sample rate, channels, bit depth, and duration from the STREAMINFO block.
  • 2.Check the artist, title, album, and other tag fields, pulled from the file's VORBIS_COMMENT block when present.
  • 3.Use the REST API or an SDK to batch-read metadata across a music library, e.g. to audit sample rates or find files missing tags.

Frequently asked questions

Does this decode or play the actual audio?
No, it only reads the STREAMINFO and VORBIS_COMMENT metadata blocks to report format info and tags; it never decodes or plays back any audio frames.
What happens if the file has no tags?
Stream info (sample rate, channels, bit depth, duration) is always returned. Tag fields like artist and title are simply omitted if the file has no VORBIS_COMMENT block, since tags are optional in the FLAC format.
Is my file uploaded to a server?
In the browser tool, no, the file is read and parsed entirely client-side using the File API. The REST API and SDKs do process the bytes you send them, same as any other API call.
Does it support Ogg FLAC (FLAC-in-Ogg)?
No, this tool expects the native FLAC container that starts with the "fLaC" marker, not FLAC audio wrapped in an Ogg container, which uses a different page structure.

Use via API, SDK, or MCP

cURL# Free: 1,000 req/day · Pro: 10,000 req/day
curl -X POST https://api.utilix.tech/v1/tools/flac-metadata-reader \
  -H "Authorization: Bearer utx_live_..." \
  -F "file=@track.flac"

Get an API key from your dashboard · Full API docs →

Related tools

WAV Audio InfoRead sample rate, channel count, bit depth, and duration directly from a WAV file's RIFF/fmt/data chunk headersDataID3 Tag ReaderRead title, artist, album, year, genre, comment, and track number directly from an MP3 file's ID3 tagsDataImage InfoRead format, dimensions, bit depth, and alpha channel from image file bytes: no decoding requiredImage