Why game and app developers use OGG
OGG Vorbis has been the standard compressed format in game development for years. It is royalty-free, supported by engines such as Godot, Unity and Unreal, and decodes quickly. A game with an hour of music would need over 600 MB as WAV but only around 60 to 80 MB as OGG. Web developers and open-source projects use it for the same reasons, and Wikimedia Commons accepts it for audio uploads.
Settings for different content
| Content | Suggested setting | Size per minute |
|---|---|---|
| Background music | 160 to 192 kbps, stereo | 1.2 to 1.4 MB |
| Ambience loops | 128 kbps, stereo | about 1 MB |
| Sound effects | 64 to 96 kbps, mono | 0.5 to 0.7 MB |
| Dialogue and voice-over | 64 kbps, mono | about 0.5 MB |
Positional sound effects in 3D games should be mono anyway, because the engine places them in space itself. Choosing mono output also halves the data the encoder has to spend.
Seamless loops
Vorbis is a good format for looping music because it does not add the extra silence at the start that MP3 encoders insert. To get a perfect loop, the WAV itself must start and end at matching points. Check the loop in the audio editor with loop playback before converting. Small fades at the edges are not needed for a well-cut loop and would cause a dip in volume.
Quality and other notes
Starting from WAV means a single, clean encode. At 160 kbps and above, Vorbis is transparent for most game and web use. Keep the sample rate at 44.1 or 48 kHz to match your project. WAV files usually have no tags, and none are needed for game assets.
OGG is not supported everywhere: older Safari versions and many car stereos cannot play it. If your target is a web page that must work on every device, also make an MP3 or M4A version. For voice chat or very small files, WAV to OPUS is even more efficient.