How OGG playback is selected
OGG is a container, so playback depends on the codec inside it as well as the browser. This audio-focused player first tries native HTML media playback, then Web Audio decoding, and finally the deployed ffmpeg.wasm fallback when available. It also reports best-effort file and stream metadata.
Supported use and limitations
- Vorbis and Opus audio are commonly supported, but availability varies by browser and operating system.
- An OGG container can also hold video or uncommon codecs; this page is designed for audio and may not render those streams.
- Waveform generation requires decoded audio samples and can remain unavailable even when native playback succeeds.
Choose a local .ogg or .oga file, drag it onto the player, or load a URL with CORS permission. A decoder failure is reported explicitly and does not imply that every player will reject the file.
Ndani file processing stays in the browser. URL mode contacts the address supplied, and the optional WASM decoder runs locally after it loads.
