RedpandaCompress Blog

Free Video Compression for Everyone.

Page 3 of 17

Which Audio Format Should You Use? MP3, AAC, WAV, FLAC and Opus Compared

Every audio tool eventually asks you the same question: which format do you want? MP3, AAC, WAV, FLAC, OGG, Opus, M4A, WMA. Most guides answer it with a wall of specifications that leaves you no better off than before.

The honest answer is that there are only three questions that matter, and once you have answered them the format picks itself. This guide walks through those three questions, then gives you the numbers and a straight recommendation for each common situation.

The one distinction that explains everything else

Audio formats split into two families, and almost every practical difference follows from which family a format belongs to.

Lossless formats keep every sample the recorder captured. WAV and AIFF store them raw; FLAC and ALAC compress them the way a ZIP file compresses a document — smaller, but you get back exactly what went in. Decode a FLAC and you have the original bit for bit.

Lossy formats — MP3, AAC, Opus, Vorbis, WMA — throw information away permanently. They use a model of human hearing to discard what you are unlikely to notice: sounds masked by louder sounds, frequencies past the edge of your hearing. The result is dramatically smaller, and for listening it is usually indistinguishable. But the discarded data is gone, and no later conversion brings it back.

This is why “convert my MP3 to FLAC to improve the quality” does not work. You get a large file that faithfully preserves the damage the MP3 already did.

The formats, briefly and honestly

  • MP3 — the oldest lossy format still in wide use, and technically the weakest. It survives because it plays on absolutely everything: car stereos, gym equipment, DJ gear, cheap MP3 players, every phone and computer ever made. Compatibility is its entire argument, and it is a very strong argument.
  • AAC (usually in an .m4a file) — the successor to MP3 and meaningfully better at the same bitrate, especially below 128 kbps. It is what Apple Music, YouTube and iPhone recordings use. Support is excellent nearly everywhere, with older or cheaper hardware the exception.
  • WAV — raw, uncompressed, universally readable, and enormous. The standard interchange format for editing and mastering.
  • AIFF — Apple’s equivalent of WAV. Same idea, same size, slightly less universal.
  • FLAC — lossless compression at roughly half the size of WAV. The right choice for archiving. Its weakness is playback support: it works in most modern players but not reliably in car systems or older devices.
  • ALAC — Apple’s lossless format. Essentially FLAC’s equivalent, preferred inside the Apple ecosystem.
  • Opus — the best-sounding lossy codec at low bitrates by a clear margin, and the reason voice chat sounds as good as it does. It is what Discord, WhatsApp voice notes and modern video calls run on. Its weakness is that it is a web and messaging codec: many editors and consumer devices still will not open a bare .opus file.
  • OGG Vorbis — an older open-source lossy format, largely superseded by Opus. You mostly meet it in game audio and older downloads.
  • WMA — a Microsoft format from the Windows Media era. There is no reason to choose it today; you only encounter it in old libraries and need to convert away from it.

The numbers side by side

Sizes below are for five minutes of stereo audio at CD quality (44.1 kHz, 16-bit). They are arithmetic, not estimates: uncompressed stereo CD audio runs at 1,411 kbps, so five minutes is 1411 × 300 ÷ 8 ≈ 53,000 KB.

FormatTypeTypical bitrate5 min stereoPlays on
WAV / AIFFUncompressed1,411 kbps~53 MBEverything
FLAC / ALACLossless~700–900 kbps~28 MBMost modern players
MP3 (320)Lossy320 kbps12 MBEverything
MP3 (192)Lossy192 kbps7.2 MBEverything
MP3 (128)Lossy128 kbps4.8 MBEverything
AAC (128)Lossy128 kbps4.8 MBNearly everything
Opus (96)Lossy96 kbps3.6 MBBrowsers, apps
Opus (64)Lossy64 kbps2.4 MBBrowsers, apps

The important comparison in that table is not top to bottom, it is AAC 128 against MP3 128. Identical size, audibly different result — the newer codec simply spends its bits better. Wherever compatibility allows it, AAC beats MP3 at the same size, and Opus beats both.

So which one should you use?

Your situationUseWhy
Sharing music or a podcast with anyone, anywhereMP3, 192–256 kbpsNothing on earth fails to play it, and the quality is beyond most listening conditions
Spoken word — lectures, interviews, meetingsMP3, 96–128 kbps monoSpeech needs a fraction of music’s bitrate; stereo buys you nothing
Archiving a master recordingFLACLossless, but half the size of WAV
Handing audio to an editor or studioWAVThe universal interchange format; no decode step, no ambiguity
Audio for a website or app you controlOpus, or AAC as a fallbackSmallest files at listenable quality; browsers all support it
Inside the Apple ecosystemAAC/M4A, or ALAC for losslessNative everywhere Apple made it
You have WMA, OGG or bare AAC filesConvert to MP3These are legacy or niche; MP3 ends the compatibility problem permanently

