Why is Wispr Flow not working?

Wispr Flow usually stops working for one of four reasons: a missing permission, a shortcut that another app has taken, a microphone that the system cannot hear, or a lost internet connection. First, recover what you dictated: press Ctrl + Cmd + V on Mac or Alt + Shift + Z on Windows to paste the last transcript ¹. Then find your symptom below. The steps follow Wispr's help center as read on October 27, 2026, and they sit alongside our guide to Wispr Flow: price, privacy and what users say in our overview of dictation software.

Check the connection first, because Flow cannot work offline

Flow sends every dictation to Wispr's servers, and its help center says an internet connection is required for transcription ². If your Wi-Fi is down, behind a captive portal, or blocked by a company firewall, Flow will fail however you set it up. Open a web page to confirm the connection before changing anything else. If you need dictation without a network, see whether Wispr Flow works offline.

Text that does not paste usually needs a permission or a different paste key

If Flow heard you but the words never landed, work down this list. After each change, dictate one short phrase to test it.

1. Recover the text. Use the paste-last-transcript shortcut above, with the cursor inside an editable field. Press and release every key rather than holding the modifiers.
2. Test in a plain app. Try Notes on Mac or Notepad on Windows. If it works there, the problem is the other app: quit it, reopen it and try again.
3. Mac: allow Accessibility. The Mac app needs Accessibility access to insert text, and the Windows app does not ³. Open System Settings > Privacy & Security > Accessibility and enable Wispr Flow. If it is already on, switch it off and on. Our glossary explains the macOS Accessibility permission.
4. Windows: check for an admin-level app. The message "Update admin settings to paste!" means a privilege-level block ⁴. Wispr says to quit Flow, then relaunch it as Administrator yourself.
5. Terminals and code editors. On Windows, Flow uses Shift+Insert in supported coding editors instead of Ctrl+V ⁵. If you use another terminal that pastes differently, expect trouble there only.

Microphone problems are mostly permissions, the wrong input or a silent device

When Flow warns it cannot hear you, first record a short clip in Voice Memos (Mac) or Sound Recorder (Windows). Silence there points to the microphone or system setup, not to Flow ⁶. The same checks as our general question on why your microphone is not working for dictation apply. Then:

• Look for a hardware mute on your headset, keyboard or laptop.
• Mac: enable Flow under System Settings > Privacy & Security > Microphone.
• Windows: both switches must be on, Microphone access and Let desktop apps access your microphone ⁷.
• Pick the microphone by name in Settings > General > Microphone rather than leaving auto-detect, and watch the level meter move as you speak.
• A closed MacBook has an unusable built-in microphone, so use an external one. Bluetooth headsets can capture silence when out of range.
• Releasing the shortcut too fast can trigger a no-audio notice. Dictate again and hold a little longer ⁸.

If the meter moves but text is missing, check History for the saved audio and retry it. That points to transcription, not capture.

A shortcut that does nothing is usually taken, changed or never released

Flow works on hold, speak, release. The defaults are Fn on Mac and Ctrl + Win on Windows, and both can be changed ⁹. Another app or a system setting can intercept the same keys. Wispr says to change an intercepted shortcut in Settings > General > Shortcuts, or from the tray menu. Our answer on why a dictation shortcut stops working covers the system side. The idea behind it is push-to-talk: nothing records until you press the key.

Restart Flow after you switch your keyboard layout, so it picks up the new one.

If Flow will not open or keeps crashing, quit it fully and check the build

Closing Flow's window only hides it. The app keeps running in the menu bar or tray ¹⁰. So a "stuck" Flow often needs a real Quit from that menu, then a relaunch. If it still hangs, end the Wispr processes in Activity Monitor on Mac or Task Manager on Windows.

For an app that will not open, Wispr's startup guide lists specific causes:

Save or stop any dictation before force-quitting, since a crash can lose unsaved audio. A reviewer on Windows also reported Flow using 800 MB of RAM when idle and taking 8 to 10 seconds to start ¹⁴. That is one reviewer's measurement.

When the fix is not a fix

It depends on your setup:

• iPad, Linux and Chromebook are not supported ¹⁵, so Flow cannot work there. See Wispr Flow on Windows, Android and Linux.
• Windows on ARM PCs, such as Snapdragon laptops, are also unsupported ¹³.
• Hit the free word cap? Dictation slows and then stops on the free plan. See whether Wispr Flow is free.
• Needs to work every time, offline or on locked-down machines? A cloud app will keep failing there. Yap, which we make, runs dictation on your own Mac or Windows PC; see Wispr Flow alternatives.

If all else fails, reinstall from the official downloads page, then contact Wispr support from its help center with your OS version and exactly what happens when you press the shortcut.