Wispr Flow is slow or down: how to check its status and recover your dictation
By Ryleigh Newman · Published
When Wispr Flow shows Taking longer than usual, stalls, or returns no text, the cause is either Wispr's service or your connection to it, because Flow transcribes in the cloud. Look for an orange or red banner on the Hub home page first. If there is none, check your connection and VPN, then retry the saved recording from History.
I built YapToText, a dictation app for the Mac, so read what I say about Wispr Flow with that in mind. Every fact about Wispr Flow here comes from its own help center, read on October 11, 2026.
This 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: 7 sections
Check whether the problem is on Wispr's side
From Wispr Flow's article on service status alerts, read October 11, 2026.
| Banner | What Wispr says it means | Wording on Mac and Windows |
|---|---|---|
| Orange | Degraded performance. Dictation may be slower than usual | Dictation is a bit slower than usual. We're on it. |
| Red | Outage. Dictation may be unavailable or unreliable | Service disruption: dictation may not work reliably right now. |
On a Mac or PC the banner appears only on the Hub home page, and View status opens Wispr's status page. A banner means the issue is on Flow's side and there is nothing for you to fix. It goes away by itself when the incident is resolved.
Flow can also send a desktop notification after a dictation, but only when it measured a delay longer than 3 seconds and already knows of an incident. Those appear at most once an hour, and notification preferences do not silence them. No banner does not prove the service is fine: the help center says banners cover incidents involving dictation delays, and other service issues are not shown there.
Check your own connection
- Load a website. If it does not load, fix the connection first.
- Update Flow: Check for updates in the Flow menu.
- Quit and reopen Flow, then dictate a short phrase.
- Test without your VPN or proxy, if it is yours to turn off.
- Turn it back on and set up approved access if the result changed.
A VPN, proxy, firewall or DNS filter can block dictation even while websites load. The help center says allowing Wispr's website and download domains is not enough for dictation, and that on a managed network the change belongs to your IT administrator. Flow uses the computer's proxy settings, under System Settings, Network on a Mac.
Retry the recording you already made
Reconnect first. Retry sends the saved audio again. It cannot recover speech the microphone never captured, or audio that was deleted.
- From the notice. Something's not right means a transcription failed or stalled. Its Retry button retries the last transcript and pastes it into the focused field.
- From History. Choose Open History on the notice, or open Flow's Dictation page. Use Retry, or the menu's Retry transcript, on the entry. Recover works on a dismissed entry. A History retry updates the entry and does not paste, so copy the text yourself.
- While it is processing. Pressing the dictation shortcut again does not start another recording.
- Do not dismiss recovery while you wait for an interrupted result. The help center warns that can stop the earlier transcript from pasting.
From Wispr Flow's article Fix slow or failed transcription, read October 11, 2026.
| Limit | What the help center says |
|---|---|
| Age | Audio older than 14 days cannot be retried, played or downloaded |
| Short recordings | Inline Retry needs a failed or empty recording of at least five seconds. Shorter ones use Retry transcript in the menu |
| Very short clips | Dismissed clips shorter than about half a second are not stored |
| Long recordings | Desktop recordings warn at 19 minutes and stop at 20, and then offer Recover text |
| No audio | An entry that says Couldn't access your microphone has no Retry or Recover |
Storage warnings
- Storage Full. Free disk space, then restart. Restarting alone cannot free space.
- There was an error. Restart Flow, and contact support if it returns.
- Local database corruption. Restarting deletes the corrupted local data and does not repair it, which loses local history, Notes and meetings.
Reset and restart goes further and deletes local history, notes, notifications and meetings. The help center says to use it only when support advises it. Your dictionary, stats and settings re-sync.
Why a cloud app can be slow when your Mac is not
Every Wispr Flow dictation makes a round trip to its servers, so its speed depends on your connection and on Wispr's service as well as on your computer. An app that transcribes on the Mac has no such dependency, and it has a different limit: its speed is whatever your Mac can do.
YapToText, the free app I built, runs speech recognition and cleanup on an Apple silicon Mac, with no account and no server. There is no status page because there is no service to go down. I publish no speed numbers. Each entry in its History shows its own stop-to-text time, so you can see what your Mac does. Wispr Flow offline covers what Flow can and cannot do without a connection, and Wispr Flow not working covers the other failures.
This 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.
The short version
- Orange or red banner. Wispr's side. Wait, and watch the status page.
- No banner. Test your connection, then your VPN or proxy.
- Lost a dictation. History, then Retry or Recover, within 14 days.
- Storage notice. Free space, then restart Flow.
If Wispr changes these steps, open an issue on GitHub and I will update this page. Every one gets read.
This 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.
Related
Sources
- https://docs.wisprflow.ai/articles/4984532368-fix-taking-longer-than-usual-and-transcription-errors (checked 2026-10-11)
- https://docs.wisprflow.ai/articles/8923966034-service-status-alerts-incident-banners-and-slow-dictation-notifications (checked 2026-10-11)
- https://docs.wisprflow.ai/articles/3834764683-why-vpns-or-security-tools-can-block-wispr-flow (checked 2026-10-11)
- https://github.com/ryleighnewman/YapToText (checked 2026-10-11)
- https://apps.apple.com/us/app/yaptotext/id6786382289 (checked 2026-10-11)
Questions
Why is Wispr Flow so slow?
Flow transcribes in the cloud, so a slow connection, a VPN or proxy, or an incident on Wispr's side all slow it down. An orange banner on the Hub home page means degraded performance.
Is Wispr Flow down?
Open the Flow Hub home page. A red banner means an outage, and View status opens Wispr's status page with live updates.
How do I recover a failed Wispr Flow dictation?
Open History, then choose Retry or Retry transcript on the entry, or Recover on a dismissed one. Audio older than 14 days cannot be retried.
What does Taking longer than usual mean in Wispr Flow?
It appears while Flow is stopping or processing and clears when the text pastes. Its only action hides the notice without changing transcription.
Can a VPN stop Wispr Flow from working?
Yes. The help center says a VPN, proxy, firewall or filtering service can affect Flow even when websites still load.