YapToText not working: fix it in this order

By · Published · Updated

If YapToText is not working, the fix is almost always one of two permissions: Microphone, so it can hear you, and Accessibility, so it can type into other apps. Without Accessibility nothing is lost, because every dictation is still transcribed and copied to your clipboard, so press Command V and your words are there.

This page is for YapToText's own problems, in the order I would check them. If Apple's built-in Dictation is the one that stopped working, Mac dictation not working covers it.

Download YapToText on the Mac App StoreThis app is completely free. You don't have to make an account. There are no subscriptions, no difficult downloads, and nothing is locked. Made for Apple silicon Macs. Source on GitHub.

On this page: 15 sections
  1. Steps
  2. Find your symptom
  3. Check the two permissions first
    1. Step 1: Microphone
    2. Step 2: Accessibility
  4. If it heard silence
  5. If Right Command does nothing
  6. If the words land on the clipboard
  7. If an app ignores the text
    1. Pin a method for that app
  8. If your Mac beeps when text lands
  9. If it says no speech model is installed
  10. If the first dictation is slow
  11. If a dictation went missing
  12. What this page cannot fix
  13. Still stuck
  14. The short version
  15. Questions

Steps

  1. Grant Microphone and Accessibility to YapToText in System Settings, Privacy & Security.
  2. If it heard silence, pick your microphone in the Input picker and watch the meter in Settings, General, Microphone.
  3. If the words went to the clipboard, press Command V, then check Accessibility and Insert text automatically.
  4. If one app ignores the text, add it under Per-app method in Settings, Advanced, Text output.
  5. If it still fails, use Copy Diagnostics in Settings, About and open a GitHub issue.

Find your symptom

Find what you see, then jump to its fix.

What you seeWhere to go
Nothing happens when you tap Right CommandIf Right Command does nothing
It says “Didn't catch that”, or the wave stays flatIf it heard silence
The words land on the clipboard, not at the cursorIf the words land on the clipboard
One app ignores the textIf an app ignores the text
Your Mac beeps when text landsIf your Mac beeps when text lands
It says no speech model is installedIf it says no speech model is installed
The first dictation is slowIf the first dictation is slow
A dictation disappearedIf a dictation went missing
Anything elseStill stuck

When in doubt, check the two permissions first.

Check the two permissions first

Both permissions live in System Settings, Privacy & Security, and the Get set up card on the Home page shows while either one is missing.

YapToText's Home page: the Start Dictation button, the Keys card with Right Command and Right Option, and Intelligent Insert.
Figure 1. Once both permissions are granted, the Get set up card is gone, and the Home page opens on Start Dictation and the Keys card.

Step 1: Microphone

  • You: Press Continue next to Microphone on the Home page, or switch YapToText on in System Settings, Privacy & Security, Microphone.
  • macOS: Asks once, on the first try. After a no, only System Settings can change it, and the Continue button takes you there.
  • Check: A green check next to Microphone. Without it, dictation cannot start.

Step 2: Accessibility

  • You: Press Grant next to Accessibility, then switch YapToText on in System Settings, Privacy & Security, Accessibility.
  • macOS: Lets YapToText type into other apps, watch the dictation key and read selected text.
  • Check: With Microphone already granted, the Get set up card leaves the Home page within a couple of seconds. If the switch will not stay on, press Show in Finder and drag the app into the list, then press Recheck.

Without Accessibility, the words still reach your clipboard. If you are setting up a Mac without using your hands, typing on a Mac without hands walks through the setup I use.

If it heard silence

When YapToText says “Didn't catch that. Nothing was transcribed.”, or the wave stays flat while you talk, your voice is not reaching it. If the wave stays flat while you talk, fix the microphone before anything else.

YapToText's floating dictation panel on a Mac: a live waveform, the sentence being typed, and cancel, pause and stop buttons.
Figure 2. The wave moves with your voice. A flat line while you talk means the app is not getting your microphone.
  1. Move closer. Speak toward the microphone and watch the wave.
  2. Pick the microphone. Click the capybara and choose yours in the Input picker, or set Settings, General, Microphone, Input source. If the chosen one is unplugged, YapToText falls back to the system default.
  3. Watch the meter. In that Microphone card, say a sentence and raise Input boost until normal speech reaches the green-to-yellow zone without sitting in the red.
  4. Raise the Mac's input volume. YapToText warns when it is low and can raise it for you, or drag the input volume slider yourself in System Settings, Sound, Input.
  5. Mind the room. The Dictation page warns when the room or the fans are too loud for the microphone. Auto-amplify quiet speech is on by default, and the app measures the room on every dictation and subtracts steady noise when it needs to.
  6. Quit call apps. The app's microphone tip suggests quitting call apps such as Teams or Zoom, which may be turning your input down. That is caution, not something I measured.
