Mac dictation not working? Find the failure before changing settings
Dylan de Heer
If dictation is not working on your Mac, first establish where it stops: starting the feature, hearing your voice, recognising the words or inserting them into the document. Check that Dictation is enabled, confirm the selected microphone and language, and try one short sentence in a new TextEdit document. That comparison gives you a much more useful starting point than changing several settings at once.
This guide covers Apple's built-in Dictation first, followed by checks for Weeve. A dictation button inside another app may use a different service. Keep those tests separate so you know which system you are diagnosing.
Start with a short, repeatable test
Save your current work. Open a new TextEdit document, click in its body and type a few characters to confirm that the insertion point is active. Start macOS Dictation from Edit → Start Dictation, where available, or use the shortcut shown in Keyboard settings. Say a neutral sentence such as “The next meeting is on Thursday”, then stop dictating.
Notice three things: whether Dictation starts, whether it appears to respond while you speak, and whether words reach the document. Do not use confidential material for this test. Repeat the same sentence after each change so that the result remains comparable.
Apple documents the insertion-point requirement, menu command and keyboard options in its guide to dictating messages and documents. Names and locations can vary between macOS releases; use the version selector in Apple's guide if your settings look different.
Use the symptom to choose your next check:
Nothing happens when you press the shortcut: check whether Dictation is enabled and whether that is the shortcut currently assigned to it.
Dictation starts but no words appear: check the microphone source, input level and selected language.
Words appear in TextEdit but not in your usual app: investigate the destination app, editable field and the dictation service you are actually invoking.
Words appear but are consistently wrong: check language, recording conditions and the particular words being misrecognised.
It works briefly, then stops: note whether it stopped after silence, after changing devices or only in one app.
These observations narrow the investigation. They do not, on their own, identify a hardware fault or prove that a particular macOS release is responsible.
1. Confirm which dictation feature you are using
Open System Settings → Keyboard and find Dictation. Confirm that it is enabled and inspect its shortcut, language and microphone settings.
A microphone icon is not enough to identify the service. Apple's Dictation, Voice Control and a voice-input feature inside an app can have different controls. If an app's own button fails but the macOS menu command works in the same document, you have evidence that the two routes behave differently. Continue with that app's documentation rather than repeatedly changing the Mac's Dictation settings.
There is one specific interaction to check: when Voice Control is on, Apple says that you dictate through Voice Control and standard macOS Dictation is unavailable. If you rely on Voice Control to use your Mac, keep using its commands; do not switch it off merely to follow an unrelated troubleshooting checklist. See Apple's explanation of Dictation and Voice Control.
2. Separate a shortcut problem from a dictation problem
Start Dictation through the menu in TextEdit, then try the configured keyboard shortcut. If the menu works and the shortcut does not, concentrate on activation.
Read the current shortcut rather than assuming it is a particular key combination. If you recently changed keyboards, installed a shortcut utility or reassigned a function key, make a note of that change. Temporarily testing another shortcut can help isolate an activation conflict; record the original setting so you can restore it.
Apple also distinguishes pressing and releasing the microphone key from holding it: a press starts Dictation, while holding it can activate Siri when Siri is enabled. That distinction matters when the wrong feature appears instead of a text cursor. Apple's keyboard instructions describe the available activation methods.
A useful result: Dictation starts reliably from both the menu and your chosen shortcut. If only the shortcut still fails, changing the microphone is unlikely to address the observation you just made.
3. Check the microphone actually selected for Dictation
Do not assume that a microphone working in a call is the one Dictation is using. Check the microphone source in Keyboard settings, then inspect the selected input under System Settings → Sound → Input.
Speak at your usual distance and watch for an input response. If there is none, check the microphone's connection and any physical mute control. If you use a headset, compare it with another available microphone. Change one device at a time and repeat the same sentence.
If the input responds but Dictation still produces no text, keep investigating the dictation path. An active input meter is evidence that sound is reaching the selected input; it does not demonstrate successful speech recognition or insertion into another app.
Apple's Dictation troubleshooting guidance recommends checking the microphone selection and input volume, keeping the microphone unobstructed and reducing noise or echo. Treat those as targeted checks: a headset comparison is useful when the result changes with the room or microphone, rather than as a guaranteed fix for every failure.
4. Match the language to the words you are speaking
Check the language and region selected for Dictation. If several languages are enabled, confirm which one is active during the test. A language mismatch can make a working voice-input feature appear unreliable.
Start with ordinary words. Then test the name, abbreviation or technical phrase that caused the problem. If the ordinary sentence is accurate but a specialist term is wrong, you are dealing with a different issue from Dictation failing to start. Keep a note of repeatable examples and correct the output before using it.
Be precise about what is wrong. “It missed the first word”, “it heard the sentence in another language” and “it consistently changed a project name” are three different observations. Each is more useful than “dictation is broken”.
Apple notes that availability and features vary by language and region. Its Dictation guide explains how to select and switch languages; the relevant setting is the dictation language, not simply the language in which your document happens to be written.
5. If words appear in one app but not another, test the destination
Return to the app where the problem occurred. Click inside an editable text area and type a short word manually. Make sure you are in the document body rather than a title, search box, read-only preview or another field.
Repeat the same dictation test without switching windows midway. Compare the result with TextEdit. If TextEdit succeeds, note the affected app and the exact type of field that fails. Try a new blank document in that app if doing so is straightforward and does not disturb your work.
For browser-based editors, record the browser as well as the website. A report that says “fails in this editor's comment box, works in a new TextEdit document” gives support a reproducible boundary. It does not establish which component caused the failure, but it removes several guesses.
Avoid testing in password fields or changing broad security settings to force text insertion. The aim is to find an ordinary editable field where the behaviour is repeatable.
6. Check whether the interruption is expected
If Dictation stops after you pause, record how long the pause was. Apple's current guide says it stops automatically after 30 seconds without speech and does not impose a timeout on the length of continuous dictated text. Do not apply an old article's fixed session limit to every current Mac. Apple's troubleshooting page describes this behaviour.
Network requirements also need a specific check. Apple directs users to the text below Dictation in Keyboard settings to see whether an internet connection is required and whether general text dictation is processed on the device. Read what your Mac says instead of assuming that all dictation is either always offline or always sent to a server.
If the interruption happens after connecting a headset, waking the Mac or moving between applications, repeat that small sequence with a neutral sentence. Note the last step that worked. This is useful evidence even if you cannot yet reproduce the failure every time.
When dictation fails in Weeve
Weeve's dictation is a separate workflow from Apple's built-in Dictation. Its current implementation checks microphone access, transcribes your speech and inserts the result into the active text field. External text insertion requires Accessibility access. Turning Apple's Dictation on does not configure those Weeve permissions.
Genuine Weeve settings capture. Check the shortcuts in your installation; the displayed combinations are an example.
Start with three checks:
Activation: inspect Weeve's recording and dictation shortcuts. The displayed workflow distinguishes tapping to record from holding to dictate and releasing to insert. Confirm which action you are triggering. If the shortcut works inside Weeve but not in other apps, also check the “Shortcuts outside of Weeve” toggle in Weeve’s settings.
Access: check Weeve's microphone and Accessibility permissions in macOS Privacy & Security settings. Microphone access and permission to insert text solve different parts of the workflow.
Destination: place the insertion point in a new TextEdit document, keep that app active and test a short sentence. Compare with the original destination before changing more settings.
If the same Weeve test works in one destination and fails in another, include both results when contacting support. Do not assume the transcript will always remain on your clipboard as a recovery mechanism: Weeve's clipboard retention is a separate user choice.
The Weeve dictation overview explains the intended workflow. These checks are for using that workflow; installing another dictation app is not a diagnosis of a fault in Apple's feature.
What to collect if the problem continues
Save your work before reopening an affected application or restarting your Mac, then rerun the same short test. If the problem remains, prepare a compact report containing:
Your macOS version and the affected app's version.
Whether you are using Apple Dictation, Voice Control, Weeve or an app-specific dictation button.
The selected microphone, language and activation method.
Whether the identical sentence works in TextEdit.
What happens at each stage: activation, audio response, recognition and insertion.
A recent change that reliably precedes the failure, if you found one.
Keep private speech and documents out of the report unless they are necessary and you deliberately choose to share them. For a Weeve-specific issue, use Weeve support. For the macOS feature, start from Apple's version-matched guidance linked above.
A successful final check is simple: you can start the intended feature, dictate an ordinary sentence into the app you need and repeat the result. If that still fails, the observations you collected give the next investigation a concrete starting point.
