Dictation Not Working on Mac? 8 Proven Fixes (2026)

TL;DR: Dictation not working on Mac is usually caused by conflicts with Voice Control, corrupted speech caches, or microphone permission issues. Most fixes take under two minutes. Start by toggling Dictation off and on in System Settings > Keyboard > Dictation, then check whether Voice Control is enabled (it conflicts with Dictation). If those don't work, run killall corespeechd in Terminal to restart the speech daemon, or clear the speech recognition cache.

These fixes also apply if you're searching for "Mac speech to text not working" or "voice to text not working on Mac" — they all refer to the same macOS feature.

Tried everything and dictation is still broken? Jump to third-party alternatives — the underlying tool may be the problem.

Disclosure: Voibe is our product. We include it as an alternative to Apple Dictation where relevant, and we compare all tools factually.

Mac dictation can stop working for several distinct reasons. Understanding the root cause helps you skip straight to the right fix instead of trying every solution sequentially.

Voice Control conflict. This is the number-one hidden cause. When Voice Control is enabled in System Settings > Accessibility, it takes over the microphone and blocks Dictation from activating. Both features listen for voice input, but they can't operate simultaneously. Many users enable Voice Control accidentally or during accessibility setup without realizing it disables Dictation.

Corrupted speech recognition cache. macOS stores speech recognition data in ~/Library/Caches/com.apple.SpeechRecognitionCore. After macOS updates, migrations, or unexpected shutdowns, these cache files can become corrupted. When that happens, the Dictation system fails silently — you press the shortcut, the microphone icon appears briefly, but no text is transcribed.

Microphone permission issues. macOS requires explicit microphone access for each application. If the app you're trying to dictate in doesn't have microphone permission, Dictation won't produce any text in that specific app. This explains why dictation might work in Notes but fail in a third-party text editor.

Stuck corespeechd process. The corespeechd daemon manages speech recognition on macOS. If it crashes or hangs, Dictation stops responding entirely until the process is restarted.

Internet dependency. On Intel Macs or when enhanced dictation is disabled, macOS sends audio to Apple's servers for processing. If your internet connection is unstable or blocked (such as on corporate networks or VPNs), dictation fails without a clear error message.

"Improve Siri & Dictation" consent dialog stuck. During initial Dictation setup, macOS shows a consent dialog asking whether to share audio samples to improve Siri and Dictation. A small subset of users report this dialog refusing to dismiss — both Share Audio and Not Now fail silently, and Dictation never finishes enabling. The fix: open System Settings > Privacy & Security > Analytics & Improvements, toggle Improve Siri & Dictation off, restart your Mac, then re-enable Dictation from scratch in Keyboard settings.

"Dictation automatically ends when you stop speaking" is a checkbox in System Settings > Keyboard > Dictation that tells macOS to stop listening as soon as it detects a stretch of silence. When it is on, the microphone icon disappears the moment you pause; when it is off, macOS keeps listening until you press the shortcut again or hit Apple's hard timeout.

The setting is helpful for short voice commands and one-off sentences — you don't have to deactivate dictation manually. It hurts for long-form dictation, slower speakers, and any flow that involves pausing to think mid-sentence. If your speech-to-text seems to cut off the second you stop talking, this is the lever.

To toggle it: open System Settings > Keyboard > Dictation, then check or uncheck Auto-Ends Dictation When You Stop Speaking (the exact label varies slightly by macOS version). One gotcha: even with this setting off, Apple's separate 30-second hard timeout still applies — Apple Dictation is architecturally capped at roughly 30 seconds of continuous listening regardless of this checkbox. For continuous dictation without any timeout, see Voibe.

Toggling Dictation off and on resets the speech recognition system and resolves temporary glitches. This is the fastest fix and should be your first step when dictation stops working on Mac.

1. Open System Settings (click the Apple menu in the top-left corner and select System Settings).
2. Click Keyboard in the left sidebar.
3. Scroll down to the Dictation section.
4. Toggle Dictation off.
5. Wait 10 seconds. This gives macOS time to fully shut down the speech recognition processes.
6. Toggle Dictation back on.
7. Confirm your microphone source is correct (select your preferred microphone from the dropdown).
8. Verify your language setting matches the language you'll be speaking.

