A WebView white screen almost always means the page loaded but couldn’t run or couldn’t fetch what it needs. The usual causes are JavaScript or DOM storage left at their default of off, an SSL error or an http:// request that Android blocked, or a local file the WebView refused to read. Open the page in Chrome’s remote debugger first, and the console tells you which one it is.
Find the cause first with chrome://inspect
Chrome’s remote debugger shows the real error behind a WebView white screen in a couple of minutes. Without it, you’re guessing.
The remote debugging guide says “WebView debugging must be enabled from within your application.” Add one line before you load the page:
WebView.setWebContentsDebuggingEnabled(true)
Then plug the phone into your computer, open chrome://inspect in desktop Chrome and click inspect under your WebView. Check the Console tab for red errors and the Network tab for failed requests. Each error message maps to a row in the table below.
WebView white screen causes at a glance
Most WebView white screen cases come down to a default setting that’s off in a WebView but on in Chrome.
| What you see | Likely cause | Default | Fix |
|---|---|---|---|
| Nothing renders, no console output | JavaScript is off | false |
setJavaScriptEnabled(true) |
Errors about localStorage |
DOM storage is off | false |
setDomStorageEnabled(true) |
net::ERR_CLEARTEXT_NOT_PERMITTED |
http:// blocked |
cleartext off from API level 28 | Serve over HTTPS |
| Blank on one site, others fine | SSL certificate error | load cancelled | Fix the certificate |
| Local HTML blank, assets missing | File access off | false when targeting R |
WebViewAssetLoader |
| Mixed content warnings | http assets on an https page |
never allowed | Move assets to HTTPS |
| Page turns white after a while | Renderer process died | app crashes or is killed | Handle onRenderProcessGone |
The defaults come from the WebSettings reference and the WebViewClient reference.
JavaScript and DOM storage are off by default
JavaScript being disabled is the most common cause of a blank WebView with modern sites. Android’s WebView guide says it plainly: “JavaScript is disabled in a WebView by default.”
A React, Vue or Angular site sends an almost empty HTML file and builds the page with JavaScript. With scripts off, you get exactly what the file contains: nothing.
DOM storage has the same trap. The reference says setDomStorageEnabled has “The default value is false.” A site that reads localStorage on startup can throw and stop rendering. Turn both on:
webView.settings.javaScriptEnabled = true
webView.settings.domStorageEnabled = true
SSL errors and blocked http requests
A certificate problem gives you a silent blank page. For onReceivedSslError, the WebViewClient reference says “The default behavior is to cancel the resource loading process.” An expired certificate, a self-signed one on a staging server, or a missing intermediate certificate all end the same way.
Don’t fix this by calling proceed() on every error. That accepts any certificate, including an attacker’s. Fix the certificate on the server.
Plain http:// has a similar rule. Android’s network security configuration says “Starting with Android 9 (API level 28), cleartext support is disabled by default.” I cover that error in detail in ERR_CLEARTEXT_NOT_PERMITTED in WebView.
Mixed content is the quieter version. An https page that loads a script over http gets that script blocked, because apps targeting Lollipop and later default to MIXED_CONTENT_NEVER_ALLOW. If that script draws the page, the page stays white.
Local HTML files that load blank
Local HTML shows a white screen when the WebView can’t read the file or the page can’t load its other files. For setAllowFileAccess, the default is “true for apps targeting Q and below, and false when targeting R and above.”
Even with access on, file:// pages are limited. The local content guide explains that file:// and data: URLs “are considered to be opaque origins,” so they can’t use fetch() or XMLHttpRequest. A page that fetches its own JSON breaks.
Use WebViewAssetLoader instead. It serves your bundled files from an HTTPS-style address such as https://appassets.androidplatform.net/assets/index.html, so the page behaves like a normal website. Don’t flip the old setAllowUniversalAccessFromFileURLs switch. It was deprecated in API level 30 because “This setting is not secure.”
When the page goes white later
A page that loads, then turns white minutes later, often means the WebView’s renderer process died. onRenderProcessGone, added in API level 26, tells you the render process has exited. If you don’t handle it, the reference says the “application will crash if render process crashed, or be killed if render process was killed by the system.”
Heavy pages, big images and memory pressure on cheap phones make this more likely. Handle the callback, throw away the dead WebView and create a new one.
Errors you should catch and show
A white screen is a bad error message. Catch load failures and show something the user can act on.
onReceivedErrorfires when the WebView can’t reach the server. Since API level 23 it’s called “for any resource (iframe, image, etc.), not just for the main page,” so check that the failed request is the main frame before showing an error.onReceivedHttpErrorfires for server replies with status codes >= 400.
My take: every app should show its own retry screen for main-frame failures. A blank app gets uninstalled faster than one that says “No connection, try again.” It also helps with offline cases, which I cover in what happens to a WebView app without internet.
Outdated Android System WebView
An old Android System WebView on the user’s phone can also break newer sites. Forum threads about blank WebViews often end with “updating WebView fixed it.” I can’t point to an official source that names a version, so treat it as a last check after the settings above. My guide to updating Android System WebView without the Play Store walks through it.
How WebToAPK Free handles these cases
Apps built with WebToAPK Free avoid some of these traps by design. Website sections need a complete HTTPS address, so cleartext http sites aren’t an option. Generated apps need Android 8.0 or newer, and since the October 2026 runtime update they show an error screen with a Try again button instead of a blank page.
The limitation is with local content. The HTML importer takes one self-contained file, with no ZIP or folder imports, so a page that expects separate script, image or JSON files next to it will load without them. The HTML APK blank screen guide walks through testing a minimal page and adding your content back piece by piece.
FAQ
Why does my site work in Chrome but show a white screen in my app?
Chrome turns on things a WebView leaves off. In a WebView, JavaScript and DOM storage are both off by default, so a JavaScript-built site renders nothing until you enable them.
How do I see the error behind a WebView white screen?
Call WebView.setWebContentsDebuggingEnabled(true), connect the phone to a computer, open chrome://inspect in desktop Chrome and click inspect under your WebView. The console shows the failing script or request.
Can an SSL certificate problem cause a blank WebView?
Yes. The default behavior of onReceivedSslError is to cancel the resource loading process, so a bad certificate leaves the page empty. Fix the certificate rather than calling proceed().
Why is my local HTML file blank in WebView?
File access is off by default for apps targeting Android R and above, and file:// pages can’t use fetch() or XMLHttpRequest. Load local files through WebViewAssetLoader instead.