If you want the single-sentence version: MP3 when the file is going to other people, FLAC when it is going into storage, WAV when it is going into an editor. That covers the large majority of real decisions.

Bitrate matters more than format

People agonise over MP3 versus AAC and then export at whatever the default happens to be. Bitrate is the bigger lever. A 320 kbps MP3 sounds better than a 96 kbps AAC, despite AAC being the superior codec, because it was given three times the data to work with.

Useful anchors for MP3:

  • 320 kbps — transparent for practical purposes. Use when storage is irrelevant.
  • 192–256 kbps — the sweet spot for music. Most listeners cannot reliably distinguish 256 from the original on normal equipment.
  • 128 kbps — fine for casual listening, audibly thin on good headphones.
  • 96 kbps or below — acceptable for speech, poor for music.

Doubling the bitrate doubles the file. Going from 128 to 256 kbps is a real, hearable improvement on music; going from 256 to 320 is mostly insurance.

The mistake that actually costs you quality

Format choice is a small effect. Repeated lossy re-encoding is a large one.

Every time a lossy file is decoded and encoded again — MP3 to AAC, AAC back to MP3, or even MP3 to MP3 at a different bitrate — the new encoder discards data based on what it hears, and what it hears is already a lossy approximation. The damage compounds. This is generation loss, and it is the one audio mistake that is genuinely irreversible.

Worked example. You record a 40-minute interview. The recorder gives you a 400 MB WAV. Two sensible paths:

  1. Keep the WAV as your master (or convert it once to FLAC, roughly 200 MB, to halve the storage without losing anything).
  2. Export a 128 kbps mono MP3 for distribution — 40 × 60 × 128 ÷ 8 ÷ 1024 ≈ 37 MB. Small enough to email, and speech at 128 kbps mono is comfortably clear.

What you should not do is edit the 37 MB MP3, export it as MP3 again, then send that to someone who converts it once more. Every export from your lossless master is a first-generation copy; every export from an MP3 is another step down. Keep the master, generate distribution copies from it, and never chain conversions.

Converting between formats without uploading anything

Audio files are frequently the most private things people convert — voice memos, therapy notes, interviews with sources, confidential meetings, unreleased music. Most online converters upload all of it to a server and process it there.

Our audio converter runs the encoder inside your browser tab with WebAssembly, so the recording never leaves your device. There is no upload step and no queue — conversion starts the moment you pick the file. It reads MP3, M4A, AAC, WAV, FLAC, OGG, Opus and WMA, plus the audio track of any common video file.

Direct converters for the most common jobs: WAV to MP3, M4A to MP3, FLAC to MP3, WMA to MP3, Opus to MP3 and MP3 to WAV. If you only need the audio out of a video, use video to MP3.

Frequently asked questions

Does converting MP3 to FLAC improve the quality?

No. FLAC will perfectly preserve whatever it is given, but the data the MP3 encoder discarded is permanently gone. You end up with a file several times larger that sounds exactly like the MP3. Convert to FLAC only when your source is lossless to begin with.

Can people actually hear the difference between MP3 and lossless?

At 256–320 kbps, in blind tests and on ordinary equipment, most listeners cannot reliably tell. It becomes easier on studio monitors or good headphones, with certain material — cymbals, applause, reverb tails. The practical reason to keep lossless is not daily listening, it is that a lossless master survives future editing and re-encoding without compounding damage.

What is the difference between M4A and AAC?

M4A is a container; AAC is the codec inside it. Almost every .m4a holds AAC audio (Apple Lossless is the exception). A bare .aac file is the same audio without the container, which is why .m4a is better behaved — the container carries duration, chapters and artwork.

Which format is best for a podcast?

Record and edit in WAV, publish as MP3. Most podcast hosts require or strongly prefer MP3, and it is the only format guaranteed to work across every podcast app and car system. 96–128 kbps mono for pure speech, 128–192 kbps if you have music beds.

The short version

Decide lossy or lossless first — that follows from whether the file is for listening or for keeping. Then let compatibility break the tie: MP3 for anything going to other people, FLAC for archives, WAV for editors, AAC or Opus when you control the playback. Pick a sensible bitrate, keep your lossless master, and never convert a lossy file into another lossy file.

