The work is executed in the page through browser workers, WebAssembly, Web Audio, or WebGPU as stated.
BPM Detector
Find the pulse. Estimate tempo and display a confidence range for music and loops.
What does bpm detector do?
A BPM detector compares repeating changes in signal energy to find the most likely beat interval. SoundTools analyzes a mono representation locally and reports the strongest tempo between 60 and 200 BPM.
A real local processor, not a decorative upload box
Local rhythm analysis runs after you choose a source and explicitly start the operation. The audio samples remain in browser memory; SoundTools does not send the selected media to an application endpoint.
Choose a rhythmic section, run the analysis, then compare the main estimate with its half-time and double-time interpretations. Results remain available for preview and download only in the current tab. Closing or refreshing the page releases those temporary objects.
How to use bpm detector
- 01
Choose the local source
Open a compatible file in the dedicated workbench at the top of this page. The browser validates and decodes it without an upload step.
- 02
Set the useful controls
Choose a rhythmic section, run the analysis, then compare the main estimate with its half-time and double-time interpretations.
- 03
Process, check, and export
Run the local processor, inspect the status and preview, then save BPM estimate · confidence when the result is ready.
What this tool actually does
Clear limits are part of a useful tool. These values describe the processor currently running in this page.
Runtime and model assets may be downloaded, but the selected file is not attached to those requests.
The dedicated workbench exposes only formats it can actually produce in the current browser.
Useful reasons to open bpm detector
- Loop matching
Estimate a loop before fitting it into a project tempo.
- DJ preparation
Get a quick local reference before detailed beat-grid work.
- Practice planning
Find an approximate metronome setting for a steady song.
Questions about this tool
Answers based on the current browser processor—not promises about a future version.
01Is my audio uploaded for processing?
No. Audio samples stay in browser memory. The page may download a codec or model asset, but it does not send the selected file with that request.
02Why can the first run take longer?
This tool uses Local rhythm analysis. A browser may need to download and initialize that runtime before the first operation; later runs can reuse cached assets.
03Can I preview the result before saving?
Yes. Audio-producing tools expose local result players, while analysis and transcription tools show their detected data before download.
04What happens when the browser is unsupported?
The workbench reports the missing capability instead of uploading the media or pretending that processing is still running.