Ogg Audio MIME Type

What does audio/ogg mean?

The audio/ogg media type identifies an Ogg container whose content is predominantly audio. Ogg supplies the framing, timestamps, stream boundaries, and error checks. A codec such as Vorbis, Opus, Speex, or FLAC supplies the actual audio compression.¹²

That distinction explains why “Ogg” and “Ogg Vorbis” are often treated as synonyms even though they are not. A traditional .ogg music file normally contains Vorbis. An Ogg file can instead carry another codec, and software must support both the container and the codec to play it.

The first four bytes of every Ogg page are 4F 67 67 53, the ASCII text OggS. That capture pattern identifies the container, not the codec inside it. Ogg pages also carry a stream serial number, sequence number, granule position, and CRC checksum. Together, those fields let a decoder separate interleaved logical streams, detect lost or damaged pages, and seek using codec-specific timing information.³

Which extensions belong to audio/ogg?

IANA currently registers four extensions for audio/ogg: .oga, .ogg, .spx, and .opus.¹ They communicate useful conventions:

For an Ogg Opus file, RFC 7845 recommends audio/ogg; codecs=opus and the .opus extension.⁴ A server can similarly declare audio/ogg; codecs=vorbis when it knows the codec. The plain audio/ogg value remains valid when the codec parameter is unnecessary or unavailable.

Use video/ogg when the presentation requires a visual interface. Use application/ogg for complex Ogg content that does not fit the audio or video categories. RFC 5334 recommends audio/ogg when audio predominates, even if the file also contains lyrics, metadata, or cover art.²

How was audio/ogg standardized?

Xiph.Org developed Ogg as a freely available, stream-oriented multimedia container. The container was documented as Ogg bitstream format version 0 in RFC 3533 in May 2003.³ Its design groups packets into independently recognizable pages and allows multiple logical bitstreams to be interleaved in one physical stream.

Early software often used application/ogg for every kind of Ogg content. RFC 5334 replaced that broad convention in September 2008 with the more descriptive audio/ogg and video/ogg media types, while retaining application/ogg for complex data.² RFC 7845 updated the registrations in April 2016 to describe Opus in Ogg and add .opus to audio/ogg.⁴

How to open an Ogg audio file

Current Chrome, Edge, Firefox, and Opera can play common Ogg audio in an HTML <audio> element. Safari added Ogg-container playback for Vorbis and Opus in Safari 18.4 on the corresponding Apple operating-system releases.⁵⁶ Older Safari versions still need another format.

Codec support matters as much as container support. A browser that plays Ogg Vorbis may not necessarily decode Ogg FLAC, Speex, or an unusual multiplexed stream. On the web, include the codec when known and provide a fallback source when older clients matter:

<audio controls>
  <source src="interview.ogg" type="audio/ogg; codecs=vorbis">
  <source src="interview.mp3" type="audio/mpeg">
</audio>

For desktop work, Audacity can export Ogg Vorbis and lets you select the encoding quality.⁷ FFmpeg can demux and mux the Ogg container and encode Vorbis or Opus when the corresponding encoders are available.⁸

Support in Poly

Poly recognizes .ogg filenames as audio/ogg. Its audio loader includes Ogg and Vorbis support, so a valid Ogg Vorbis file can enter the normal audio pipeline. Poly extracts duration and available tags, uses embedded artwork as a thumbnail when present, transcribes spoken audio, and creates audio-similarity data. The filename, transcript, and audio representation can then participate in search.

The file opens in Poly's audio player, including seeking to transcript matches. Browser playback remains codec-dependent. A current browser can normally play Vorbis or Opus in Ogg, but uncommon codecs can still fail even though the container is valid.

Poly's agent backend explicitly accepts audio/ogg as direct audio input. It can also read the stored transcript after transcription. Direct analysis and transcription are separate paths, so a missing transcript does not by itself mean that the agent cannot inspect a supported Ogg file.

Converting Ogg audio

Choose the output based on the next use:

• FLAC or WAV for a lossless decoded copy that will be edited again. This preserves the decoded samples, but it cannot recover information already discarded by Vorbis, Opus, or Speex.
• Opus in Ogg for compact speech or music delivery on modern software.
• MP3 or AAC in MP4 when compatibility with older players matters more than avoiding another lossy encode.

FFmpeg can identify the input before conversion:

ffprobe recording.ogg
ffmpeg -i recording.ogg -c:a flac recording.flac
ffmpeg -i recording.ogg -c:a libopus -b:a 96k recording.opus

Avoid converting one lossy codec directly to another unless you need a delivery copy. Decoding Vorbis and encoding MP3, AAC, or Opus introduces another lossy generation. Keep the original Ogg file or a lossless master.

Metadata and security

Ogg itself does not provide generic signing or encryption. RFC 5334 warns that the container can carry arbitrary binary content and that decoders must handle manipulated streams, extreme declared media properties, and malformed input safely.² Open untrusted files with maintained software.

Audio codecs in Ogg commonly carry user-supplied comment metadata. Titles, artist names, comments, lyrics, encoder details, and attached artwork may reveal information that is not obvious from listening. Review both the sound and its metadata before sharing a private recording.