Convert a tempo into delay and reverb timing. One beat at BPM = 60000 / BPM milliseconds.
Updates automatically as you type.
Calculated in your browser; your inputs are not sent to us. Privacy
Calculation details
Planning estimate only, not financial, tax, or legal advice. Verify assumptions and current rules before making decisions.
This tool runs in your browser. Your calculator inputs and results are never transmitted to us or to ad/affiliate partners. Ads and sponsored links may set third-party cookies to serve and measure them, but they never receive your calculation values. If you explicitly save a scenario, its permitted fields stay in local browser storage until you clear them. See our Privacy Policy.
Use this result
Share the current inputs or ask ChatGPT to explain the calculation in context.
More options
What does this calculator estimate?
BPM to delay time calculator: convert your track tempo into ms per beat, quarter, eighth, and dotted eighth delay times for music production. Free, no signup.
How this calculator works
Formula
Beat time (ms) = 60,000 / BPM; subdivisions scale the beat (eighth = half, dotted eighth = 0.75, sixteenth = quarter, triplet eighth = one third).
Worked example
At 120 BPM: quarter note 500 ms, eighth 250 ms, dotted eighth 375 ms, sixteenth 125 ms, triplet eighth 167 ms, one bar 2,000 ms.
Frequently asked questions
What does a bpm to delay time calculator do?
It calculates the exact delay time in milliseconds based on your chosen beats per minute and delay type to help you sync echoes with your track's tempo.
Do I need to create an account or sign up to use this bpm to delay time calculator?
No, this is a no-signup, browser-based tool that runs entirely on your device without requiring any personal data or account creation.
How accurate is the delay time calculation on this tool?
It is mathematically precise, converting BPM to milliseconds instantly based on the standard formula, ensuring perfectly synced echoes every time.
Cite this tool
BoringToolsKit. “BPM to Delay Time Calculator.” boringtoolskit.com/bpm-to-delay-calculator/. Free to reference in articles, syllabi, and answer posts with a link.
Privacy: Inputs and results stay in this browser. Any future sponsored recommendation or advertisement will be clearly labeled and kept separate from the calculation.
A worked example at 90 BPM
Take a common hip-hop tempo, 90 BPM. The base number is 60000 / 90 = 666.667 ms per beat, which the table rounds to 667 ms for a quarter note. Every other row is a simple division or multiplication of that base figure, so you can check the whole table by hand: an eighth note is 666.667 / 2 = 333.333, rounded to 333 ms. A dotted eighth is 666.667 x 0.75 = 500 ms exactly, since a dotted note lasts one and a half beats and 60000 x 0.75 / 90 divides cleanly.
The remaining rows at 90 BPM: a sixteenth note is 666.667 / 4 = 166.667, shown as 167 ms. A triplet eighth is 666.667 / 3 = 222.222, shown as 222 ms. A full bar of four beats is 666.667 x 4 = 2666.667, shown as 2667 ms. If you set a delay pedal to 667 ms and tap in quarter notes, the repeats land on each beat; set it to 333 ms for eighth-note echoes or 500 ms for the dotted-eighth guitar stutter made famous in 1980s new wave and U2-style playing.
One practical detail: the displayed values are rounded to whole milliseconds, so the sum of parts does not always equal the whole. 167 + 167 + 167 + 167 = 668, not 667, because four sixteenths each rounded up slightly. The underlying math 60000 / 90 stays exact; only the display rounds. When chaining subdivisions on hardware, prefer computing from the base value rather than stacking rounded numbers.
Rounding, extreme tempos, and where a delay table stops helping
The rounding error grows as the subdivision shrinks. At 200 BPM a quarter note is 60000 / 200 = 300 ms exactly and a sixteenth note is 75 ms exactly, both clean. But at 118 BPM the quarter note is 508.475 ms (displayed 508) and the sixteenth is 127.119 ms (displayed 127). A 1 ms offset is inaudible for a single echo, but it becomes audible feedback drift when long delay feedback keeps repeating, because the same rounding error compounds once per repeat cycle.
The formula behaves differently at the extremes. At a very slow 30 BPM, a bar is 60000 / 30 x 4 = 8000 ms, longer than many hardware delays max out at 5,000 ms, so the row is correct but physically unusable on that pedal. At a fast 240 BPM the quarter note is 250 ms and the sixteenth is 62.5 ms, rounded to 63; most delay units only step in 1 ms increments, so 62.5 is not settable at all and you would pick 62 or 63 and accept roughly 0.8 percent error. Non-integer tempos work fine: 75.5 BPM gives 794.7 ms, displayed 795. The calculator rejects zero and negative values outright, returning the prompt to enter a tempo greater than zero, which is the correct behavior since 60000 / 0 is undefined.
Honest boundary: this table covers one beat divided by 2, 3, and 4 and one whole bar. It does not cover half-time feel (where the perceived downbeat is twice as slow), swing percentages, dotted rhythms beyond the dotted eighth, or sample-rate-locked delays in plugins that quantify time to samples rather than milliseconds. It also assumes 4/4 time; in 6/8 the musical bar is six beats, so multiply the quarter-note value by 6 yourself instead of trusting the bar row.