RFC 9639: Free Lossless Audio Codec (FLAC)
In plain English — editorial summary, not part of the RFC
This document defines the Free Lossless Audio Codec (FLAC) format and its streamable subset. FLAC is designed to reduce the amount of computer storage space needed to store digital audio signals. It does this losslessly, i.e., it does so without losing information. FLAC is free in the sense that its specification is open and its reference implementation is open source. Compared to other lossless audio coding formats, FLAC is a format with low complexity and can be encoded and decoded with little computing resources. Decoding of FLAC has been implemented independently for many different platforms, and both encoding and decoding can be implemented without needing floating-point arithmetic.
Document record
- Document ID
- RFC9639
- Published
- December 2024
- Authors
- M.Q.C. van Beurden; A. Weaver
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 75
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8949Concise Binary Object Representation (CBOR)Current
December 2020
- RFC 7875Additional WebRTC Audio Codecs for InteroperabilityCurrent
May 2016
- RFC 6381The 'Codecs' and 'Profiles' Parameters for "Bucket" Media TypesCurrent
August 2011
- RFC 4281The Codecs Parameter for "Bucket" Media TypesObsoleted
December 2005
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8153Digital Preservation Considerations for the RFC SeriesCurrent
April 2017
- RFC 6849An Extension to the Session Description Protocol (SDP) and Real-time Transport Protocol (RTP) for Media LoopbackCurrent
February 2013
- RFC 6716Definition of the Opus Audio CodecUpdated
September 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?