Wispr Flow not working on a Mac: what each symptom means, and the fix

By · Published · Updated

When Wispr Flow stops working on a Mac, the cause is usually one of five things: a missing Accessibility or Microphone permission, often after an update; a shortcut that macOS is blocking; text that was transcribed but never pasted; a network, VPN or service problem, because every dictation goes through Wispr's cloud; or, on the Free plan, the weekly word limit. Wispr's help center has an article for each, and this page puts them in the order to try them.

I built YapToText, a different dictation app for the Mac, and I mention it once, near the end. Everything about Wispr Flow here comes from its own help center, read on October 6, 2026, and each article is linked under Sources. I have not reproduced these problems myself, so the steps are Wispr's, in my words.

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.

This guide in other languages: العربية, Čeština, Dansk, Deutsch, Ελληνικά, Español, Suomi, Français, עברית, हिन्दी, Magyar, Bahasa Indonesia, Italiano, 日本語, 한국어, Norsk, Nederlands, Polski, Português, Română, Русский, Slovenčina, Svenska, ไทย, Türkçe, Українська, Tiếng Việt, 简体中文, 繁體中文

On this page: 10 sections
  1. Steps
  2. Match what you see to a fix
  3. If the Fn key or a shortcut does nothing
  4. If it transcribes but nothing is typed
  5. If it is slow, says taking longer than usual, or fails
  6. If it records silence
  7. If it stopped working after an update
  8. When the problem is the cloud
  9. The short version
  10. Questions

Steps

  1. Check that Wispr Flow is running and has Accessibility and Microphone permission.
  2. If Fn and Space fail but Fn works, release Secure Event Input.
  3. If nothing was typed, press Control-Command-V to paste the last transcript.
  4. If it is slow, check the connection and Flow's status banner, then retry.

Match what you see to a fix

From Wispr Flow's help center, read October 6, 2026. Mac defaults: hold Fn to talk, Fn and Space for hands-free, Escape to cancel.

What you seeThe likely causeTry first
Holding Fn does nothingFlow is not running, or it lost AccessibilityLook for its menu bar icon, then turn Wispr Flow on in Privacy & Security, Accessibility
Fn and Space, or Escape, do nothing, but holding Fn worksmacOS Secure Event Input, often from a password field or TerminalClick out of the password field or switch apps, then try again
It transcribed, but nothing was typedThe paste did not landPress Control-Command-V to paste the last transcript
Taking longer than usual, or no text at allThe connection, a VPN or proxy, or an incident at WisprLoad a website, look for a status banner on Flow's Home page, then retry the saved recording
It records silenceMicrophone, output device, or a closed laptop lidRecord a clip in Voice Memos; if that is silent too, the problem is the Mac's audio, not Flow
The first words are missingSpeaking the instant you pressPause a moment after pressing, especially with a wireless microphone
It stopped after a macOS or Flow updatePermissions changedQuit Flow, turn its Microphone permission off and on, check Accessibility, reopen it from Applications
A dictation is refused on the Free planThe weekly word limitWait for the reset, Sunday at 23:45 UTC, or move to a paid plan

Read the notification Flow shows before changing anything: most of Wispr's fixes start from the exact message.

If the Fn key or a shortcut does nothing

A shortcut that does nothing has three usual causes, in this order. Accessibility first, then whatever is holding Secure Event Input, then the shortcut itself.

  1. Check that Flow is running. Its icon sits in the menu bar. If it is missing, open Wispr Flow from the Applications folder.
  2. Check Accessibility. In System Settings, Privacy & Security, Accessibility, Wispr Flow must be on. Wispr says shortcuts and dictation need it, and Flow notices the change without a relaunch.
  3. Release Secure Event Input. If holding Fn works but Fn and Space or Escape do not, a password field, Terminal with Secure Keyboard Entry checked, or a password manager may be holding secure input. Click out of the password field, uncheck Terminal, Secure Keyboard Entry, or close the suspected app. If the app has already quit and the block remains, Wispr says a lock and unlock of the Mac, or logging out, clears it.
  4. Check the shortcut. In Flow, Settings, General, Shortcuts, click Change to see or replace the keys. Each action takes up to four shortcuts, and custom shortcuts are saved per device.

While shortcuts are blocked, Wispr notes that holding Fn still dictates and pressing Fn twice starts hands-free, because Fn is a modifier key.

If it transcribes but nothing is typed

If Flow heard you but the words never appeared, the transcript is usually still there. Recover the text first, then work out why the paste missed.

  1. Paste the last transcript. Click into a text field and press Control-Command-V. Control-Command-C copies it without pasting.
  2. Keep the field focused. Wispr's article says to keep the intended field focused until processing and insertion finish, then test in Notes. If Notes works, quit and reopen the app that failed.
  3. Check permissions. Accessibility is what lets Flow type into other apps.

The Flow Bar, the small control on screen, can also be hidden: Settings, System, App settings, Show Flow Bar at all times brings it back, and also clears a Hide for 1 hour snooze.

If it is slow, says taking longer than usual, or fails

