Select eligible WAV files
Add non-empty .wav files up to 100 MB each. The source must contain audio that host FFmpeg can read.
Server-backed WAV to OGG conversion
Upload supported WAV audio and create an audio-only Vorbis OGG download from its first audio stream.
Processed by our self-hosted conversion engine
Supported files
The server decodes a supported WAV file and encodes its first audio stream as a new Vorbis OGG at fixed quality 5.
How it works
Add non-empty .wav files up to 100 MB each. The source must contain audio that host FFmpeg can read.
Start the queue to process one file at a time with this route’s Vorbis quality 5 FFmpeg profile.
Review a completed result in compatible software, then download its separately named OGG file.
Processing boundaries
The profile maps only the first audio stream, drops video, removes metadata and chapters, and uses libvorbis quality setting 5.
Convert WAV to OGGOnly non-empty .wav uploads of 100 MB or less are accepted. Unsupported or unreadable audio sources cannot be converted.
WAV is decoded and re-encoded as Vorbis OGG. It is not a stream copy, and output size or sound can differ.
Only the first audio stream is mapped. Video, alternate tracks, subtitles, and attachments are excluded from this audio-only result.
Source metadata and chapters are removed. This route provides no trim, stream-selection, bitrate, sample-rate, channel, or quality controls.
WAV-to-OGG details
Use non-empty .wav files up to 100 MB. Host FFmpeg must be able to read an audio stream in the source.
A successful conversion contains a newly encoded, audio-only OGG result from only the first audio stream using Vorbis quality 5.
Yes. Add multiple eligible files. The browser submits each queue item sequentially and every completed result has a separate download.
WAV is decoded and re-encoded as Vorbis OGG. It is not a stream copy, and output size or sound can differ.
No. The conversion profile removes source metadata and chapters. Alternate audio tracks, video, subtitles, and attachments are not included.
No. There are no trimming, stream-selection, bitrate, sample-rate, channel, or quality controls.
No. Browser playback support and host FFmpeg readability are different checks. A file must be readable by FFmpeg for conversion, and playback depends on browser support.