Account

What new tool do you want?

Video & Audio

MIDI Player & Piano Roll — MIDI to MP3/WAV

Play MIDI files online with a piano-roll view, mute tracks, change speed or transpose, and convert MIDI to MP3 or WAV — all in your browser.

How to use

  1. 1Upload a .mid file (or try the demo song).
  2. 2Press Play; toggle tracks, change speed or transpose.
  3. 3Download the rendered audio as MP3 or WAV.

Frequently asked questions

Why doesn't it sound like my keyboard?

A MIDI file contains notes, not sound. It's played here by a simple built-in synthesizer that approximates each instrument family, so it won't match a high-end sound font.

Can I see sheet music?

It shows a piano roll (notes over time), which works for any MIDI file. Notation software such as MuseScore can open MIDI files as sheet music.

Is the file uploaded?

No — everything runs in your browser.

Why it can't sound like your actual keyboard or a real orchestra

A MIDI file is fundamentally a list of instructions — which note, how hard it was pressed, when it started and stopped — with zero actual audio data inside it. This player interprets General MIDI's instrument families (piano, strings, brass, bass...) with a small built-in synthesizer that picks a matching oscillator waveform and envelope shape for each family — a piano gets a triangle wave with a fast attack and long decay, strings get a sawtooth wave with a slow attack that swells in. That's a reasonable approximation of the instrument's character, but it's built from a handful of basic waveforms and filters, not the sampled recordings of real instruments that a proper sound font or DAW would use — which is exactly why it won't match what the same file sounds like in a dedicated MIDI workstation.

A worked example of how the drum track gets synthesized without any instrument family at all

Percussion tracks skip the oscillator-based instrument voices entirely because General MIDI maps specific drum sounds to specific note numbers rather than using the pitch-and-instrument-family model — note 36 is always a kick drum, note 38 is always a snare, note 42 is always a closed hi-hat, regardless of which 'instrument' the track claims. The synthesizer hardcodes this mapping directly: notes 35-36 get a pitched sine wave sweeping from 150Hz down to 45Hz (a kick's characteristic thump), toms get a similar pitched sweep at different frequencies, and everything else (snares, hi-hats, cymbals) is built from filtered white noise — a highpass filter for bright cymbals, a bandpass filter for body-heavy snares and toms. It's effectively a miniature drum machine triggered by the MIDI file's own percussion events.

Why the exact same rendering pipeline powers both playback and the MP3/WAV download

Rather than maintaining two separate code paths, the tool always renders the complete song into an in-memory audio buffer first (using an OfflineAudioContext, which computes audio as fast as possible rather than in real time), caches that buffer keyed by the current speed/transpose/mute settings, and then either plays that buffer live or encodes it straight to MP3/WAV for download — both actions pull from the identical rendered audio. That's why changing the speed slider or muting a track forces a quick re-render before playback resumes: the cache key no longer matches, so a fresh buffer has to be computed with the new settings before anything — live playback or export — can use it.

Related tools

More: Video & Audio