Convert OGG to AIFF

Converting OGG to AIFF produces the uncompressed file a repository or funder asked for, at roughly ten times the size and with exactly the audio the Ogg already held. Read the metadata section before converting a collection: the Vorbis comments describing who is speaking do not survive the crossing.

  • Where it runs In your browser. The file is never uploaded.
  • Lossy Some detail is traded for size. AIFF cannot hold everything an OGG can.
  • File size limit Up to 100 MB per file, free, without an account.
  • Worth knowing The file becomes much larger without becoming better. AIFF stores every sample it is given, but what the original compression discarded is already gone.

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

Uncompressed is not the same word as preserved

It is worth saying at the top, because the whole vocabulary of archival practice pushes the other way. Vorbis and Opus discard parts of a recording permanently, according to a model of what a listener will not miss. AIFF then stores every sample it is handed, uncompressed, exactly as handed over. The result is a large file containing precisely what the Ogg contained.

That satisfies a specification written around file formats. It does not protect the recording, improve it, or recover anything the original encoder removed. Where the specification is a proxy for "give us something we can still open in forty years", it is doing useful work; where it is read as "give us the best copy", the best copy is whatever the recorder originally wrote, and converting cannot manufacture one.

Every Vorbis comment ends at the boundary

An AIFF is a sequence of chunks and the file produced here holds exactly two. COMM states the channel count, the frame count, the bit depth and the sample rate. SSND holds the samples. There is no name chunk, no annotation chunk, no author chunk and no artwork.

Ogg, by contrast, carries an open list of Vorbis comments, and in oral history and language documentation those fields routinely hold the speaker, the interviewer, the place, the date, the language, the project code and the consent reference. All of it is dropped. Export the comments to a sidecar — a CSV or a per-file text document — before converting, and deposit the two together, because the AIFF cannot be asked afterwards what it contains.

Where FLAC is the better answer, and when to ignore that

If the repository accepts FLAC, deposit FLAC. It is lossless, roughly half the size of the same audio as AIFF, and it carries a proper tag block so the descriptive metadata stays inside the file rather than beside it. It also holds an MD5 of its own decoded audio, so a decoder can prove years later that nothing has rotted, which no AIFF can do.

Many archives have added it to their accepted lists for exactly those reasons. Where the specification still names AIFF or WAV outright, comply — an argument in a deposit form is not a good use of anyone's time, and a rejected submission is worse than an inefficient one. But it is worth one email to the collection manager before converting several hundred hours of interviews.

What the Ogg holds changes the honesty of the deposit

Ogg is a container and the registry lists Vorbis, Opus and FLAC for it. Recordings from older open-source tooling are Vorbis; anything from a recent recorder or converter may be Opus; an Ogg holding FLAC is already lossless. Size distinguishes them — one hour is roughly 57 MB for Vorbis at 128 kbps and several hundred for FLAC.

If the container holds FLAC, converting to AIFF is a lossless step in audio terms and still discards the tags, which makes it a poor trade unless the specification forces it. If it holds Vorbis or Opus, the deposit should record somewhere that the uncompressed file was derived from a lossy original, because a future researcher looking at a 600 MB AIFF will otherwise assume it is a master.

Sixteen bits, and the 24-bit deposit you may be expected to find

The PCM written here is signed 16-bit. From a lossless master that would be worth examining, since a 24-bit field recording carries depth that 16 bits cannot hold. From a Vorbis or Opus source it is not a decision at all — a lossy codec has no additional depth to preserve, and writing 24-bit output would produce a file half again as large with no more information in it.

Where a specification asks for 24-bit uncompressed audio, this converter cannot produce it, and the correct response is to go back to the original recordings rather than to pad a lossy file. If the field recorder wrote 24-bit WAV before anything was compressed to Ogg, those files are the deposit the specification was written for, and they are worth looking for before converting anything.

Sample rate is inherited, except from an Opus stream

Nothing here resamples. Whatever rate the decoder reports is the rate the AIFF gets, so a 44,100 Hz Vorbis recording produces a 44,100 Hz AIFF and a 48,000 Hz one produces 48,000. That is the correct behaviour for a deposit, since resampling is a decision with consequences and should be made deliberately.

Opus is the exception and it is not optional. The codec runs on a fixed 48,000 Hz clock and a decoder reports that rate regardless of what was recorded, so an Opus recording made at 44.1 or 32 kHz arrives as a 48 kHz AIFF. A catalogue that records the technical rate from the deposited file will therefore disagree with the field notes, and it is worth writing the original rate into the sidecar.

Ten megabytes a minute, and what a collection costs

Uncompressed 16-bit stereo at 44,100 Hz costs 176,400 bytes a second — about 10 MB a minute — whether the minute is speech or silence, because every sample is written out as a plain number. Mono halves it. A Vorbis recording at 128 kbps costs about 0.96 MB a minute, so the multiplier is roughly ten.

A one-hour interview goes from around 57 MB to about 600 MB, and a hundred hours of fieldwork from under 6 GB to nearly 60. That is the number to take to whoever is paying for the storage, and it is the strongest practical argument for asking whether FLAC would be accepted instead — the same lossless-in-form deposit at half the size.

