Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Check the address and browser permission
Use the HTTPS production site and inspect its microphone permission in the browser’s site controls. Reset a prior block only if you intend to be asked again.
Check operating-system access
Confirm the browser itself is allowed to use the microphone in your system privacy settings, then fully restart it if the system requires that.
Retry one controlled recording
Select Record, speak briefly, stop, and preview. This recorder is mono and permits up to ten minutes of active audio.
Separate the three permission layers
The page must run in a secure context, the browser must have a site-level microphone decision, and the operating system may need to allow that browser to access the selected input. A denial at an earlier layer can prevent a new browser prompt.
Changing a browser setting cannot grant a system-level permission, and changing a system permission does not remove a prior site block. Check one layer at a time so the next symptom has a clear meaning.
Swipe or scroll sideways to read all columns.
| Observation | Likely layer to inspect | Controlled next check |
|---|---|---|
| No prompt after a prior block | Browser site permission | Reset the site microphone decision |
| Browser cannot access any site microphone | Operating-system privacy | Allow the browser, then restart it |
| Prompt allows access but no signal appears | Input device or system routing | Test the selected microphone in another trusted app |
Use one short diagnostic instead of repeated attempts
Close other applications that might reserve an input, select the intended microphone in your system settings if available, then record a short phrase. Stop and preview before attempting a longer take.
This procedure does not test every headset, browser, or operating system. Keep the displayed error text and the browser version if the controlled attempt still fails.
Know what this recorder does not request
The recorder captures one mono microphone input. It does not record system audio, another tab, stereo pairs, or multiple tracks, and it does not provide cloud backup or automatic noise removal.
After a successful take, save WAV or MP3 and keep a local copy. A preview is not a permanent backup.
Permission-layer worksheet: change one layer at a time
Follow this sequence: secure top-level page → saved site permission → browser’s operating-system permission → available input device → a short recording. Record the visible result after each step; stop when the recorder starts and its input meter responds. This is a diagnostic decision path, not an automated inspection of your computer.
If permission is already granted, a second prompt may correctly never appear. Press Start recording and inspect the actual status before resetting permissions. If access is denied at the operating-system layer, changing only the site setting cannot grant the browser access.
Swipe or scroll sideways to read all columns.
| Observation | Possible explanation | Next check |
|---|---|---|
| No prompt, recorder starts | Existing permission may already allow access | Make and save a short check |
| Immediate permission-denied status | Saved site denial or OS restriction | Inspect the named permission layer |
| Request remains pending | Prompt may be unanswered or hidden | Check browser UI and OS dialog |
| No device found | No usable microphone reported | Connect or choose a working input |
Common questions
Why does the site not ask again?
Browsers generally retain a prior allow or block decision. Inspect the site permission rather than expecting a new prompt.
Does a secure site guarantee microphone access?
No. HTTPS is required for this browser API, but browser and operating-system permission can still block access.