Mac Dictation Not Working in Arc? 9 Fixes That Work

Short answer: If Mac dictation is not working in Arc, enable Arc under System Settings, Privacy & Security, Microphone, then quit Arc completely and reopen it. If the shortcut does nothing, check that the Command Bar or a password field has not taken keyboard focus, since Arc holds focus differently from other browsers.

Arc is built on Chromium, so on paper dictation should behave exactly as it does in Chrome. In practice it often does not, and the reason is the layer Arc adds on top: a command-driven interface with its own focus rules, a sidebar that doubles as an address bar, pop-out windows that are not quite normal windows, and a customisation system that can rewrite the page you are typing into.

None of those are bugs. They are the reason people like Arc. But each one can quietly sit between your voice and the text field, and the failure looks identical from the outside: you trigger dictation, something may or may not appear on screen, and no words land.

Work through the checks below in order. They are arranged by how often they turn out to be the cause, so most people are fixed within the first three.

First, identify which dictation is failing

This takes thirty seconds and saves an hour. Two different systems both get called "dictation in Arc," they break for unrelated reasons, and a fix for one does nothing at all for the other.

System dictation, which belongs to macOS

This is the Mac's own voice input, triggered by the shortcut you set in System Settings, most commonly a double press of the Globe or Fn key. It is part of the operating system. It has no opinion about which website you are on. It listens, then inserts characters into whatever field currently has keyboard focus, the same way a keyboard would. When this is the thing that fails, the cause is nearly always a macOS permission or a focus problem, not an Arc setting.

In-page voice input, which belongs to the website

This is the microphone button inside a web app, or Google Docs Voice typing, or the record button in a browser-based recorder. The page asks the browser for microphone access, and the browser asks macOS. When this fails, the cause sits in Arc's site permissions or in the page itself.

The test: open TextEdit or Notes, trigger your dictation shortcut, and say a sentence. If text appears there but not in Arc, you have an Arc-specific problem and the fixes below apply directly. If it fails in TextEdit too, the problem is system-wide and you should start with the full macOS dictation fix list instead.

Fix 1: Grant Arc the microphone permission, then fully quit it

This is the single most common cause, and the second half of the instruction matters as much as the first.

Open System Settings, go to Privacy & Security, then Microphone. Find Arc in the list and switch it on. If Arc is not in the list at all, it has never requested the permission, which usually means you have never triggered anything that needed it inside Arc.

Now quit Arc properly. Not closing the window, which in Arc often leaves the application running. Press Command Q, or right click the Arc icon in the Dock and choose Quit. macOS hands the new permission to an application when it launches, so a browser that stayed alive through the change keeps behaving as though the permission were still denied. This is why people swear they toggled the setting and nothing changed. They did toggle it. Arc simply never restarted to receive it.

Relaunch Arc and try again.

Fix 2: Confirm dictation is actually enabled in macOS

Worth ruling out early, particularly on a Mac that has been through a recent system upgrade, because major macOS updates have been known to reset the toggle.

Go to System Settings, Keyboard, and find Dictation. Make sure it is on, and note the shortcut listed underneath. Change it to something deliberate if you are unsure what yours is. A single press of a key you already use is a bad choice, because normal typing will trigger it. If the shortcut is the part that seems broken rather than dictation itself, there is a longer walkthrough in our guide to the Mac dictation shortcut not working.

While you are there, check the dictation language matches what you are speaking. A mismatch does not produce silence, it produces nonsense, which people often misread as a microphone fault.

Fix 3: Make sure the text field actually has focus

Arc earns this its own fix, because its interface invites the exact mistake that causes it.

Arc's Command Bar is both a launcher and an address bar, and it opens over the page. If it is open, or if it closed but focus never returned to the page, your dictation shortcut fires into a field that is not the one you are looking at. Words either vanish or turn into a search.

Before dictating, click directly inside the text box you want to fill, and look for a visible cursor blinking in it. Press Escape first if the Command Bar is showing. If you switched to Arc from another application using Command Tab, click into the field rather than assuming focus followed you.

The sidebar causes a subtler version of the same problem. Clicking a tab in the sidebar gives the sidebar focus. The page is visible and looks active, but the keyboard is still pointed at the list of tabs. One click in the body of the page fixes it.

