Online Metronome & Tap Tempo
Places short sine clicks every 60/BPM seconds. Every fourth click uses 1200 Hz; the others use 880 Hz. Tap tempo averages up to eight recent taps from the last five seconds.
About this online metronome & tap tempo
Online Metronome & Tap Tempo — browser-based utility.
How this tool works
Places short sine clicks every 60/BPM seconds. Every fourth click uses 1200 Hz; the others use 880 Hz. Tap tempo averages up to eight recent taps from the last five seconds.
- Set the visible controls to: Duration (seconds) = 3; Tempo (BPM) = 120
- Click “Process locally”.
- Download the result and inspect: czoa-metronome-tap-tempo.wav — PCM16; 48000 Hz; 1 channel; 144000 frames; 6 clicks / 0.5 s
Worked example
Scenario: Set the visible controls to: Duration (seconds) = 3; Tempo (BPM) = 120 Click “Process locally”. Download the result and inspect: czoa-metronome-tap-tempo.wav — PCM16; 48000 Hz; 1 channel; 144000 frames; 6 clicks / 0.5 s
Sample input:
Illustrative output:
Limits and verification
Tempo must be 20–300 BPM and duration 0.2–30 seconds. The accent cycle is fixed at four beats. A click ending at the file boundary may be truncated; this exports WAV rather than running a continuous timing clock.
Examples demonstrate an expected workflow; they do not prove every input or every branch of an external specification. Check important results with an independent source before using them for money, security, compliance, safety, or irreversible file changes.
Browser processing boundary
Tool input is processed by code running in the browser and is not intentionally sent to a CZOA processing API. The page can still request ordinary site assets, analytics, or advertising when those services are enabled. Browser extensions and managed-device software remain outside this tool's control.
Relevant references
These references govern or help explain the format, protocol, or calculation used here. Listing a reference does not claim certification or complete implementation of every optional feature.
- W3C Web Audio API 1.0 — browser decoding and offline rendering
- Microsoft RIFF/WAVE PCM and WAVEFORMATEXTENSIBLE
Content owner: CZOA Tools · Last reviewed: 2026-09-15 · Review methodology
How to use it
- Set the visible controls to: Duration (seconds) = 3; Tempo (BPM) = 120
- Click “Process locally”.
- Download the result and inspect: czoa-metronome-tap-tempo.wav — PCM16; 48000 Hz; 1 channel; 144000 frames; 6 clicks / 0.5 s
Frequently asked questions
How does Online Metronome & Tap Tempo process the signal or file?+
Places short sine clicks every 60/BPM seconds. Every fourth click uses 1200 Hz; the others use 880 Hz. Tap tempo averages up to eight recent taps from the last five seconds.
How can I reproduce the Online Metronome & Tap Tempo example?+
Set the visible controls to: Duration (seconds) = 3; Tempo (BPM) = 120 Click “Process locally”. Download the result and inspect: czoa-metronome-tap-tempo.wav — PCM16; 48000 Hz; 1 channel; 144000 frames; 6 clicks / 0.5 s
What limits apply to Online Metronome & Tap Tempo?+
Tempo must be 20–300 BPM and duration 0.2–30 seconds. The accent cycle is fixed at four beats. A click ending at the file boundary may be truncated; this exports WAV rather than running a continuous timing clock.
What does browser-isolation evidence establish for the metronome?+
Network requests observed during the example contained no selected-audio payload while the fixture generated a finite click WAV and FFmpeg decoded it. This supports only the tested browser value path, not clock accuracy outside the rendered file or every resource and extension environment.