After toggling, test Dictation by opening a text field in Notes or TextEdit and pressing the Fn key twice (the default Dictation shortcut). If the microphone icon appears and transcribes your speech, the issue is resolved.

Voice Control is the most common hidden cause of dictation not working on Mac. When Voice Control is active, it takes exclusive control of the microphone for voice commands, which blocks the Dictation feature from activating. Many users don't realize Voice Control is enabled because it can be turned on accidentally through Siri suggestions or accessibility setup.

1. Open System Settings.
2. Click Accessibility in the left sidebar.
3. Scroll down and click Voice Control.
4. If the toggle is on, switch it off.
5. Return to Keyboard > Dictation and verify Dictation is still enabled.
6. Test Dictation by pressing Fn twice in any text field.

Voice Control and Dictation are separate macOS features that both use the microphone. Apple does not display a clear error message when they conflict — Dictation simply fails silently. If you need both features, you'll have to toggle between them manually, as they cannot run simultaneously.

macOS requires explicit microphone access for each application. If dictation works in Apple's built-in apps (like Notes or TextEdit) but fails in third-party apps (like Slack, Chrome, or VS Code), the issue is almost certainly a missing microphone permission.

1. Open System Settings.
2. Click Privacy & Security in the left sidebar.
3. Click Microphone.
4. Review the list of apps. Find the app where dictation isn't working.
5. If the app is listed but the toggle is off, switch it on.
6. If the app is not listed, open the app and try to use dictation — macOS should prompt you to grant access. If no prompt appears, you may need to remove the app from the list (click the minus button) and re-add it.
7. After granting permissions, quit and reopen the affected app for the change to take effect.

Some apps require a full restart (not just closing the window) before new microphone permissions are recognized. Right-click the app icon in the Dock and select Quit, then reopen it.

Quick answer: Run killall corespeechd in Terminal to restart macOS speech recognition. macOS automatically respawns the daemon within a few seconds — no full system restart needed.

killall corespeechd

If the Dictation microphone icon appears but no text is transcribed, or if the icon is stuck and won't dismiss, the corespeechd process has likely crashed or frozen. Killing it forces macOS to restart it fresh.

1. Open Terminal (find it in Applications > Utilities, or search with Spotlight by pressing Cmd + Space and typing "Terminal").
2. Type the following command and press Enter:

killall corespeechd

3. macOS will automatically restart the corespeechd daemon within a few seconds.
4. Wait 5 seconds, then test Dictation in any text field.

The corespeechd process is the core speech daemon that manages all speech recognition on macOS. Killing it is safe — macOS restarts it automatically. This is equivalent to a targeted restart of just the speech system, without needing to restart your entire Mac.

If you want to verify the process restarted, run this command in Terminal:

ps aux | grep corespeechd

You should see a new corespeechd process listed with a recent start time.

For a deeper explanation — what corespeechd is, whether the command is safe, how it differs from other macOS speech daemons, and what to do when it does not help — see our dedicated guide to killall corespeechd.

macOS caches speech recognition data to improve performance. After macOS updates, system migrations, or unexpected shutdowns, these cache files can become corrupted and cause dictation to fail. Clearing the cache forces macOS to rebuild it from scratch.

1. Open Finder.
2. Press Cmd + Shift + G to open the "Go to Folder" dialog.
3. Paste the following path and press Enter:

~/Library/Caches/com.apple.SpeechRecognitionCore

4. Select all files in this folder (Cmd + A).
5. Move them to the Trash (Cmd + Delete).
6. Restart your Mac (Apple menu > Restart).
7. After restarting, macOS will regenerate the speech recognition cache automatically.
8. Test Dictation in a text field.

If the folder doesn't exist or is empty, your issue isn't cache-related. Move on to Fix 6.

macOS stores Dictation preferences in a property list file. If this file becomes corrupted, Dictation may fail even though it appears enabled in System Settings. Deleting the preference file forces macOS to create a fresh one.

1. Open Finder.
2. Press Cmd + Shift + G to open "Go to Folder."
3. Paste the following path and press Enter:

~/Library/Preferences/com.apple.assistant.plist

4. Move the com.apple.assistant.plist file to the Trash.
5. Restart your Mac.
6. After restarting, go to System Settings > Keyboard > Dictation and re-enable Dictation.
7. Reconfigure your microphone source and language.
8. Test Dictation.

