Chrome APK Old Versions for Android 7, 8 & 9
Current Chrome releases require Android 10 or later. Users with Android 7, 8, or 9 may need the last Chrome branch made for their operating system. Choose the version by Android release and processor architecture—not by file size or version number alone. Older browser builds no longer receive current Chrome security fixes, so use them only when a device cannot run a supported release.
Chrome 138 for Android 8 and Android 9
com.android.chromeChoose the package that matches your device architecture.
Chrome 119 for Android 7
com.android.chromeCheck the package format and signing certificate before installation.
Which Old Chrome Version Should You Download?
Google ended Chrome support for Android 8 Oreo and Android 9 Pie after the Chrome 138 branch. Chrome 119 was the last major release to support Android 7 Nougat. Newer versions require a newer operating system.
| Your Android version | Chrome branch to use | Support position |
|---|---|---|
| Android 10 or later | Current stable Chrome | Use the latest Chrome APK |
| Android 8 or Android 9 | Chrome 138 | Last supported branch |
| Android 7 | Chrome 119 | Last supported branch |
| Android 6 or earlier | No version listed here | Consider a supported browser or newer device |
Open Settings → About phone → Android version to check the operating system. Menu names can differ by device maker.
An old Chrome APK may install on more than one Android release, but that does not make it the right package for every phone. The CPU architecture, version code, signing certificate, and APK format must also match.
Check the Processor Architecture
Chrome packages are published in different hardware variants:
arm64-v8a: used by most 64-bit Android phonesarmeabi-v7a: used by older 32-bit ARM devicesx86orx86_64: mainly used by emulators and a small number of older devices- Combined package: may contain files for both ARM64 and ARMv7
Do not select a package by guessing. Check the phone manufacturer’s specification or use a known hardware-information app. A package built for the wrong processor may fail with App not installed or a parsing message.
Check Whether the Download Is an APK or Bundle
A standard APK can usually be opened through Android’s package installer. A split APK, XAPK, or bundle contains a base package plus configuration files for the processor, language, or screen density.
Opening only the base APK can cause an incomplete or failed installation. Download the complete file set and use a package installer that supports the supplied format.
Before adding either download link, display these file details beside the selected variant:
- Full version number
- Version code
- Minimum Android version
- CPU architecture
- Package format
- File size
- Screen DPI
- SHA-256 hash
- Signing-certificate fingerprint
- File source
- Verification date
Do not use one hash or file size for every variant. Each architecture and package format can produce a different file.
Are Old Chrome Versions Safe?
An old version may be compatible with a legacy phone, but it is not equal to a supported browser. Chrome 138 and Chrome 119 no longer receive the security work added to current releases. Newly discovered browser faults may remain unfixed on those branches.
Avoid unsupported Chrome versions for:
- Online banking
- Payment accounts
- Password management
- Work or school accounts
- Private documents
- Sensitive email
- Cryptocurrency services
A valid Google signing certificate can help confirm who signed the package. A matching SHA-256 hash can confirm that the downloaded file matches the published file. Neither check makes an unsupported browser current or free from known and future security faults.
Use a supported browser or replace the device when possible.
How to Install an Older Chrome APK
- Sync or export any bookmarks and other browser data you need.
- Check the installed Chrome version under Chrome → Settings → About Chrome.
- Confirm the downloaded package supports your Android release and CPU architecture.
- Compare its file size, SHA-256 hash, package name, and signing certificate with the published record.
- Open the completed download.
- Allow installation from that browser or file manager when Android requests permission.
- Select Install.
- Remove the unknown-app permission after installation.
Android normally prevents an older version code from replacing a newer installed build. Uninstalling the current app may be required for a downgrade, but doing so can remove local browser data. Preinstalled Chrome may only allow updates to be removed rather than the full system app.
Do not remove the existing installation solely to bypass a signature mismatch. A different signer may indicate that the package is altered or comes from another publisher.
Common Old-Version Installation Problems
| Problem | Likely cause | What to check |
|---|---|---|
| App not installed | Lower version code or signature conflict | Installed version, certificate, and package ID |
| Parsing error | Unsupported Android release or damaged file | Android requirement, size, and SHA-256 |
| Package appears invalid | Missing split files | Download and install the complete bundle |
| Installation stops | Wrong CPU architecture | ARM64, ARMv7, x86, or x86_64 |
| Chrome closes after launch | Device incompatibility or damaged app data | Storage, app cache, and correct branch |
| Play Protect warning | Unknown, changed, or suspicious package | Stop and verify the source and signer |
| Chrome updates automatically | Google Play automatic updates are enabled | Review Play Store update settings |
Do not disable browser updates permanently on a supported device. Security releases are part of the protection against malicious websites, harmful downloads, and browser exploits.
Why Does an Older Phone Need an Older Chrome APK?
Every Chrome release has a minimum Android API level. When Google ends support for an Android generation, later Chrome builds stop installing on that operating system. This can produce a Play Store compatibility message or installation failure even when the phone has enough storage.
Using the last compatible release may restore access to Chrome on an old phone, but it does not restore security support from Google.