Web Worker Unavailable? Platform Troubleshooting
Symptoms You'll See
Any3D shows a yellow warning at the bottom: "Your current browser does not support Web Worker". Preview may still work, but large file processing can easily freeze the page, as Worker-based paths for texture compression and image-to-model conversion are unavailable.
Web Worker allows time-consuming computations to run in a background thread. Any3D's texture compression and certain conversion pipelines rely on the trio: Worker + OffscreenCanvas + createImageBitmap.
Common Causes
| Cause | Typical Scenario |
|---|---|
| Non-secure context | Opening via file://, HTTP intranet pages (not localhost) |
| Outdated browser / WebView | Legacy system browsers, in-app embedded pages |
| CSP restrictions | Enterprise portal iframes, Zero Trust clients injecting worker-src |
| Extension blocking | Privacy plugins blocking Worker or blob: URLs |
| Network cache anomaly | Proxy/VPN returning incomplete Worker scripts |
| Device management | Supervised profiles disabling background scripts |
Troubleshooting by Platform
Windows
- Access must be via HTTPS (
https://any3d.cc); do not use local HTML files. - Edge Enterprise Policy: Check in
Computer Configuration → Administrative Templates → Microsoft Edgeif Worker or third-party cookies are restricted (which can indirectly affect some Worker loading). - Windows Family Safety: Web restrictions on child accounts may cause Worker creation to fail.
macOS
- Safari / Chrome both require macOS 12+ and a recent browser version.
- Screen Time → Content & Privacy → Enabling "Limit Adult Websites" or custom filters may inadvertently block Worker script domains.
- Company MDM profiles that disable scripting capabilities beyond "cross-site tracking"—contact IT.
Linux
- Confirm the access URL is HTTPS; enterprise Squid proxies must allow
blob:andworker-srcrelated requests.
iOS / Android
- Do not complete large file processing in WeChat/DingTalk in-app browsers; use the system browser.
- iOS Low Power Mode typically does not disable Workers, but older WebKit may lack APIs—keep the system updated.
- Android WebView version being too old (system WebView not updated) can make Workers unavailable: update "Android System WebView" from the Play Store.
Network, VPN & Enterprise Intranet
| Scenario | Description |
|---|---|
| Corporate VPN | Some VPNs enforce HTTPS decryption and inject CSP; IT needs to whitelist Workers |
| Intranet SSO portal iframe | The outer page's CSP may forbid worker-src blob:; configure the nested page separately or open Any3D in a new tab |
| Reverse proxy | Incorrect Nginx/gateway configuration may cause incorrect MIME types for Worker scripts |
| Parental router DNS filtering | Rare for Workers, but if the entire site is downgraded to an HTTP mirror, Workers will fail |
Self-test: Disconnect VPN, switch to a 4G/5G hotspot, and see if the warning disappears.
Enterprise CSP Reference (For IT)
If Any3D is embedded in an iframe, it's recommended to allow:
worker-src 'self' blob:;
script-src 'self' 'unsafe-eval' blob:;
Individual users do not need to manually modify CSP.
Step-by-Step Fix (General)
- Confirm HTTPS access; refresh the page (Ctrl+F5 / Cmd+Shift+R).
- Use an Incognito/Private window to rule out extensions.
- Update your browser and (on Android) the System WebView.
- Open Any3D directly in a new tab, avoiding embedding within enterprise portal iframes.
Quick Self-Test
typeof Worker !== "undefined"
Returning true only indicates the API exists; Any3D also requires OffscreenCanvas and createImageBitmap to be fully available to use the complete Worker path.
Impact Without Workers
| Feature | Impact |
|---|---|
| Vertex compression (Draco, etc.) | Usually still available (main thread + WASM) |
| Texture / KTX2 compression | Worker path unavailable; large files may stutter |
| Image-to-Model | May degrade or suffer significant performance drop |
Summary
Web Worker warnings typically stem from non-HTTPS, outdated WebView, enterprise CSP/VPN, or extension blocking. By updating the browser per platform, switching networks to verify, and having IT check iframes/CSP, you can usually restore background processing capabilities.