Deleting this preference file resets all Dictation-related settings to their defaults. You'll need to re-select your preferred microphone and language after restarting, but this is a one-time reconfiguration.

Apple periodically fixes speech recognition bugs in macOS updates. If your dictation issue started after a specific macOS version or has persisted through other fixes, an available update may contain the patch you need.

1. Click the Apple menu in the top-left corner.
2. Select System Settings.
3. Click General in the left sidebar.
4. Click Software Update.
5. If an update is available, click Update Now or Upgrade Now.
6. After the update completes, your Mac will restart automatically.
7. Once restarted, go to System Settings > Keyboard > Dictation and verify Dictation is still enabled.
8. Test Dictation in a text field.

If you're running a macOS beta, note that beta versions frequently have dictation bugs that are fixed in the stable release. Consider switching to the stable channel if dictation is critical to your workflow.

The keyboard shortcut for Dictation has shifted across macOS versions, and several popular third-party utilities silently intercept the Fn key. Both are common reasons users hit a "Dictation shortcut not working" wall even when Dictation itself is enabled.

1. Open System Settings > Keyboard > Dictation.
2. Find the Shortcut dropdown and note what is currently assigned.
3. If the dropdown is greyed out, Dictation isn't fully enabled — toggle Dictation off and on (see Fix 1), then return here.
4. If the current shortcut is set to something you don't recognize or doesn't match your keyboard, pick something unambiguous like F5 (Customize) or Press Control Key Twice.
5. Test in any text field by pressing the new shortcut.

Default shortcut by macOS version. Apple has changed the default Dictation shortcut multiple times, which is why what worked on your old Mac may not work on a new one:

• macOS Monterey and earlier: Press Fn twice
• macOS Ventura and later: Press Globe (🌐) key on MacBook keyboards, or Press Control Key Twice on Magic Keyboards without the Globe key
• macOS Sequoia and Tahoe: same as Ventura, with the additional option to assign any custom Function key

Magic Keyboard vs MacBook keyboard. The Globe key looks different across keyboards. On modern MacBook Pro and MacBook Air keyboards it is the bottom-left key labeled 🌐 (replacing the older Fn label). On the standalone Magic Keyboard — and on older MacBooks running newer macOS — there is no dedicated Globe key, and Dictation defaults to "Press Control Key Twice" instead. If your shortcut "stopped working" after switching between an external keyboard and your built-in MacBook keyboard, this mismatch is why.

Third-party apps that intercept the Fn key. Several popular utilities remap or capture the Fn key for their own functions, which prevents Dictation from registering the double-tap:

• Karabiner-Elements — a deep keyboard remapper and the single most common conflict
• BetterTouchTool — if you have assigned anything to Fn or Fn + key combinations
• Raycast — when Raycast's launch hotkey is bound to Fn
• Hyperkey — by design, it converts Fn into a hyper-modifier and swallows the double-tap
• Rectangle Pro — only when Fn is bound to a window-snap action

To isolate the conflict, quit each one from its menu bar icon (not just close the window) and retest Dictation between quits. If Dictation starts working, the last app you quit was the conflict. Re-enable it and either change its hotkey or switch Dictation to a different shortcut (F5 is a reliable fallback that no other utility tends to bind).

For the full reference — every shortcut option, the trigger by macOS version, the Globe key explained, and a step-by-step method for isolating which app is intercepting your shortcut — see our complete guide to Mac dictation keyboard shortcuts.

Some apps handle dictation differently from macOS's standard text fields. If Dictation works in Notes but fails in a specific app, the issue is rarely Dictation itself — it's how that app interacts with the system speech APIs.

Microsoft Word on Mac

Word has its own built-in dictation engine (Microsoft Speech, the same engine that powers Word on Windows and Microsoft 365 on the web), and it is separate from macOS Dictation. Users frequently confuse the two and assume both are broken when only one is.

• Word's Dictate button (Home tab > Dictate) uses Microsoft's cloud speech service, requires an active internet connection, and needs Word itself to have microphone permission separately from any other app.
• macOS Dictation also works in Word — but only when your cursor is active in an editable text field. Word's ribbon, menu bar, and dialog boxes are not text fields, so the Fn key shortcut will silently do nothing if focus is on the wrong element.

Fix steps:

