arm64-v8a, armeabi-v7a and x86: picking the right APK
Java and Kotlin code runs anywhere, but most substantial apps also ship native libraries compiled for a specific instruction set. That is why a download page offers several variants of the same version. Picking wrongly produces either a refusal to install or an app that starts and immediately dies.
What the four names mean
| Name | What it is | Who has it |
|---|---|---|
| arm64-v8a | 64-bit ARM | Almost every phone sold since about 2018 |
| armeabi-v7a | 32-bit ARM | Older phones, some budget models and cheap tablets |
| x86_64 | 64-bit Intel or AMD | Emulators, Chromebooks, a few tablets |
| x86 | 32-bit Intel | Old emulators and a handful of discontinued phones |
廣告
Finding out which one you have
APKCombo detects your architecture and marks the matching variant on the download page, which is the easiest route. If you are downloading on a computer for a different phone, you need to check the phone itself.
- Check the app page on the phone The download list marks the recommended variant based on the device asking.
- Or use a hardware info app Any of them report the CPU ABI directly, which removes the guesswork.
- Or look up the chipset Every Snapdragon, Dimensity, Exynos and Helio from the last several years is arm64.
Reports the CPU ABI, core layout and instruction set. Small, free and does one job well.
More detail than most people need, including the exact ABI list the system reports.
Universal builds and what they cost
A universal APK contains the native code for every architecture. It always installs, and it is roughly twice the size of the variant you actually need. The unused libraries sit on your storage doing nothing.
- You are archiving a file for several phones
- You do not know the target device
- The app is small and the difference is trivial
- Storage is tight
- The download is large
- You are on a metered connection
- The app is a game with big native libraries
Why modern apps hide this from you
App bundles let the Play Store deliver only the code a specific device needs, which is why the Play install of a large game is smaller than its universal APK. Outside Play, that same split arrives as an XAPK or APKS bundle, and an installer app picks the right pieces for you.
That is the practical resolution to this whole topic: use a bundle installer and the architecture question answers itself.
Almost certainly arm64-v8a. Check with a hardware info app if you are unsure, and let a bundle installer decide when the app ships as a bundle.
Frequently asked questions
What happens if I install the wrong architecture?
Either the install fails outright, or the app installs and crashes the moment it tries to load its native library.
Is arm64 faster than armeabi-v7a on the same phone?
Usually somewhat, thanks to more registers and better instructions. The difference is real but small for most app types.
Why does my emulator need an x86 build?
Because it runs on a desktop processor. ARM builds either will not run or run through slow translation.
Read next
This is not a rivalry. Each does something the other cannot.
You are not buying encryption. You are buying an operator whose income does not depend on you.
For a plain ZIP either works. For a split, password-protected archive, only one does.