YapToText's Settings, General tab: the Shortcuts card, the Auto mode card, and the Microphone card with a live input level meter.
Figure 3. Settings, General, Microphone: pick the input source, then watch the live meter while you say a sentence. If the chosen microphone is unplugged, YapToText falls back to the system default.

Bluetooth headsets and hearing aids send their microphones at phone quality, so the Mac's own microphone hears better. Dictating with hearing aids covers keeping the good sound and the good microphone. If YapToText says the microphone is not delivering audio, try again or pick another input.

If Right Command does nothing

  1. Check Accessibility. The dictation key needs it. Until it is on, the backup shortcut, Control Option Space, and Start Dictation in the capybara's panel both still work.
  2. Press Recheck. After granting, Recheck on the Home page re-reads the permissions and re-arms the shortcuts.
  3. Check the menu. On the Dictation page, Keys card, the menu beside the key must not say Off.
  4. Look for red. A red key field means the dictation key and the Quick Edit key are the same key. Change one of them.

The backup shortcut works even before Accessibility is on. Every key and its settings are in YapToText's keys.

If the words land on the clipboard

Your words are safe: press Command V. Then find out why they were not typed.

  1. Accessibility. Without it, macOS drops the keystrokes that type, so YapToText copies the words instead.
  2. Insert text automatically. On the Dictation page, Delivery card. When it is off, every dictation goes to the clipboard.
  3. The method. In Settings, Advanced, Text output, Method should be Paste (fast, recommended). Check the Per-app method list for that app too, and the mode's Where the text goes card, which can be set to Copy to clipboard.
  4. The app in front. If YapToText cannot bring the app you were dictating into back to the front in time, it keeps the words on the clipboard rather than pasting them into the wrong window. Click into the app and paste.
  5. YapToText's own window. It never types into itself. A dictation started there goes to the app you used just before, or to the clipboard when there is none.

To see what happened, open the dictation in History and click Show pipeline details. The Delivery line says pasted, typed, copied to clipboard, or that it needed Accessibility and was copied instead. Nothing that goes to the clipboard is lost.

A YapToText History entry with pipeline details open: raw transcript, cleaned transcript, mode, delivery, target app and timings.
Figure 4. The Delivery line in the pipeline details says where a dictation went, here pasted into Notes.

If an app ignores the text

Paste is the default because it is fast, and a few apps handle a simulated paste badly. Some of them accept typed keystrokes instead.

Pin a method for that app

  • You: Open the stubborn app so it is running, then in Settings, Advanced, Text output, under Per-app method, press Add App Override and pick it.
  • YapToText: Adds the app set to Type character-by-character. The pin wins for that app, and every other app keeps the default.
  • Check: A test dictation lands in that app. If it still does not, set its pin to Copy to clipboard only and paste with Command V.

The three methods:

  • Paste (fast, recommended). The default. Your clipboard is put back afterward, images and files included.
  • Type character-by-character. Slower, for apps that ignore a paste.
  • Copy to clipboard only. Always works, with or without Accessibility. You paste by hand.

In a password field, while Secure Input is on, YapToText types instead of pasting on its own. In terminals, Intelligent Insert stays off automatically. A per-app pin fixes one stubborn app without changing any other.

If your Mac beeps when text lands

That is Intelligent Insert reading the words around your cursor with a few invisible keystrokes. Some apps refuse one of them and macOS plays its alert sound. It is harmless, and the text lands either way.

  • Quiet it. In System Settings, Sound, drag Alert volume, in Sound Effects, all the way down. Only alert sounds go quiet. Open Sound Settings, under the Intelligent Insert switch, takes you there.
  • Skip it for one app. On the Dictation page, Delivery card, add the app with Turn off in another app.
YapToText's Dictation settings page on a Mac: the Keys, Recording, Microphone and Delivery cards.
Figure 5. The Delivery card on the Dictation page explains the beep, links to Sound settings, and lists the apps where Intelligent Insert stays off.

One slider, or one entry in a list, ends the beep. The Intelligent Insert guide explains the read itself.

