Initializing... drag & drop files here
Supports: MP4, M4V
12.5) or HH:MM:SS.sss (00:01:30.500).MP4 is the universal video container — H.264 or H.265 video paired with AAC audio, used by phones, cameras, YouTube, and almost every streaming platform. OGA is the audio-only file extension for the Ogg container, a royalty-free format from Xiph.Org that wraps Vorbis, Opus, FLAC, or Speex. Pulling the audio track out of an MP4 and saving it as OGA drops the video weight (often 90%+ of the file) and produces a small, patent-free audio file that drops cleanly into open-source pipelines, Linux apps, and web games.
If you need universal device playback instead, see MP4 to MP3 or MP4 to M4A. For lossless audio extraction without re-encoding loss, MP4 to FLAC keeps the audio bit-exact after decoding.
| Property | MP4 | OGA (Ogg) |
|---|---|---|
| Container | ISO Base Media (MPEG-4 Part 14, 2003) | Ogg (Xiph.Org, 2003) |
| Carries | Video + audio + subtitles + chapters | Audio only |
| Typical inner audio codec | AAC (occasionally ALAC, AC-3, MP3) | Vorbis, Opus, FLAC, Speex |
| Compression | Lossy video + lossy audio | Lossy (Vorbis/Opus/Speex) or lossless (FLAC) |
| Patent / license | AAC and H.264/H.265 are patent-encumbered | Royalty-free |
| Apple device playback | Native (iPhone, iPad, Mac, Apple TV) | Not native on iOS/macOS |
| Linux / open-source playback | Works with codec packs | Native and preferred |
| Browser playback | All major browsers | Firefox, Chrome, Edge (not Safari) |
| Game engine support | Limited (video-oriented) | Native in Unity, Godot, Unreal |
| Best for | Distribution of video and mixed media | Open-source apps, web games, Wikimedia, Linux |
| Codec | Best for | Recommended bitrate | Notes |
|---|---|---|---|
| Vorbis | Music, game audio, general listening | 128-256 kbps CBR or quality 5-8 VBR | The classic Ogg codec; transparent at 192 kbps stereo |
| Opus | Voice notes, podcasts, low-bitrate streaming | 24-96 kbps mono for voice, 96-160 kbps stereo for music | Best codec available at low bitrates; transparent for speech at 32 kbps |
| FLAC (in Ogg) | Lossless archive of the MP4's decoded audio | Lossless; size is roughly 50-60% of an equivalent WAV | Use when you want bit-exact preservation of the decoded audio with Ogg framing |
| Speex | Legacy VoIP, voicemail | 8-32 kbps mono | Largely superseded by Opus; pick only for compatibility with old systems |
If you're not sure, Vorbis at 192 kbps stereo is a safe default for music and works cleanly for game audio and most web use.
Yes — the MP4's audio track is already lossy (typically AAC), and re-encoding to Vorbis or Opus stacks a second lossy compression on top. At 192 kbps Vorbis stereo, the additional loss is inaudible to almost everyone, even on good headphones. At 96 kbps you may notice softer cymbals and slight artifacts on dense music; for voice it remains clean. If you need to preserve the source audio bit-exact after decoding, pick FLAC inside the Ogg container — no further generational loss beyond what the MP4 already had.
For music and general listening at typical bitrates (128 kbps and up), Vorbis is the right pick — it's the historical default for Ogg, every game engine and Linux media player handles it without surprises, and quality is transparent at 192-256 kbps. For voice notes, podcasts, and anything under ~96 kbps, Opus wins decisively — it's the most efficient codec available today and sounds clean down to 32 kbps mono. If you're encoding speech, choose Opus; for everything else, Vorbis is the safer pick.
.oga different from .ogg and .opus?All three are Ogg containers from Xiph.Org. .ogg is the original generic extension and can carry Vorbis audio OR Theora video. .oga was added later to explicitly mark audio-only Ogg files, so an operating system or browser knows there's no video track inside. .opus is reserved for Ogg containers carrying Opus specifically. The audio bytes are identical across all three; only the extension and the OS hint differ. Some Linux file managers and Wikimedia upload tools prefer .oga for audio-only uploads.
No — Apple has never shipped Ogg Vorbis or Opus support in iOS or macOS. iPhones, iPads, Apple Music, iTunes, and CarPlay all refuse .oga files natively. Third-party apps like VLC for iOS will play them, but anything routed through Apple's own Music app or Files preview will fail. If your target audience is on Apple devices, convert to MP4 to MP3 or MP4 to M4A instead.
The MP4 contains both video (which is the bulk of the file size) and audio (a small fraction). OGA keeps only the audio stream and applies its own compression on top. Typical reduction: 80-95% smaller than the original MP4. A 500 MB lecture MP4 routinely lands around 25-40 MB as Vorbis OGA at 192 kbps stereo. This is the main practical advantage of converting when you only need the audio.
Yes. Use the trim section to enter a start time and duration. Both fields accept seconds (12.5) or HH:MM:SS.sss format (00:01:30.500). Useful for pulling a single song from a long concert MP4, extracting one quote from an interview, or grabbing a music loop from a longer master.
Match the engine's expectations. Unity and Godot work cleanly with 44.1 kHz or 48 kHz stereo Vorbis for music and ambience, and 22.05 kHz mono for short SFX where size matters more than fidelity. For 3D-positioned SFX (gunshots, footsteps, UI clicks) mono is correct because the engine pans them at runtime — encoding a stereo source for a positional effect wastes 50% of the file with no benefit.
Standard text tags map to Vorbis comments in the Ogg container, which is the canonical metadata format Xiph defined. MP4 metadata stored in the standard moov/ilst atoms (title, artist, album, year) generally maps across cleanly. iTunes-specific fields and embedded chapter markers are not part of the Ogg specification and may not survive — you can edit Vorbis comments after conversion using free tools like Mp3tag or Kid3.
Yes — drop the entire folder in. Each file converts in parallel on our servers and downloads individually or as a single ZIP. The same encoder settings apply uniformly to the batch (typical when extracting audio from a series of lecture recordings or podcast episodes) or you can tune per file. There's no count cap or per-file size limit beyond your device memory.