Need to change a file’s format right now? The RedPandaCompress audio converter is free, has no signup or watermark, and runs entirely in your browser — nothing is uploaded. For a closer look at the lossless-versus-lossy trade-off, see WAV vs MP3, and if you are curious how in-browser conversion works at all, we took the pipeline apart here.

How to Convert WebM to MP4 — And Why This One Can’t Be Lossless

You stopped a browser screen recording, hit save, and got a .webm file. It plays perfectly in Chrome. Then you drag it into Premiere and nothing happens. You AirDrop it to your phone and iOS refuses to save it. You attach it to a Slack message and it uploads as a dead grey rectangle with no preview.

WebM is not a broken format — it is a format built for one job (streaming video inside a browser) that is now being asked to do a different job (moving between apps, devices and people). This guide covers where WebM files come from, why they get rejected, and the one thing about WebM-to-MP4 conversion that almost every other guide leaves out: unlike MOV or MKV, this conversion can never be a lossless rewrap.

Where your WebM file came from

WebM shows up in a handful of predictable places, and knowing which one you are dealing with tells you what to expect:

  • Browser-based screen recorders. Anything that records a tab, a window or your camera from inside a web page uses the browser’s MediaRecorder API. On Chrome, Edge and Firefox that API writes WebM. (Safari writes MP4 — which is why the same tool can hand different people different formats.)
  • Downloaded web video. Video pulled from streaming sites with browser extensions or command-line downloaders very often arrives as WebM, because that is the format the site was serving.
  • OBS and other capture tools configured with a WebM output profile, usually chosen for the smaller files.
  • Exports from web apps that render video in the browser — design tools, animation tools, meeting recorders.

In every one of these cases the file was produced to be played back in a browser. Nothing about it was chosen for compatibility with the rest of your computer.

Why WebM won’t open in your editor or on your phone

A video file is a container holding a video stream and an audio stream. WebM is deliberately restrictive about what it can hold — that was the whole point of the format, which was designed around royalty-free codecs. The result is a set of streams that a lot of software has simply never been built to decode.

 WebMMP4 (H.264/AAC)
Video codecVP8, VP9 or AV1H.264
Audio codecOpus or VorbisAAC
Premiere / Final Cut / ResolveNot imported nativelyImported everywhere
Save to iOS PhotosNoYes
Smart TVs, older Android, set-top boxesUnreliableReliable
Preview in chat and email appsUsually notUsually yes
Playback in a browser tabYesYes

Notice the last two rows together — that is the trap. Modern Safari will happily play a WebM in a tab, so the file looks fine when you double-click it. The problems only start once the file has to leave the browser and be understood by an editor, a phone’s photo library or a TV.

The part most guides skip: this conversion always re-encodes

Converting between video containers is often nearly free. A MOV from an iPhone, an MKV from a download, an AVI from an old camcorder — these frequently already contain H.264 video inside them. In that case a converter can simply lift the existing streams out of one container and drop them into an MP4 without touching a single pixel. No quality loss, no waiting: a multi-gigabyte file finishes in seconds. That operation is called remuxing, and it is why our MOV to MP4 and AVI to MP4 converters are sometimes startlingly fast.

WebM cannot do this, and the reason is structural. WebM is not allowed to contain H.264 — the format’s entire design excludes it. So a WebM file always contains VP8, VP9 or AV1, and none of those is what you need on the other side. Every genuine WebM-to-MP4 conversion therefore has to fully decode the video and encode it again as H.264.

SourceTypical contentsWhat conversion does
MOV (iPhone, GoPro)Often H.264 alreadyRemux — lossless, seconds
MKV (downloads)Often H.264 alreadyRemux — lossless, seconds
AVI (old camcorders)DV, MJPEG, DivXRe-encode
WebMAlways VP8/VP9/AV1Always re-encode

The practical consequence: this is a generation of quality loss, and you only want to take it once. Convert from your original recording, not from a copy someone already converted and sent back to you. And do not convert to MP4, edit, export, and then convert again — get to MP4 first and stay there.

Expect the file to get bigger, not smaller

This surprises people, so it is worth stating plainly: converting WebM to MP4 usually produces a larger file. VP9 is a newer codec than H.264 and roughly 30–50% more efficient, meaning it reaches the same visual quality with fewer bits. Going back to H.264 means spending those bits again.

Worked example. A 12-minute 1080p browser screen recording encoded as VP9 at about 1.0 Mbps comes out around 90 MB (12 × 60 × 1.0 ÷ 8). To hold roughly the same perceived quality in H.264 you need somewhere near 1.5× the bitrate, so about 1.5 Mbps — which lands the MP4 at roughly 135 MB. Same picture, same length, half again the size, and now it opens in everything.

