When Mac dictation is not working, test the input path in this order: microphone, permissions, shortcut, focused text field, then mode and connectivity. Change one thing at a time. A short test in Notes tells you whether the failure belongs to macOS, the dictation app, or the field where text should appear.
Setting up speech to text for the first time? Use the complete speech-to-text setup guide for Mac. This page starts with a live dictation workflow that has already failed.
Start With One Plain Notes Test
Open Notes, create a blank note, click in the note body, and type a few characters. You now know the field accepts text and the cursor is active. Leave it there for the first voice test.
If you use Apple's built-in Dictation, start it with the Microphone key when available, your configured Dictation shortcut, or Edit > Start Dictation. Apple documents all three in its current Dictation guide.
If you use Paraspeech, hold the assigned recording shortcut, speak, then release it. The current Paraspeech docs use Control as the default and require Microphone and Accessibility permission for this Mac flow. After processing, text goes to the current cursor.
Your result chooses the next check:
| What happens in Notes | Next check | What the result means |
|---|---|---|
| The Mac input meter does not move when you speak | Audio input | macOS is not receiving a usable signal from the selected microphone. |
| The meter moves, but the app cannot listen or detect its shortcut | Permissions | The audio device works; app authorization is the next boundary. |
| Permissions are on, but the trigger does nothing | Shortcut | Confirm the shortcut you are pressing and whether the app expects a hold or a press. |
| Recording or processing starts, but no text appears | Text-field focus | Prove that the cursor is in an editable field before investigating the target app. |
| The test works with a connection but fails without one | Mode and connectivity | Check whether the active mode needs internet or a downloaded local model. |
| Notes works, but another app does not | Target app | The shared Mac input path works; isolate that app's editor or focus behavior. |
1. Prove the Mac Is Receiving Audio
Open System Settings > Sound > Input and select the microphone you intend to use. Speak at your normal volume and watch the input level. Apple's current Dictation troubleshooting guide recommends checking the selected microphone and input volume when the Mac does not respond to your voice.
No movement means you should stay at this layer. Confirm that an external microphone is connected and selected, or select the built-in microphone. Shortcuts and text insertion cannot compensate for missing audio.
A moving meter proves only that the microphone reaches macOS. It does not prove that a particular app may use it. Continue to permissions.
2. Check the Permissions the App Uses
For Paraspeech, open System Settings > Privacy & Security > Microphone and confirm that Paraspeech is allowed. Apple documents that path in Control access to the microphone on Mac.
Next, open System Settings > Privacy & Security > Accessibility and confirm Paraspeech there. Paraspeech uses Accessibility permission to detect its shortcut across apps. Apple's Accessibility permission guide explains how to enable a trusted app and add one that is not listed.
If macOS refuses the permission, or the app never appears after requesting access, stop treating the symptom as a recognition problem. The failing layer is authorization or the platform permission flow.
3. Verify the Shortcut You Are Using
For Paraspeech, check Settings > General > Recording Shortcut. Control is the documented default, but your setting may differ. Hold the configured key while speaking and release it when you finish. Tapping the key is not the same test as the documented hold-talk-release flow.
For Apple Dictation, open System Settings > Keyboard > Dictation and read the Shortcut setting. Apple notes that this choice can affect Fn or Globe key behavior. Use the shortcut shown on your Mac instead of relying on memory.
Once the correct trigger works in Notes, leave the shortcut alone. Move to the field where the failure originally happened.
4. Isolate the Text Field
Audio can be captured and processed while the insertion target is wrong. Return to the blank note, click after the characters you typed, and repeat one short phrase.
If text appears in Notes but not in another app, the Mac-wide audio path and trigger are working. In the failing app, click into a simple editable field and type one character before dictating. If the same phrase still fails only there, the remaining problem belongs to that app or editor, not the microphone.
If Paraspeech finishes its recording flow but text never appears in Notes, preserve that clean reproduction. Recheck Accessibility once, then continue to the mode check. Random editor workarounds will only blur the result.
5. Match the Processing Mode to Connectivity
Connectivity comes last because it cannot explain a dead input meter, denied permission, or wrong shortcut.
For Apple Dictation, read the text below System Settings > Keyboard > Dictation. Apple says this area tells you whether general text Dictation is processed on the device or needs an internet connection for the current setup.
For Paraspeech, local transcription and local rewriting can run offline after setup where supported. Initial model downloads and cloud-backed features require internet. If an offline test fails, confirm that you selected a supported local mode and completed its model download while connected. One mode's result does not describe every Paraspeech feature.
Classify the Failure Before Changing Anything Else
| Outcome | Evidence | What to do next |
|---|---|---|
| Configuration gap | Wrong input device, permission off, shortcut mismatch, no focused field, missing local model, or a cloud-backed mode without connectivity | Correct that one setting and repeat the same Notes phrase. |
| Target-app refusal | The same voice test works in Notes but not in the original app or editor | Confirm the target is editable, then use that app's current support path. |
| Likely app defect | macOS receives audio, required permissions are on, the documented trigger is correct, the mode is available, and the failure repeats in Notes for one app | Record the app version, macOS version, selected mode, and exact stopping point, then contact the app's support team. |
| Platform refusal | macOS does not expose or grant the required input, permission, language, or Dictation capability | Follow Apple's current support guidance for that system boundary; do not add an unverified workaround. |
Reproducibility makes the classification useful. “It failed once” is a symptom. “The input meter moves, permissions are on, the configured shortcut starts the flow, and no text reaches Notes” is a defect report a support team can act on.
When Paraspeech Fits the Working Input Path
Fix the Mac input path before changing tools. Once the Notes test works, Paraspeech offers a dedicated hold-to-talk Mac workflow that inserts processed text at the current cursor. Its local transcription and local rewriting modes can run offline after setup where supported; initial model downloads and cloud-backed features still require internet.
Download Paraspeech for Mac if that workflow fits your next test. Read offline speech to text for Mac for the processing boundary, or return to the Mac speech-to-text setup guide for installation and full setup.
Frequently Asked Questions
Why does the microphone work but no text appears?
The audio device and insertion path are separate layers. Test in a blank Notes field. If audio reaches macOS but text does not appear, check app permission, the configured shortcut, and field focus before changing the microphone.
Why does dictation work in Notes but not another Mac app?
The result isolates the problem to the target app or field. Click into a plainly editable field, type one character, and repeat the same phrase. If it still fails only there, use that app's support path instead of resetting the Mac-wide input setup.
Does Mac dictation need internet?
It depends on the active system or app mode. Apple's Keyboard settings show whether its general text Dictation needs a connection for your current setup. Paraspeech local modes can run offline after setup where supported; initial model downloads and cloud-backed features require internet.
Should I reinstall the app first?
No. Reinstalling does not prove whether the failure is audio input, permission, shortcut, focus, or connectivity. Run the Notes test and fix the first failing layer before considering a reinstall.