If it says no speech model is installed

The Homebrew build ships without models, so it cannot dictate until a speech model is installed. The App Store build ships both models and needs nothing.

  • You: On the AI Models page, download Whisper Large v3 Turbo (Q5), 574 MB, from the Dictation Model Library and select it. For Auto mode and the other AI modes, add Phi-3.5 Mini Instruct, 2.3 GB, from the Cleanup Model Library.
  • YapToText: Fetches each file over HTTPS from Hugging Face and keeps it in its own container, where it survives updates.
  • Check: The row says Installed, and a test dictation types text.

If a download will not finish, the file is coming straight from Hugging Face. YapToText has no server of its own. The install guide covers both builds, and the models guide covers every model. The App Store build needs no download at all.

If the first dictation is slow

The models load once per launch, and again after they have been unloaded. By default they stay loaded for 2 minutes after use, and the next dictation after an unload takes a few extra seconds while the model reloads. When macOS runs short of memory, the models are dropped at once, and the app waits five minutes before warming them again.

Keep models in memory, on the Energy page, sets how long they stay. To see where the time goes, open a dictation in History: Show pipeline details splits the stop-to-text time into transcription, AI cleanup and delivery. A slow first dictation is the model loading, not something broken.

If a dictation went missing

Four places to look:

  • A canceled dictation. Esc while you talk saves the words to History, marked as canceled, unless Keep canceled dictations is off. A press of Esc after you stop, while the app is still transcribing or cleaning up, is ignored, so it cannot be the reason a dictation went missing.
  • A crash. If the app or the Mac quits mid-sentence, the audio survives. On the next launch it is transcribed, copied to your clipboard and filed in History as Recovered after a crash.
  • The clipboard. Press Command V, or copy it again from History or from the Recent list in the capybara's panel.
  • History settings. Settings, Advanced, History & audio keeps the last 500 dictations and deletes anything older than 30 days by default. This session only or Clear history when I quit keep less.

By default, canceled dictations and ones cut off by a crash both end up in History. The History guide has the rest.

What this page cannot fix

  • Apple's Dictation. A different tool with different fixes: Mac dictation not working.
  • Intel Macs and older macOS. YapToText needs an Apple silicon Mac with macOS 14 or later.

Still stuck

Open Settings, About, and press Copy Diagnostics. It gathers your Mac model, versions, model setup and latency stats, never your words. Paste it into a GitHub issue and tell me which app you were dictating into, what YapToText said, and what History shows for that dictation. Copy Diagnostics never includes your words.

If you need dictation to keep working in the meantime, Copy to clipboard only always works, with or without Accessibility.

The short version

  • Permissions first. Microphone to hear you, Accessibility to type for you.
  • The clipboard second. If the words are on the clipboard, nothing is lost.
  • History third. Show pipeline details says what was heard and where it went.

Check the permissions, paste what is on the clipboard, then read History. If none of this matches what you see, open an issue on GitHub. Every one gets read.

Download YapToText on the Mac App StoreThis app is completely free. You don't have to make an account. There are no subscriptions, no difficult downloads, and nothing is locked. Made for Apple silicon Macs. Source on GitHub.

About the author. Ryleigh Newman is a developer whose hands make typing difficult and who dictates every day with YapToText, the app this site describes. Facts about other apps come from their own sites, with the date they were read. More about the project.

Sources

Questions

Why is speech to text not working on my Mac?

For YapToText, it is usually a permission: Microphone to hear you, or Accessibility to type into other apps. If it is Apple's built-in Dictation, the Mac dictation not working guide on this site covers that.

Why does YapToText type nothing?

Most often Accessibility is off, so the words went to your clipboard instead. Press Command V. If it said Didn't catch that, it heard silence, so check the microphone.

Why did my dictation go to the clipboard?

Accessibility is off, Insert text automatically is off, the method is set to Copy to clipboard only, or the app could not be brought back to the front. The Delivery line in History says which.

Why does my Mac beep when YapToText inserts text?

Intelligent Insert reads the words around your cursor with invisible keystrokes, and some apps refuse one. Turn Alert volume down in System Settings, Sound, or turn Intelligent Insert off for that app.

Does YapToText need to download anything?

Not the App Store build: both models ship inside it. The Homebrew build needs a speech model from the AI Models page before it can dictate.

Why is the first dictation slow?

The model loads once per launch, and again after it has been unloaded to save memory. The dictations after that are quick.