YouTubeBPMFinder.onlineYour taps are the only tempo input
This YouTube BPM finder is a local companion for a video you control elsewhere. Start playback in another window or on another device, choose a recurring pulse, and tap the large surface above with Space, Enter, a mouse, or touch. The page times those human actions. It does not receive the video, hear audio, or know what you are watching. The step-by-step YouTube tap BPM guide explains how to prepare a clean run.
That separation is the product promise. There is no YouTube URL box, embedded player, authorization prompt, microphone permission, upload, or automatic tempo claim. The observer supplies a pulse through taps, and the browser exposes how those intervals behave.
One tap creates a point; two create an interval
The first tap starts a session. Each later tap closes another interval. Eight taps create seven intervals. The page uses performance.now(), a monotonic clock available to the current document, so calculations depend on elapsed page time rather than a readable calendar timestamp.
After at least four taps, a provisional result can appear. A longer clean run usually offers better context, but tapping through a section change can make the summary less representative. Choose a recent-window length from 3 through 20 intervals and stop when the musical evidence changes. The tap section guide can help you select a steady passage first.
A recent median keeps the answer focused
The homepage converts each recent inter-tap interval to BPM and reports the median. That choice resists one unusually early or late tap better than a simple average while keeping the output easy to read. The selected recent-window setting determines how many of the newest intervals participate; older taps fall outside the current answer.
The result also shows half-time and double-time values as arithmetic candidates. They are not automatic musical verdicts. Human anticipation, a missed tap, swing, a fill, browser scheduling, or real performance movement can shift the median, so repeat the same passage when the decision matters.
A twelve-tap example
Imagine twelve taps producing eleven intervals around 500 milliseconds. If the selected recent intervals have a median of 500 milliseconds, the displayed rate is 60,000 ÷ 500 = 120 BPM. The half-time candidate is 60 and the double-time candidate is 240. Those values describe pulse levels; they do not automatically identify which level fits the music.
The homepage does not read or correct the video’s playback speed. If external playback was at 0.75×, record that fact and use the playback speed BPM corrector after tapping. Keeping observed rate and source-time estimate separate prevents a correction from being applied twice.
Select the pulse before selecting a result
A hi-hat subdivision can invite taps at twice the practical beat. A backbeat can invite half-time taps. The half, base, and double candidates are a listening aid, not a detector. Choose the pulse that matches your task. The subdivision guide explains how to keep one pulse level through a session.
More focused tools handle questions the homepage intentionally leaves out. Use the tap window planner before a session, the stability checker for a prepared interval list, or the half-time and double-time checker for a prepared BPM value. Their inputs remain separate so one result is not confused with another.
Product limitations
Tap timing cannot identify a song, infer meter, isolate drums, distinguish intentional swing from error, or establish the tempo of every section. A session describes one observer, one pulse choice, one playback speed, and one period of tapping. Browser clock resolution and event scheduling can introduce small variation, especially when the page is backgrounded or the device is busy.
The site never fetches, embeds, downloads, records, parses, or listens to YouTube media. It does not call the YouTube API, use a microphone, read a player setting, access an account, search a song library, store a history, or send tap values to an analytics vendor.
Local memory and independent identity
Tap times, optional labels, settings, and results live in current-page memory. Reset removes the session, and closing or reloading ends the defined state. Copy places a plain-text card on the device clipboard when browser permission allows; the operator does not receive it.
YouTube is a trademark of Google LLC. This independent site is not affiliated with, endorsed by, sponsored by, or operated by Google LLC or YouTube. Its violet, amber, aqua, and lavender pulse-lantern identity avoids logos, thumbnails, player controls, and red-and-white trade dress.
Frequently asked questions
Can I paste a YouTube link?
No. Control playback elsewhere and tap on this page. No URL retrieval or embed exists.
Which key should I use?
Space or Enter works when focus is on the tap surface. Pointer and touch input are also supported. Held-key repeats are ignored.
Is median BPM the correct answer?
No summary is automatically musically correct. Median interval timing is simply less influenced by one extreme interval.
Does slowing playback change source BPM?
It changes observed tap rate. The homepage does not read playback speed; use the dedicated speed corrector and keep both observed and source-time values in your note.
Tap a clean run and inspect the result
Use the tap surface above, choose one pulse, and collect at least four taps. Read the recent-median BPM and compare its half-time and double-time candidates before repeating the same section.