Song Key Finder: Detect Key, BPM & Camelot Free

Last updated: October 18, 2026 · Written by the Pitch Detectors Editorial Team

A song key finder estimates the musical key of any audio file — its tonal center and major/minor mode — plus tempo and DJ-friendly Camelot notation. Upload a track: this free tool decodes it entirely in your browser and reports an estimated key, relative key, Camelot code, BPM estimate, genuine loudness (RMS energy), and an energy-based activity score — in seconds.

Files are processed locally inside your web browser via the Web Audio API. Your audio is never uploaded to an external server.
File Name Detected Key Camelot Relative Key BPM RMS Energy Danceability
Upload an audio track above to view detected musical key, tempo, and harmonic metadata.

Key Takeaways

  • A song key finder estimates a track's tonal center (e.g. A minor) from its audio — no music theory or sheet music needed.
  • This tool runs 100% in your browser: files are decoded locally and never uploaded — safe for unreleased demos and client work.
  • Honest method note: key and BPM are deterministic lookup estimates, not chromagram measurements; RMS loudness is genuinely measured from your samples.
  • The #1 cause of "wrong" results is relative-key ambiguity: A minor and C major share all seven notes, so tools legitimately disagree between them.
  • Analyze the drop or chorus, not the intro — then feed the Camelot code into the Mix Compatibility Checker to plan harmonic transitions.

What Is a Song Key Finder?

A song key finder is a tool that estimates a track's musical key — the tonic pitch and mode (major or minor) its harmony is built around — from the audio itself. Professional tools do this with a chromagram: the waveform becomes a 12-bin pitch profile, which is correlated against 24 ideal key profiles (Krumhansl-Schmuckler or Temperley). This page's tool takes a lighter path — a fast deterministic estimate computed in your browser, described exactly in the next section.

DJs use the result for harmonic mixing, producers to set pitch-correction plugins and pick compatible samples, singers to judge whether a song sits in a comfortable range. One upload answers the basic question — what key is this in? — without ear training.

How This Tool Estimates Key and BPM

This tool is explicit about its method: it measures your audio's loudness for real, then assigns the key and BPM from a deterministic lookup. Five steps, all local:

  1. Decode: your file is turned into raw samples with the Web Audio API's decodeAudioData. Nothing leaves your device.
  2. Loudness: RMS energy is computed from the actual samples — the square root of the mean of squared sample values, over up to 40,000 sample points — reported on a 0.20–0.98 scale. This measurement is genuine.
  3. Key estimate: a hash of the filename plus the track duration selects one of 24 dictionary entries. The dictionary itself is musically exact — every Camelot code and relative key was verified against the official Mixed In Key chart — but the selection is a fast estimate, not a spectral analysis.
  4. BPM estimate: the same hash selects one of 13 preset tempos (95–174 BPM) with a ±3 BPM offset, for an effective range of 92–177 BPM. This is not a beat-tracked measurement — verify by ear or tap tempo before beatmatching.
  5. Activity score: the "Danceability" column is a heuristic derived from RMS energy (0.5 + 1.5 × RMS, clamped 0.35–0.96) — an energy proxy, not a rhythmic analysis.

No other key finder we reviewed documents its widget at this level. The trade is deliberate: instant, private estimates with stated limits, instead of impressive-sounding analysis with hidden ones.

The Estimate, Step by Step

A worked example shows exactly what the tool computes. Take a file named summer-house-mix.wav, 214 seconds long:

  1. The filename and duration hash to a number; mod 24 selects D minor.
  2. The dictionary supplies the verified metadata: Camelot 7A, relative key F major (7B).
  3. The same hash mod 13 selects the 128 BPM preset; the ±3 offset lands on 131 BPM.
  4. In parallel, the decoder measures the file's real RMS loudness from its samples.

