Short answer: Pages has no dictation feature of its own, so when dictation fails there, the fault is either in the system Dictation service or in where your cursor is sitting. Confirm dictation works in TextEdit first. If it does, the problem is the document: placeholder text, a locked object, or read-only permissions.
The single most useful thing to know about this problem is that Pages does not have a dictation feature. There is no dictation button in the Pages toolbar, no dictation preference in Pages settings, and no Pages update that can fix or break it. What you are using is Apple's system-wide Dictation, a macOS service that types into whatever text field currently has focus. Pages is simply the app receiving the text.
That one fact reorganises the whole troubleshooting process. When people search for why dictation is broken in Pages specifically, they are usually looking for a Pages setting that does not exist. The real answers live in two places: the system service that produces the text, and the state of the document that is supposed to receive it. Pages happens to be unusually good at putting your cursor somewhere that looks like a text field but is not one, which is why this app generates the complaint more often than its share of users would suggest.
Below is the sequence we would work through, ordered so the cheapest and most common checks come first. Most people are finished by fix three.
Start here: the TextEdit split test
Before changing a single setting, open TextEdit and create a blank document. Use whatever shortcut normally starts dictation. Say a short sentence, something like "this is a test of dictation, period."
You now have two very different problems depending on what happened.
If nothing appears in TextEdit either, Pages is innocent. The system Dictation service is off, misconfigured, or not hearing your microphone. Work through fixes 1, 2, 3, and 8 below and ignore everything about documents.
If text appears normally in TextEdit, the service is healthy and the words are being produced. Something about your Pages document is refusing them, or accepting them and then changing them. Skip to fixes 4, 5, 6, and 7.
This thirty-second test saves people from resetting permissions and reinstalling things for a problem that turned out to be a locked text box. It is worth doing every single time before anything else.
Fix 1: Confirm Dictation is actually turned on
Open System Settings, go to Keyboard, and look at the Dictation section. The toggle needs to be on. If it is off, switch it on and accept the confirmation sheet that appears.
Two things commonly turn this off without the user noticing. A major macOS upgrade can reset it, particularly if the previous state was carried over from a much older version. And a Mac that was set up from a migration or a Setup Assistant restore sometimes arrives with Dictation off even though the old machine had it on.
While you are on that screen, note two settings you will need later: the language list and the shortcut. Both are involved in later fixes.
If the toggle refuses to stay on, or the section is greyed out entirely, jump ahead to fix 9. That is the signature of a device management profile or a Screen Time restriction, not a bug.
Fix 2: The shortcut is being pressed, but nothing is listening
The default trigger on modern Macs is pressing the Globe key twice, or on some hardware, pressing Control twice. Both defaults share the same weakness: they are a double press of a key that also does something on a single press, and the timing window is narrow. If your two presses are slightly too slow, macOS reads them as two separate presses of the Globe key, which means it opens the emoji picker or cycles your input source instead of starting dictation.
The tell is simple. If pressing the trigger makes the emoji viewer appear, or makes the menu bar language flag change, the shortcut fired but the timing missed. Try again, faster.
The permanent fix is to change the shortcut to something that is not a double press. In the Dictation section of Keyboard settings, use the Shortcut dropdown and choose a single dedicated key. The function keys F13 through F19 are unclaimed by almost everything and are a common landing spot. A key nothing else wants cannot be mistimed and cannot be stolen by an app.
Pages itself claims relatively few global shortcuts compared to a code editor, so conflicts with Pages menu commands are rare. If you are the kind of person who also fights this in other apps, our guide to the Mac dictation shortcut not working covers the conflict-hunting process in more detail.
Fix 3: Pages is not in the Microphone list, and that is normal
This is the fix people spend the most time on for no reward, so it deserves stating clearly. Open System Settings, go to Privacy & Security, then Microphone. Scroll the list. Pages is very likely not there at all.
That is expected behaviour. Apple Dictation runs as a system service, not inside Pages, so Pages never requests microphone access and never appears in that list. Nothing is missing. Adding it is not possible, and its absence is not the cause of your problem.
What does matter is the microphone itself. Open System Settings, go to Sound, then the Input tab. Speak normally and watch the input level meter. If the bars do not move, dictation has nothing to transcribe, and no amount of permission-fiddling will change that. Check that the correct input device is selected, especially if you have a headset, a webcam with a built-in mic, an audio interface, or a monitor that presents itself as an input device.
The microphone permission list does become relevant if you use a third-party dictation app rather than Apple's. Those apps do appear there, and they usually also need Accessibility permission to type into other applications.
Fix 4: Your cursor is not in a text field, even though it looks like it is
This is the Pages-specific one, and in our experience it accounts for most cases where TextEdit works and Pages does not.
Pages documents are made of objects. Body text, text boxes, shapes with text inside them, table cells, headers and footers, captions, and template placeholders are all separate things with separate rules about when they accept typed input. Dictation types into the focused text-editing context. If nothing is in a text-editing state, the words have nowhere to go and are silently dropped.
The specific traps, in the order we see them:
- Template placeholder text. Open any Pages template and the grey sample text is placeholder content. A single click selects the whole placeholder as an object rather than putting a cursor inside it. Double-click into it first, then dictate.
- Text boxes and shapes. One click selects the box. You need a second click, or a double-click, to get an insertion point inside it. A selected box with no insertion point will not take dictated text.
- Locked objects. If an object is locked, it will not accept edits at all. Select it and check the Arrange menu for the Unlock command.
- Page layout documents. In a page layout document, unlike a word processing one, there is no continuous body text flow. Every scrap of text lives in a box, so there is no default place for a cursor to be. Clicking an empty area of the page puts you nowhere.
- Headers, footers, and the table of contents. Headers and footers only become editable when you move the pointer to the top or bottom margin and click in the field that appears. An auto-generated table of contents is not directly editable at all.
The test is to type a single character on your keyboard before you dictate. If typing does nothing, dictation was never going to work either, and you have found your problem in a form that has nothing to do with dictation. If typing works and dictation does not, move on to the next fix.
Fix 5: The document is read-only, locked, or shared with view-only access
A document that will not accept edits will not accept dictated edits. Pages presents this state in several different ways, and not all of them are loud about it.
Check the title at the top of the window. If it shows a Locked label, click the title and turn off Locked in the sheet that appears. macOS also auto-locks documents that have not been changed in a long time, which surprises people returning to an old draft.
If the file came from someone else, it may be read-only at the filesystem level. Select the file in Finder, press Command-I, and check the Sharing & Permissions section at the bottom of the info window. Files copied off a locked disk image, a read-only network share, or an email attachment opened directly from the message often arrive this way. Duplicating the file gives you an editable copy.
For collaborative documents, check your own access level. If the owner shared the document with view-only permission, you can select and copy text but not change it. Pages will show the document normally, which makes this look like a dictation failure rather than a permissions one.
Fix 6: Dictation language does not match what you are speaking
Dictation transcribes in the language it is configured for, not the language it hears. When the two disagree, you do not get an error. You get plausible nonsense, or a handful of words followed by nothing, which reads as a malfunction rather than a settings mismatch.
In System Settings, Keyboard, Dictation, check the Languages list. If you speak more than one language, add each one there rather than switching the whole system. Note also that the dictation language and your keyboard input source are separate settings that do not follow each other. Someone with a UK keyboard layout dictating in US English is fine. Someone with dictation set to a language they are not speaking is not.
Bilingual writers hit a subtler version of this: names, technical terms, and place names from a second language get force-fitted into the phonetics of the configured language. That is not a bug being triggered by Pages, it is the expected behaviour of any transcription that has been told to expect one language.
Fix 7: The text arrives, then Pages changes it
This is a different failure from the ones above, and it is worth separating because the fix is in Pages rather than in system settings. Here, dictation is working perfectly. Pages is rewriting the output afterwards.
Open the Edit menu, go to Substitutions, and look at Show Substitutions. The relevant offenders are:
- Smart quotes, which convert straight quotes to curly ones. Harmless in prose, damaging if you are writing anything that will later be pasted into code or a form.
- Smart dashes, which convert typed hyphen sequences into en and em dashes.
- Text replacement, which swaps abbreviations for expansions. If you have replacement rules configured, dictated words that happen to match a trigger will be swapped without warning.
- Automatic capitalisation and spelling correction, which will helpfully "fix" surnames, product names, and technical vocabulary into more common words.
Separately, check the auto-punctuation setting in the Dictation section of Keyboard settings. When it is on, the system inserts commas and full stops based on your phrasing and pauses, and it will also ignore some spoken punctuation commands because it believes it is handling punctuation for you. When it is off, spoken commands like "comma" and "new paragraph" are honoured literally. Neither setting is correct in general, but having the wrong one for your speaking style produces text that looks broken. We cover the whole punctuation problem in Mac dictation punctuation not working.
Fix 8: Bluetooth audio, sleep, and the input device that changed under you
If TextEdit failed too, and Sound settings showed no input level, the cause is usually the audio chain rather than dictation.
Bluetooth headsets are the most frequent culprit. A headset that is connected for listening is not necessarily connected as an input device, and when it does switch to its microphone mode, audio quality drops sharply because the profile changes. Some headsets take a second or two to make that switch, which clips the beginning of your first sentence and makes it look like dictation is missing words. Try disconnecting the headset entirely and using the built-in microphone to isolate this.
Waking from sleep is the other one. Audio devices can come back in a confused state after a long sleep, particularly on a Mac that also has an external display with speakers or a dock. If dictation worked yesterday and stopped today without anything changing, and your Mac has not been restarted in a while, restart it before investigating further. That is unsatisfying advice but it resolves a real class of audio-stack problems.
Also check whether another app is holding the microphone. A video call left running in the background, a recording app, or a browser tab with an active call can claim the input in a way that leaves dictation hearing silence. Quit anything with a live microphone session and try again.
Fix 9: Managed Macs, Screen Time, and profiles
If the Dictation toggle is greyed out, refuses to stay on, or disappears entirely, the machine is being managed.
On a work Mac, an MDM profile can disable Dictation and Siri outright, usually as a data-handling policy rather than a targeted decision about dictation. Check System Settings, General, then Device Management. If a profile is listed, its restrictions are enforced by the system and cannot be overridden locally.
On a personal Mac, Screen Time content restrictions can produce a similar effect. Check Screen Time, then Content & Privacy, and look for restrictions covering Siri and Dictation. Family-managed accounts sometimes acquire these without the account holder knowing.
Neither situation is fixable from your side. What is worth knowing is that these policies target Apple's Dictation service specifically. They do not necessarily cover other input methods, though your organisation's policy may have views about that. Ask before installing something on a managed machine.
Four behaviours that look like bugs and are not
Dictation stops after a pause. The system stops listening after a period of silence. That is a timeout, not a crash. If you plan your sentence in silence and then speak, you will keep hitting it. Start the sentence and think aloud instead.
The first word or two goes missing. There is a short window between triggering dictation and the microphone being live. Speaking instantly loses the beginning. Pause for a beat after the trigger.
Names and jargon come out wrong. Transcription resolves ambiguous sounds toward common words. An unusual surname or a product name will lose that contest most times. This is not a Pages problem and not a microphone problem.
Numbers format inconsistently. Whether you get "twenty five" or "25" depends on context and phrasing, and it is genuinely inconsistent across sentence positions. If a document depends on exact numeric formatting, expect to fix it afterwards regardless of which tool produced it.
Why Pages amplifies all of this
Pages is a good app that happens to combine three properties that are hard on dictation. It is object-based, so the cursor can be in a state that looks editable and is not. It is a layout tool as well as a writing tool, so a large fraction of its surface area is not text at all. And it autosaves to iCloud continuously, so a document can be in a syncing or locked state without any visible signal.
None of that is a defect. It is the price of a page-layout tool that is also a word processor. But it does mean that when dictation misbehaves in Pages, the odds favour the document over the microphone, which is the opposite of what most troubleshooting guides assume.
If your work in Pages is mostly straight prose, our guide to dictating in Apple Pages on Mac covers the workflow side of it: where dictation genuinely pays off, and which parts of a document are still faster with a keyboard. The equivalent problem in Microsoft's word processor is covered in dictation not working in Microsoft Word on Mac, and the failure modes are noticeably different because Word handles text focus in its own way.
If you want dictation that behaves the same everywhere
Working through nine fixes to make one app cooperate is a reasonable thing to do once. Doing it again next month, after an update changes something, is less reasonable. The underlying awkwardness is that Apple's Dictation is a mode: you enter it, it listens, it decides when you are finished, and you leave it. Modes interact badly with apps that have opinions about focus.
Voice Keyboard Pro works differently. You hold a hotkey, speak, and release, and the text appears at your cursor in whichever app you are in. There is no dictation session to start or end, no timeout to run out, and no separate window to type into and copy from. Because the gesture is a hold rather than a double press, there is no timing window to miss and no double-press to be mistaken for something else.
Two features matter specifically for the kind of writing people do in Pages. Smart Vocabulary is a personal dictionary with replacement rules, so the surnames, client names, and technical terms that transcription usually mangles come out right without you editing them afterwards. Meeting Mode handles the longer-form case, with speaker detection and AI notes for when the document you are writing is the record of a conversation. On the privacy side, our servers store only operational pings. No audio and no transcript content is retained.
There is a free tier with daily limits, and Pro is $4.99 a month or $34.99 a year. If Pages is where you do your real writing, it is worth an afternoon's trial before you spend another evening in System Settings.
Frequently asked questions
Does Pages have its own dictation feature?
No. Every dictation feature you can use in Pages belongs to macOS or to a third-party app. There is no Pages setting to enable, which is why the fix is never in Pages preferences.
Why does dictation work in Notes but not in Pages?
Almost always because Notes has exactly one place for a cursor to be and Pages has dozens. In Notes, clicking anywhere in the note body gives you an insertion point. In Pages, clicking can select an object, select a locked object, or select nothing at all. Type one character to confirm you have a live insertion point before blaming dictation.
Do I need to give Pages microphone permission?
No, and you cannot. Apple Dictation runs as a system service outside Pages, so Pages never appears in the Microphone privacy list. If you are using a third-party dictation app, that app needs microphone access and typically Accessibility access as well.
Why does dictated text appear and then disappear?
Check for an iCloud sync conflict. If the same document is open on another device, or was edited elsewhere while your Mac was offline, Pages may resolve the conflict by keeping the other version. Close the document on other devices, let sync settle, and try again.
Can I dictate into a Pages table?
Yes, but you need an insertion point inside a cell, not a selected cell. Double-click the cell first. The same rule applies in Numbers, where nearly every dictation complaint traces back to cell selection versus cell editing.
Will reinstalling Pages fix dictation?
No. Since Pages contains no dictation code, reinstalling it cannot change dictation behaviour. Reinstalling is worth doing for other Pages problems, but not this one.
Does dictation work offline in Pages?
Apple's Dictation keeps many languages on-device, in which case it works without a connection. Which languages qualify varies by macOS version and hardware, and the setting is managed by the system rather than by Pages. If dictation works offline for you in TextEdit, it will work offline in Pages too.
The words land at your cursor in whatever app you are already in — Mail, Slack, Word, a browser form. No dictation window, nothing to copy across.
Free forever for casual use · Apple Silicon & Intel