1. Grant microphone permission to Microsoft Word in System Settings > Privacy & Security > Microphone.
2. Quit and relaunch Word — the permission change doesn't take effect until Word restarts.
3. Test both Word's Dictate button and macOS Dictation separately to isolate which engine is broken. If one works and the other doesn't, you have narrowed down the cause.

Terminal

Terminal is a non-standard text input: it doesn't use AppKit's standard text-field controls, which means several macOS text services — including Dictation — have inconsistent or no support inside it. The Fn shortcut may appear to do nothing, or transcribed characters may insert in the wrong position.

Workarounds:

• Use iTerm2 instead — its text rendering is closer to a standard text field and Dictation tends to work more reliably.
• Dictate into a regular text editor (TextEdit, Notes, VS Code) and paste the result into Terminal.

This is the kind of edge case where a system-wide dictation tool that types keystrokes rather than calling the macOS Dictation API — like Voibe — works inside Terminal, iTerm2, and any text input field, because it is driving the keyboard directly.

Chrome and Browser Text Fields

Web text fields don't all behave the same way. Standard HTML <input> and <textarea> elements support Dictation cleanly. Rich-text editors like Gmail's compose window, Google Docs, and Notion's web app intercept input differently and can swallow dictation events.

• Grant Google Chrome microphone permission in System Settings > Privacy & Security > Microphone. This is separate from Chrome's per-site microphone permission (the lock-icon prompt). You need both layers.
• For Google Docs specifically: use Docs's own Voice Typing (Tools > Voice typing), which runs independently of macOS Dictation and is purpose-built for the Docs editor.
• For Gmail compose and other rich-text web fields: macOS Dictation usually works, but if it doesn't, click into the field first, then activate Dictation — sometimes the editor steals focus from the dictation overlay if you activate Dictation before clicking in.

If you've fixed the immediate issue but find yourself repeatedly troubleshooting Apple Dictation, the underlying problem may be the tool itself. Built-in Mac dictation has several structural limitations that third-party apps address.

Known limitations of Apple Dictation:

• 30-second auto-timeout — architectural, not a bug. Apple Dictation stops listening after approximately 30 seconds of continuous speech or silence. This is a built-in architectural constraint with no workaround. You cannot extend it in settings. Users report having to tap the Fn key repeatedly during longer sessions, which breaks dictation flow entirely.
• Accuracy reportedly declining. Multiple users on Apple Community forums and Reddit report that Apple Dictation accuracy has worsened across recent macOS updates rather than improving. Technical terms, API names, framework names, and code-related vocabulary are frequently misrecognized.
• Words dropped mid-sentence. A common symptom on recent macOS versions is mid-sentence word drops — the first or last word of a phrase gets cut, leading to incoherent output.
• Stops working randomly. Users report dictation appearing active (mic icon shown) but producing no transcription output — essentially "ghost dictation." Community reports describe this happening 3 out of 10 times, requiring repeated Fn key presses to recover.
• No custom vocabulary. You cannot add technical terms, API names, framework names, product names, or niche jargon. This is especially painful for developers and medical or legal professionals who depend on accurate transcription of specialized terminology.
• Inconsistent auto-punctuation. Auto-punctuation on Apple Silicon Macs inserts commas and periods unreliably in complex or long sentences.
• No developer or IDE awareness. Apple Dictation has no context about what application you're using or what you're working on. It cannot handle code-related terms like variable names, method calls, or framework identifiers.
• Particularly painful for RSI and mobility-limited users. Users with repetitive strain injury or limited mobility who depend on dictation as their primary input method are hit hardest by the 30-second timeout and random stop behavior — reactivating dictation repeatedly is the exact physical strain they're trying to avoid.

If these limitations affect your workflow, consider a dedicated dictation app. For a comprehensive overview of all Mac dictation options, see our complete guide to dictation on Mac.

Voibe: Offline Dictation That Doesn't Break

Voibe is an offline dictation app for macOS that runs entirely on-device using OpenAI's Whisper models on Apple Silicon (M1-M4). Because it operates independently from macOS Dictation, it doesn't suffer from the same corespeechd crashes, Voice Control conflicts, or cache corruption issues.

