Speech to Text Chrome Extensions vs Native Mac Apps: What Actually Works

Chrome has a built-in speech recognition API, and a handful of extensions put a dictation interface on top of it. Voice In, Speechnotes, LipSurf — these are real tools that work in Gmail, Google Docs, and most other sites you'd open in a browser tab.

But they have a hard limit that isn't always clear from the extension store listing: they only work inside Chrome. The moment you switch to a native Mac app — Slack desktop, Mail.app, Microsoft Word, Notion, your IDE — the extension goes dark.

If you spend most of your day in Chrome, that might be fine. If you need dictation across your whole Mac, it's a fundamental mismatch between the tool and the task.

This post covers how Chrome speech-to-text extensions work, what the best options are, where they fall short, and how they compare to native Mac dictation.

How Chrome dictation extensions work#

Every Chrome extension that does voice-to-text is built on the same foundation: the Web Speech API, a browser standard that exposes speech recognition to websites and extensions.

When you activate a Chrome dictation extension, it taps Chrome's built-in speech engine. Chrome records your microphone, sends the audio to Google's servers for processing, and returns the transcript. The extension receives that text and types it into the active text field.

This has an important implication: even when an extension says it processes audio "locally in your browser," your audio still goes to Google. The extension doesn't store your voice — but Chrome's speech recognition backend does the processing, and that happens on Google's infrastructure.

The Web Speech API is also sandboxed to the browser. Extensions run inside Chrome's process and can only interact with content inside Chrome tabs. They have no access to other running applications on your Mac.

Voice In: the most capable Chrome dictation extension#

Voice In by Dictanote is the most fully featured Chrome speech-to-text extension available.

• Works in over 10,000 websites within Chrome
• Free tier covers major sites (Gmail, Google Docs, WhatsApp Web, Twitter)
• Paid tier (Voice In Plus, $39.99/year or $99.99 lifetime as of writing) unlocks broader site support, custom voice commands, and multi-tab dictation
• 50+ languages, 100+ dialects
• Activated via keyboard shortcut (Alt+L by default), or a click-to-talk button the extension adds to text fields

The accuracy is whatever Chrome's Web Speech API delivers — which is generally solid for everyday speech, comparable to what you'd get dictating into Google Docs natively.

Voice In is genuinely well-built for what it does. If you work primarily in Chrome and want dictation in web apps, it's the right tool.

The limitation is architectural: it works in Chrome tabs. That's it.

Other Chrome speech-to-text options#

Speechnotes is a web-based notepad (speechnotes.co) that uses Chrome's speech engine for dictation in their own app. It's more of a browser-based writing tool than an extension you'd use across Chrome — you go to their site and dictate there, then copy the text elsewhere.

LipSurf focuses more on voice navigation of websites (clicking links, filling forms, navigating) than pure dictation. It has a dictation mode but it's secondary to the navigation feature set.

Dragon Web Extension requires Dragon NaturallySpeaking desktop software on Windows. It's not relevant for Mac users.

The core limitation: browser-only#

Chrome extensions run inside Chrome's process. That's not a design choice any extension maker made — it's how Chrome works. Extensions interact with web content. They have no mechanism to communicate with other Mac applications.

In practice, this means:

