ToolCraft
HomeAI ToolsDeveloper ToolsUnit ConverterImage Tools
ToolCraft

© 2026 ToolCraft. All rights reserved.

Privacy PolicyTerms of Service
DMCA.com Protection Status
HomeAudio ToolsBPM Detector

Audio Tools

Audio Converter & TrimmerAudio NormalizerBPM DetectorText to Speech

BPM Detector

Detect the tempo (BPM) of any song or beat by analyzing peak intervals — runs entirely in your browser.

Drop an audio file here or click to browse

WAV, MP3, OGG, M4A, FLAC, WebM Opus.

Tempo analysis runs entirely in your browser. Audio never leaves the page.

View all Audio Tools

View all
100% offline
New

Audio Converter & Trimmer

Trim, resample, mono/stereo, gain, fade — convert any audio to 16-bit WAV right in your browser.

Audio Tools
100% offline
New

Audio Normalizer

Normalize audio loudness to Spotify/YouTube/Podcast/Broadcast targets via peak or LUFS — entirely in-browser.

Audio Tools
100% offline
New

Text to Speech

Convert any text to speech using your browser's built-in voices. 50+ languages, runs offline once voices are installed.

Audio Tools

What is the BPM Detector?

BPM (beats per minute) is the speed at which a song's underlying pulse repeats — 128 BPM is typical for house, 140 BPM for trap, 174 BPM for drum & bass, 120 BPM for most pop. DJs need exact BPM to beatmatch tracks; music producers need it to sync samples; runners and gym-goers pick playlists by BPM to match cadence. This BPM Detector lets you drop any audio file and get a tempo estimate in 1–3 seconds, entirely in your browser. The algorithm low-pass-filters the signal to isolate the kick/bass band where beats are most consistent, finds peaks above a dynamic threshold, computes inter-peak intervals, and folds the resulting BPM candidates into a histogram. The strongest bin is the dominant tempo, with up to five runner-up candidates shown for cases where the song straddles a half-time / double-time ambiguity (a 70-BPM ballad and a 140-BPM remix have the same peak structure — the detector picks the most likely, you can pick the other from the alternatives list).

Why might the detected BPM be half or double the "real" one?

Tempo is inherently ambiguous: a kick drum on every quarter note at 120 BPM looks identical to a kick on every eighth note at 60 BPM. Algorithms fold candidates into the 60–200 BPM range, but the right answer depends on musical context the algorithm cannot know. If the detected tempo feels off by 2×, check the alternatives list — the right one is usually shown. The folding range starts at MIN=60 because slower tempos are typically unfolded fast ones.

FAQ