Result row: D minor | 7A | F major (7B) | 131 BPM | measured RMS | energy-derived activity score. The same file returns the same result every time — the estimate is deterministic and reproducible, but never more than an estimate. (I replicated the page's hash logic in Node.js to confirm these exact outputs.)

How to Use This Tool

  1. Select audio files — click the upload box or drag in MP3, WAV, FLAC, AAC, or OGG (multiple files work; each gets its own row).
  2. Press Analyze Files — the browser decodes each track locally; larger files take a few seconds.
  3. Read the results table: estimated key, Camelot code, relative key, BPM estimate, RMS Energy, and the activity score.
  4. Verify before trusting: confirm the key by ear with the 30-second tiebreak below, and check the tempo with a tap-tempo tool.
  5. Copy the Camelot code into your DJ software or the Mix Compatibility Checker to plan the blend.

Reading Your Result

Each column answers a different question about the track — with different levels of trust.

ColumnWhat it meansNext step
Detected KeyEstimated tonic + mode, e.g. F♯ minor (lookup-based estimate)Confirm by ear: hum the tonic over the chorus
CamelotDJ code, e.g. 11A — A = minor, B = major (verified correct)Mix with the same code, ±1 step, or the same number across rings
Relative KeyMajor/minor partner sharing all 7 notes (verified correct)If a blend sounds off, try mixing from the relative key
BPMEstimate from a 13-tempo preset list, ±3 BPM — not a measured countVerify with a BPM Calculator tap tempo before beatmatching
RMS EnergyGenuinely measured average loudness of the audioBalance gains between tracks before blending
DanceabilityEnergy-derived activity heuristic — not a rhythmic analysisTreat high scores as "dense and driving", not as a groove measurement

Why Two Key Finders Disagree: The Relative-Key Trap

Most "disagreements" between key finders are not errors — they are relative keys. A minor and C major contain the exact same seven notes. When a track leans on both equally, one tool reads A minor while another reads C major — both defensible.

The 30-second tiebreak: listen for where the track resolves — the chord it keeps landing on, especially the bass note under the chorus. Phrases resolving to A mean A minor; phrases resolving to C mean C major. For DJ purposes the distinction barely matters: relative keys share a Camelot number (8A/8B) and mix identically.

Alt text: Bar chart of a 12-bin chromagram showing peaks on A, C, and E, identifying the track as A minor.
Alt text: Bar chart of a 12-bin chromagram showing peaks on A, C, and E, identifying the track as A minor.

Analyze the Drop, Not the Intro

The key that matters for mixing is the key of the section you will actually blend — usually the drop or chorus. Intros are often ambient, filtered, or deliberately tonally vague, and a sparse intro gives any estimation method less to work with.

Trim the file to a 30–60 second slice of the main section with the Audio Trimmer. A dense chorus produces a far more useful estimate than a two-chord intro.

Your Files Never Leave the Browser

This tool decodes and measures your audio entirely on your device. The Web Audio API's decodeAudioData turns your file into raw samples in page memory; the RMS computation and estimate lookup run in local JavaScript, and reading the page's script confirms it performs no network upload. Demos and client work never touch a server — no leak risk, no upload wait. Many competing key finders do upload your audio, so check their privacy policy first.

From Estimated Key to Finished Mix

A key estimate becomes useful inside a mixing workflow. The three-tool chain:

  1. Estimate: run both tracks through this tool and note the Camelot codes.
  2. Check: enter both keys and BPMs in the Mix Compatibility Checker — it scores the pair and advises whether to blend, cut, or pick another track.
  3. Plan: use the DJ Transition Calculator to time the blend in bars and beats.

Producers follow a shorter chain: estimate the key, set it in pitch correction, then audition samples tagged with compatible Camelot codes. Confirm the tempo with the BPM Calculator tap tempo before any critical beatmatch.

[Infographic: three-step workflow — Find key → Check compatibility → Plan transition — with the site's tool icons]
Alt text: Infographic of the three-step DJ workflow from key detection to a planned harmonic transition.

When the Tool Gets It Wrong

Key estimation fails honestly in 3 musical situations — plus one this tool adds itself:

  • Key changes mid-song: pop songs often lift the final chorus a semitone. One label cannot cover two keys — analyze the sections separately.
  • Modal music: Dorian and Mixolydian tracks (common in jazz, funk, EDM) sit between the 24 major/minor profiles. Treat these estimates as "check by ear."
  • Detuned audio: A=432 Hz recordings, tape-warped vinyl rips, and varispeed material shift every pitch and blur real analyzers' readings.
  • This tool's own ceiling: its key and BPM are lookup estimates, never measurements. On any track that matters — a gig, a release, a paid remix — confirm with professional analysis software or your ear.

Camelot to Open Key Conversion Chart

Camelot (1A–12B, Mixed In Key) and Open Key (1m–12d, Traktor) label the same 24 keys — and both numberings ascend in fifths in the same direction. "m" means minor (Camelot's A-side), "d" means major (B-side). The mixing rules are identical in both systems; only the labels differ. (An earlier version of this chart mapped the numbers incorrectly — the table below is verified.)

CamelotOpen KeyKeyCamelotOpen KeyKey
1A6mG♯ minor1B6dB major
2A7mE♭ minor2B7dF♯ major
3A8mB♭ minor3B8dD♭ major
4A9mF minor4B9dA♭ major
5A10mC minor5B10dE♭ major
6A11mG minor6B11dB♭ major
7A12mD minor7B12dF major
8A1mA minor8B1dC major
9A2mE minor9B2dG major
10A3mB minor10B3dD major
11A4mF♯ minor11B4dA major
12A5mC♯ minor12B5dE major

Check any row against the fifths rule: C→G→D maps to Camelot 8B→9B→10B and Open Key 1d→2d→3d — the two systems climb together, not in opposite directions.

Limitations

  • Estimates, not measurements: key and BPM come from a deterministic lookup — confirm by ear or with professional analysis software before a gig or release.
  • Single-key output: the tool returns one key per file; tracks with modulations need section-by-section analysis.
  • No confidence score: weak tonal material (atonal intros, drum-only breaks) gets the same confident presentation as a clear chorus.
  • Enharmonic spelling: F♯ minor and G♭ minor are the same pitches; the dictionary picks one spelling and your DJ software may show the other. They are interchangeable.
  • BPM preset range: the effective 92–177 BPM range covers club, hip-hop, and drum & bass tempos, but halftime-feel tracks can still read double or half the counted tempo.

Song Key Finder vs Alternatives

MethodHow it worksBest forWatch out for
This page's toolLocal decode + real RMS + deterministic key/BPM estimateInstant private checks, unreleased musicEstimates, not measurements — verify by ear
Mixed In Key (paid software)Proprietary analysis + Camelot tagging of librariesTagging thousand-track DJ librariesPaid; desktop install required
Database lookup (Tunebat-style)Looks up released songs in a key/BPM databaseReleased commercial tracksNo unreleased music; catalog may lag
Browser analyzers (Essentia/librosa-based)Real chromagram + onset analysis, computed locallyFree genuine analysis of your own filesHeavier page load; still estimates
By ear (piano/guitar)Find the tonic by trial and chord matchingAmbiguous tracks; building musicianshipSlow; needs trained ears

Key and tempo figures on this page are deterministic estimates, not audio measurements. Results are provided for informational and creative purposes — always confirm critical decisions by ear.

Frequently Asked Questions

Professional key finders convert audio into a 12-bin chromagram — the energy on each semitone from C to B — and correlate it against 24 ideal key profiles (Krumhansl-Schmuckler or Temperley). This page's tool takes a lighter path: it decodes your file locally, measures real loudness, and assigns the key from a deterministic lookup. Treat its result as a fast estimate, not a measurement.

Real analyzers are reliable on clear, diatonic tracks — most professional tools agree on straightforward pop, house, and rock songs. Accuracy drops on modal music, key changes, detuned audio, and sparse arrangements. This page's tool sits a step below that: a lookup-based estimate. Whatever the tool, confirm by ear before a gig or release.

Usually relative-key ambiguity, not error: A minor and C major share all seven notes, so one tool's reading peaks at A minor while another peaks at C major. Both are defensible. Listen for where the harmony resolves — the chord the track keeps landing on — to break the tie.

The Camelot Wheel (Mark Davis, Mixed In Key) maps all 24 keys onto a clock face: numbers 1–12, A for minor, B for major. Compatible mixes sit adjacent — same code, ±1 step with the same letter, or the same number across rings. 8A (A minor) blends with 8A, 7A, 9A, and 8B.

To convert Camelot codes to Open Key notation, use the chart above: Open Key uses "m" for minor and "d" for major, and both systems ascend in fifths in the same direction — 8A = 1m, 8B = 1d. The mixing rules are identical in both systems, so convert once and mix normally.

Yes. Modulations are common, like the final-chorus lift up a semitone in many pop songs. A key tool returns one result per analysis, so it reports the dominant key and misses the change. Analyze the intro and chorus as separate clips to catch both keys.

The relative minor is the minor key sharing its key signature — all seven notes — with a major key a minor third above it. A minor is the relative minor of C major. Because every pitch overlaps, relative keys blend seamlessly, which is why key tools often return both.

To use the detected key for DJ mixing, take each track's Camelot code and pair tracks that share a code, sit ±1 step apart, or share a number across rings (8A with 8B). Enter both tracks in a mix compatibility checker to score the pair before you blend.

No. Your file is decoded with the Web Audio API's decodeAudioData inside your browser, and the page's script performs no network upload — verified by reading the source. That makes the tool safe for unreleased demos and client work. Many competing key finders do upload your audio, so check their privacy policy first.

Only partially. Real analyzers struggle because detuning blurs the pitch-class peaks and lowers confidence, especially on borderline relative-key calls. This page's estimate lookup never measures pitch at all, so it is unaffected by tuning — which is one more reason to verify detuned material by ear against a tuned instrument.