Fix 4: Check the site's microphone permission inside Arc

This one applies to in-page voice input, not the macOS shortcut.

Arc uses Chromium's permission model, so each site is granted or denied the microphone individually, and a denial is sticky. If you dismissed a permission prompt in a hurry weeks ago, the site is now permanently blocked and will never ask again.

Click the padlock or site information control next to the address for the site in question and look for the Microphone entry. Set it to Allow, then reload the page. If you cannot find the per-site control, open Arc's settings and look under Privacy and security, Site settings, Microphone, where blocked sites are listed together and can be removed from the block list.

Reload after any change. Permission state is read when the page loads, so a page that was already open will keep acting on the old answer.

Fix 5: Watch out for Little Arc and pop-out windows

Arc opens external links in a lightweight window rather than a full tab. It is genuinely useful, and it is also a common dictation trap.

These transient windows are designed to be dismissed quickly, which means focus behaves differently inside them and anything you dictate can disappear along with the window when it closes or gets promoted into a tab. If you are trying to dictate a real reply into one of these windows, move it into a proper tab first, then dictate.

The same caution applies to any small floating composer, including the reply windows some web mail clients open. Give the text a stable home before you start speaking into it.

Fix 6: Disable Boosts for the page

Boosts let you change how a site looks and behaves with custom styling and scripts. If you have a Boost active on the site where dictation fails, it is a legitimate suspect, because it can restyle or replace the very input element you are dictating into.

Turn the Boost off for that site and reload. If dictation starts working, you have your answer, and you can decide whether the Boost is worth the friction. Boosts that hide elements or rearrange layouts are the most likely offenders, since a hidden or relocated input can still hold focus while behaving oddly.

Extensions deserve the same treatment. Arc supports Chrome extensions, and grammar checkers, clipboard managers and password managers all intercept input events. Disable them one at a time on the failing page rather than all at once, or you will not learn which one was responsible.

Fix 7: Break a Secure Input lock

This is the fix that looks like magic when it works, because the symptom is so absolute: dictation does nothing anywhere, in every application, with no error message at all.

macOS has a mode called Secure Input that blocks other processes from reading keystrokes. Password fields switch it on, which is exactly right. The problem is that an application can fail to switch it off, and then the entire system behaves as though dictation has been uninstalled. Browsers are a frequent culprit, because password fields live inside web pages.

To clear it, close any tab or window containing a password field, log out of your Mac account and back in, or restart if that is quicker. If it keeps coming back, note which site you were on when it started, since the same login page usually triggers it repeatedly.

Fix 8: Reset Arc's permissions and clear site data

If the site permission looks correct but the microphone still fails on one particular site, its stored state may be corrupt.

In Arc's settings, under Privacy and security, Site settings, find the site and reset its permissions entirely. Clearing cookies and site data for that domain is the more thorough version, at the cost of signing you out. Reload, and answer the permission prompt when it appears rather than dismissing it.

Do this for one site at a time. A blanket clear of all browsing data will sign you out of everything and rarely tells you anything useful about the cause.

Fix 9: Rule out the hardware and the input source

Before blaming software, confirm the Mac is listening to the microphone you think it is.

Open System Settings, Sound, then Input, and speak. The level meter should move. If it does not, the selected input device is wrong or unavailable. Bluetooth headsets are the usual explanation: the Mac connects to them silently and routes input away from the built-in microphone, and a headset that is out of battery or across the room still holds the input source.

Video calls are the other one. A call application that did not release the microphone when the call ended can keep the device occupied. Quit it fully rather than closing its window, and check the orange microphone indicator in the menu bar to see whether something is still recording.

Quick triage table

When Google Docs Voice typing is greyed out

This deserves separating from the rest, because it is not a permission problem and no amount of toggling will fix it.

Google Docs Voice typing relies on a speech service that Chrome provides. Chromium-based browsers other than Chrome do not always ship it, and when it is missing the menu item is simply greyed out or absent. There is no setting to enable it, because the component is not there to be enabled.

