Wispr Flow website loads but sign-in and downloads fail in one browser

Last updated: August 6, 2026

Available on: Mac, Windows

If the Wispr Flow homepage loads but the download page, sign-in page, or Help Center hangs or comes up blank — and it works fine in another browser or on your phone — the fix is usually a browser setting. Most cases resolve in under 5 minutes.

Quick checks

  • Is there an active incident? Check the Wispr Flow status page. Any outage in your region is posted there.

  • Does another browser work? Open the same page in a different browser on the same computer. If it loads there, the problem is limited to the first browser.

  • Does your phone load the site? Open the site on a phone or tablet on the same Wi-Fi. If it loads on your phone but not your computer, the problem is on that computer or in that browser — continue with the steps below.

Why this happens

Browsers can run their own DNS lookups using DNS over HTTPS, also shown as Secure DNS. That lookup works independently of your operating system and your router, so a browser can resolve addresses differently from the rest of your computer.

When the browser resolves the main domain but fails on the supporting addresses a page needs, the homepage loads while everything else breaks. The browser reports this as a cross-origin or blocked-resource error, which looks like a website fault but is a name-resolution failure inside the browser.

Each browser keeps its own DNS over HTTPS setting, so fixing one browser does not fix the others. That is why the site can work in Chrome and still fail in Firefox on the same machine.

How to fix this

Step 1: Adjust your browser's DNS setting

Apply this in each browser where the site fails. Either turn the setting off so the browser follows your system and router DNS, or leave it on and pick a mainstream provider.

Chrome and Edge

In Chrome or Edge:

  1. Open Settings, then Privacy and security, then Security.

  2. Scroll to the Use secure DNS row.

  3. Switch it off, or leave it on and select a mainstream provider such as Cloudflare or Google.

  4. Quit the browser completely, reopen it, and load the page again.

The page that was failing should now load. If it does, you're done.

Firefox

In Firefox:

  1. Open Settings, then Privacy & Security.

  2. Scroll to the DNS over HTTPS section.

  3. Select Off, or keep it enabled and choose a mainstream provider such as Cloudflare.

  4. Quit Firefox completely, reopen it, and load the page again.

The page that was failing should now load. If it does, you're done.

Safari

Safari has no DNS over HTTPS setting of its own — it follows macOS.

  1. Open System Settings, then Network, and review the DNS settings for your active connection.

  2. Check for a configuration profile or content-filtering app that is overriding DNS for the whole system.

  3. Reload the page in Safari.

Step 2: Rule out extensions, security software, and VPNs

If the page still fails, work through these in order:

  1. Open the site in a private or incognito window, where extensions are disabled. If it loads, an extension is interfering — re-enable your extensions one at a time to find it.

  2. Pause antivirus, endpoint-protection, or web-filtering software, then reload the page. These tools often filter subdomains while allowing the main domain.

  3. Disconnect from any VPN or proxy, then reload the page. Wispr Flow is not compatible with most VPNs. If you need to stay connected, enable split tunneling and exclude the Wispr Flow domains.

  4. Check your hosts file for stale entries pointing at Wispr Flow domains, and remove them.

Domains to allow

If you or your IT team maintain an allowlist, include these over HTTPS on port 443:

  • wisprflow.ai

  • api.wisprflow.ai

  • inference.wisprflow.com

How to install or update Flow while the site is blocked

You do not need the website working to install or update Flow.

Update a copy you already have

  1. Right-click the Wispr Flow icon in your Windows system tray or Mac menu bar.

  2. Select Check for updates… at the top of the menu. Flow downloads the latest build without using a browser.

Download a fresh installer

These direct links bypass the download page:

Note: Do not copy an installer from another computer. You get whatever version that machine happened to have, which may be many builds behind. Update through the app or a direct link instead.

FAQs

My router already uses Cloudflare DNS. Why would the browser matter?

A browser using DNS over HTTPS bypasses your router entirely and sends lookups to its own resolver. Your router setting has no effect on that traffic, so the browser setting has to be changed separately.

Is a cross-origin error in the console a bug on Wispr Flow's side?

Usually not. When part of a page never loads because its address failed to resolve, the browser often reports it as a cross-origin or blocked-resource error. If the site loads on another device on the same network, the cause is local.

It fails on two computers at once. Doesn't that mean it's your servers?

Not necessarily. Computers that share an operating system version, browser defaults, or security software often share the same DNS behavior, so they can fail together for the same local reason. Confirm with the quick checks above.

Was my account locked or restricted?

No. This is a connectivity issue, and it does not affect your account, subscription, dictionary, or history. Once the site loads, you can sign in normally.

Still stuck?

Contact support and include the following so we can pinpoint which address is being blocked:

  • The full URL of the page that fails and the exact error text shown in your browser console

  • Your platform, browser, and browser version

  • Which steps above you already tried, and whether the site loads on your phone on the same network

Most cases like this are resolved in one reply.