You can update Android System WebView without the Play Store by installing a newer, Google-signed WebView APK yourself, either from a file on the phone or with adb install from a computer. Then pick it under Developer options > WebView implementation. On Android 7, 8 and 9, WebView comes from Chrome, so you update Chrome instead.
Why WebView normally updates through the Play Store
Android System WebView is an updatable system component, not a fixed part of the OS. Per the Chromium WebView providers doc, the updatable part ships as an APK or App Bundle. On phones with Google services, Play delivers it.
The Chromium WebView FAQ says a new version ships every 6 weeks, and that WebView needs regular security updates just like your browser. If Play is missing, blocked or broken, those updates stop, and every app that shows web content inside itself runs on an old engine.
Website-wrapper apps are the obvious case. Your users’ WebView version decides how your site renders, and a stale one causes bugs you can’t reproduce on your own phone. Before publishing one, read whether WebView apps get rejected on Google Play.
Step 1: Find out which app provides WebView
The app that renders WebView on your phone depends on the Android version, so check it before downloading anything. Enable Developer options, then open WebView implementation. The prerelease guide uses that exact path.
| Android version | Who provides WebView | What you update |
|---|---|---|
| Android 7, 8 and 9 | Chrome, while it’s enabled | Chrome |
| Android 10 and later, with Google services | com.google.android.webview |
Android System WebView |
| Android 10 and later, AOSP builds | com.android.webview |
Only through a system update |
The Chrome row comes from the Android 7.0 release notes: starting with Chrome version 51 on Android 7.0 and above, the Chrome APK provides and renders WebView. The standalone WebView APK isn’t updated while Chrome stays enabled. Disable Chrome, the FAQ says, and WebView switches to the standalone version.
This is where most “WebView won’t update” reports come from: someone updating the WebView app on an Android 8 phone whose apps actually run on Chrome.
Step 2: Get the right APK
You need an APK of the same package that’s signed with Google’s release key. The providers doc says Android only permits apps signed with the expected release keys, so a rebuilt or re-signed copy is refused however new it is.
Match these before you download:
- Package: Chrome on Android 7 to 9, or Android System WebView on Android 10 and later.
- CPU architecture and Android version: WebView ships in several builds, and a mismatched build either won’t install or won’t be offered as a provider.
- Version: the framework enforces a minimum
versionCode, so a very old build may be refused.
Dev and Canary are the one case where Google expects a manual install: the prerelease guide says those channels are downloaded and installed as separate apps. On Android 7 and later, several channels can sit side by side.
Unsure where an APK came from? Compare its signing certificate with the copy already on your phone. Our post on signed and unsigned APKs explains what that certificate proves.
Step 3: Install the APK
Install it like any APK from outside a store, either on the phone or from a computer.
On the phone. Android 8.0 dropped the old Allow unknown sources switch. The Android 8.0 behavior changes replace it with the Install unknown apps permission, which you grant to the file manager or browser that opens the APK.
From a computer. Turn on USB debugging under Developer options, connect the phone, and run the command from the adb documentation:
adb install path_to_apkA conflict or “App not installed” error usually means the signature doesn’t match the copy on the phone. Other causes are in why an APK says “App not installed”.
Step 4: Switch to the new WebView and check it
Installing an update to the current provider is enough on its own. If you installed a different channel, select it under Developer options > WebView implementation. The providers doc also gives a terminal route:
adb shell cmd webviewupdate set-webview-implementation com.google.android.webviewThen reopen WebView implementation and confirm the new entry is selected. From code, the managing WebView guide shows WebViewCompat.getCurrentWebViewPackage(), which returns the package and its version name. It can return null if the device lacks an updatable WebView implementation.
When you can’t update Android System WebView without the Play Store
Some devices can’t be fixed by sideloading. Check this list before you spend an hour on it.
- Android 5 to 9. The prerelease guide says Google no longer supports devices running Android 5-9. They can reach the last supported release and nothing newer.
- Work profiles. Managed profiles created on Android 8.0 (API level 26) block installs from unknown sources by default, per the Android 8.0 changes page. Ask your IT admin to push the update.
- Multiple users. A WebView provider must be installed and enabled for all user profiles, per the providers doc. One profile isn’t enough.
- AOSP-based builds. Their default WebView is
com.android.webview, so updates come only from the device maker’s system updates.
What this means for WebView-based apps
Apps made with WebToAPK Free are WebView-based, so they render your site with whatever WebView the phone has. They require Android 8.0 or newer (minimum SDK 26), which keeps the oldest devices out but doesn’t force anyone onto a current engine.
The app can’t update WebView for the user, and the builder doesn’t promise every website works in a WebView. When someone reports a blank screen, ask for their WebView version first. The HTML APK blank screen guide covers the other causes.
My take
Only sideload WebView when Play isn’t an option, like a de-Googled phone or a kiosk device. For an Android 8 phone that “won’t update”, update Chrome and skip the signature trouble entirely. I wouldn’t install a WebView APK from any site that doesn’t show the signing certificate, because WebView sees every login page your apps open.
FAQ
Can I update Android System WebView manually?
Yes. Install a newer APK of the same WebView package, signed with Google’s release key, from a file or with adb install. Android rejects a provider that isn’t signed with the expected key.
Why does my WebView not update on Android 7, 8 or 9?
On those versions WebView is built into Chrome, so the standalone WebView app stops getting updates while Chrome is enabled. Update Chrome instead, or disable Chrome so the standalone version takes over.
Do Android 5 to 9 still get WebView updates?
No. Chromium’s docs say devices on Android 5 to 9 are no longer supported. They can install the last supported release but get no newer versions.
How do I check which WebView my phone uses?
Turn on Developer options and open WebView implementation. It lists the installed providers and marks the one in use.