Drop in a song and get its tempo, musical key and Camelot code in seconds. The analysis runs on your device - the file never uploads anywhere.
100% in your browser - your files never leave your device.
Pick any MP3, WAV, OGG, FLAC or M4A - a full track or just a loop of four seconds or more. The file is decoded locally by your browser.
Tempo comes from autocorrelating the onset envelope of the audio; the key comes from matching a chroma fingerprint against the classic Krumhansl key profiles. No servers involved.
You get the BPM with the beat grid drawn over the waveform, plus the detected key with its Camelot wheel code and the most likely alternative.
Tempo and key are the two numbers that make music fit together. DJs use them to beatmatch and mix harmonically: two tracks in compatible Camelot positions (same number, or one step apart) blend without clashing. Producers need the BPM to lock samples and loops to their project grid, and the key to layer melodies, write basslines or pick an acapella that sits in tune.
The same goes for practice and covers: knowing a song is, say, 96 BPM in F# minor tells you where to set your metronome and which scale to solo in. Instead of tapping along with a stopwatch or hunting the key by ear at the piano, this analyzer measures both directly from the audio.
Unlike most online BPM detectors, nothing here is uploaded. Your audio is decoded and analyzed by code running in the page itself - the same detection the TuttiDAW studio uses to align transcribed audio to the beat grid - so it works offline-fast, on demos and unreleased material you would never send to a random server.
Very reliable on steadily played material with a clear pulse (electronic, pop, rock). Expect trouble on rubato performances, tempo changes mid-song, and ambiguity between half and double time - which is why the result also shows the half-time and double-time readings.
The Camelot wheel maps the 24 musical keys onto positions 1A-12A (minor) and 1B-12B (major). Tracks whose codes match or sit one step apart (e.g. 8A and 9A, or 8A and 8B) are harmonically compatible, which is how DJs pick the next song without key clashes.
No. The file is decoded by your browser and analyzed by JavaScript running on your device. It never leaves your computer, which also means the analysis starts instantly instead of waiting for an upload.
Drum loops, percussion and noise-heavy sound design have no tonal center, so key detection is meaningless there. If a melodic track comes back keyless, it may be too short or the tonal content too buried - try a section with clear chords or bass.
Anything your browser can decode: MP3, WAV, OGG, FLAC and usually M4A/AAC. Tempo detection needs at least about four seconds of audio; for key detection, longer excerpts with chord changes give more confident results.
Need to do more than analyze? Load the track into TuttiDAW and edit, loop and mix it right in your browser.
Explore TuttiDAW - the free browser DAW