BPM and Picture: How Editors Cut to Music Without Losing Their Mind
The Cut That Syncs, and the Cut That Fights
The montage sequence is 2 minutes long. The track is at 128 BPM. The director wants hard cuts on every beat. You have been manually counting frames on the timeline for 40 minutes. The cut works for the first 30 seconds, then drifts by half a beat, then drifts further, and by 1:30 the cuts are landing a full beat off the music with no obvious fix short of rebuilding the section from scratch.
The drift came from one source: you were cutting to feel rather than to frame count, and feel is not mathematically consistent enough for tempo-locked editing.
Cutting picture to a musical tempo is a mathematical problem with a precise solution. The BPM Sync Tool calculates exact frame counts per beat at any BPM for any frame rate. This post explains how to use those numbers -- and when not to.
How BPM, Frame Rate, and Cut Points Relate
A beat is a unit of musical time. At 120 BPM, there are 2 beats per second. At 24fps, there are 24 frames per second. One beat at 120 BPM in a 24fps timeline is exactly 12 frames.
The calculation is: frames per beat = (frame rate / BPM) x 60.
At 120 BPM and 24fps: (24 / 120) x 60 = 12.0 frames per beat. Every cut should land 12 frames after the previous one to sync exactly with the downbeat.
At 128 BPM and 24fps: (24 / 128) x 60 = 11.25 frames per beat. The non-integer result is where the drift comes from: your NLE snaps cuts to whole frames, but the mathematical beat position is not always on a whole frame. Over 64 beats, the accumulated rounding error is 16 frames -- more than half a second at 24fps.
The BPM Sync Tool handles this by calculating the nearest whole frame to each beat position across the full cue duration, showing you exactly where each beat lands (in frames and timecode) and flagging where rounding errors accumulate.
Three Cutting-to-Music Scenarios
Scenario 1 -- Montage at 100 BPM, 25fps delivery (PAL broadcast), 64 cuts.
Frame rate: 25fps. BPM: 100. Frames per beat: (25/100) x 60 = 15 frames exactly. No rounding error. Every cut falls on a whole frame. This is the cleanest possible scenario: an integer result. At 64 cuts over 128 beats, the edit takes exactly 76.8 seconds. Run the sequence from the first beat and every cut will land exactly.
Scenario 2 -- Action sequence at 140 BPM, 23.976fps (NTSC drop-frame), 96 cuts.
Frame rate: 23.976fps. BPM: 140. Frames per beat: (23.976/140) x 60 = 10.277 frames per beat. Non-integer. Over 96 beats, the accumulated rounding error is approximately 26 frames -- more than 1 second. The BPM Sync Tool generates a full beat-by-beat cut list in timecode, accounting for the drift and giving you the corrected frame position for each of the 96 cuts. Without this, the cut will drift audibly by the second half of the sequence.
Scenario 3 -- Documentary interview with music underscore at 72 BPM, 29.97fps.
Frame rate: 29.97fps. BPM: 72. Frames per beat: (29.97/72) x 60 = 24.975 frames per beat. The cut positions are not meant to be hard cuts on downbeats -- instead the music is running under dialogue and the editor wants to align B-roll cuts to the musical phrasing (every 4 beats = 1 bar). The BPM Sync Tool calculates bar-length frame counts for the phrasing-based approach: 4 beats at 72 BPM / 29.97fps = 99.9 frames per bar. The editor cuts B-roll in 100-frame blocks aligned to the musical bars, creating a subliminal rhythmic coherence without hard musical sync.
Frame Counts Per Beat at Common BPM and Frame Rate Combinations
| BPM | 23.976fps (frames) | 24fps (frames) | 25fps (frames) | 29.97fps (frames) |
|---|---|---|---|---|
| 60 | 23.976 | 24.0 | 25.0 | 29.97 |
| 80 | 17.982 | 18.0 | 18.75 | 22.478 |
| 100 | 14.386 | 14.4 | 15.0 | 17.982 |
| 120 | 11.988 | 12.0 | 12.5 | 14.985 |
| 128 | 11.238 | 11.25 | 11.719 | 14.048 |
| 140 | 10.277 | 10.286 | 10.714 | 12.844 |
| 160 | 8.991 | 9.0 | 9.375 | 11.239 |
Integer or near-integer results (highlighted by the tool) are the most practical BPM/frame rate combinations for precise beat-locked editing.
How to Cut to Music Frame-Accurately: Step by Step
- Identify the BPM of your track precisely. Do not estimate by tapping a spacebar. Import the track into a DAW (Logic Pro, Ableton, DaVinci Resolve's Fairlight, or Premiere's Essential Sound panel) and use the BPM detection function. Most modern tracks have a consistent BPM; older recordings may drift slightly. For tempo-drifting tracks, the BPM sync approach only works for the section where the BPM is consistent.
- Enter your BPM and frame rate into the [BPM Sync Tool](/tools/bpm-sync). The tool generates a full beat-position table for your cue duration: each beat's timecode position, the nearest whole frame, and the cumulative drift. Export or screenshot this table as your cutting reference.
- Set a sequence marker or beat marker in your NLE at the downbeat of the first bar. This is your sync point -- the frame in your timeline that corresponds to beat 1, bar 1 of your music. All subsequent cut calculations derive from this anchor point.
- Place cuts using the frame count table rather than by ear. Instead of listening and clicking, count the frames from your sync point to the first cut position (as specified in the tool's output), place the cut, advance to the next cut position, and repeat. For short montages (under 30 cuts), this is faster than it sounds. For long sequences, use your NLE's "slip to frame" or timecode entry function to navigate precisely.
- Review the sync after placing all cuts and adjust for feels that are technically correct but visually wrong. Mathematical sync gets you to a correct starting position. Film is not metronome -- a technically perfect beat cut can feel wrong if the image content does not support it. Review the cut in context and use your judgment to adjust individual cuts by 1-3 frames for visual rhythm. A 2-frame adjustment on any single cut is invisible to all but the most analytical viewer and can significantly improve the felt rhythm of the scene.
- Render a reference mix of picture and music together and play it at speed. Slow-reviewing a cut sequence masks drift that is obvious at full speed. Play the sequence from start to finish at full playback speed and listen for the moment where the music and the cuts part company. If it is still drifting, return to the beat-position table and find the cut that was placed on the wrong frame.
Pro Tips and Common Mistakes
Pro Tip: In Premiere Pro, you can create sequence markers from imported audio beats using the "Set Clip Marker" function with the music track highlighted, then snap your cuts to those markers. In DaVinci Resolve, the Beat Detection feature in Fairlight can extract beat markers from audio and display them in the Edit timeline. Either approach significantly reduces the manual frame-counting process for long sequences.
Pro Tip: If the track you are cutting to has a musical intro of a different tempo or a brief tempo change, segment the cue and calculate beat positions for each tempo section independently in the BPM Sync Tool. Applying a single BPM calculation to a track with a mid-song tempo change will create cumulative drift in the second half regardless of how accurate your initial cut placement is.
Common Mistake: Snapping cuts to the audio waveform peak rather than to the beat position. A waveform peak in a compressed musical track does not necessarily correspond to the true beat position -- the attack transient may be slightly ahead of or behind the mathematical beat. Use the calculated frame position from the beat position table, not the visual waveform, as your cut placement guide.
Common Mistake: Assuming that cutting to every beat serves every scene. Cutting to every beat works for high-energy montages and action sequences. For emotional sequences, cutting every 2 or 4 beats (on the bar or every other bar) creates the felt rhythmic connection with the music while allowing the image time to register. An editor who cuts every beat in a quiet, grief-driven sequence is fighting the music rather than working with it.
Frequently Asked Questions
What if my track has a half-time or double-time feel?
Some tracks feel like they are at half the mathematically measured BPM because the producer has emphasised every other beat (the 2 and 4) rather than all four. In this case, your effective cutting BPM is half the track's actual BPM. Conversely, tracks with a driving 16th-note feel may support cutting at double the base BPM on fast rhythmic subdivisions. The BPM Sync Tool lets you enter any BPM, so you can calculate cut positions at half-time (BPM/2) or double-time (BPM x 2) easily.
How do I find the BPM of a track if the BPM detection tool gives conflicting results?
Manual tap-BPM over at least 16 bars, then average. Online tap-BPM tools (TapTempo.net, GetSongBPM.com) allow you to tap the beat manually and generate an average BPM. For highly produced electronic music with clear kick-drum transients, automated detection is reliable. For acoustic music with variable tempo, manual tapping over a longer passage is more accurate.
Can I use this approach for cutting dialogue scenes to music?
For dialogue scenes underscored with music, you are not cutting on beats -- you are cutting on dialogue rhythm and reaction beats that happen to interact with the music. The music supports the dialogue's rhythm rather than dictating it. The BPM sync approach is most useful for sequences with no (or minimal) dialogue where the music is the primary rhythmic driver.
Does this work for music with irregular time signatures (5/4, 7/8)?
Yes, but the calculation changes. In 5/4 time at 120 BPM, a bar contains 5 quarter-note beats instead of 4. The frame count per beat remains the same, but the bar length is 5 beats rather than 4. Enter the BPM normally in the BPM Sync Tool and calculate bar length by multiplying the beat frame count by the number of beats in the bar (5 for 5/4, 7 for 7/4, and so on). Cutting to bars rather than individual beats is generally more practical for irregular time signatures.
Related Tools and Posts
The BPM Sync Tool generates a full beat-position table for any BPM and frame rate combination, with cumulative drift correction across the full cue length -- use it before placing your first cut in any music-driven sequence. For the music delivery specifications that govern how your final mixed audio must be prepared before delivery, Delivering Audio for Netflix, Amazon, and Apple TV Plus covers the platform specs. For the audio format decision that precedes the mix stage, Mono vs. Stereo vs. 5.1 vs. Atmos: Which Audio Format Does Your Film Actually Need? covers the channel format decision.
Cut to the Math, Then Cut to the Feel
Cutting to music is both a calculation and a craft decision. The BPM Sync Tool eliminates the drift that comes from cutting by ear alone. What you do with the mathematically correct cut positions -- whether you hold them, loosen them, or tighten them by a frame -- is the editor's contribution that cannot be automated.
What is the trickiest music-to-picture sync problem you have solved in an editing session -- and what was the technique that finally made it work?