Convert FLAC to OPUS

Converting FLAC to OPUS makes a small mirror of a lossless collection for a phone or a metered connection — around a tenth of the size at the Balanced band, with the tags carried straight across. Opus is the most efficient codec offered here, which is why it is the right answer when bytes per listening hour is the constraint.

  • Where it runs In your browser. The file is never uploaded.
  • Lossy Some detail is traded for size. OPUS cannot hold everything a FLAC can.
  • File size limit Up to 100 MB per file, free, without an account.

Up to 100 files at once. Mixed formats are fine.

A tenth of the size, and the arithmetic behind that claim

FLAC compresses losslessly to roughly half of raw PCM, which works out at about 5 to 6 MB a minute for CD-quality stereo — the exact figure depends on how dense the music is, not on any setting. Opus at the Balanced band writes 64 kbps, which is about 0.5 MB a minute regardless of material.

So a four-minute track goes from around 22 MB to under 2 MB, and a 500 GB collection lands near 50 GB. That is the number that decides whether a library fits on a phone, and it is roughly half what the same collection would occupy as MP3 at a comparable listening quality. Nothing else on this site produces that ratio from a lossless source without an audible penalty.

Why the phone copy should be Opus rather than MP3

MP3 was standardised in 1993 and Opus in 2012, and nineteen years of research sits between them. The gap is not uniform: at 256 kbps the two are hard to separate, and at 64 kbps MP3 is unpleasant while Opus is comfortable. A phone copy lives at exactly the bitrates where the difference is largest, which is why this pairing is worth the trouble.

The practical translation is that Opus at 64 kbps holds its own against MP3 at 128, and Opus at 128 against MP3 at 192 or 256. Halving a library's size for the same experience is not a marginal gain when the library is the reason a phone is full. The cost is compatibility, and that is the next section rather than a footnote.

The devices that will not play an Opus file

The registry marks Opus with patchy support, and it earns that. Android has decoded it natively for years, every current browser reads it, VLC and foobar2000 read it, and the self-hosted music clients — Symfonium, Substreamer, Finamp, the Jellyfin and Plex apps — all handle it because they bundle their own decoders. That covers most of the reason anyone converts a library.

What does not: car head units, older iPods and portable players, a good deal of hi-fi and network streamer firmware, and the built-in file preview on iOS in some situations. If the destination is a dashboard or a bedside streamer, this is the wrong conversion and MP3 or AAC is the pragmatic answer. Convert one album, put it on the actual device, and listen before converting two thousand.

Choosing between 38, 64 and 128 kbps for your own collection

The three bands resolve inside the encoder rather than being set here: Small file writes 38 kbps, Balanced 64 and High quality 128. Those numbers look alarming to anyone raised on MP3 and should not. Streaming services send around 64 kbps Opus on their low-data settings, and most listeners never notice on a commute.

The sensible rule is to match the band to where the copy will be heard. Podcasts, audiobooks and spoken word: Small file, and the saving is enormous. Music on a phone through earbuds or in a car: Balanced. Music on good headphones, or a copy you might transcode again for something else: High quality. The FLAC is still at home, so a wrong choice costs a re-run rather than a recording.

Everything is resampled to 48 kHz, including your CD rips

Opus works on a fixed 48,000 Hz clock. A decoder reports 48 kHz whatever the encoder was given, so a 44,100 Hz CD rip presents as a 48 kHz file after conversion and a 96 kHz high-resolution FLAC is brought down to the same place. This is a property of the codec rather than a setting, and there is no version of this conversion that avoids it.

For listening it is a non-issue — the resampling is done properly and no one has ever identified it by ear. It matters in exactly two situations: a cataloguing tool that records the technical sample rate from the file will disagree with the master, and anyone converting high-resolution material should understand that the extra bandwidth they paid for is discarded here, as it is by every lossy codec.

Album seams, and what a re-encode does to a continuous record

A live album, a DJ mix or a classical record with attacca movements is one continuous performance cut into tracks. FLAC reproduces the joins exactly because it reproduces the samples exactly. Any lossy encoder works in fixed blocks and has to pad the ends of each track to fill the final one, which is where audible seams come from.

Opus handles this better than MP3 does — the Ogg container records a pre-skip value that tells a decoder how much of the start to discard, and players that honour it rejoin the tracks cleanly. Whether your player honours it is the variable. If a gapless album matters, test that album specifically before converting the rest, and keep the FLAC either way so a bad result costs nothing.

Vorbis comments at both ends, so the library keeps its shape

A converted collection is worthless if the metadata scatters, and this is the one crossing on this site where nothing has to be rebuilt. FLAC tags are Vorbis comments; Ogg carries Vorbis comments; the fields are the same uppercase keys with the same text. Album artist, track and disc numbers, date, genre, composer, replay-gain values and anything custom all arrive as they were.

Cover art crosses as a METADATA_BLOCK_PICTURE comment, which is the standard encoding and what music servers, foobar2000, VLC and the mobile clients read. The practical consequence is that a converted library scans into a music server with its albums intact rather than as two thousand unknown tracks, which is the failure mode that makes people abandon this exercise halfway.

