If the Online Pitch Detector is not detecting your microphone, shows unstable notes, reports the wrong octave, feels delayed, or cannot analyze an audio file, start with the checks below.
Most problems come from microphone permissions, weak or noisy input, browser/device settings, harmonics, or unsupported audio-file behavior rather than from the pitch calculation itself.
Start With These Quick Checks
Before changing advanced settings, try these steps:
- Make sure microphone permission is allowed for PitchDetector.com.
- Confirm the correct microphone or input device is selected.
- Produce one clear, sustained note instead of a chord or rapidly changing sound.
- Reduce background noise and make sure the signal is neither extremely weak nor clipping.
- Reload the page and try again.
If the problem remains, use the section below that best matches what you are seeing.
Microphone Not Working
If the detector does not receive microphone input, check permissions first.
Check Browser Permission
Your browser must allow PitchDetector.com to use the microphone.
If you previously denied or dismissed the request:
- open your browser’s site permissions;
- find the microphone permission;
- allow access for PitchDetector.com;
- reload the tool.
Browser permission behavior varies by platform, so the exact controls may look different on Chrome, Edge, Firefox, Safari, Android, or iOS.
For more information about browser microphone permissions, see the official MDN getUserMedia documentation.
Check Operating-System Permission
Your browser may have permission while the operating system still blocks microphone access.
Check the privacy or microphone settings on your device and make sure your browser is allowed to use the microphone.
Check the Input Device
If your device has several audio inputs, make sure the intended microphone is selected.
This is especially important when using:
- USB microphones;
- audio interfaces;
- Bluetooth devices;
- webcams with built-in microphones;
- external headsets.
Temporarily disconnecting unused audio devices can sometimes make diagnosis easier.
Close Other Audio Applications
Applications such as recording software, video-call tools, streaming software, or DAWs can sometimes interfere with device selection or audio routing.
Close them temporarily and test again.
No Signal or Signal Too Weak
If the tool starts but does not detect a stable pitch, the incoming signal may be too weak.
Try:
- moving closer to the microphone;
- increasing the input level if appropriate;
- singing or playing slightly louder;
- pointing the microphone toward the sound source;
- reducing distance from the instrument.
Do not increase the input so much that the signal clips or distorts.
A strong, clean signal is more useful than simply making the microphone as loud as possible.
Signal Too Loud or Clipping
If the signal is distorted or overloaded, the detector may receive a waveform that is harder to interpret.
Try:
- reducing microphone gain;
- moving slightly farther from the microphone;
- singing or playing at a more moderate level;
- disabling unnecessary boost settings.
If the tool provides a signal-quality indicator, use it together with the note display rather than focusing only on volume.
The Note or Frequency Keeps Jumping
A moving reading does not automatically mean the detector is broken.
Common causes include:
- background noise;
- room reflections;
- strong vibrato;
- weak input;
- clipping;
- chords;
- multiple people or instruments;
- instrument overtones;
- rapid note transitions.
For a more stable test, hold one note for a moment and avoid changing pitch while the detector settles.
Natural vibrato will cause the cents value to move. If you want a stable reference reading, sing or play as steadily as is comfortable.
For a deeper explanation, see Why Does My Pitch Detector Give Unstable Readings?.
The Detector Shows the Wrong Note or Octave
Wrong-note and octave errors are often caused by harmonics.
A musical sound rarely contains only one frequency. For example, a note with a fundamental around 220 Hz may also contain strong energy near 440 Hz, 660 Hz, and higher harmonics.
If an upper harmonic becomes more prominent than the fundamental, a detector may temporarily show a higher octave.
Try:
- holding the note longer after the initial attack;
- reducing background noise;
- changing microphone position;
- producing one isolated note;
- avoiding chords;
- trying a cleaner tone or different vowel when singing.
You can learn more about this behavior in our Methodology and our guide to why tuners sometimes show multiple notes.
The Result Seems Consistently Sharp or Flat
Before assuming the detector is inaccurate, check the tuning reference.
The common default is:
A4 = 440 Hz
but the Online Pitch Detector allows the A4 reference to be adjusted.
Make sure the selected reference matches the tuning system or instrument you are using.
Also remember that a sung or played A4 does not automatically have to be exactly 440 Hz. To test detector accuracy, compare it with a known reference signal, not an unverified sung or instrumental note.
If a verified 440 Hz reference is consistently displayed differently under controlled conditions, that is more useful evidence of a technical issue.
Background Noise Is Interfering With Detection
Environmental noise can compete with the sound you want the detector to analyze.
Common sources include:
- fans;
- air conditioning;
- traffic;
- conversations;
- computer fans;
- electrical hum;
- speakers;
- room echo.
Try:
- moving to a quieter area;
- moving the microphone closer to the intended source;
- turning off unnecessary nearby noise sources;
- reducing speaker volume;
- using headphones when reference audio would otherwise feed back into the microphone.
Some operating systems and browsers provide audio-enhancement or noise-suppression options. These can sometimes help, but speech-oriented processing can also alter musical signals.
If results become less stable after enabling audio enhancements, try turning them off.
For more detail, see Noise and Background Interference.
Microphone Quality Seems to Affect Results
A built-in phone or laptop microphone can often be sufficient for ordinary pitch practice.
A cleaner microphone may improve signal quality, but price alone does not determine whether a microphone will work well for pitch detection.
If you suspect the input hardware is contributing to the problem:
- test the same note with another microphone or device;
- keep the room and sound source as similar as possible;
- compare whether the reading becomes more stable.
Our guide to how microphone quality affects pitch detection accuracy covers this in more detail.
The Detector Feels Delayed
Some delay is normal because the system needs enough audio information to estimate pitch.
Extra latency may come from:
- Bluetooth audio;
- high device CPU load;
- other applications using audio resources;
- browser performance;
- audio routing through external devices.
Try:
- closing unnecessary applications and tabs;
- using a wired audio path instead of Bluetooth when practical;
- testing without external audio-routing software;
- updating your browser;
- testing another modern browser to see whether the issue is browser-specific.
Bluetooth delay mainly affects responsiveness. It does not necessarily mean the detected frequency will be incorrect once the signal reaches the detector.
Audio File Will Not Analyze
The current Online Pitch Detector includes an Audio File mode, but browser support for audio files can vary.
If a file does not work:
- confirm the file is not corrupted;
- try another supported recording;
- try a modern browser;
- make sure the file actually contains audible audio;
- avoid extremely noisy or complex recordings when testing pitch;
- use a recording with one dominant note where possible.
Audio codecs and container formats can behave differently across browsers, even when file extensions look familiar.
A full song or dense mix may also produce unstable results because many frequencies and notes are present simultaneously.
Audio File Works but Microphone Mode Does Not
This is a useful diagnostic clue.
If audio-file analysis works but live microphone mode does not, the pitch-analysis system itself may be functioning while the problem is more likely related to:
- microphone permission;
- input-device selection;
- operating-system privacy settings;
- live audio routing.
Return to the microphone-permission and device-selection checks above.
Microphone Works Elsewhere but Not on PitchDetector.com
An independent microphone test can help narrow down the issue.
For example, a successful browser microphone test suggests that:
- your microphone hardware is functioning;
- the browser can access it in at least one context.
It does not guarantee that every website or tool will work, because site permissions, audio initialization, selected input devices, and application code can still differ.
You can use a browser microphone diagnostic such as the WebRTC microphone test as one additional troubleshooting step.
Then return to PitchDetector.com and re-check site permission and input selection.
The Tool Is Frozen or Not Responding
If the interface stops updating:
- stop the detector if the Stop button still works;
- reload the page;
- close unnecessary browser tabs or CPU-heavy applications;
- reconnect the microphone or audio device if needed;
- try the tool again;
- test another modern browser if the issue persists.
If the page itself loads but the detector remains frozen across multiple browsers or devices, report the problem to us.
Results Changed After Connecting Bluetooth, Headphones, or an Audio Interface
Connecting or disconnecting audio hardware can change the device selected by the browser or operating system.
After changing hardware:
- check which microphone is active;
- reload the detector if necessary;
- verify site permission again;
- confirm that the new input is receiving sound.
If Bluetooth is involved, additional latency may also be noticeable.
Privacy or Microphone Concerns
Troubleshooting microphone access does not require granting permission permanently.
You can deny access or change microphone permission through your browser’s site settings.
For detailed information about browser permissions, audio handling, local processing, and other website data, see Data Security & Audio Privacy.
For broader information about cookies, analytics, and privacy rights, see our Privacy Policy.
Still Not Working?
If you have tried the relevant steps and the problem continues, contact us at:
Please include:
- page URL or tool name;
- whether you used Microphone or Audio File mode;
- device;
- operating system;
- browser and version;
- what you expected to happen;
- what actually happened;
- any visible error message;
- a screenshot if useful.
You can also use our Contact Us page.
For general questions about pitch results, cents, audio files, microphone permissions, and accuracy, see the PitchDetector.com FAQ.
Last reviewed: August 19, 2026