Mono recordings stay mono, and should

A great deal of documentation audio is genuinely single-source: one lapel microphone, one handheld recorder on a table. Converting does not promote it to stereo, and it should not — two identical channels double the file for no information. The COMM chunk records the count faithfully, so a mono recording arrives as a mono AIFF.

Where two microphones were used and the channels carry different speakers, that separation is often the most useful technical property the recording has, because it makes a transcript attributable. Nothing here folds it down. What the AIFF cannot record is what the channels mean: COMM states how many there are and not which microphone was where, so that belongs in the sidecar with everything else.

Consented recordings converted without a third party touching them

This is not an incidental property for this reader. Interviews are conducted under consent forms that name the project and frequently prohibit disclosure to third parties, and passing a file through a conversion service that holds it for an hour is a disclosure whether or not anyone reads it.

Nothing here goes anywhere. Writing AIFF costs no dependency — the samples are muxed as a WAV and rewrapped by arithmetic — and the Ogg decoder is already on your machine, so no package is downloaded and no audio is transmitted. Files are capped at 100 MB each, which at 128 kbps is about an hour and three quarters of Vorbis, and a hundred can be dropped at once and returned as a ZIP.

How to turn an OGG recording into an AIFF file

  1. Ask whether the repository accepts FLAC — it is half the size and keeps the metadata.
  2. Export the Vorbis comments to a sidecar file, then drop the OGG recordings here.
  3. Download the AIFF files, or take a session of interviews back together as a ZIP.

OGG and AIFF for preservation: a compressed stream against raw samples

OGG compared with AIFF
OGGAIFF
Full nameOgg AudioAudio Interchange File Format
File extension.ogg, .oga.aiff, .aif
Media typeaudio/oggaudio/aiff
CompressionLossy — file size is bought with qualityUncompressed
First published20001988
Published byXiph.OrgApple
SpecificationRFC 3533
LicensingOpen standardPublished, not standardised
Standing todayCurrentCurrent
Bit depth32
Audio channelsup to 8
Opens in a browserCurrent browsersSome browsers
Considered insteadMP3, AAC, OPUSWAV, FLAC

What survives

document properties can cross over — both OGG and AIFF have somewhere to store it.

What the target format adds

AIFF is a working format and OGG is a finished one. What comes back is editable text and objects rather than a picture of a page, which is usually the reason for the conversion and also where its limits are.

Opening the result

Only some browsers read AIFF. 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.

AIFF is a container rather than a single format. What actually plays is the codec inside it — usually PCM — which is why two files with the same extension can behave differently on the same device.

Audacity reads both OGG and AIFF, so there is a way to check the result against the original without a second tool.

What each format is for

The two are aimed at different work: OGG at the web and handing a finished file over, AIFF at editing and archiving. That is worth weighing before converting, because the reason one exists is usually the reason the other is awkward.

OGG is Xiph.Org's format, published in 2000. The specification is RFC 3533, and it is worth reading if the file has to outlive the tool that wrote it.

AIFF comes from Apple and dates from 1988. Logic Pro, Audacity and Adobe Audition all read it.

OGG to AIFF: deposits, metadata and storage

Does converting to AIFF preserve the recording better?

No. AIFF stores every sample it is handed without compressing it, and those samples are whatever survived the Vorbis or Opus encoding. The result is about ten times larger and contains exactly the same audio. It satisfies a specification asking for uncompressed PCM; it does not improve or protect the recording in any way the original file did not already.

Will my speaker names and dates survive?

No. The AIFF written here holds a format chunk and a sound chunk and nothing else, so every Vorbis comment is dropped — speaker, place, date, language, collector, consent reference, everything. In this field that metadata is frequently the most valuable part of the file. Export it to a sidecar document before converting, and deposit the two together.

Would FLAC be a better deposit format?

Usually, where the repository allows it. FLAC is lossless, roughly half the size of AIFF, carries a proper tag block so the descriptive metadata stays inside the file, and holds an MD5 of its own audio so corruption announces itself. Many archives now accept it explicitly for those reasons. Convert to AIFF when the specification names it and not otherwise.

How much larger will the deposit be?

About ten times. Uncompressed 16-bit stereo at 44,100 Hz costs 176,400 bytes a second, or roughly 10 MB a minute; a Vorbis recording at 128 kbps costs about 0.96. A one-hour interview goes from around 57 MB to about 600 MB, and a mono recording halves both figures. Plan the storage before converting a collection.

What bit depth and sample rate do I get?

16-bit, at the rate the Ogg carried — 44,100 Hz stays 44,100 and 48,000 stays 48,000. Nothing resamples. The exception is an Ogg holding Opus, which always decodes at 48,000 Hz regardless of what it was recorded at, so those files will present at 48 kHz even if the field recorder was set lower.

Do the interviews leave my machine?

No, and for consented human-subject recordings that is the condition on which this can be done at all. The Ogg is decoded by your own device and the AIFF header assembled in the tab with arithmetic rather than a codec, so nothing is downloaded and nothing is transmitted. Files are capped at 100 MB each and a hundred can be dropped at once.

More about these formats