The FLAC collection is the library; this is a cache

Treat the Opus files as disposable. They can be regenerated from the masters in an evening, at a different bitrate if the first choice was wrong, or into a different codec entirely when the next phone or the next car refuses them. The FLACs cannot be regenerated from anything.

The failure this warns against is specific and common: someone converts a collection, sees that it sounds fine, and reclaims the disk. A year later a device needs AAC, or a better encoder arrives, and every re-encode now starts from a lossy source. Keeping the masters costs a drive that is cheaper than the collection was to assemble.

No encoder to download, and no album leaves the tab

Opus is the only audio target on this site that fetches nothing. Every browser implemented it for calls, so the encoder is already present, and your machine already decodes FLAC — the conversion starts the instant a file lands and contacts no server at any point. You can watch the network tab during a batch and see nothing move.

Files are capped at 100 MB each, which is around twenty minutes of CD-quality FLAC, and a hundred can be dropped together and taken back as a ZIP. For a collection that means working album by album rather than in one pass, which is also the sensible way to do it: convert one, put it on the device, confirm it plays, then work through the rest.

How to convert a FLAC collection into OPUS files

  1. Convert one album first and play it on the actual phone, car or streamer.
  2. If it plays, drop the rest of the FLACs here and pick a band — Balanced writes 64 kbps.
  3. Download the OPUS files, or take each album back together as a ZIP.

FLAC against OPUS: an archive codec and a transmission codec

FLAC compared with OPUS
FLACOPUS
Full nameFree Lossless Audio CodecOpus Audio
File extension.flac.opus
Media typeaudio/flacaudio/opus
CompressionLossless — nothing is discardedLossy — file size is bought with quality
First published20012012
Published byXiph.OrgXiph.Org
SpecificationRFC 9639RFC 6716
LicensingOpen standardOpen standard
Standing todayCurrentCurrent
Bit depth32
Audio channelsup to 8up to 255
Opens in a browserEvery browserCurrent browsers
Considered insteadWAV, AIFF, MP3AAC, MP3

Opening the result

Current browsers read OPUS; older ones do not. It is the less portable of the two, so it is worth being sure the program at the other end accepts it before sending one.

Audacity and VLC read both FLAC and OPUS, so there is a way to check the result against the original without a second tool.

File size and quality

The file gets substantially smaller, and it gets smaller by discarding detail. FLAC keeps everything; OPUS keeps what the eye is poor at noticing. On a photograph that trade is close to free; on text, a screenshot or a line drawing it is visible as haloing around the edges.

What each format is for

The two are aimed at different work: FLAC at archiving, OPUS at streaming and the web. That is worth weighing before converting, because the reason one exists is usually the reason the other is awkward.

FLAC is Xiph.Org's format, published in 2001. It records 32 bits per channel.

OPUS comes from Xiph.Org and dates from 2012, specified as RFC 6716. VLC, FFmpeg and Audacity all read it.

FLAC to OPUS: bitrates, devices and library size

What bitrate should I use for music from FLAC?

Balanced writes 64 kbps and High quality writes 128 kbps. For a phone in a noisy environment, over headphones on a commute, 64 kbps Opus is genuinely fine and is roughly what a streaming service sends on its low setting. For critical listening on good headphones, or for anything you might re-encode later, take 128 kbps — it is still a third of the size of the MP3 you would otherwise carry.

Is Opus better than MP3 at the same file size?

Substantially, and the gap is widest exactly where it matters here. Opus was standardised in 2012 as RFC 6716, nineteen years after MP3, and it holds up at bitrates where MP3 falls apart. A 64 kbps Opus file is comparable to an MP3 at roughly twice the bitrate, so a collection converted to Opus is about half the size of the same collection as MP3 for the same listening experience.

Will my phone and my car play .opus files?

Android has played Opus natively for years and every current desktop and mobile browser decodes it. Car head units, older iPods and many hi-fi streamers do not. iOS plays Opus in apps that bundle their own decoder — including most self-hosted music clients — but not always through the built-in Files preview. Test one file on the actual device before converting a library.

How much space does a whole library save?

FLAC runs about 5 to 6 MB a minute for CD-quality stereo. Opus at 64 kbps is about 0.5 MB a minute, so the collection lands near a tenth of its size; at 128 kbps, near a fifth. A 500 GB FLAC library becomes roughly 50 GB at Balanced, which is the difference between a library that fits on a phone and one that does not.

Do album tags and cover art survive?

Yes, and this crossing is unusually clean. FLAC stores its tags as Vorbis comments and Ogg carries the same structure, so title, artist, album artist, track and disc numbers, date, genre and any custom field arrive spelled as they were. Cover art travels as a METADATA_BLOCK_PICTURE comment, which is what music servers and players read.

Does my collection get uploaded?

No. Opus is the one audio target that needs no encoder download at all, because every browser had to implement it for calls, and your machine already decodes FLAC. The conversion runs entirely in the tab. Files are capped at 100 MB each — around twenty minutes of CD-quality FLAC — and a hundred can be dropped at once and taken as a ZIP.

More about these formats