Local audio analysis
Key & BPM Finder — estimate a song's key and tempo
A key finder estimates a song's musical key, tempo, and Camelot code from a local audio file. Audio is decoded and analyzed in this browser.
Analysis result
Your BPM, key, mode, and Camelot code will appear here.
Experimental estimate. Results are hidden when beat or tonal evidence is weak; ambiguous harmony can still produce a neighboring key. Analyzed locally in your browser; audio is not uploaded for this check.
A key finder gives you two useful coordinates for working with a track: its musical key and its tempo in beats per minute. Choose an audio file on your device to analyze it locally in your browser, then use the result to plan a mix, a cover, or your next arrangement.
01
Key and BPM are different musical clues
BPM, or beats per minute, describes speed. A track at 120 BPM has a regular pulse that is twice as fast as one at 60 BPM, even though those two readings can sometimes describe the same groove at different beat interpretations. Musical key describes the pitch center: the note and scale that make the harmony feel settled. A fast song can be in A minor, and a slow song can be in A minor; tempo and key answer different questions.
The Camelot Wheel translates common key names into a DJ-friendly system such as 8A or 9B. Nearby Camelot positions often share notes and can make harmonic transitions easier to audition, but the wheel is a planning aid rather than a rule. Use the detected key as a starting point, listen to the phrase boundaries, and account for edits, samples, tuning, and modulation.
Major and minor labels describe the scale quality, while relative keys share the same key signature: C major and A minor are relative keys. They can contain the same notes but have different tonal centers and emotional pull. A displayed result such as F♯ minor may also be shown with its Camelot equivalent, so you can move between theory terminology and a practical DJ notation.
02
How a Key Finder Analyzes a Local Audio File
Select one supported audio file from your device. The browser first reads and decodes the complete file locally; the key and BPM algorithms then use a middle window of up to 90 seconds as their analysis sample. Files can be up to 20 MB and 10 minutes long.
Keep the tab open while the file is being decoded and analyzed. Browser decoding depends on the file format, codec, device, and available memory; a file that plays in one application may not decode in every browser. The audio is analyzed on your device rather than uploaded as part of this tool's normal workflow.
When you need a quick tempo check without automatic file analysis, use BPM Tapper and tap along with the beat. Manual tapping is useful for live listening and for checking whether an automatic reading represents the half-time or double-time feel you hear.
03
Useful starting points for DJs and musicians
DJs can compare a track's BPM and Camelot position before preparing a harmonic mix. Matching or gently changing tempo helps preserve the groove, while neighboring keys can suggest a transition worth testing. Preview the blend: vocals, bass notes, tuning, and musical phrasing can matter more than a simple wheel distance.
For an instrumental, the detected key can provide a sensible first pitch for a vocalist or cover arrangement. A singer may transpose the song to a comfortable range rather than perform in the original key; the result is a reference point, not a fixed requirement. If you are removing vocals or creating an accompaniment, checking the instrumental separately can also reveal whether the harmony remains clear.
Producers and arrangers can use key and tempo notes to organize samples, build a chord palette, sketch a bass line, or prepare a DAW session. Write down the source file, the reported values, and any tuning or tempo changes you hear. That small record makes it easier to revisit a decision when the song contains a modulation or a flexible live performance.
04
How to read a key, scale, and Camelot result
A result normally combines a tonic note with Major or Minor, such as G Major or E Minor. The tonic is the pitch that feels like home; the scale quality describes the interval pattern around it. Relative-key information can explain why two labels use the same notes while still sounding centered on different notes.
Camelot notation adds a number and A/B letter to support quick harmonic-mixing decisions. A and B distinguish the minor and major sides of the wheel, while adjacent numbers represent nearby tonal relationships in the system. Treat this notation as a compact map: confirm the musical relationship by ear before changing a track's pitch or committing to a transition.
BPM is likewise an estimate of the track's perceived pulse, not a promise that every section has one unchanging tempo. Half-time arrangements, double-time readings, swing, rubato, intros without drums, and tempo automation can all produce a value that differs from a musician's preferred count. Compare the number with a metronome, grid, or manual tap when the context matters.
05
Why an analysis may be uncertain
Key detection is harder when a track has a quiet or ambiguous bass, dense effects, layered chords, strong borrowed notes, or more than one tonal center. A short intro, an exposed vocal, a live recording, or a song that changes key can give the analyzer less consistent evidence. BPM detection can likewise be affected by syncopation, sparse percussion, swing, pauses, and half-time or double-time interpretations.
Use the reported key and BPM as practical guidance and verify important decisions by listening. Try a chorus or another representative passage, compare the value with a piano or DAW keyboard, and check the beat with BPM Tapper when needed. The tool may not return a useful result for every file, and an unclear result is a reason to investigate the arrangement rather than force a label.
For release preparation, keep the original audio, note any pitch or tempo adjustment, and test the final edit again. A converted file, a live version, or a remaster can have different timing and tuning from the source you first analyzed.
FAQ
Key & BPM Finder FAQ
Answers to common questions about local audio analysis, key notation, tempo readings, and practical music workflows.
How do I find a song's key?
Choose a local audio file and the browser estimates its key as a note with Major or Minor. Treat the result as a starting point and confirm important choices by listening.
Can the tool detect both key and BPM?
Yes. A supported local file can produce estimates for BPM, musical key, Major or Minor, Camelot code, and duration, although weak evidence may leave one or more values Uncertain.
Why might the detected key be uncertain or wrong?
Modulation, complex harmony, sparse rhythm, live noise, weak bass or stable pitch, and an exposed vocal can reduce the evidence. The analyzer checks up to a middle 90-second window, so compare another representative passage before treating the estimate as final.
What do Major, Minor, and Camelot mean?
Major and Minor describe scale modes around a tonal center, while Camelot is a DJ-friendly code for planning harmonic transitions. Camelot is not a third kind of key, and a nearby code still needs an audio check.
Is my audio uploaded, and do I need an account?
No account is required, and the selected file is decoded and analyzed locally in your browser rather than sent to the server. The file still needs to meet the 20 MB and 10-minute limits, and decoding depends on browser support.