Why Dictation Works in One App but Not Another

You dictate a whole paragraph into Notes and it lands perfectly. You switch to another app, say the same words, and nothing happens. It feels random, but it almost never is. The reason usually comes down to how each app builds its text fields.

Why the same dictation behaves differently per app

Mac dictation is not a single switch that either works everywhere or nowhere. When you trigger it, macOS has to hand the recognized words to whatever app currently has your cursor. It does this through a set of shared text and accessibility interfaces. If the app is built with Apple's native text controls, those interfaces are already wired up and dictation flows straight in. If the app rolls its own text engine or wraps a web page, the connection is often missing.

That is why Notes, Mail and TextEdit almost always cooperate, while some chat clients, code editors and browser-based tools feel hit or miss. The dictation engine still hears you correctly. The words simply have nowhere to land. Apple describes the basics of turning the feature on in its own Mac dictation guide, but it does not promise identical behavior across every third-party app.

The usual culprits

When dictation refuses to type into a specific app, the cause is almost always one of these:

• Web-based apps. Many popular tools are browser windows in a native shell. Their text boxes are web elements, and macOS dictation cannot always target them the way it targets a real text field.
• Custom text engines. Some editors and creative apps draw their own text canvas instead of using Apple's controls, so the standard insertion path is missing.
• Secure input fields. Password boxes and other protected fields deliberately block automated text tools. This is a security feature, not a fault.
• Permissions and focus. If the app never received focus, or accessibility permission is off, macOS quietly drops the text with no error.
• Language mismatch. If the dictation language does not match what you are speaking, recognition fails and it looks like the app is at fault.

If your dictation starts fine and then quits mid-sentence rather than never firing, that is a different pattern worth its own read: see why Mac dictation stops after a few seconds. For a broader sweep of settings and system fixes, our full Mac dictation fix guide walks through each one in order.

How to fix dictation in a stubborn app

Work through these in order. Most cases clear up by step three.

A quick compatibility checklist

Before you blame the app, run this short check. It catches the silent failures that look like bugs but are really settings.

The system-wide fix that ignores app quirks

Native Mac dictation asks every app to meet it halfway. A system-wide dictation app flips that around. Instead of relying on each app to implement the dictation API, it records what you say, transcribes it on-device, and inserts the finished text wherever your cursor is, using the same standard paste path that already works everywhere.

That is how BlaBlaType stays consistent across email, chat, editors and browser tools. Speech recognition runs entirely on your Mac with local Whisper and Parakeet models, so your audio never leaves the device, and on-device AI cleanup removes filler and fixes punctuation before the words land. Because most people speak around three to four times faster than they type, getting dictation to work in the one app you actually live in is worth the setup. It is a good fit for anyone who drafts all day, from writers to paralegals capturing case notes by voice to people who find typing draining, including many who use voice to text for ADHD. You can compare plans on the pricing page once the trial confirms it types into your stubborn app.