Convert AAC to OGG — Free Online Tool
Convert AAC audio files to OGG Vorbis format directly in your browser — no upload required. This conversion transcodes AAC's proprietary lossy compression into the open-source Vorbis codec inside an OGG container, making your audio fully compatible with open-source platforms, Linux systems, and apps that reject patent-encumbered formats.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your AAC file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
AAC (Advanced Audio Coding) stores compressed audio using a proprietary codec developed by Fraunhofer and licensed under patents, which restricts its use in certain open-source environments. During this conversion, FFmpeg decodes the AAC bitstream back to raw PCM audio, then re-encodes it using the libvorbis encoder into an OGG container. Because both AAC and Vorbis are lossy formats, this is a lossy-to-lossy transcode — the audio is decompressed and re-compressed, which introduces a small additional generation of quality loss. The default quality setting of -q:a 4 targets roughly 128–160 kbps with Vorbis's variable bitrate engine, which is perceptually transparent for most listeners at typical AAC source quality levels. No video, subtitle, or chapter data is carried over, as AAC files contain only audio.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg program, the open-source multimedia processing engine that handles decoding the AAC input, transcoding through PCM, and re-encoding to Vorbis. The browser-based tool runs this same engine compiled to WebAssembly via FFmpeg.wasm. |
-i input.aac
|
Specifies the AAC input file. FFmpeg automatically detects whether it is a raw ADTS AAC stream or an AAC file wrapped in an MPEG-4 container and selects the appropriate demuxer to extract the audio for decoding. |
-c:a libvorbis
|
Sets the audio encoder to libvorbis, the reference implementation of the open-source Vorbis codec. This is what converts the decoded PCM audio into Vorbis-compressed data to be stored in the OGG container, replacing AAC's proprietary compression entirely. |
-q:a 4
|
Sets the Vorbis variable bitrate quality level to 4 on a 0–10 scale, targeting approximately 128–160 kbps output. This is a balanced default that matches the perceived quality of a typical 128 kbps AAC source without producing unnecessarily large files. |
output.ogg
|
Defines the output filename and tells FFmpeg to use the OGG container format, which is inferred from the .ogg file extension. The OGG container wraps the Vorbis audio stream along with any transferred metadata tags from the original AAC file. |
Common Use Cases
- Preparing audio files for use in open-source games or game engines like Godot, which natively support OGG Vorbis but not AAC
- Publishing podcast episodes or audio content to platforms that require patent-free formats, such as certain open-source podcast hosts
- Converting iTunes-purchased or Apple device recordings in AAC to OGG so they play on Linux desktops and media players like VLC or Rhythmbox without codec packs
- Supplying background music or sound effects for web projects using the HTML5 Audio API, where OGG Vorbis provides a royalty-free alternative to AAC for Firefox and other browsers
- Archiving AAC recordings from mobile devices into an open container format to avoid long-term dependence on proprietary codec licensing
- Converting AAC audio from video exports or screen recordings into OGG for use in open-source video editors like Kdenlive or OpenShot that prefer Vorbis-encoded OGG tracks
Frequently Asked Questions
Yes, there will be a small additional quality loss because this is a lossy-to-lossy transcode. The AAC file is first decoded back to raw audio, then re-encoded by the Vorbis encoder — meaning the audio goes through two rounds of lossy compression rather than one. In practice, at the default quality setting of -q:a 4, the degradation is subtle and often imperceptible, especially if the source AAC was encoded at 128 kbps or higher. However, if audio fidelity is critical, you should always convert from an uncompressed source like WAV or FLAC rather than re-encoding from AAC.
Vorbis uses a variable bitrate quality scale from 0 to 10, where -q:a 4 targets approximately 128–160 kbps. This is roughly comparable in perceived quality to a 128 kbps AAC file, though direct comparisons are imperfect because the two codecs use different psychoacoustic models. If your source AAC was encoded at a higher bitrate like 256 kbps, you may want to increase the Vorbis quality to -q:a 6 or -q:a 7 to better preserve the original fidelity, though the fundamental lossy-to-lossy ceiling still applies.
Replace the value after -q:a with a number between 0 and 10. For example, use -q:a 6 for higher quality output (roughly 192 kbps) or -q:a 2 for a smaller file at lower quality (roughly 80 kbps). The command would look like: ffmpeg -i input.aac -c:a libvorbis -q:a 6 output.ogg. Unlike AAC's -b:a parameter which sets a fixed bitrate, Vorbis's -q:a controls a quality target and the encoder adjusts bitrate dynamically across the file.
FFmpeg will attempt to copy standard metadata tags such as title, artist, album, and track number from the AAC file into OGG's Vorbis comment tag format automatically. However, some AAC files — particularly those from iTunes — may contain proprietary metadata fields or DRM-linked tags that do not have a direct equivalent in Vorbis comments and will be dropped. Core ID3-style tags typically transfer without issues.
Android devices and most Android media apps support OGG Vorbis natively. iPhones and Safari do not support OGG Vorbis playback, which is one reason AAC remains the dominant format in Apple ecosystems. In web browsers, Firefox and Chrome support OGG Vorbis via the HTML5 Audio API, but Safari does not. If cross-platform compatibility including Apple devices is a requirement, AAC is actually the better choice — OGG Vorbis is ideal for open-source, Linux, and Android-first environments.
The single-file command shown converts one file at a time, but you can batch process on your desktop using a shell loop. On Linux or macOS, run: for f in *.aac; do ffmpeg -i "$f" -c:a libvorbis -q:a 4 "${f%.aac}.ogg"; done. On Windows Command Prompt, use: for %f in (*.aac) do ffmpeg -i "%f" -c:a libvorbis -q:a 4 "%~nf.ogg". The browser-based tool processes files individually, so batch conversion of large collections is better handled locally with FFmpeg.
Technical Notes
AAC files typically use the .aac extension with a raw ADTS bitstream or are wrapped in an MPEG-4 container. FFmpeg handles both variants transparently as input. The output OGG container produced by this conversion uses the Vorbis codec (libvorbis), which is the most universally supported OGG audio codec — the OGG container also supports Opus and FLAC, but Vorbis is the default for broad compatibility. Vorbis is a fully open, patent-free codec maintained by Xiph.Org, which is the core reason to prefer it over AAC in open-source contexts. One notable limitation is that AAC supports multichannel audio (e.g., 5.1 surround), and while OGG Vorbis also supports multichannel audio, most AAC files encountered in practice are stereo or mono and convert cleanly. DRM-protected AAC files (such as older iTunes purchases with FairPlay DRM) cannot be decoded or converted by FFmpeg — only DRM-free AAC files are supported. The OGG format supports chapter markers and multiple audio tracks at the container level, but since AAC source files contain neither, these OGG features are irrelevant for this specific conversion path.