Media type / audio
audio/ogg
An Ogg container of audio, usually Vorbis or Opus.
Served inline: Browsers display this in the tab without granting it script access to the page. Safe to serve inline, provided the bytes really are what the header claims.
Browser behaviour
Renders inertly
Charset
no charset
Compression
Already compressed
Send it like this
Content-Type: audio/oggA binary payload has no character encoding. A charset parameter here is meaningless and occasionally confuses strict parsers.
Handling verdict
Browsers display this in the tab without granting it script access to the page. Safe to serve inline, provided the bytes really are what the header claims.
A binary payload has no character encoding. A charset parameter here is meaningless and occasionally confuses strict parsers.
The format compresses internally. Another transport encoding costs CPU on both ends and typically changes the size by less than a percent — sometimes upward.
Registered with IANA through a public review process, so the name is stable and every implementation can rely on it meaning the same thing.
Anatomy of the name
RFC 6838Top-level type
audio
Audio
Subtype
ogg
Registered in the standards tree.
Structured syntax
none
No suffix, so the payload format is defined entirely by the subtype itself.
Parameters
codecs
Defined for this type in addition to any charset rule above.
What trips people up
1 note- Opus in Ogg is the best-quality open option for speech and low bitrates; declare it as codecs=opus.
Response headers
Content-Type: audio/ogg
X-Content-Type-Options: nosniff
Content-Disposition: inlinenosniff stops the browser second-guessing the type you declared, which is what makes the rest of this reliable. Serving it inline is safe here because the browser renders it without granting it script access.
Server configuration
extension mappingnginx
types {
audio/ogg ogg oga opus spx;
}Apache
AddType audio/ogg .ogg .oga .opus .spxCaddy
@type path *.ogg *.oga *.opus *.spx
header @type Content-Type "audio/ogg"Extensions and other spellings
with signatureFile extensions
File signature
4F 67 67 53
Check these bytes rather than the client-supplied Content-Type when validating an upload. The header is a claim; the signature is evidence.