• Slack desktop app: Chrome extension can't reach it. (Slack's web version at slack.com in Chrome: yes.)
• Mail.app: No.
• Microsoft Word for Mac: No.
• Notion desktop: No. (Notion's website in Chrome: yes.)
• Xcode, VS Code, Cursor: No.
• Terminal: No.
• Any native Mac app: No.

If you dictate into Gmail in Chrome, a Chrome extension works fine. The moment you open a different app, dictation stops working until you switch back.

This isn't a bug. It's the architectural boundary of browser extensions.

Privacy: audio goes to Google's servers#

When you use a Chrome extension for dictation, your audio takes this path:

1. Chrome records your microphone
2. Chrome sends the audio to Google's speech recognition servers
3. Google returns a transcript
4. The extension types that text into the active field

The extension vendors (like Dictanote, which makes Voice In) don't receive your audio. But Google does. Voice In's privacy policy acknowledges this: audio processing is handled by the browser's native speech recognition, which is Google's implementation.

Google reportedly does not retain or use this audio for training — there are contractual agreements between Chrome extension developers and Google about this. But the processing happens on Google's servers regardless. If your work involves anything sensitive — legal, medical, financial, confidential business — that's a meaningful distinction.

Native Mac dictation apps that run on-device (using Whisper or Apple's speech engine) process audio without it ever leaving your Mac.

Chrome extensions vs native Mac apps: direct comparison#

The two categories of tools are solving different problems. Chrome extensions are browser utilities. Native Mac apps are system-level dictation tools.

When a Chrome extension is the right choice#

A Chrome extension makes sense if:

• You spend almost all your dictation time inside Chrome (Gmail, Google Docs, Notion web, Slack web)
• You're comfortable with audio going through Google's servers
• You want free or low-cost dictation for occasional browser use
• You don't need to dictate outside the browser

For that use case, Voice In is a reasonable solution. It's free for the most common sites and works well within its scope.

When a native Mac app is the better fit#

A Chrome extension stops being sufficient when:

• You use native Mac apps — any desktop apps, not just browser-based ones
• You need dictation to work reliably across your whole Mac with a single hotkey
• You want audio to stay on your device (privacy, sensitive content, no internet required)
• You need offline dictation that keeps working on a plane or in a spotty connection
• You want AI cleanup — turning raw speech into polished text — before it pastes

If your work crosses browser and desktop apps throughout the day, constantly switching back to Chrome just to dictate becomes friction. The right tool for this is a system-wide dictation app.

System-wide dictation on Mac#

macOS has built-in dictation (System Settings > Keyboard > Dictation) that works across all apps — not just Chrome. It's free, and on Apple Silicon it runs on-device. The downside: it has a session timeout around 30–60 seconds, which cuts off mid-dictation for anything longer than a paragraph. There's also no AI cleanup step.

Hearsy is a Mac menu bar app that handles system-wide dictation without the timeout. Press a global hotkey from any app — Chrome, Mail, Slack desktop, VS Code — record as long as you need, and the transcribed (and optionally AI-polished) text pastes directly into whatever was active. Transcription uses the Parakeet model (about 0.2 seconds on M-series chips) or Whisper for broader language support. Nothing leaves your Mac.

For a comparison of the built-in options, see Mac dictation guide and Siri Dictation on Mac: what it can and can't do.

FAQ#

Do speech to text Chrome extensions work in all Mac apps?#

No. Chrome extensions can only reach text fields inside Chrome or Edge browser tabs. They have no access to native Mac applications — Mail.app, Slack desktop, Microsoft Word, Notion desktop, code editors, or any other app running on your Mac.

What is the best speech to text Chrome extension?#

Voice In by Dictanote is the most capable Chrome dictation extension. The free tier covers Gmail, Google Docs, and major sites. Voice In Plus ($39.99/year as of March 2026) unlocks custom voice commands and broader site coverage across 10,000+ websites within Chrome.

Do Chrome voice typing extensions work offline?#

No. Chrome's Web Speech API — the engine behind most dictation extensions — requires an internet connection. Audio is sent to Google's servers for recognition. For offline dictation, you need a native Mac app that runs a local speech model on-device.

Does audio go to Google when I use a Chrome extension for dictation?#

Yes. Chrome's built-in speech recognition sends audio to Google's servers for processing, even when the extension describes its processing as "in-browser" or "local." The extension itself doesn't store the audio, but Google receives and processes it.

What is the difference between a Chrome dictation extension and a Mac dictation app?#

Scope. Chrome extensions work inside browser tabs only. Native Mac dictation apps — like macOS built-in Dictation or Hearsy — use a global hotkey that works from any app on your Mac, paste text directly into whatever's active, and can run speech recognition entirely on-device.

---

Chrome speech-to-text extensions are useful browser tools, not system-wide dictation solutions. If your workflow is browser-based, Voice In handles it well. If you need dictation that follows you across every app on your Mac — with a single hotkey, offline, and without audio leaving your device — a native Mac app is the right category of tool.

For more on Mac-native dictation options, see the complete speech to text Mac guide and Voice Control on Mac.