That is a fair trade when the goal is compatibility. If the goal is a smaller file — because you are emailing it or posting it somewhere with a size cap — convert first and then run the MP4 through a video compressor with an explicit target size, rather than hoping the conversion alone shrinks it.

The other WebM quirk: the file doesn’t know how long it is

If your WebM came from a browser screen recorder, there is a good chance it has no duration written into its header. This is a well-known consequence of how MediaRecorder works: it writes the file as a live stream, and a live stream has no idea when it will end, so the duration field is left unknown. Stopping the recording does not go back and fill it in.

We checked this rather than assuming it. Recording a short clip with the browser’s own MediaRecorder API and handing the resulting file to a standard HTML video element, the duration came back as NaN — the player could not say how long its own file was. That single missing number is behind a whole family of symptoms people blame on a corrupt file:

  • A seek bar stuck at 0:00, or showing an absurd length, while the video plays normally
  • Scrubbing that jumps to the wrong place or refuses to move
  • Upload forms rejecting the file for “invalid duration”
  • Editors that do import WebM placing a clip of the wrong length on the timeline

Converting to MP4 fixes this as a side effect, because the encoder writes a complete, finalised header with a real duration. If your recording plays but behaves strangely, the file is very likely fine — it is just missing its own metadata.

How to convert WebM to MP4 without uploading it

Most online converters work by uploading your file to a server, encoding it there, and letting you download the result. For a screen recording that is often exactly the wrong model — screen recordings routinely contain internal dashboards, customer data, email in a background tab, or a client’s unreleased work.

Our WebM to MP4 converter runs the encoder itself inside your browser tab using WebAssembly, so the video is never transmitted anywhere. There is no upload step, no queue, and no size-based pricing — files up to 8 GB on desktop and 2 GB on mobile.

  1. Open the WebM to MP4 converter and choose or drag in your file.
  2. Click Start Converting. The video is decoded from VP8/VP9 and re-encoded to H.264, with Opus or Vorbis audio converted to AAC.
  3. Download the MP4. It plays on Windows, macOS, iOS, Android, smart TVs, and imports into every mainstream editor.

Because the encoding happens on your own machine, conversion speed depends on your computer rather than on how busy a server is — and it starts instantly instead of waiting out an upload. If you want to confirm the no-upload claim for yourself rather than taking our word for it, we wrote up how to check whether a converter uploads your files, including the exact measurements from our own tool.

It is also worth knowing how niche the format remains on disk: in The State of Everyday Video, 2026, WebM accounts for well under 1% of the files people compress, while nine files in ten are MP4.

When you should keep the WebM

Converting is not automatically the right answer. If the video’s only destination is a web page you control — a background video, a product demo embedded on your site, an autoplaying hero clip — WebM is the better file. It is smaller at the same quality, every modern browser plays it, and smaller means faster page loads.

The rule of thumb: WebM for delivery inside a browser, MP4 for everything that leaves one. If the file is going into an editor, onto a phone, into a chat thread, or to another person, convert it.

Frequently asked questions

Does converting WebM to MP4 lose quality?

Technically yes, because the video must be re-encoded rather than rewrapped. In practice a single conversion at a sensible bitrate is very hard to see. What you should avoid is repeated round trips — converting, editing, exporting, converting again — since each pass compounds the loss. Convert once, from the original, and work in MP4 from then on.

Why is my converted MP4 larger than the WebM?

That is expected. VP9 compresses roughly 30–50% more efficiently than H.264, so matching the original’s quality in H.264 costs more bits. You are trading file size for the ability to open the file anywhere. If size matters, compress the MP4 afterwards to a specific target.

Can I just rename the .webm file to .mp4?

No, and this is the one format where the trick never works. Renaming changes the extension but not the contents, and MP4 players will find VP9 video they cannot decode. With some other formats a rename occasionally appears to work because the underlying stream happened to be compatible — with WebM it cannot be, by design.

Will this work for a long screen recording?

Yes. The converter handles files up to 8 GB on desktop browsers, which covers hour-long 1080p recordings comfortably. Since it re-encodes, expect the conversion to take a meaningful fraction of the recording’s length rather than finishing instantly, and leave the tab open while it runs.

The short version

WebM is a browser-native format that stops being convenient the moment your video needs to go somewhere else. Because it can only hold VP8, VP9 or AV1, the conversion to MP4 is always a real re-encode — so do it once, from your original, and expect the file to grow a little in exchange for playing everywhere.

Convert your WebM to MP4 free at RedPandaCompress — in your browser, with nothing uploaded. Working with other formats? The video converter handles MOV, MKV, AVI and WMV as well.

« Older posts Newer posts »