Enter the total beats per minute (BPM) into the FPS from BPM Calculator. The calculator will evaluate the FPS from BPM.
BPM to FPS Formula
The calculator converts between music tempo and video frame timing using three rearrangements of the same relationship.
frames_per_beat = FPS * 60 / BPM
BPM = FPS * 60 / frames_per_beat
FPS = BPM * frames_per_beat / 60
- BPM: music tempo in beats per minute
- FPS: project frame rate in frames per second
- frames_per_beat: number of video frames that fit in one beat
- beats_per_bar: time signature numerator, used to scale beat results to bar results
The math assumes a constant tempo and a constant frame rate. Drop-frame timecodes (29.97 and 59.94) are treated as true fractional frame rates, not as 30 or 60. A beat lands cleanly on a frame only when FPS × 60 ÷ BPM is a whole number. Anything else introduces a sub-frame error that accumulates across a bar.
The three modes map to the formulas above:
- Frames per beat: you enter BPM and FPS, and you get the exact and rounded frame count for one beat plus the bar totals.
- BPM from frames: you pick a whole-frame beat length and FPS, and you get the exact tempo that locks to that frame grid.
- FPS from frames: you fix BPM and the beat length in frames, and you get the frame rate that makes the beat land on a whole frame.
Common BPM and FPS Reference Tables
Use these to sanity-check the calculator output or to pick a tempo that locks cleanly to your timeline.
| BPM | 24 fps | 25 fps | 29.97 fps | 30 fps | 60 fps |
|---|---|---|---|---|---|
| 60 | 24.00 | 25.00 | 29.97 | 30.00 | 60.00 |
| 90 | 16.00 | 16.67 | 19.98 | 20.00 | 40.00 |
| 100 | 14.40 | 15.00 | 17.98 | 18.00 | 36.00 |
| 120 | 12.00 | 12.50 | 14.99 | 15.00 | 30.00 |
| 128 | 11.25 | 11.72 | 14.05 | 14.06 | 28.13 |
| 140 | 10.29 | 10.71 | 12.84 | 12.86 | 25.71 |
| 150 | 9.60 | 10.00 | 11.99 | 12.00 | 24.00 |
| 174 | 8.28 | 8.62 | 10.33 | 10.34 | 20.69 |
Cells where the value is a whole number are the safest tempos for cuts, flashes, and one-frame holds. Everything else means you are rounding.
| FPS | Whole-frame BPMs (common) |
|---|---|
| 24 | 60, 72, 80, 90, 96, 120, 144, 160, 180 |
| 25 | 60, 75, 100, 125, 150, 187.5 |
| 30 | 60, 72, 90, 100, 120, 150, 180 |
| 60 | 60, 72, 75, 90, 100, 120, 144, 150, 180, 200 |
Worked Examples and FAQ
Example 1: 120 BPM at 30 fps. frames_per_beat = 30 × 60 ÷ 120 = 15 frames. Every beat lands on a frame, and a 4/4 bar is exactly 60 frames long.
Example 2: 128 BPM at 24 fps. frames_per_beat = 24 × 60 ÷ 128 = 11.25 frames. Rounding to 11 frames per beat gives an effective tempo of 24 × 60 ÷ 11 = 130.91 BPM, almost 3 BPM faster than the track. Either pick 120 BPM, change the project to 25.6 fps (not standard), or place beat markers from the audio instead of snapping to whole frames.
Example 3: Solving for FPS. You want a 140 BPM track to land on 12 frames per beat. FPS = 140 × 12 ÷ 60 = 28 fps. Closest standard rate is 30 fps, which gives 12.857 frames per beat instead.
Why does 29.97 fps almost never line up? 29.97 is 30000 ÷ 1001. For a beat to land on a whole frame, BPM has to divide 29.97 × 60 = 1798.2 evenly, which only happens at a few odd tempos. Treat 29.97 as 30 for rough planning and use exact markers for tight syncs.
What does the calculator mean by "rounded-frame tempo"? It is the BPM that would make your rounded frame count exact. If it is within a fraction of a BPM of your real tempo, the timing drift across a bar is negligible. If the shift is large, the visible beats will run ahead of or behind the music.
Should I match BPM to FPS or pick a different FPS? If the music is fixed, change FPS only when you control the export and the platform allows it. Otherwise, nudge the tempo, use half-beat or quarter-beat divisions, or accept a one-frame rounding.
