about:blank#blocked is a blank result shown when a Chromium-based browser blocks or rewrites a navigation that the page was not allowed to make. It does not identify the exact rule, and it does not mean your device has a virus.
What about:blank#blocked actually means
Chrome, Edge, and other Chromium-based browsers separate ordinary web pages from privileged browser and local resources. When a page-controlled process tries to navigate somewhere it is not permitted to access, Chromium can replace the target with a special blocked URL. One form of that result is about:blank#blocked.
The phrase is deliberately sparse. It confirms that a navigation did not proceed, but it does not tell you whether the trigger was a popup rule, a local-file link, a browser-internal address, an extension, a sandboxed frame, an application policy, or a malformed redirect. Treat it as a symptom, not a diagnosis.
The blocked page is not malware and the #blocked fragment is not a virus name. In many cases, the browser is enforcing a security boundary as designed.
This wording is most closely associated with Chromium. Firefox and Safari may show different messages, icons, or error pages for a similar failed action, so instructions that describe about:blank#blocked as a universal browser warning are misleading.
Common causes, ordered by context
| When it happens | Likely cause | First check |
|---|---|---|
| After clicking a button | A popup or redirect was blocked, or its target was invalid | Look for a popup indicator and retry from the original page |
| Opening a document or PDF link | The site tried to open a local, generated, or restricted resource | Use the site's explicit Download button instead of the preview link |
| Inside a business web app | An embedded frame, SSO flow, security policy, or browser extension interrupted navigation | Check whether the app is supported and whether the device is managed |
| Only with one extension enabled | The extension blocked or rewrote the target | Test in a private window with extensions disabled where possible |
Opening a file: link from a website | Web content generally cannot navigate freely to local files | Access the file through the approved application or local file picker |
| Typed directly in the address bar | You opened the literal internal blank URL and fragment | No fix is needed; navigate elsewhere |
Ad blockers and security extensions can contribute, but they are not the only explanation. Likewise, an overly long URL can fail in a particular application, but length alone is not the general definition of this page.
A safe troubleshooting sequence
- Return to the original page. Close the blocked tab and confirm that the page you came from is the expected, trusted site.
- Repeat the action once. A temporary navigation or sign-in timing issue may clear. Do not repeat a download or payment action if it could create duplicates.
- Check for a popup-blocked indicator. If the action genuinely needs a popup, allow popups for that one trusted site only. Keep global blocking enabled.
- Try a private window. This can isolate stored site data and many extensions. If the action works there, review extensions and site permissions in the normal profile.
- Update the browser. Business apps and sign-in providers may depend on current browser behavior.
- Contact the site or app owner. If one specific action fails across updated browsers, the target URL or application code may need correction.
Do not turn off Safe Browsing, SmartScreen, antivirus protection, popup blocking, or every extension just to make one link open. Narrow the test to the affected site and restore settings afterward.
Fixes for specific situations
A login or payment popup stays blank
Start the flow from the merchant or service's original page, not from an old bookmarked callback URL. Allow popups for that domain only, make sure the browser clock is correct, and avoid opening multiple copies of the flow. If the window is still blank, use the service's support path rather than entering payment or account data into a different page.
A PDF, report, or download opens #blocked
Look for a dedicated Download or Export control. Some applications generate a temporary file in memory and then open it through a popup; privacy extensions or an expired session can interrupt the handoff. Sign in again, retry once, and test in a private window. Never paste an unknown generated URL into a third-party downloader.
A link to a local file is blocked
A normal web page should not receive broad access to files on your device. Open the approved desktop app, network drive, or file picker instead. On a company system, use the organization's documented workflow rather than changing browser security flags.
An extension seems involved
Disable extensions one at a time, starting with popup, script, privacy, download, and link-handling tools. Re-enable each extension after the test. If the issue disappears, review that extension's site-specific allowlist rather than removing all protection.
On a work or school device
Managed browsers can apply policies that users cannot or should not override. A blocked internal tool, local resource, or sign-in window may reflect an organization rule. Check whether the browser says “managed by your organization,” record the original page and action, and send those details to your IT administrator.
Avoid installing “fix” extensions, launching the browser with security-disabling flags, or changing registry and policy settings from an unofficial tutorial. Those actions can create a genuine security or compliance problem while hiding the useful evidence your administrator needs.
For developers: why the label can appear
Chromium's source defines about:blank#blocked as a special blocked URL. Navigation from a renderer process is filtered against URLs that process is allowed to request. This matters for targets such as privileged browser pages, local resources, and navigations across sandbox or process boundaries.
When debugging, capture the attempted destination before it is rewritten, inspect console and network output, and check popup return values. A blocked window.open() can return null; not every failed popup produces this exact page. Also review iframe sandbox tokens, Content Security Policy, redirects, and whether the action retains a user gesture.
Do not add code that treats every literal URL ending in #blocked as proof that Chromium blocked a secret target. Chromium distinguishes a browser-generated blocked result from a user who manually navigates to the same text.
What not to do
- Do not install a program marketed as an “about:blank remover.” There is no built-in component to remove.
- Do not assume an ad blocker is guilty before testing the exact site and action.
- Do not disable browser security features globally.
- Do not treat the label as proof of malware—or proof that the destination was safe.
- Do not bypass an organization policy on a managed device.
Primary sources
- Chromium source: blocked navigation URL constantDefines the special
about:blank#blockedURL used by Chromium. - Chromium: Special Case URLsExplains why
about:blankhas more browser and origin edge cases than its name suggests. - MDN: Window.open()Documents initial blank contexts, popup behavior, and return values.
- Google Chrome Help: Block or allow popupsOfficial site-specific popup control instructions.
- Microsoft Support: Block popups in EdgeOfficial Edge popup guidance.