BPM to FPS Calculator

Two Rates That Count Different Things

A tempo in beats per minute counts musical beats, and a frame rate counts pictures. Neither number converts into the other until you decide how many frames each beat should hold. That single choice is what the calculator asks for.

Beat length follows from tempo alone: beat seconds = 60 / BPM. At 120 BPM a beat lasts 0.5 seconds, and at 90 BPM it lasts 0.6667 seconds. Frame length follows from the frame rate alone: frame seconds = 1 / fps, so 24 fps gives 0.041667 seconds per frame and 12 fps gives 0.08333 seconds. The second itself is one of the seven SI base units, and the NIST SI units page lists it among the defining constants.

The two rates meet when a beat spans a whole number of frames. If a beat holds exactly 4 frames, the film runs at 4 frames per beat and the frame rate is set by the tempo. If a beat holds 12 frames, the same tempo produces three times the frame rate. Nothing about the music changed, only the number of pictures per beat.

The Conversion Formula, Step by Step

Start with the beat in seconds, then ask how many frames fit inside it. If each beat holds f frames, one frame lasts 60 / (BPM x f) seconds, and the frame rate is the reciprocal of that:

fps = BPM x f / 60, which is the same as fps = BPM / 60 x frames per beat

Turning the equation around gives the frame count needed for a target rate:

frames per beat = fps x 60 / BPM

The units cancel cleanly. BPM is beats per minute, dividing by 60 turns it into beats per second, and multiplying by frames per beat gives frames per second. A common slip is to multiply by 60 at that step instead of dividing, which returns a frame rate sixty times too high. A minute is 60 seconds exactly, a non-SI unit accepted for use with the SI in the BIPM SI Brochure, so the 60 in these formulas is exact rather than rounded.

The one frame per beat case drops straight out of the formula. Set f = 1 and fps = BPM / 60, so 60 BPM gives 1 fps, 120 BPM gives 2 fps, and 180 BPM gives 3 fps. That is the tightest lock between music and picture available, and it is rarely what an animator wants at normal tempos.

Worked Example: 120 BPM on Two Frames per Beat

Take a 120 BPM track and hold each drawing for 2 frames. The frame rate is 120 / 60 x 2 = 4 fps. One beat lasts 60 / 120 = 0.5 seconds, one frame lasts 1 / 4 = 0.25 seconds, and two frames of 0.25 seconds fill the beat exactly. That last check is the one to run when the numbers feel off.

Over a 16 beat phrase the animation shows 16 x 2 = 32 distinct drawings, and the phrase runs 16 x 0.5 = 8 seconds. Animate the same track on 1 frame per beat and the rate falls to 2 fps, so the phrase needs 16 drawings instead of 32. The beat timing stays identical while the motion gets choppier, because half the frames are gone.

Worked Example: 90 BPM Against a 24 fps Target

A 90 BPM cue has to sit on a 24 fps timeline. The frame count per beat is 24 x 60 / 90 = 16. Each beat spans 16 frames, and 16 frames at 1/24 second each is 0.6667 seconds, which matches 60 / 90. Beat markers land every 16 frames, so cuts on the beat fall on frames 0, 16, 32, 48, and onward.

Change the target to 30 fps and the same tempo needs 30 x 60 / 90 = 20 frames per beat. The beat still lasts 0.6667 seconds, because 20 frames at 1/30 second each is the same span. Tempo sets the clock and the frame rate sets the resolution of that clock, which is why the frame count moves while the beat length holds still.

A third check: 60 BPM against 30 fps needs 30 x 60 / 60 = 30 frames per beat, one full second of footage per beat. Every one of these answers can be verified by multiplying the frame count by the frame duration and landing back on the beat length.

Reference Table for Common Tempos

The table below covers tempos that show up often in production music, and three hold values that animators use. Read a row left to right and the beat length shrinks as the tempo climbs, while the frame rate climbs with the hold count.

Two rows are worth memorizing. At 120 BPM the beat is half a second, so 12 frames per beat gives 24 fps and 15 frames per beat gives 30 fps. At 128 BPM, a common electronic tempo, the beat is 0.46875 seconds, and a 60 fps canvas spends 28.125 frames on each beat.

Frames per Beat in Animation Practice

Hand drawn animation has long used holds as a timing tool, and the arithmetic explains why. Holding each drawing for two frames halves the frame rate at a given tempo, and holding for three cuts it to a third. Motion gets steppier in exchange for fewer drawings, which is the trade every small team makes.

At 120 BPM, a 12 fps result needs 6 frames per beat, a 24 fps result needs 12 frames per beat, and a 30 fps result needs 15 frames per beat. Those numbers are worth keeping nearby, because 120 BPM is a common default and 12, 24, and 30 are common delivery rates. At 100 BPM the same targets need 7.2, 14.4, and 18 frames per beat, which is a sign that the tempo will never sit on a clean frame grid.

For music visualizers the useful direction runs the other way. Given a 60 fps canvas and a 128 BPM track, each beat spans 28.125 frames. That is not a whole number, so a beat marker snapped to the nearest frame lands up to half a frame off, and the shortfall adds up: 0.125 frames per beat means one full frame every 8 beats, so by beat 32 the grid sits 4 frames away from the audio. Either pick a tempo that divides evenly into the frame rate, or drive the grid from the audio clock instead of the frame counter.

The table below reads in the other direction. Pick a hold count, then read the frame rate that hold count produces at three tempos, so the same drawing count can be checked against a delivery rate before any work starts.

Each cell is the tempo divided by 60, then multiplied by the hold count. The 120 BPM column is the easy one to remember because the tempo divides evenly, and the 100 BPM column never lands on a whole number, which is the signal that a 100 BPM track cannot hold a clean grid at any of these delivery rates.

Errors That Throw Off the Timing

Treating BPM / 60 as the final answer is the most common error. That expression assumes one frame per beat, so it is correct only when the picture changes once per beat. Multiply by the hold count before you trust the result.

Rounding the frame rate too early is the second. A track at 137 BPM with 2 frames per beat gives 4.5667 fps. Rounded to 5 fps, the picture runs about 9.5 percent fast, and a four minute sequence ends roughly 21 seconds ahead of the music. Keep the decimals until the last step, and round the frame count rather than the rate when the two disagree.

Confusing frame duration with beat duration is the third. A 4 fps animation has 0.25 second frames, not 4 second frames. Reciprocals trip people up when they check their own work by hand, so write the unit next to every number.

Assuming a whole number of frames per beat is the fourth. Plenty of tempos do not divide evenly into a delivery rate, and pretending they do pushes the error into the edit. When the division leaves a remainder, hold the grid on the audio and accept that some beats land between frames.

Last, do not mix a frame count from one frame rate with a duration from another. Sixteen frames per beat is true at 24 fps for 90 BPM. At 30 fps the same tempo needs 20 frames per beat, and quoting the 24 fps count against a 30 fps export shortens every beat by a fifth.