• No timeout limit — dictate continuously without reactivation
• 100% on-device — zero data uploaded, no internet required, no Apple server dependency
• Developer mode — VS Code and Cursor integration with project-aware context
• Pricing: $7.50/mo or $149 lifetime

Download Voibe and try it as a replacement or backup for Apple Dictation.

Other Alternatives

Wispr Flow (~$10/mo) offers cloud-based AI dictation with text rewriting capabilities — note that it captures screenshots of active windows for context awareness, a privacy trade-off to consider. Superwhisper ($249.99 lifetime or $8.49/mo) provides multiple on-device Whisper model options — be aware that audio recordings are saved by default and API keys are stored in plaintext. For a full breakdown of these tools, read our Apple Dictation alternatives guide.

Troubleshooting

Why does my Mac dictation keep stopping after 30 seconds?

Apple Dictation has a built-in 30-second auto-timeout. This is an architectural limitation, not a bug — and there is no setting to extend or disable it. You need to reactivate dictation by pressing Fn twice each time it stops. This is especially disruptive for users who rely on dictation due to RSI or limited mobility, since the repeated reactivation triggers the exact physical strain they're trying to avoid. Third-party dictation apps like Voibe don't have this timeout restriction and allow continuous dictation without interruption.

Why does dictation work in some apps but not others?

App-specific dictation failures are caused by missing microphone permissions. Go to System Settings > Privacy & Security > Microphone and verify the affected app has microphone access enabled. Some apps also need to be quit and relaunched after granting permissions. See Fix 3 for detailed steps.

Setup and Configuration

How do I reset dictation on Mac?

To fully reset dictation on Mac: (1) Toggle Dictation off in System Settings > Keyboard > Dictation, (2) delete the preference file at ~/Library/Preferences/com.apple.assistant.plist, (3) clear the cache at ~/Library/Caches/com.apple.SpeechRecognitionCore, (4) restart your Mac, and (5) re-enable Dictation in System Settings. This performs a complete reset of the speech recognition system.

Does Mac dictation work offline?

On Apple Silicon Macs (M1-M4), Apple Dictation can work offline using on-device speech recognition. On Intel Macs, dictation requires an internet connection because audio is processed on Apple's servers. To verify your setup, check System Settings > Keyboard > Dictation — if you see an option about sending audio to Apple, your Mac is using cloud processing. For guaranteed offline dictation on any Apple Silicon Mac, tools like Voibe process all speech locally without any internet dependency.

Alternatives

What is the best alternative to Apple Dictation on Mac?

The best alternative depends on your priorities. For offline privacy and developer integration, Voibe ($7.50/mo or $149 lifetime) runs Whisper models entirely on-device with VS Code and Cursor support. For AI-powered text rewriting, Wispr Flow (~$10/mo) processes dictation through cloud AI. For maximum Whisper model flexibility, Superwhisper ($249.99 lifetime or $8.49/mo) lets you choose from multiple model sizes. See our complete guide to dictation on Mac for a detailed comparison of all options.

Dictation not working on Mac is almost always caused by one of six issues: a Voice Control conflict, corrupted speech caches, missing microphone permissions, a frozen corespeechd process, an outdated macOS version, or a third-party app intercepting the Fn key. The eight fixes in this guide address all of these causes, and most take under two minutes to complete.

Start with Fix 1 (toggle Dictation off and on) and Fix 2 (disable Voice Control) — these resolve the majority of cases. If the issue persists, work through Fixes 3-7 in order, then Fix 8 if the shortcut itself isn't firing. For app-specific failures (Word, Terminal, Chrome), see the App-Specific Troubleshooting section.

If you find yourself repeatedly troubleshooting Apple Dictation — or running into its architectural constraints like the 30-second timeout, declining accuracy across macOS updates, or random transcription failures — consider switching to a dedicated dictation app. Voibe runs independently from macOS Dictation, so it isn't affected by the system-level issues covered in this guide. It also has no timeout limit, making it suitable for users who rely on continuous dictation.

Related guides:

• Dictation on Mac: Complete Guide to Voice-to-Text in 2026
• How to Use Dictation on Mac: Setup and Voice Commands
• Speech to Text on Mac: Best Apps and Comparison
• Apple Dictation vs Wispr Flow: Should You Upgrade from Free?
• Apple Dictation vs OpenAI Whisper: Built-In vs Open-Source Model
• Apple Dictation Alternatives