mp3 to midi
Runs locally in your browser

TIMING GRID

How to Quantize Audio-to-MIDI Notes

Choose the smallest grid that corrects the timing you want without flattening intentional rhythm. Start with quantize off, download a baseline, then try 1/16 or 1/8 on the same audio. In this tool, quantize changes the event timing written into the downloaded MIDI file; it does not move the detected-note preview on this page.

The same detected note positions snapped to eighth, sixteenth, and thirty-second-note MIDI timing grids
A coarser grid moves events farther; a finer grid keeps more of the detected timing detail.

MAKE A TIMING TEST

Convert one file with a named grid

Keep the source and detection controls fixed. Change only Quantize, download each trial, and compare the same passage.

INPUT  MP3 / WAV / M4A / FLAC / OGG → OUTPUT  .MID

Drop one timing test here

or click to choose audio from your device

Choose audioMP3, WAV, M4A, FLAC, or OGG · one file · up to 50 MB / 5 minutes
Or capture one clear melody with your microphone.

Your audio stays on your device. All processing happens in this browser. No file is uploaded to a server.

No sign-upOne file at a timeNo watermark
SettingGrid in this MIDI writerAt 120 BPMUse it to test
Off1 tick; no musical grid selectedDetected timing is converted to ticks, then rounded to a whole tickBaseline timing before musical-grid snapping
1/3260 ticks62.5 ms grid stepSmall corrections while retaining more timing detail
1/16120 ticks125 ms grid stepA first comparison for many short-note passages
1/8240 ticks250 ms grid stepStronger timing correction with fewer allowed positions
1/4480 ticks500 ms grid stepVery coarse placement where beat-level timing is intended
Controlled test path from quantize off to one grid setting, DAW comparison, and keep or revert decision
Change only the quantize setting so a timing difference can be attributed to that grid.

CODE-VERIFIED GRID

Each quarter note has 480 ticks

The current writer calculates grid ticks as 480 × 4 ÷ division. That produces 480, 240, 120, and 60 ticks for quarter, eighth, sixteenth, and thirty-second notes.

SNAP RULE

Starts and ends go to the nearest grid point

The writer divides a raw tick position by the selected grid, rounds it, and multiplies back by the grid size. It also keeps every written note at least one selected grid step long.

TEMPO MATTERS

The same tick grid has a different time length

Ticks are calculated from the chosen BPM. At 120 BPM, a quarter note is 500 ms; at another tempo, the musical division stays the same while its duration in milliseconds changes.

PREVIEW BOUNDARY

Check the downloaded MIDI in a DAW

The piano roll on this page draws detected notes before MIDI writing. Quantize is applied inside the file writer, so import each download into the same DAW project to compare snapped event timing.

QUICK ANSWERS

Audio-to-MIDI quantize questions

What quantize setting should I use for audio to MIDI?

Start with off as a baseline, then try the finest grid that targets the timing problem. Compare 1/16 before moving to the coarser 1/8 or 1/4 grids.

Why did the on-page piano roll not move?

This page shows detected-note timing. The selected quantize grid is applied when the MIDI file is written, so inspect the downloaded event positions after import.

Does quantize fix wrong pitches or extra notes?

No. Quantize changes timing positions. Use pitch boundaries for out-of-range notes, minimum-note duration for short fragments, and the troubleshooting guide for symptom-specific adjustments.

Can a coarse grid remove rhythmic detail?

Yes. A coarser grid offers fewer timing positions and can move notes farther from the detected timing. Keep a trial only when the intended rhythm still reads correctly.

How do I compare two quantize settings?

Use the same file, tempo, and detection controls. Download one version with quantize off and one with a single grid setting, then compare the same passage in the same DAW project.

Download the quantize comparison sheet (.csv)