Short answer: Voice to text fails in third-party Mac apps because Apple Dictation only inserts into standard macOS text fields. Browsers, Electron apps, and custom editors skip that protocol, so dictation drops silently. Grant microphone access, quit apps holding secure input, or use a tool that types at the cursor anywhere.
Dictation works perfectly in Notes and Mail, so you know your microphone is fine and the feature is on. Then you switch to Chrome, Slack, VS Code, or a Java app, press the dictation key, and nothing happens. No text. No error. Just the little microphone icon listening to you and dropping every word. If voice to text is not working in third-party apps on your Mac, the problem is almost never your hardware. It is how Apple Dictation decides where to put your words.
This guide explains why dictation silently fails in non-Apple apps, gives you a checklist of fixes to try, and shows you the approach that works in every app on your Mac regardless of how it was built.
Why Apple Dictation Fails in Third-Party Apps
Apple Dictation does not "type" your words. It hands the recognized text to whatever input field currently has focus, using the standard macOS text input protocol. Apple's own apps implement that protocol fully, which is why dictation feels flawless in Notes, Mail, Messages, and TextEdit. The trouble starts the moment your text field is not a standard Cocoa text field.
1. Non-standard text fields
Web browsers render text inside a web view, not a native text field. Electron apps (Slack, Notion, Discord, VS Code, and many others) are essentially packaged web pages. Java and Qt apps draw their own text widgets. None of these necessarily implement Apple's text input protocol the way a native field does, so when dictation tries to insert text, there is nowhere standard to put it, and the words are dropped.
2. Secure input mode is locked on
When any app enables "secure input" (the mode that stops keyloggers from reading password fields), it can stay locked on even after you leave the password field. While secure input is active, dictation and many text-insertion features stop working system-wide. A password manager, a terminal, or a browser login form that did not release secure input cleanly is a very common culprit, and it makes dictation fail in apps that would otherwise work fine.
3. Per-app microphone permission
macOS gates microphone access per app. Even though dictation is a system feature, the app you are dictating into may not have microphone permission, or may have had it revoked. Without it, the system can refuse to route dictation into that app.
4. Accessibility and automation restrictions
Some managed or hardened apps restrict the accessibility hooks that text insertion relies on. Corporate-managed Macs and certain security tools can block the very mechanism dictation uses to deliver text.
5. The app simply does not accept dictated input
A few apps intentionally or accidentally reject programmatic text insertion. Code editors with custom input handling and some design tools fall into this bucket. The field looks like a text field, but it does not behave like one as far as dictation is concerned. This is the same family of problems behind dictation not working in Microsoft Word on Mac and dictation not working in Safari.
The Fix Checklist
Run through these in order. The first few resolve most cases.
Fix 1: Confirm dictation works somewhere first
Open TextEdit or Notes and dictate a sentence. If it works there, your microphone, language, and dictation setup are all fine, and the problem is specific to the app you were using. If it fails everywhere, start with the broader Mac dictation not working fixes first, then come back here.
Fix 2: Clear a stuck secure input lock
This is the highest-value fix and the one most people miss. A wedged secure input session silently disables dictation across apps.
- Quit your password manager, then quit any terminal apps.
- Quit your browser if you recently used a login form.
- Log out of your macOS account and back in, or restart, to force-release secure input.
- Test dictation again in the third-party app.
If dictation springs back to life after this, secure input was the cause, and the app that held it is the one to watch next time.
Fix 3: Grant the app microphone permission
Open System Settings → Privacy & Security → Microphone and make sure the app you want to dictate into is listed and enabled. If it is missing, the app may need to request access once. Quit and reopen the app after granting permission.
Fix 4: Toggle Dictation off and on
Go to System Settings → Keyboard → Dictation, turn it off, wait ten seconds, and turn it back on. This rebuilds the dictation session and clears a service that may have wedged itself against a particular app.
Fix 5: Restart the app, then the Mac
Quit the third-party app completely (right-click the Dock icon and choose Quit, or use Force Quit) and reopen it. If that does not help, restart the Mac to reset the accessibility and dictation services every app depends on.
Fix 6: Update macOS and the app
Input-handling bugs get patched on both sides. Install pending updates from System Settings → General → Software Update, and update the third-party app to its current version. Electron apps in particular fix text-input regressions regularly.
Fix 7: Check for a conflicting Voice Control or accessibility tool
If Voice Control is running, it competes with Dictation for the same text fields and can block insertion. Turn it off under System Settings → Accessibility → Voice Control unless you need it. Other text-expansion or automation utilities can interfere similarly.
Fix 8: Use the dictate-then-paste workaround
If a specific app simply refuses dictation, dictate into Notes or TextEdit, then copy and paste into the stubborn app. It is friction, not a fix, but it keeps you moving while you decide on a permanent solution.
The Limitation You Cannot Fix
Here is the uncomfortable part. Fixes 2 through 7 address misconfiguration, but Fix 1's root cause, the app not implementing Apple's text input protocol, is not something you can change from System Settings. If an Electron app or a custom editor does not accept dictated input the way a native field does, no toggle will make Apple Dictation reliably insert text into it. You are dependent on each app's developer to support a protocol that many of them never fully implemented. That is why dictation feels like a lottery across your Mac: flawless in Apple apps, hit-or-miss everywhere else.
The way out is to stop relying on the app to cooperate, and instead place text the way a keyboard does.
The Approach That Works in Every App
Voice Keyboard Pro is a native macOS app that lives in your menu bar and takes a fundamentally different route to your text. You hold a hotkey, speak, and release, and your words are inserted at the cursor in whatever app is in front of you. It does not negotiate with each app's input protocol the way Apple Dictation does. It places text at your cursor system-wide, so it works the same in Chrome, Slack, VS Code, Notion, Discord, design tools, and the Terminal, exactly the apps where Apple's dictation tends to fail.
Because the text is delivered at the cursor rather than handed to a specific field type, the entire category of "this app does not support dictation" problems disappears. If you can type into it, you can dictate into it. That single design difference is why people who gave up on Apple Dictation in their daily tools come back to voice. There is more on the mechanism in how voice typing inserts text at the cursor in any app and how to dictate in any Mac app.
A few things that follow from that approach:
- Universal app coverage. Browsers, Electron apps, code editors, chat apps, terminals, the same places Apple Dictation drops words.
- One consistent hotkey. The same hold-to-talk gesture everywhere, instead of per-app behavior that changes from one window to the next.
- Smart Vocabulary. A personal dictionary with replacement rules so names, code identifiers, and jargon come out correct in every app.
- Meeting Mode. Speaker detection and AI notes for calls, plus calendar meeting detection so transcription is ready when your meeting starts.
- Privacy by design. Our servers store only operational pings. Your audio and transcribed text are not retained on the server.
The transcription runs on Voice Keyboard Pro's advanced AI transcription engine, so accuracy stays high across accents and background noise, and the finalized text lands at your cursor in about a second. If you want dictation that behaves identically in every app instead of a feature that works in five apps and fails in the other twenty, that is the entire point of the design.
Apple Dictation asks each app to accept your words. A cursor-insert approach just types them, so the app never gets a vote on whether voice works.
Quick Reference
If voice to text is not working in third-party apps on your Mac, do these first:
- Test in Notes. Confirms the problem is app-specific, not system-wide.
- Clear secure input. Quit your password manager, terminal, and browser, then restart. This fixes the most common silent failure.
- Grant microphone permission to the target app under Privacy & Security.
- Turn off Voice Control if it is running.
Those steps recover dictation in apps that were merely misconfigured. For the apps that never supported it properly, the fix is to deliver text at the cursor instead. Voice Keyboard Pro has a free tier, so you can open the app that has been ignoring your voice, hold the hotkey, and watch the words appear where Apple Dictation would not put them. For an overview of dictation that works everywhere on Mac, see the dictation app that works everywhere on Mac.
Frequently Asked Questions
Why does dictation work in Notes but not in Chrome?
Notes is a native Apple app that fully implements the macOS text input protocol, so dictation has a standard place to deliver your words. Chrome renders text inside a web view rather than a native field, and that web view does not always accept dictated input the way a native field does. The microphone and recognition are identical in both cases; only the destination differs. The same gap explains why dictation can fail in Electron apps like Slack and Discord that are built on web technology.
How do I know if secure input is blocking dictation?
The telltale sign is dictation failing across several unrelated apps at once, including apps where it normally works, often right after you used a password field or a terminal. Secure input is a system-wide lock, so when it is stuck on, it does not fail in just one place. The quickest test is to quit your password manager, terminal, and browser, then log out and back in. If dictation returns afterward, secure input was the cause.
Does Voice Control work in third-party apps when Dictation does not?
Voice Control uses a different and broader mechanism, so it can interact with some apps that Dictation cannot, but it is a full accessibility navigation system rather than a quick dictate-and-go feature, and it carries its own learning curve. It also competes with Dictation for control of text fields, so running both at once tends to cause conflicts. For straightforward dictation everywhere, a cursor-insert tool is simpler than switching your whole workflow to Voice Control.
Will third-party apps ever fully support Apple Dictation?
Some will, some will not, and you do not control which. Support depends on each developer choosing to implement Apple's text input protocol completely, and many web-based and cross-platform apps never have. Rather than wait on dozens of separate developers, the more reliable path is a tool that does not depend on the app cooperating at all, because it inserts text at the cursor the way a keyboard does. That is why the same hold-to-talk gesture works identically across every app on your Mac.