Initializing... drag & drop files here
Supports: AIF, AIFF
AIFF is Apple's uncompressed PCM format — perfect fidelity, roughly 10.6 MB a minute, and no compression of any kind. OGA is the Xiph.Org Ogg container carrying compressed audio, normally Vorbis. The short answer: convert to OGA when the file has to be small, royalty-free and playable on the open web or in a game engine, and keep the AIFF when it is a master you will edit again. The interesting decision on this page is not really AIFF versus OGA — it is which codec the Ogg container should carry, because .oga can hold four of them and they are not interchangeable.
| Property | AIFF | OGA (Ogg audio) |
|---|---|---|
| What it is | A container holding uncompressed linear PCM | A container holding a compressed audio bitstream |
| Origin | Apple; specification v1.3 dated January 1989 | Xiph.Org; the .oga extension was registered by RFC 5334 in September 2008 |
| Licensing | Open format, no licensing body | Royalty-free by design, with a BSD-style reference implementation |
| Default payload here | — | Vorbis |
| Data rate | 1,411 kbps at 44.1 kHz 16-bit stereo | Typically 96-256 kbps, or lossless if you choose FLAC |
| Size, 3 minutes stereo | ~31.8 MB | ~2.9 MB at 128 kbps |
| Metadata | NAME, AUTH, ANNO chunks, markers, loop points |
Vorbis comments — free-form FIELD=value tags with Unicode support |
| Streaming | Not designed for it | Built for it; Ogg pages are self-delimiting and seekable |
| Browser playback | Inconsistent | Chrome 4+, Firefox 3.5+, Edge 17+, Opera 10.5+; Safari gained full Ogg Vorbis support in 18.4 |
| Best for | Recording, editing, archiving | Web audio, game assets, podcasts, anything size-sensitive |
The Audio Codec dropdown on this page decides what actually goes inside the Ogg container. Vorbis is the default and the safe choice; the others are for specific jobs.
| Codec | Type | Standardised | Pick it when |
|---|---|---|---|
| Vorbis | Lossy | Xiph.Org; version 1.0 released in July 2002 | You want the widest compatibility for a .oga or .ogg file — every Ogg-capable player reads it |
| Opus | Lossy | IETF RFC 6716, September 2012 | You care about quality per bit, especially below 96 kbps, and the target is modern software |
| FLAC | Lossless | Xiph.Org, in Ogg encapsulation | You want an exact copy at roughly half the size — though a plain .flac file is more widely recognised |
| Speex | Lossy, speech-only | Xiph.Org, superseded by Opus | Only for legacy voice pipelines that were built around it; new work should use Opus |
.aif or .aiff files onto the page or click "+ Add Files". Several files can be queued under one set of settings..oga. No sign-up, no watermark.RFC 5334 draws the line clearly: .ogg is reserved for Ogg files that contain nothing but a Vorbis bitstream, while .oga is the general extension for Ogg audio of any kind. Both are served as audio/ogg. In practice a Vorbis file works under either name, so if a player or upload form only recognises .ogg, renaming a Vorbis .oga is legitimate — but do not rename an Opus or FLAC Ogg that way, because tools that assume .ogg means Vorbis may reject it.
With Vorbis, Opus or Speex, yes — they are lossy codecs and the discarded detail cannot be recovered by converting back. At 160-192 kbps Vorbis the difference is very hard to hear on music. If you need the samples intact, choose FLAC in the Audio Codec dropdown: it compresses losslessly, typically to about half the AIFF's size, with the audio bit-identical when decoded.
At the page's 128 kbps default the arithmetic is direct: 128,000 ÷ 8 = 16,000 bytes per second, so three minutes is about 2.9 MB against roughly 31.8 MB for the same audio as 44.1 kHz 16-bit stereo AIFF — about an eleven-fold reduction. Variable bitrate moves that figure up or down a little depending on the material, since it spends more bits on dense passages.
Opus generally wins on quality per bit, particularly below about 96 kbps, and it handles speech and music equally well — it is the newer design and was standardised by the IETF in 2012. The catch is recognition: Ogg Opus is normally distributed as .opus, and some older Ogg tools expect Vorbis when they see an Ogg audio file. Choose Opus when you control the playback software, Vorbis when you do not.
With Vorbis and FLAC, yes — leave Audio Sample Rate on ORIGINAL and the rate carries through. Opus is different by design: it always runs its internal machinery at 48 kHz and records the original rate in its header, so a 44.1 kHz source is resampled during encoding. That is normal Opus behaviour, not a fault in the conversion.
Text metadata can map onto Vorbis comments, the free-form FIELD=value tag block that Ogg files use, so a title or author has somewhere to go. AIFF-specific structures do not: markers, instrument chunks and loop points have no representation in Ogg and are dropped. Keep the AIFF if you rely on them.
.oga straight into a web page?Yes, with one caveat. <audio src="track.oga"> works in Chrome, Firefox, Edge and Opera and has for many years, and Safari reached full Ogg Vorbis support in version 18.4 — but visitors on older Safari and iOS releases will get silence. The usual fix is to offer a second <source> in MP3 or AAC alongside the Ogg one.
Ogg stores timing as granule positions inside self-delimiting pages rather than in a fixed index at the front of the file, which is what makes it good for streaming. Some players estimate duration from the last page they can find, so a file that has been truncated or partially downloaded may report an odd length. Re-encoding a complete source, as this page does, produces a clean granule sequence.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.
If your target actually expects the Vorbis-only extension, AIFF to OGG writes the same audio under .ogg; for a standalone Opus file, use AIFF to Opus.