What Is an APK File? A Plain-English Guide for Android Users

An APK is the package format Android uses to install apps; it is a signed ZIP archive holding the app's code, resources and manifest, and it is what the Play Store delivers behind the scenes.

You have probably seen the letters APK on a download page, in a forum thread or in an error message. Maybe someone told you to "just grab the APK", and you nodded along without being quite sure what that meant. This guide explains it from scratch: what an APK is, what is inside it, how it relates to the Play Store, and what you should know before you open one.

APK in one sentence

APK stands for Android Package. It is the file format Android uses to distribute and install apps. If you have ever installed an app on an Android phone, you have used an APK, even if you never saw the file. When you tap Install in the Play Store, the system downloads the package and installs it for you.

A useful comparison is a program installer on a computer. On Windows, you might run a setup file to put a program on your machine. On Android, the APK plays a similar role. The difference is that Android handles most of the process for you, and apps are kept in tidy, separate containers.

What is inside an APK

An APK is really a ZIP archive with a different name. If you rename one to .zip and open it on a computer, you can see its contents. A typical APK contains the following:

• AndroidManifest.xml: a description of the app, including its name, package name, version, the permissions it asks for and the screens it includes.
• classes.dex: the compiled program code, in a format Android's runtime can execute. Larger apps have several of these files.
• resources.arsc and the res folder: compiled text, colours, layouts and images.
• lib folder: native code libraries, separated by processor type such as arm64-v8a.
• assets folder: raw files the app uses directly, such as fonts, sounds or data.
• META-INF folder: the digital signature and a list of fingerprints for every file.

That last item deserves attention. Every APK must be signed with the developer's certificate before Android will install it. The signature proves who built the app and shows whether anything was changed after signing. It is the reason Android can stop a stranger from slipping a modified file in as an update to your real banking app. We use this fact in our guide on checking that an app is official.

How apps reach your phone

The Play Store does not work the way it used to. Developers once uploaded a single APK, and everyone downloaded the same one. These days new apps are published as an Android App Bundle, usually shortened to AAB. The bundle holds everything for every kind of device, and Google generates optimised APKs from it for each phone.

The result is a set of smaller files, sometimes called split APKs: one base file, plus separate pieces for your screen density, your processor and your language. You get only what your phone needs, which saves storage and download time.

This is relevant when you download an app from outside the store. There may be no single universal file to give you. That is why you will sometimes meet bundles such as XAPK and APKS, which we explain in what an XAPK file is.

APK, AAB, XAPK, OBB: what is what

The abbreviations pile up quickly, so here is a short reference.

• APK: the installable package. One file, installs with a tap.
• AAB: the publishing format used by developers. You never install this directly.
• Split APKs: several APKs that together make up one app.
• XAPK, APKS and APKM: bundles that group split APKs, and sometimes game data, into one download. They need an installer app or manual steps.
• OBB: an expansion data file used mainly by large games.

Only the first one installs by simply tapping it. For anything else, you will need to follow a different process.

Why people use APK files

Most people never need to touch one, and for them the Play Store is the best option. Still, there are good reasons to work with APKs directly.

1. Regional availability. An app might not be released in your country yet.
2. Older versions. An update may have removed a feature, or may not run well on your phone. Going back to an earlier release can fix that.
3. Phones without Google Play. Some devices ship without it, so installing from a developer's website may be the only option.
4. Beta and early access builds. Developers sometimes distribute test versions directly.
5. Backups. Keeping a copy of a version you like gives you a fallback.
6. Offline installation. An APK can be installed on a device with no internet connection once it has been transferred.

The risks

The format itself is harmless, but the way it is used can be risky. Because an APK can request broad access to your phone, a malicious one can cause real harm. The dangers are well known:

• Malware that steals passwords, messages or banking details.
• Adware that fills your phone with pop-ups.
• Repackaged apps, where criminals take a genuine app, add their own code and publish it under the same name.
• Spyware that quietly records what you do.
• Fake versions of popular apps that exist only to trick you into entering your details.

Most of the problems come from unknown websites and modified apps, such as "premium unlocked" versions. They are rarely the result of installing the genuine file from the developer. That is why the single most important habit is checking where a file comes from.

How Android protects you

Android was designed with the assumption that some apps will be bad, so several layers of protection are built in.

• Sandboxing. Each app runs in its own isolated space and cannot read other apps' data.
• Permissions. An app has to ask before accessing your camera, contacts, location and similar features.
• Signature checks. An update has to be signed by the same developer as the original app, or the system refuses it.
• Install unknown apps permission. Since Android 8, you grant this per app, and it is off by default.
• Google Play Protect. It scans apps, including those from outside the store, and warns you about harmful ones.

These protections work best when you do not weaken them. Do not leave unknown-source installs switched on, and do not ignore warnings. If you are unsure which Android version your phone runs, which affects some of these features, see how to check your Android version.

How to install an APK, in brief

The process is short. You download the file from a source you trust, allow your browser or file manager to install unknown apps, open the file, tap Install, and then turn the permission off. We cover every step, including common problems, in our full guide to installing an APK file on Android.

If you hit the dreaded error message, our guide to fixing "App not installed" goes through every common cause.

Can you open an APK on a computer or iPhone?

An APK is designed for Android, so it does not run natively anywhere else. There are ways to use one on a computer, such as Android emulators or the Android subsystem on some versions of Windows, but those are for testing and for people who want to run mobile apps on a PC. On an iPhone, APK files do nothing, because iOS uses a different format and a different system for app distribution.

If you only want to look inside an APK, you can change the extension to .zip and extract it on any computer. Just remember that you are looking at compiled files, and most of them will not make sense without special tools.

How to tell what you are dealing with

When you come across a file, a quick look at the extension tells you what to do.

• .apk: a single installable app.
• .xapk, .apks, .apkm: a bundle. You need an installer or a manual process.
• .obb: game data, not an app. It goes in a folder named after the game's package.
• .zip: it might contain any of the above. Open it before you decide.

Each page on this site lists the version, size, required Android version and the package name, so you know what to expect before you download. You can browse the Android apps directory or the games section and compare these details for yourself.

A quick example from everyday life

Imagine a friend sends you a link to a small app that is not on the store in your country. You open the page, see a file ending in .apk, and wonder whether to tap it. Now you know the questions to ask. Who made this file? Does the package name match the official listing? Is the size sensible? Does the app ask for permissions that fit its purpose? If the answers are reassuring, installing it is a perfectly normal thing to do. If any of them feel off, you can simply close the page. Knowing what an APK is turns a vague worry into a short, practical checklist you can run in a couple of minutes.

Frequently asked questions