You have three options. Open that document in Chrome when you need to dictate into it, which works but means keeping a second browser around for one feature. Dictate elsewhere and paste, which is tedious. Or use dictation that operates at the system level and types into the page the same way your keyboard does, which never asks the browser for anything. The same pattern shows up in other privacy-focused Chromium browsers, and we covered it in more detail in the guide to dictation not working in Brave.

The approach that sidesteps the browser entirely

Look at what the fixes above have in common. You are negotiating with three separate permission layers, plus the website, plus whichever browser feature happens to hold focus at that moment. That negotiation resets every time you adopt a new web app, and a browser update can undo it. For occasional dictation that is a tolerable annoyance. If speaking is how you write, it is a recurring tax.

Voice Keyboard Pro removes the browser from the equation. It lives in your Mac's menu bar. You hold your hotkey, speak, release, and the text appears at your cursor in whatever app has focus, including Arc, including a Boosted page, including a Little Arc window. Because it types at the cursor rather than asking the page for microphone access, Arc's own behaviour is irrelevant to it. One permission, granted once, applies everywhere on the machine.

That also resolves the Google Docs problem, since nothing is asked of any browser speech service. On privacy, our servers store only operational pings. No audio and no transcript content is kept.

A few things that matter once dictation becomes your main input method rather than an occasional trick:

• Smart Vocabulary is a personal dictionary with replacement rules, so the client names, product names and jargon that browser dictation mangles come out right every time.
• Meeting Mode detects who is speaking and drafts notes, which covers the browser-based calls where in-page transcription is exactly the kind of script an extension or Boost is likely to interfere with.
• Calendar meeting detection notices a meeting starting and offers to capture it.
• The iPhone keyboard carries the same thing to your phone, with a built-in mic button that works in any iOS app, plus Voice Edit for fixing a sentence by speaking the change, two-way translation across 24 languages, and swipe typing for when speaking is not an option.

On speed, the arithmetic is unchanged. Comfortable speech runs at 130 to 150 words per minute. The average adult types around 40, and even a genuinely fast typist lands around 80 to 100. The reason people push through permission dialogs at all is that the payoff is real. It is simply better to collect that payoff without the dialogs.

If dictating one paragraph requires a permission, a relaunch, and a check on which part of the browser holds focus, the tool is sitting in the wrong layer of the stack.

Frequently asked questions

Does Arc support voice typing?

Arc supports microphone access for websites, so web apps that record and transcribe on their own work normally once the macOS permission and the site permission are both granted. Arc does not add a dictation feature of its own, so the Mac's system dictation and any app-level tool work in Arc the same way they work in any other application.

Why does dictation work in Chrome but not Arc on the same Mac?

Usually because Chrome already holds the macOS microphone permission and Arc does not, which fix 1 resolves. The other two common reasons are focus, since Arc's Command Bar and sidebar can take the keyboard when you think the page has it, and the Google speech service that Chrome ships and other Chromium browsers may not.

Do Boosts break dictation?

Not by design, but they can. A Boost that restyles, hides or rearranges page elements may affect the input field you are dictating into. Turning the Boost off for that one site and reloading is a quick way to confirm or eliminate it.

Will an Arc update reset my microphone permission?

Browser updates usually preserve site permissions. macOS upgrades are the ones that reset operating-system level grants for applications. If dictation stopped right after a system update, recheck Privacy & Security, Microphone before changing anything inside Arc.

What about dictation in Arc on iPhone?

On iOS the picture is different, because dictation comes from the keyboard rather than the browser. Any keyboard with a microphone works in Arc on iPhone the same way it works in Safari, which is why a keyboard-level tool ends up being the more portable answer across both devices.

What to do next

Start with the triage table. For most people the answer is fix 1, a macOS microphone permission that Arc never received, followed by a genuine quit and relaunch rather than closing the window. If the shortcut fires but the words go somewhere unexpected, it is focus, and fix 3 is a single click. If Google Docs Voice typing is greyed out, stop troubleshooting, because the service is not present to be repaired.

And if you are reading this because dictation has now needed babysitting in a third browser, that is the signal to move voice input down a layer. Voice Keyboard Pro has a free tier on both Mac and iPhone. Install it, grant one permission, and dictate into Arc with your Boosts and your sidebar exactly as you like them.