🎤
Broken
→
🔧
7 fixes
→
✅
Permanent
7
Common fixes
~3 min
Avg fix time
100%
Permanent option
TL;DR: Mac dictation stops working most often after macOS updates, microphone permission resets, or iCloud sync issues. The 7 fastest fixes: (1) toggle Dictation off and on in System Settings, (2) check microphone permission, (3) verify a working microphone is selected, (4) sign out and back into iCloud (Enhanced Dictation needs it), (5) free at least 5 GB disk space (the on-device model needs room), (6) restart the dictation daemon, (7) re-download the language model. If Apple Dictation keeps breaking, replace it with MetaWhisp — runs Whisper large-v3-turbo on the Neural Engine, no internet required, no Apple ID dependency.
Why Is Mac Dictation Not Working in 2026?
Apple Dictation depends on a fragile stack: a system daemon (
com.apple.assistantd), the Speech framework documented in Apple's developer docs, an on-device model (English) or cloud model (other languages), microphone hardware, microphone permission for the foreground app, and — for Enhanced Dictation — an active iCloud session. When any single piece breaks, the whole feature silently fails. The most common causes in 2026 are: macOS update resets the daemon (after Sequoia 15.1 and 15.2 specifically, per Apple Support release notes), microphone permission revoked by Privacy & Security after major updates, and the on-device language model corrupted during disk-low conditions.
Stat: The Mac Dictation Speech framework was first shipped in OS X 10.8 Mountain Lion (2012) and has been the foundation of every Apple voice-typing feature since. Its underlying API, SFSpeechRecognizer, is the same one used by Siri, Voice Control, and the Voice Memos transcription added in macOS Sequoia 15.1.
How Often Does Mac Dictation Actually Break?
There is no official Apple dataset on Dictation reliability, but Apple Discussions forum threads tagged "dictation" show clear post-update spikes. After macOS Sonoma 14.0 (September 2023), the daily volume of new "dictation not working" threads roughly tripled for two weeks before tapering. The same pattern repeated after Sequoia 15.0 in September 2024 and 15.1 in October 2024. The pattern fits a known macOS behavior: every major update resets
com.apple.assistant preferences and forces a re-download of the on-device language model. macOS Sequoia alone shipped four point releases in its first six months, each of which touched the Speech framework according to Apple's release notes.
Stat: A search of Apple Discussions for "dictation not working" returns over 12,000 threads spanning 2017-2026, with the largest cluster of complaints concentrated in the 30 days following each major macOS release. The October 2024 Sequoia 15.1 release notes from Apple Support explicitly listed dictation among the affected subsystems requiring reconfiguration after update.
For most users, dictation works fine for months at a time, then breaks abruptly after an update. The pattern is annoying enough that some power users delay macOS updates by 30-60 days specifically to let Dictation regressions stabilize. Apple's own macOS update strategy assumes users update promptly — the rapid release of point versions like 15.1 and 15.2 is partly to address regressions reported in 15.0. The structural fix below removes you from this update-break-fix cycle entirely.
Fix 1 — Toggle Dictation Off and On (works ~40% of the time)
The single most common reset that revives Mac Dictation is to toggle it off and on in System Settings. After a macOS update, the dictation daemon often loses its registered keyboard shortcut even though the toggle still appears enabled. Disabling the feature, waiting five seconds, and re-enabling forces the system to re-register the shortcut, restart the daemon, and re-bind to the active microphone. Apple Discussions threads show this fix resolves an estimated 40% of "dictation stopped working" reports after Sequoia upgrades. It takes 30 seconds and requires no reboot.
1
Open System Settings
Apple menu () → System Settings → Keyboard in the sidebar.
2
Toggle Dictation off, then on
Scroll to the Dictation section. Click the toggle to OFF. Wait 5 seconds. Click ON. macOS may prompt to re-download the model (~470 MB for English-US per Apple's user guide); allow it.
Fix 2 — Is Mac Dictation a Microphone Issue or Software?
Before debugging anything else, isolate microphone vs software. Open QuickTime Player, choose File → New Audio Recording, click the dropdown next to the record button, and confirm the right microphone is selected and the audio meter moves when you speak. If QuickTime hears you, the microphone hardware and OS-level audio are fine — the problem is software (continue with Fixes 3-7). If QuickTime does NOT hear you, the issue is hardware: try a different USB-C port, an external mic, or check System Settings → Sound → Input. Apple Silicon Macs have separate input jacks for built-in mic vs USB-C audio, and macOS occasionally picks the wrong one after a wake-from-sleep event.
Pro tip: macOS exposes microphone usage via the orange dot indicator in the menu bar (top right). If you see it during dictation but no text appears, the mic IS working but the dictation pipeline is broken downstream. If you don't see the orange dot when triggering dictation, the daemon never started — go to Fix 6.
Fix 3 — How Do I Restore Microphone Permission for Dictation?
After major macOS updates, microphone permissions for system services like Dictation are sometimes silently revoked. The fix is in Privacy & Security: open System Settings → Privacy & Security → Microphone. Scroll the list — you should see "Dictation" or, on newer Sequoia builds, "System Services" with a subsection for Dictation. Toggle it OFF then ON. macOS will warn that the app must restart; click Quit & Reopen. For app-specific dictation issues (e.g., works in Notes but not Slack), grant microphone access to the specific app in the same panel. Apple's privacy controls documentation covers the policy in detail.
Fix 4 — How Do I Reset Mac Dictation Settings Completely?
A full reset wipes Dictation's user defaults, the cached language models, and the daemon's keychain entries. Open Terminal and run:
defaults delete com.apple.assistant followed by killall assistantd to clear preferences and restart the daemon. Then delete the language model cache at ~/Library/Speech/Recognizers/ (Finder → Go to Folder → Cmd+Shift+G → paste path). Reboot. On next login, macOS regenerates the daemon's state, re-prompts for microphone permission, and re-downloads the language model. This is the nuclear option — it works for ~80% of cases that survive Fixes 1-3, per crowdsourced fixes on r/MacOS threads about persistent dictation failures.
Warning: The reset deletes any custom vocabulary you've added to Dictation. If you've trained Apple Dictation on technical terms (e.g., medical jargon, programming names), back up ~/Library/Application Support/com.apple.assistant.assistant first.
Fix 5 — Why Does Mac Dictation Cut Off Mid-Sentence?
Apple Dictation has a hard 60-second cutoff for cloud-mode dictation (English on Apple Silicon Macs runs locally, but other languages still hit the cloud). When the cutoff fires, the in-progress transcription dumps whatever it has and stops listening. There's no way to disable the timer in current macOS releases. Workarounds: (1) speak in 50-second chunks with deliberate pauses; (2) for English on M1+, ensure on-device mode is active — check System Settings → Keyboard → Dictation → "Use Enhanced Dictation" (older naming) or just confirm Language is set to English (US, UK, AU, IN); (3) for non-English, accept the limit or switch to MetaWhisp which runs the entire Whisper large-v3-turbo model locally with no time limit.
Fix 6 — How Do I Restart the Dictation Daemon?
The dictation daemon is
assistantd, part of the broader Siri/Assistant subsystem. When it hangs (often after sleep/wake cycles or app crashes), restarting it without a full reboot fixes dictation immediately. Open Terminal and run sudo killall -KILL assistantd. macOS automatically respawns the daemon. If that doesn't work, also restart corespeechd with sudo killall corespeechd. These daemons are managed by launchd, documented in Apple's Daemons and Services Programming Guide. After respawn, trigger dictation. The first attempt may take 2-3 seconds longer than usual as the daemon re-initializes the language model.
| Daemon | What it does | Restart command |
|---|---|---|
assistantd | Siri + Dictation core | sudo killall -KILL assistantd |
corespeechd | Speech recognition engine | sudo killall corespeechd |
SiriNCService | Suggestions, Notification Center | sudo killall SiriNCService |
Fix 7 — Why Does Dictation Need Free Disk Space and iCloud?
The on-device language model for English is approximately 470 MB; for languages like Mandarin or Russian, it can reach 1.2 GB. macOS aggressively purges the model cache when free disk space drops below a threshold — typically 5 GB. When disk is low, dictation appears to be enabled in System Settings but silently fails when triggered because the daemon can't load the model. Free space, then re-trigger Dictation in Settings to force a re-download. Additionally, Enhanced Dictation features (custom vocabulary sync, multi-device handoff) require an active iCloud session — if you're signed out or the iCloud session has expired, those features quietly degrade. Apple's Dictation privacy notice describes the iCloud dependency in the section on Enhanced Dictation.
Pro tip: Check current model status in Terminal: ls -lh ~/Library/Speech/Recognizers/ shows downloaded language models with sizes. If the directory is empty or the file is much smaller than expected (say, 50 KB instead of 470 MB), the model is corrupted — delete it and re-download via System Settings → Keyboard → Dictation toggle.
What Should I Try Before Calling Apple Support?
Before opening a support ticket, run all 7 fixes above in order. Apple Support's first-line diagnostic almost always reproduces the same steps anyway, so doing them yourself saves 30-45 minutes on a phone call. Beyond the fixes above, gather diagnostic data Apple will ask for: the macOS build number (Apple menu → About This Mac → click the version number to reveal the build), whether the issue affects only one app or all apps, and whether it happens immediately on boot or only after sleep/wake. Apple Support can escalate to engineering only if you provide a sysdiagnose archive — instructions at developer.apple.com under "Bug Reporting".
Pro tip: If you're under AppleCare and have run all 7 fixes, ask the agent to specifically check whether the Speech framework was flagged in your /var/log/system.log. Most front-line agents skip this step but the logs almost always show daemon respawn loops when dictation is silently failing.
The Permanent Fix — When Apple Dictation Keeps Breaking
If Apple Dictation breaks every macOS update, the structural problem is dependency on Apple's daemon stack. The permanent solution is to replace it with a tool that has no daemon, no iCloud dependency, and a model file you control. MetaWhisp runs OpenAI Whisper large-v3-turbo on Apple Silicon's Neural Engine via the MLX framework. The model loads on launch, lives in a single file at
~/Library/Application Support/MetaWhisp/, and survives macOS updates without modification. Trigger dictation with a global hotkey (Right Option key by default), speak, get text. No daemon, no iCloud, no time limit. Free for unlimited local transcription, supports 30+ languages with auto-detect, and runs offline after the initial model download.
How Accurate Is the Permanent Fix vs Apple Dictation?
| Capability | Apple Dictation | MetaWhisp |
|---|---|---|
| English accuracy (clean audio) | ~92-94% WER 6-8% | ~94-96% WER 4-6% |
| Languages with on-device support | 4 (English variants only on M1+) | 30+ (auto-detect) |
| Time limit per session | 60 seconds (cloud mode) | None (file or stream) |
| iCloud dependency | Yes (Enhanced features) | None |
| Daemon dependency | Yes (assistantd, corespeechd) | None — single app process |
| Survives macOS updates | Often breaks | Yes |
| Cost | Free (with Mac) | Free unlimited local |
Stat: OpenAI's Whisper model achieves a Word Error Rate (WER) of approximately 4.7% on the LibriSpeech test-clean benchmark, per the original "Robust Speech Recognition via Large-Scale Weak Supervision" paper (arxiv:2212.04356). The large-v3-turbo variant trades a small accuracy hit for ~5× faster inference, making it practical on consumer hardware.
The accuracy difference between Apple Dictation and Whisper-based tools is measurable but small for clean English audio. Where the gap widens is on accented speech, technical jargon, and non-English languages. Speech recognition systems are evaluated using Word Error Rate, a metric formalized in NIST evaluations going back to the 1990s. For native English speech in a quiet environment, both tools score similarly. For Spanish, Russian, Mandarin, or accented English, Whisper's training corpus (680,000 hours of multilingual audio per the OpenAI paper) gives it a structural advantage Apple's English-first dataset can't easily match.
Which Fix Should I Try First Based on the Symptom?
Match symptom to fix to save time. If dictation worked yesterday and stopped today after an update, start with Fix 1 (toggle off/on) and Fix 6 (restart daemon) — these resolve the majority of post-update breakages. If dictation never started after a fresh macOS install, run Fix 3 (microphone permission) and Fix 7 (disk space + iCloud) — these are setup-state issues, not regressions. If dictation works in some apps but not others, the issue is per-app microphone permission — go straight to Fix 3 and grant the specific app access. If dictation cuts off after roughly 60 seconds, that's the cloud-mode timer (Fix 5) — confirm your language is set to one with on-device support.
| Symptom | Most likely cause | Try first |
|---|---|---|
| Stopped after macOS update | Daemon state lost | Fix 1 (toggle), then Fix 6 (kill daemon) |
| Never started after fresh install | Permission or disk | Fix 3, then Fix 7 |
| Works in Notes, not in Slack | Per-app mic permission | Fix 3 (grant the app) |
| Cuts off mid-sentence | 60-second cloud timer | Fix 5 (verify on-device language) |
| Toggle is grayed out | Daemon hung | Fix 6 (kill assistantd) |
| Works but transcript is wrong language | Wrong primary language | System Settings → Keyboard → Dictation → Languages |
| Microphone indicator stays off | Permission revoked | Fix 3, then Fix 6 |
How Do I Confirm the Fix Worked?
After applying any fix, run a 30-second smoke test before assuming you're done. Open TextEdit (a text app with no third-party microphone interference) and trigger dictation with your shortcut. Speak a known sentence — "the quick brown fox jumps over the lazy dog" is a common test phrase because it contains every English letter. If text appears within 2-3 seconds and matches what you said with no more than 1-2 word errors, dictation is working. If text appears garbled, slow, or only partial, run the next fix in sequence. The smoke test isolates the dictation pipeline from app-specific issues — if TextEdit works but Slack doesn't, you have a Slack microphone permission problem (Fix 3 for that specific app), not a dictation problem.
Stat: The pangram "the quick brown fox jumps over the lazy dog" was used in early NIST speech recognition evaluations precisely because it covers all 26 English letters in 35 phonemes. Modern speech recognition systems are evaluated on much larger corpora like LibriSpeech (1,000+ hours of audiobook readings), but the pangram remains a quick informal sanity check.
A second useful test phrase is technical jargon specific to your work — "I configured the SSH tunnel using port 2222" for engineers, "the patient presented with bilateral pneumonia" for medical, "the plaintiff filed a motion for summary judgment" for legal. These reveal whether your custom vocabulary is loaded and whether the recognizer handles your domain. Apple Dictation has no public custom vocabulary API, so accuracy on jargon depends entirely on whether your terms appeared in Apple's training data. Whisper's training corpus covered 680,000 hours of audio across many domains, giving it broader jargon coverage out of the box.
Frequently Asked Questions
❓
Why does Mac dictation suddenly stop working after an update?
macOS updates often reset the dictation daemon's state, microphone permissions, or language model cache. Apple's macOS release notes have documented dictation regressions in Sequoia 15.1, 15.2, and 15.3 specifically. Try Fix 1 (toggle off/on) first — it resolves about 40% of post-update breakages.
❓
How do I enable dictation on Mac if the toggle is grayed out?
A grayed-out toggle usually means the system service is stuck. Run sudo killall assistantd in Terminal, wait 5 seconds, then re-open System Settings — the toggle should be active again. If it's still grayed, you may have a managed Mac (school/corporate device) where dictation is disabled by MDM policy.
❓
Does Mac dictation need internet?
For English on Apple Silicon (M1+), no — the model runs on-device. For other languages or older Intel Macs, dictation requests audio chunks to Apple's servers per the Dictation privacy notice. To check your mode, look at the dictation indicator: a microphone icon means cloud, a microphone with a circle around it means on-device.
❓
What's the keyboard shortcut for dictation on Mac?
The default is the right Option key (⌥) double-tap or Fn key in older macOS versions. Customize at System Settings → Keyboard → Dictation → Shortcut. If the shortcut field is empty, dictation is enabled but won't trigger — set a shortcut explicitly.
❓
Is there a permanent dictation alternative for Mac?
Yes — MetaWhisp runs Whisper large-v3-turbo entirely on the Neural Engine. No daemon, no iCloud, no 60-second cutoff, 30+ languages. Free for unlimited local use. It survives macOS updates because it doesn't depend on Apple's speech stack.
How Do I Prevent Mac Dictation From Breaking After the Next Update?
You can't fully prevent it — Apple controls the daemon stack and ships changes you don't see until they break. But you can shorten recovery time. First, screenshot your working Dictation settings before installing any major macOS update; after the update, restore the screenshot's shortcut and language values manually. Second, keep at least 10 GB free disk so the language model has room to re-download. Third, before updating, sign out and back into iCloud — this clears any expired sessions that Enhanced Dictation depends on. Fourth, install macOS point releases (15.1, 15.2) only after they've been out 14 days; the first week reveals regressions, the second sees a hotfix release.
For users who can't tolerate any downtime — court reporters, therapists writing session notes, journalists transcribing interviews on deadline — relying solely on Apple Dictation is a risk. The structural answer is to pair Apple Dictation (when it works) with a backup tool that's independent of Apple's stack. MetaWhisp fills that role: when Apple Dictation breaks, switch to MetaWhisp's global hotkey, and your workflow continues without a help-desk ticket. The dual-tool setup adds zero friction once configured — both share the same microphone permission.
Pro tip: Set MetaWhisp's global hotkey to a key Apple Dictation doesn't use (e.g., Right Shift instead of Right Option). That way the two tools coexist — Apple Dictation on Right Option, MetaWhisp on Right Shift — and you fall back to whichever works without changing keyboards.
What If None of the Fixes Work?
If you've run all 7 fixes plus the prevention checklist and dictation still fails, you've crossed into "structural incompatibility" territory. The most common root cause at this point is one of: an MDM-managed Mac (school or corporate device) where IT policy disables dictation regardless of user settings, a damaged disk or filesystem causing the language model to corrupt on every redownload (run First Aid in Disk Utility, or boot into Recovery and run
fsck), or — rarely — a hardware issue with the microphone or audio controller. For MDM-managed Macs, the only path is to ask your IT admin to grant Dictation permission in the configuration profile. For disk corruption, back up first, then reformat in Disk Utility. For hardware, an Apple Genius Bar appointment is faster than continuing to debug software.
The pragmatic recommendation: rather than spend more hours debugging, install MetaWhisp as your primary dictation tool. It bypasses every layer where Apple Dictation fails — the daemon, the iCloud session, the language model cache, the microphone permission for system services. MetaWhisp asks for microphone permission once for itself (a regular app, not a system service), loads its model once on launch, and exposes a single global hotkey. You'll have working voice-to-text in under 5 minutes, and the next macOS update won't break it. The free tier has no time limits and works offline; the optional cloud tier ($30/year) adds AI-powered post-processing for English correction. OpenAI's Whisper — the model MetaWhisp runs — has been the open-source state-of-the-art for general-purpose speech recognition since 2022.
Pro tip: Even if you eventually fix Apple Dictation, keep MetaWhisp installed as a fallback. The setup time was already paid; having a backup tool that works in 100% of cases is worth keeping around for the next time Apple ships a regression. Real estate cost: ~50 MB app + ~1.5 GB model file. That's less than the macOS Photos cache.
About the Author
I'm Andrew Dyuzhov — solo founder of MetaWhisp. After watching Apple Dictation break on three consecutive macOS updates between 2024 and 2026, I built MetaWhisp to be the dictation tool I wish existed: zero dependency on Apple's daemon stack, model file you control, no internet required. Find me on X: @hypersonq.
--- Related reading: