What does "MIDI to WAV" actually do?
A MIDI file contains no sound — only performance instructions (see MIDI Tools for the full story). So converting MIDI to WAV is not really a conversion: this page renders the instructions through a software synthesiser, records the output as PCM samples, and writes those samples into a WAV file. Think of it as printing a score with one particular orchestra: the score (MIDI) is the recipe, the WAV is one fixed performance of it. Once rendered, the WAV is ordinary audio — it plays anywhere, no synthesiser required.
Five facts to anchor the rest of the page:
• MIDI→WAV is a render, not a format conversion — the synthesiser creates sound that never existed in the file
• the sound comes from a SoundFont: a sample library of real recorded instruments (~32 MB, loaded once per browser)
• the built-in bank is GeneralUser GS: 261 instruments and 13 drum kits covering the General MIDI standard
• the same MIDI file rendered with a different SoundFont is a different, equally valid WAV
• input variants .rmi (RMID), .kar (karaoke MIDI) and .xmf are all just wrappers around the same SMF event stream
Synthesis and samples: where the sound comes from
There are two ways to make a synthesiser speak. Subtractive synthesis builds tones from oscillators and filters — cheap, but it sounds like a keyboard, not an orchestra. Sample playback uses short recordings of real instruments and repitches them across the keyboard; a SoundFont (the SF2 format) is a bundle of such samples plus envelopes and loop points. The engine on this page uses sample playback: when the MIDI says "note 60 on channel 1, piano", it looks up the piano sample, transposes it to the requested pitch, applies the velocity as level and timbre, and mixes it into the output. Rendering runs faster than real time — a 3-minute file takes well under 3 minutes because the synth is never waiting for anyone.
Rendering, not converting — and why there is no reverse
Format converters (WAV to FLAC, MP3 to M4A) preserve the same audio in different packaging. A MIDI render creates audio from scratch on every note. That has two consequences. First, quality depends on the renderer: the same .mid file through a 1990s soundcard chip, this page, and a studio sample library yields three very different WAVs, and none of them is "the" correct one — the MIDI never specified what the instruments sound like. Second, the process is strictly one-way. "WAV to MIDI" is not a conversion problem but a transcription problem: recognising which notes were played from the waveform, which is pitch-detection guesswork, not packaging. Tools that attempt it work only on clean single-instrument recordings, and they approximate.
Input wrappers and the sample rate knob
Besides plain .mid (Standard MIDI File), this page opens .rmi (RMID — a MIDI file inside a RIFF wrapper, Windows' native packaging), .kar (karaoke MIDI: the same events plus a lyrics track for display), and .xmf (an extensible wrapper that can bundle the MIDI with its sounds). All of them decode to the same event stream, so the renderer treats them identically. The sample rate option sets how finely the render is measured: 44,100 Hz matches CD, 48,000 Hz matches video and most streaming, and 96,000 Hz doubles the ceiling for archival or later processing. File size scales linearly with the rate — the same render is twice as large at 96 kHz as at 48 kHz — and for most music the difference above 48 kHz is inaudible.
Common misconceptions
- The rendered WAV is what the composer intended. It is one interpretation. MIDI fixes notes, timings and instruments by category, but not the actual sound of those instruments. Every renderer makes its own orchestration choices.
- MIDI to WAV is lossless or lossy. Neither. There is no original audio to lose. The right questions are: which SoundFont, which sample rate — those set the fidelity of the render itself.
- A bigger SoundFont always sounds better. No. Beyond covering the General MIDI set well (which the built-in 261-instrument bank does), extra size buys refinements only trained ears notice on specific instruments. A 2 GB piano library helps piano solos; it does nothing for a chiptune file.
Related tools: MIDI Tools to view, transpose and edit the MIDI before rendering, Audio to WAV / FLAC to compress the rendered WAV losslessly, Audio to MP3 / ID3 Tags for a small shareable copy, and Audio Spectrum to inspect the render's frequency content.
