Why is Serato reading the wrong BPM, and how do you fix it?

Why Serato gets the tempo wrong

This is not a bug so much as an ambiguity. Beat detection has to pick one tempo, but many tracks genuinely fit two. A track at 140 BPM sits perfectly on a 70 BPM grid, and one at 90 sits on 180, so the detector has to guess which one you meant. Two things push it toward the wrong guess:

• Your analysis range. Serato only looks for tempos inside the range set in the offline player. If a drum and bass track at 174 falls outside your range, it gets halved to 87 to fit.
• Half-time production. Trap, dubstep, some hip hop and a lot of modern pop use a half-time feel, where the snare lands on beat 3 instead of 2 and 4. The detector often reads that as half the real tempo.

So the same library can have house tracks gridded correctly and every drum and bass tune sitting at half speed. Fixing the range and re-analyzing the outliers clears most of it.

Set the analysis range before you re-analyze

Set the range to cover the bulk of your music. For most club and open-format DJs, 78 to 155 catches house, hip hop, disco and pop without halving them. Then handle the exceptions separately: if you play drum and bass or footwork, analyze those files in their own pass with a range like 130 to 200 so they are not forced down to half time. Getting the range right is what stops you fixing the same tracks over and over. For the full analysis setup, see how to analyze BPM and key in Serato the right way.

Fix one track, or a whole genre, in seconds

The manual correction is a single shortcut. Double-click the BPM column for the track and press Alt+Up Arrow to double the value or Alt+Down Arrow to halve it. Serato rescales the beatgrid to match, so a 70 that should be 140 snaps onto the right grid spacing.

The same shortcut works on a selection. Sort by BPM so the halved tracks cluster together at the low end, shift-click to select the whole block, then apply Alt+Up once. A hundred mis-detected tracks are fixed in a couple of clicks. Back up your Serato folder before a big batch edit so a wrong selection is a quick restore.

When the tempo is right but the grid still drifts

Doubling or halving fixes the number, but if the beatgrid markers are off the beat, the track will still drift when you mix it. That is a separate problem: the downbeat is in the wrong place, or the track was recorded without a steady tempo. Drag the first beat marker onto the real downbeat, adjust the grid until the markers line up with the transients, then lock it. A locked grid survives a future re-analyze, which is what you want once a track is correct. For tracks that genuinely change tempo, Serato 5’s flexible grids map the changes for you; see Serato 5 Lucid beatgrids explained. The full grid editor method, with every shortcut, is in how to edit beatgrids in Serato.

Finding the wrong ones in a big library

The slow part is not the fix, it is finding which tracks are wrong in a library of thousands. The quickest check is to sort one genre at a time by BPM. A house crate is a tight cluster around 120 to 128, so a track sitting at 62 or 250 stands out immediately. Work genre by genre rather than across the whole library, where legitimate tempos overlap too much for the outliers to show.

Crate Cleaner does not detect halved or doubled tempos on its own. What it does is cover the problems on either side of this one: it lists every track that has no BPM at all, runs BPM analysis on them on Pro, and its Smart Crates treat half and double time as the same tempo when building a set, so a track Serato reads at 64 still lands where it belongs in a 128 crate. It runs on your real library on macOS with a free plan and no card required.

Try Crate Cleaner free → · See pricing →

FAQ

Why does Serato halve or double the BPM on some tracks? Because a tempo can be read two ways at once. A 140 BPM track also fits a 70 BPM grid, so tracks that fall outside your analysis range, or use half-time drums, often get read at half or double the real tempo.

Can I fix the BPM on many tracks at once? Yes. Select all the affected tracks, double-click the BPM field and press Alt+Up to double or Alt+Down to halve. Setting a sensible analysis range first prevents most of them happening again.

Will changing the BPM move my cue points? No. Correcting the BPM value and rescaling the grid does not delete your hot cues. It is still worth backing up your Serato folder before a large batch edit.

What analysis range should I use? Pick the range that covers most of your music, such as 78 to 155. If you also play drum and bass or very slow tracks, analyze those separately with a wider or shifted range so they are not halved or doubled.