The Online Metronome accepts only plain whole-number tempos from 30 to 240 BPM and measures from 1 to 12 beats, so begin troubleshooting by validating those two fields. Use the Online Metronome to generate a simple repeating click in the current browser tab, with a higher pitch on beat one.
Troubleshooting has three layers: whether the values are valid, whether the browser can start and route the audio, and whether its scheduler delivers each click on time. The first two are setup problems; inconsistent timing is a known limitation of this lightweight browser tool. It is intended for ordinary practice and rough tempo reference, not studio-grade synchronization.
All sound is generated locally with the Web Audio API in the current tab. The metronome does not request microphone access, record audio, upload files, use an account, or send sound to a server. A microphone prompt is therefore not part of normal operation. See why this browser metronome does not use a microphone or upload audio for the privacy distinction.

Know What the Tool Can Control
The operating model is deliberately narrow. Start closes any older audio context before creating a new one. Stop closes the audio context, cancels the next scheduled click, clears the timer, and resets the visual beat. Editing either numeric field stops playback before the new value can take effect, which prevents the displayed tempo and active timer from drifting apart.
| Control or setting | Supported behavior | Troubleshooting meaning |
|---|---|---|
| Tempo field | A plain whole number from 30 through 240 BPM | Spaces, signs, decimals, exponent notation, units, blank values, and out-of-range values are rejected rather than rounded or capped. |
| Beats-per-measure field | A plain whole number from 1 through 12 | Malformed or out-of-range values fail, so check this field before expecting playback. |
| Playback controls | Start creates local clicks; Stop closes the audio context and cancels the next scheduled click | Use Stop for a clean reset. A playing guard disables duplicate starts. |
| Field edits | Changing the tempo or measure count stops playback before the new value takes effect | Select Start again after making an edit. |
| Audio startup | Unavailable Web Audio support or rejected startup shows an error and leaves no stale playing state | Confirm that the browser can initialize Web Audio for the page. |
This tool does not provide tap-tempo analysis, subdivisions, swing, polyrhythm, DAW or MIDI synchronization, latency calibration, or recording alignment. If one of those features is the real goal, changing the metronome controls will not supply it. Enter the measure as a beat count rather than a slash-style time signature. For ordinary scales, rhythm exercises, reading, or checking a rough tempo, the simple click is the intended workflow.
Run the Troubleshooting Workflow
- Validate the tempo. Enter digits only, using a value from 30 through 240. Do not add “BPM,” spaces, a sign, a decimal point, or exponent notation. A malformed value is rejected instead of being rounded, capped, or interpreted in an unexpected way.
- Validate the measure count. Enter a whole number from 1 through 12. The field represents the number of beats in the measure, not a text time-signature label. If you edited either field during playback, the resulting stop is expected; press Start again after the value is correct.
- Start playback from the tool. Choose the validated tempo and measure length, then select Start. Start closes any older audio context before creating a new one, while the playing guard prevents duplicate starts from creating overlapping playback.
- Read any startup error before adjusting volume. If Web Audio is unavailable or startup is rejected, the tool displays an error and does not retain a stale playing state. The W3C Web Audio API specification describes the browser capability involved, and playback cannot proceed until the environment can initialize it.
- Check the complete output path. Confirm that the browser tab is not muted, then check browser or device gain, the selected speakers or headphones, and the system output. Device volume, speakers, headphones, browser gain, and the listening environment determine the actual loudness. Begin with a low level, especially when using headphones.
- Keep the page active and its workload light. Background tabs, power-saving modes, busy main threads, Bluetooth latency, browser policies, and operating-system scheduling can delay audible clicks. Move the metronome tab to the foreground, close demanding pages for the test, and compare wired output with Bluetooth output if a connection-specific delay is suspected.
- Verify the measure by listening for its boundary. Beat one is higher than the remaining beats, making the measure boundary audible. If clicks are present but the accent is difficult to distinguish, recheck the beats-per-measure value and test at a modest volume in a less distracting listening environment.
- Stop cleanly before another test. Select Stop to cancel the next click, clear the timeout, close the audio context, and reset the visual beat. Then select Start again. This sequence is preferable to leaving a previous context running while testing new settings.
Match the Symptom to the Check
Use the visible result to decide which layer needs attention. A rejected input, a failed audio startup, a silent output path, and delayed scheduling produce different symptoms even though they all appear while using the same tool.
| Symptom | Likely area | Corrective check |
|---|---|---|
| An error appears after Start | Web Audio initialization | Use a browser environment that supports Web Audio startup. The metronome will not continue with a false playing state after rejection. |
| The visual beat advances but no sound is heard | Browser or device output | Unmute the tab, check browser and device gain, and confirm that the intended speaker or headphone output is active. |
| Clicks are audible but very soft | Output level or environment | Raise the browser or device gain modestly and compare the current output with another set of speakers or headphones. |
| Clicks arrive late or their spacing feels uneven | Browser scheduling or output latency | Keep the tab active, reduce page load, check power-saving settings, and test non-Bluetooth output when possible. |
| Playback stops immediately after a field edit | Expected edit behavior | Confirm the new value is valid, then select Start again. |
| The first beat does not sound distinct | Measure selection or listening conditions | Check the measure count and listen again at a reasonable level. The first click uses 1320 Hz while later clicks use 880 Hz. |
Separate Setup Errors from Timing Delay
The interval in seconds is 60 divided by the BPM. One worked example is 120 BPM: 60/120 = 0.5 seconds, so the intended spacing is half a second. This calculation defines the requested beat interval; it does not guarantee that every scheduled callback and audible click will reach the listener at precisely that moment.
The metronome calculates the interval and asks the browser to schedule the next JavaScript callback. Browser timers can be delayed by load, background throttling, power saving, Bluetooth, and operating-system scheduling. That can make the visual count appear smoother than the sound arriving from the output device. Web Audio generates the actual click, but it does not turn this page into a sample-accurate studio clock.
Do not use the display to certify the exact timing of a recorded performance, align a take to a DAW, or act as a MIDI clock. There is also no latency-calibration function. The supported purpose is a lightweight pulse for scales, rhythm exercises, reading, and checking a rough tempo, where small browser scheduling delays are acceptable.
Check the Accent and Output Level
The accent is a product cue, not a standardized tuning reference. Beat one uses a 1320 Hz click, while later beats use 880 Hz so the start of each measure is easier to recognize. These frequencies do not represent concert pitch or a note name. If every click seems identical, check that the measure was entered correctly and compare the output at a moderate level before deciding that the accent is missing.
Each sound is a short oscillator click with a quick gain envelope rather than a sustained tone. A click that seems too faint may be masked by the room, speakers, headphones, or device settings. Raise the output carefully, and use the immediate Stop control if the level becomes uncomfortable. The tool is not hearing protection or a calibrated sound-pressure source, so it should not be treated as either one.
Decide When the Browser Is the Limitation
After validating the fields, performing a clean Start and Stop cycle, keeping the tab active, and checking the output path, remaining inconsistencies in click timing are a browser or device constraint. Use the metronome as a rough pulse for practice, but choose a specialized timing workflow if exact recording alignment, MIDI synchronization, subdivisions, or calibrated latency is required.
If a startup error remains, the current environment cannot initialize the browser audio needed by the tool; changing the BPM will not resolve that. The same cleanup runs when the metronome leaves the page, closing its audio context and canceling scheduled work. If the problem is specifically discovering a tempo by tapping, this version cannot analyze taps, so enter a supported BPM manually instead.
For a deeper look, see How Do I Troubleshoot Audio Effects Online Problems?.