Flow transcribes in Wispr's cloud, so a slow or failed dictation is often about the connection. Check the network and Wispr's status before you reinstall anything.

  1. Load a website. If nothing loads, fix the Mac's connection first.
  2. Look for a status banner. An orange banner on Flow's Home page means dictation may be slower than usual, and a red one means it may not work reliably. Wispr says these are problems on its side, and no action is needed from you.
  3. Update and restart Flow. Choose Check for updates in the menu bar menu, then quit and reopen Flow and dictate a short phrase.
  4. Test without a VPN or proxy. Only if you control it, and turn it back on afterwards. On a work network, Wispr asks you to have IT allow Flow rather than leave protection off.
  5. Retry the saved recording. Retry needs a connection, and it cannot bring back speech the microphone never captured. Choose Retry on the notification or in History.

A Restart Flow button in an error message is the first thing to press. Wispr advises a full reset only when its support asks, because local transcripts may not come back afterwards.

If it records silence

When Flow records silence, find out first whether any app can hear you. If Voice Memos records silence too, no setting in Flow will fix it.

  1. Test outside Flow. Record a short clip in Voice Memos.
  2. Check for a mute switch. On a headset, keyboard or interface, and move closer to the microphone.
  3. Switch the output device. Wispr has found that an output that cannot start its audio, such as a monitor over HDMI or DisplayPort, can leave the microphone uncaptured. In System Settings, Sound, Output, choose the built-in speakers and test again.
  4. Pick the microphone in Flow. Settings, General, Microphone, Change. Wispr warns that a Mac's built-in microphone does not work with the lid closed.
  5. Grant the permission. System Settings, Privacy & Security, Microphone, with Wispr Flow on.

If only the first words go missing, Wispr's advice is to pause briefly after pressing the shortcut before you speak, especially on a wireless microphone.

If it stopped working after an update

Wispr has a whole article on Flow going quiet after a macOS or app update, and the cause is permissions. Re-grant Microphone and Accessibility by hand, then reopen Flow from Applications.

  1. Quit Flow from its menu bar icon.
  2. Turn Microphone off and on. System Settings, Privacy & Security, Microphone: switch Wispr Flow off, then on again.
  3. Check Accessibility. In Privacy & Security, Accessibility, make sure Wispr Flow is on.
  4. Reopen Flow from Applications. Wispr says Flow will not launch from outside the Applications folder.

On the Free plan there is one more thing that can stop dictation that is not a fault: the weekly limit. Wispr's help center gives 2,000 words a week on Mac and Windows as the soft cap and 5,000 as the hard cap, after which the next dictation is refused until the reset, Sunday at 23:45 UTC. Paid plans have no weekly limit.

When the problem is the cloud

Some of these problems are not faults at all. Wispr's privacy page says transcription always happens in the cloud, so a dropped connection, a VPN, a filtered work network or an incident at Wispr can stop dictation on a Mac that is otherwise fine. If you want dictation that keeps working with the Wi-Fi off, it has to run on the Mac.

That is why I built YapToText the way I did: both of its models ship inside the App Store app and run on your Mac, with no account, no word limit and nothing to reach over the network. It is a different app with different limits, Mac only and Apple silicon only, and the Wispr Flow alternative page sets out honestly what Wispr Flow does that it does not.

App Store poster headed Nothing leaves your Mac, over YapToText's AI Models page with both models marked Included.
Figure 1. YapToText's two models ship inside the App Store app, so its dictation does not depend on a server being up.

The short version

  • Fn does nothing. Check the menu bar icon and Accessibility.
  • Fn and Space do nothing. Something holds Secure Event Input: leave the password field, check Terminal, close the password manager.
  • Nothing typed. Control-Command-V pastes the last transcript.
  • Slow or failed. Check the connection and the status banner, then Retry.
  • Silence. Test in Voice Memos, and switch the output to the built-in speakers.
  • After an update. Grant Microphone and Accessibility again, then reopen it from Applications.

Start from the message Flow shows you. Wispr's help center has a fix for almost every one. If something here no longer matches Wispr's help center, tell me on GitHub.

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 Wispr Flow not working on my Mac?

Usually a missing Accessibility or Microphone permission, often after an update, a shortcut blocked by macOS Secure Event Input, a paste that did not land, or a network or service problem, since Flow transcribes in Wispr's cloud. On the Free plan, the weekly word limit can also refuse a dictation.

Why is the Wispr Flow Fn key not working?

Check that Flow is running and that it is on in Privacy & Security, Accessibility. If holding Fn works but Fn and Space does not, Wispr says macOS Secure Event Input is the likely cause, often from a focused password field, Terminal's Secure Keyboard Entry or a password manager.

Why is Wispr Flow so slow?

Wispr's help center points first to the connection, a VPN or proxy, and incidents on its side, which Flow shows as an orange or red banner on its Home page. Update and restart Flow, test without the VPN if you control it, then retry the saved recording.

Why did Wispr Flow stop working after an update?

Wispr says a system or app update can change its permissions. Quit Flow, switch its Microphone permission off and on, check Accessibility, and reopen it from the Applications folder.

Does Wispr Flow work offline?

No. Its privacy page says transcription always happens in the cloud, and retrying a failed dictation also needs a connection. YapToText's App Store build works with Wi-Fi off, because both of its models run on the Mac.

When does the Wispr Flow word limit reset?

Wispr's help center says weekly allowances reset Sunday at 23:45 UTC. On the Free plan the desktop soft cap is 2,000 words and the hard cap 5,000. Paid plans have no weekly limit.