Voice to Text Mac Not Working: 12 Fixes for Every Common Problem
Voice to text Mac not working is one of those problems that feels like it should have a simple fix. Sometimes it does. But most of the advice floating around Apple forums treats all dictation failures the same way — and they're not. Here's the thing: the fix depends entirely on which of two categories your problem falls into. Category one is cloud-dependent failures, where dictation stops because Apple's feature relies on a server connection that's unavailable, throttled, or blocked by your network. Category two is hardware and software failures — local to your machine, fixable without touching your router. This guide walks through 12 specific fixes in order, starting with the diagnostic question most guides skip entirely.
TL;DR
- Cloud-dependent failures (network timeouts, server errors, corporate firewall blocks) account for a large share of Mac dictation problems and can't be fixed with mic settings.
- Hardware and software failures include bad mic input, wrong audio source, stale speech files, and permission conflicts.
- For users who need dictation to work offline, on every network, and without sending audio anywhere, on-device processing is the only reliable solution.
Why Is My Speech to Text Not Working on Mac?
The most common cause surprises people: Apple's built-in Dictation requires an internet connection to process audio on Apple's servers. Users see their mic working fine in Zoom or FaceTime and assume it's a permissions issue. It usually isn't. If the microphone overlay appears — the small waveform indicator — your mic is working. What's failing is the round-trip to Apple's transcription servers.
Photo by Jakub Zerdzicki on Unsplash
Secondary causes include wrong microphone input source, outdated or corrupted speech recognition files, version-specific macOS bugs, and permission conflicts introduced by a recent OS update.
Step 1: Diagnose First - Is This a Cloud Failure or a Local Failure?
Before changing any settings, answer one question: does dictation fail on your home network but work fine elsewhere, or does it fail everywhere?
Photo by Sergey Meshkov on Unsplash
Fails only on certain networks — corporate VPN, office Wi-Fi, hotel connections? You're almost certainly dealing with a cloud-dependent failure. Apple's Dictation sends audio to remote servers, and many managed networks block or throttle that traffic. No settings change on your device will fix this. The problem is upstream.
Fails everywhere including home? Work through the local fixes below.
ping dictation.apple.com. If you get 100% packet loss on your work network but not at home, your IT team is blocking Apple's dictation endpoints. The only way around this is on-device processing that never touches the network.Step 2: Check Your macOS Version for Known Dictation Bugs
Not all macOS versions handle dictation equally. Here is what's documented:
Photo by Edmond Dantès on Unsplash
- macOS Ventura (13.0 - 13.2): Several users reported that Dictation would appear to activate (waveform shows up) but produce no text. Apple patched this in 13.3. If you're on 13.0-13.2, update first before anything else.
- macOS Sonoma (14.x): The introduction of Apple Intelligence in Sonoma created conflicts for some users where Voice Control and Dictation competed for the same audio session. Disabling Voice Control in Accessibility > Voice Control > Off resolves this in most cases.
- macOS Sequoia (15.x): Sequoia moved several dictation settings. The toggle is now under System Settings > Keyboard > Dictation, not under Siri & Spotlight as it was pre-Ventura. Many users look in the wrong place.
Step 3: Verify the Correct Microphone Input Source
This fix resolves the problem for a significant share of users in MacRumors and Apple Discussions threads. Go to System Settings > Sound > Input and check which device is selected. Macs with external monitors, USB audio interfaces, or Bluetooth headsets connected will often shift the default input away from the internal microphone — silently, without any notification.
Photo by Dmitrii Eremin on Unsplash
Set the input source to your intended mic, then watch the input level meter while you speak. Bars not moving? The problem is mic selection, not dictation.
Then go to System Settings > Keyboard > Dictation and check the Microphone Source dropdown. This is a separate setting from System Sound input and can be pointed at a completely different device. Set both to the same source.
Step 4: Reset Microphone Permissions
A macOS security update or new app installation can corrupt the privacy permission state. Go to System Settings > Privacy & Security > Microphone. Find the app where dictation isn't working. If it's toggled off, turn it on. If it's already on, toggle it off, wait 5 seconds, toggle it back on.
Photo by Erik Mclean on Unsplash
For Apple's own Dictation feature, the relevant entry is "Siri & Dictation" in that same list.
Step 5: Delete Stale Speech Recognition Files
Corrupted cached speech files cause dictation to silently fail — particularly after an OS upgrade. In Finder, press Cmd+Shift+G to open Go to Folder, then navigate to:
Photo by cottonbro studio on Unsplash
~/Library/Speech/Recognizers
Move any folders inside to the Trash. Then go to:
/Library/Speech/Recognizers
Do the same. Restart your Mac. macOS will rebuild these files on next use.
Step 6: Disable Voice Control If You Don't Use It
Voice Control (System Settings > Accessibility > Voice Control) is a separate system from Dictation, but both compete for the same microphone session. On macOS Sonoma and Sequoia, having Voice Control enabled while trying to use standard Dictation can cause one to silently block the other. If you don't use Voice Control for accessibility purposes, turn it off.
Why Is My Speech to Text Suddenly Not Working?
Sudden failures after a period of normal operation almost always trace back to one of three things: a macOS update that reset permissions or introduced a bug, a change in your network environment (new office, VPN policy update, IT security change), or a hardware change — like a new monitor or audio interface — that shifted your default input device.
Work through Steps 2, 3, and 4 in that order. They cover all three causes and resolve the majority of sudden-onset failures.
Step 7: Address the Microphone Overlay Appears But No Text Is Generated
One of the most frustrating failure modes because everything looks like it's working. The waveform animation shows up. It registers audio. Nothing gets typed.
Here's the thing: this specific symptom almost always means the audio is being captured locally but the transcription request to Apple's servers is failing silently. The server response timed out or returned an error, and macOS just... doesn't tell you.
Fixes to try in order:
- Disable any VPN and try again. Apple's dictation endpoints are sometimes blocked by VPN exit nodes.
- Go to System Settings > Keyboard > Dictation, turn Dictation off, wait 30 seconds, turn it back on. This forces a fresh server handshake.
- Check your Mac's date and time under System Settings > General > Date & Time. Incorrect system time causes SSL certificate failures that silently break server connections.
Step 8: Use Terminal to Reset the Dictation Assets
If the cache deletion in Step 5 didn't work, you can force macOS to fully re-download dictation language assets via Terminal:
defaults delete com.apple.assistant.support
defaults delete com.apple.Siri
Then restart your Mac. On next login, go to System Settings > Keyboard > Dictation, disable it, wait, and re-enable it. macOS will treat it as a fresh setup and pull down fresh assets.
Why Has My Dictation Stopped Working? (And What Enhanced Dictation Was)
If you used Mac dictation before macOS Ventura and remember it working offline, you were using Enhanced Dictation — a feature Apple offered from macOS Sierra through Monterey that downloaded a local language model for offline processing. Apple removed Enhanced Dictation in macOS Ventura (13.0), released in 2022. Every version since then, including Sonoma and Sequoia, requires a live server connection for standard Dictation.
This is not a bug. It's a deliberate architectural change. And it means that if your network environment has changed since Ventura, the offline-capable dictation you relied on is simply gone from the built-in tools.
Bottom line: if you're on macOS Ventura or later and your network blocks Apple's servers, Apple's built-in Dictation will not work. Period. No amount of troubleshooting changes that.
How Do I Activate Voice to Text on Mac?
Activating dictation on a MacBook Pro, MacBook Air, or iMac takes about 60 seconds:
- Open System Settings.
- Click Keyboard.
- Scroll to the Dictation section and toggle it On.
- Choose your language from the dropdown.
- Set a keyboard shortcut (the default is pressing the Fn key twice, but you can change this).
- Click the text field where you want to type, press your shortcut, and start speaking.
The first activation will prompt a download of language files. You need an internet connection for this initial setup.
Step 9: Test Dictation in a Different App
Some apps actively block text input injection from system-level services. If dictation works in TextEdit or Notes but not in Notion, Slack, or a web app, the problem is app-level — not system-level.
For web apps specifically (Google Docs, Notion web), the browser needs microphone permission granted separately, and the web app's own input model may interfere with macOS text injection. Google Docs Voice Typing uses its own separate voice input pipeline that bypasses macOS Dictation entirely.
In practice, voice-to-text not working in one specific app is rarely a macOS problem. It's a that-app problem.
Step 10: Check Hardware - Intel vs. Apple Silicon Performance Differences
If you're troubleshooting voice to text Mac not working on an older Intel Mac, there's an additional factor worth knowing: Apple's on-device speech processing features in Sequoia are primarily designed for Apple Silicon. Intel Macs running Sequoia are supported but may experience slower response times or dropped dictation sessions under CPU load.
To check: open Activity Monitor (Applications > Utilities > Activity Monitor) and watch CPU usage while dictating. Above 80%? Competing processes are starving the audio pipeline. Quit unnecessary apps and try again.
M1, M2, and M3 Macs have dedicated Neural Engine hardware that handles local audio processing without competing with general CPU workloads. On-device transcription tools optimized for Apple Silicon take particular advantage of this — which is why Apple Silicon Macs handle real-time transcription far more consistently than Intel machines.
Step 11: Evaluate Whether On-Device Processing Solves Your Root Problem
If you've worked through every step above and voice to text is still failing in certain environments, the honest answer is that Apple's cloud-dependent Dictation architecture isn't the right tool for your situation.
On-device processing means your audio never leaves your device. No server to time out. No network to block. No VPN to interfere. VoicePrivate processes everything locally using a local AI engine, downloads once on first run, and works completely offline after that — no internet connection needed for any subsequent use.
This matters specifically for:
- Healthcare environments where audio content is sensitive and HIPAA considerations apply. Because no data ever leaves the machine, VoicePrivate is designed for HIPAA environments without requiring a BAA. See VoicePrivate for Healthcare for more on how this works in clinical settings.
- Corporate networks where IT policies block external audio upload endpoints.
- Travelers and field workers who can't count on consistent internet access.
- Anyone who has had enough of cloud dictation silently failing.
Step 12: Export and Recover Your Transcription History
No other troubleshooting guide covers this. If dictation has been working intermittently and you have content you need to recover, here's what's actually available:
- Apple's Dictation doesn't save a transcript history. Text goes into whichever field you dictated into, and that's it. Mid-session failure means there's nothing to recover from the Dictation feature itself.
- VoicePrivate saves transcripts locally on your device with export options including plain text (.txt), Markdown (.md), JSON (.json), SRT subtitles (.srt), and WebVTT (.vtt). Your session history stays on your device, accessible any time, with no cloud dependency. Particularly useful for professionals who need a record of dictated notes, meeting transcriptions, or client calls.
Frequently Asked Questions
What is the difference between Basic Dictation and Enhanced Dictation?
Enhanced Dictation was a macOS feature available from Sierra through Monterey that downloaded a local speech model for offline use. Apple removed it in macOS Ventura (2022). Since Ventura, standard Mac Dictation requires a live internet connection. There is no longer a built-in offline dictation option in macOS.
Does Apple Intelligence fix the offline dictation problem in Sequoia?
No. Apple Intelligence adds on-device Siri capabilities but does not restore offline keyboard Dictation. Standard Dictation in macOS Sequoia still requires a server connection.
Why does dictation work in some apps and not others?
Some apps block system-level text injection. Web apps in browsers add another layer, since the browser needs its own microphone permission separate from the OS. Test in TextEdit first to confirm whether it's a system issue or an app issue.
For a broader look at voice-to-text options on Mac beyond just troubleshooting — including accuracy comparisons and workflow recommendations — see our Voice to Text for Mac: Speed, Accuracy, and Privacy for Power Users guide.
And if you want to understand exactly how VoicePrivate's privacy architecture works, the privacy page has the technical details.
Key Takeaways
- Voice to text Mac not working falls into two categories: cloud failures (network, server, VPN) and local failures (mic input, permissions, corrupted files). Diagnose which one before changing settings.
- Apple removed Enhanced Dictation in macOS Ventura. Every version since then requires an internet connection for built-in Dictation. This is by design, not a bug.
- If your environment blocks Apple's servers, no troubleshooting fix will restore cloud-dependent dictation. On-device processing is the only architecture that works regardless of network conditions.
- VoicePrivate processes audio entirely on your device, works offline after a one-time model download, and exports transcripts in five formats including SRT, WebVTT, and JSON.
- Apple Silicon Macs (M1/M2/M3) handle on-device transcription more consistently than Intel Macs due to dedicated Neural Engine hardware.