Tutorials 8 min read April 2026

Extracting APK Files from Your Installed Android Apps

A smartphone with app icons and a tray pulling out an app, illustrating extracting APKs

Legal & Safety Notice: This article is for educational purposes only. Extracting an APK from a device is intended for personal backup of applications you already legally installed on a device you own. XAPK to APK does not host, distribute, link to, or facilitate access to copyrighted, paid, or pirated applications. Redistributing extracted APKs of paid or copyrighted apps is not permitted. See our Disclaimer for full terms.

You have an amazing app on your phone that you spent hours setting up, only to find out it's been removed from the Play Store. Or maybe you're switching to a new device and want an offline copy of your favorite tools just in case. Extracting APK files from your currently installed apps is the solution.

Below we walk through pulling an APK off your phone without root, where this comes in handy for backups, and how to check an extracted file afterward with our online analysis tools.

Key Takeaways

You can extract almost any app's APK file directly from your device's internal storage.
Modern apps often use Split APKs, which require a specialized extractor.
Root (Superuser) access is generally not required to back up standard applications.
Once extracted, you can transfer the file to an SD card, PC, or cloud storage.

Why Extract APKs?

Before jumping into the "how," here is why you should maintain an APK backup library:

Preserve Discontinued Apps: If a developer removes their app from the store, you'll still have your installable copy.
Legacy Hardware Support: Keep versions that work on your older tablet when the official app updates to require newer Android versions.
Version Rollback: If an update introduces bugs, you can reinstall your extracted backup and be back in business.
App Sharing: Send a specific app version to a friend via Bluetooth or cable without using cellular data.

Method 1: Using an APK Extractor App (No Root)

The easiest way is to use a dedicated utility. There are dozens of "APK Extractor" apps available on the Play Store. These tools work by finding the app's installation path in /data/app/ (which is readable but normally hidden) and copying the base.apk to your public Download folder.

Steps:

Install a reputable APK Extractor.
Open the app and grant "Storage Permissions" if requested.
Scroll through the list of all installed applications.
Tap on the app you want to save.
The tool will instantly copy the APK to your internal storage.

Handling Split APKs

If you extract a complex app like Facebook or WhatsApp, you might find several `.apk` files instead of one. These are Split APKs. To use them, you'll need our APKS/APKM Merger tool to combine them into a single file.

Method 2: Manual Extraction via ADB (Advanced)

If you don't want to install extra apps on your phone, you can use a PC with Android Debug Bridge (ADB):

Connect your phone to your PC via USB and enable USB Debugging.
Open a terminal and type: adb shell pm path com.example.app
This will show the path. Example: package:/data/app/com.example.app/base.apk
Type: adb pull /data/app/com.example.app/base.apk ./backup.apk
The file is now on your PC!

What You Actually Get When You Extract

An "installed" Android app is not stored on the device as a single APK any more, especially if it came from the Play Store as an Android App Bundle. When you extract, you may get one file or several, and knowing the difference helps you decide what to keep:

A single base APK. Older or smaller apps that were uploaded to Play as a plain APK still install as a single file. Extraction returns one .apk that is self-contained.
Base APK + several config splits. Apps published as AAB are installed as multiple APKs side by side: a base.apk plus split_config.<abi>.apk (native code for your CPU), split_config.<density>.apk (resources for your screen), and split_config.<language>.apk (strings for your locale). Extraction returns all of them. To re-install the same app on the same device, you need them all.
Asset-pack data, sometimes. Modern games using Play Asset Delivery store large gameplay assets in app-private cache outside the APKs themselves. These typically cannot be exported with a regular extractor; the asset packs are designed to be re-fetched on first launch.

If your goal is a portable backup that will install on another device, you usually want either (a) a merged "universal APK" produced with our APKS to APK merger, or (b) all the splits archived together so a split-APK installer such as SAI can restore them as a unit.

How Extraction Works (No Root, Behind the Scenes)

Most "APK extractor" apps do not actually need root because Android exposes installed package files through a system-level read path. The standard flow is:

The extractor app calls PackageManager.getPackageInfo(package, ...) to get the list of installed apps.
For the chosen app, it reads ApplicationInfo.sourceDir (the path of the base APK, typically /data/app/<package>-<hash>/base.apk) and splitSourceDirs (paths of any config splits).
The user-installed extractor cannot read these paths directly, but the FileProvider mechanism in Android lets system components grant temporary read access to specific URIs. The OS does let any app open its own APKs and other apps' APKs by URI; this is intentional, since the install path was always meant to be world-readable for tasks like uninstall and update.
The extractor copies the bytes into a writable user directory (Downloads, an in-app cache folder, or external storage) and presents them as a file to share or install.

Root-only methods (su; cp /data/app/...) bypass the API and read raw paths directly. They are not faster and not necessary for non-system apps.

Extracting via ADB (Recommended for Backups)

The cleanest non-app workflow is ADB, which most developers already have set up. Two commands do the entire job:

# 1. Find the on-device path(s) for the package
adb shell pm path com.example.app

# Output (single APK):
#   package:/data/app/~~hash==/com.example.app-1/base.apk
#
# Output (split APKs):
#   package:/data/app/~~hash==/com.example.app-1/base.apk
#   package:/data/app/~~hash==/com.example.app-1/split_config.arm64_v8a.apk
#   package:/data/app/~~hash==/com.example.app-1/split_config.xxhdpi.apk
#   package:/data/app/~~hash==/com.example.app-1/split_config.en.apk

# 2. Pull each path
adb pull /data/app/~~hash==/com.example.app-1/base.apk ./

For split-APK apps, repeat adb pull for each path. To get a single installable file, drop all of them onto our APKS to APK merger.

What Cannot Be Extracted

Extraction returns the application's installation files. It does not return:

App data: preferences, databases, save files. Those live under /data/data/<package>/ and are protected from non-root extraction by the user-data sandbox.
Play Asset Delivery asset packs: downloaded on first run, cached privately, and expected to be re-fetched if missing.
Cloud-saved progress: if the app uses Google Play Games, Firebase, or similar, the cloud-stored portion is on the publisher's servers, not on your device at all.

Extraction is therefore good for "I want a copy of the installer to keep around" use cases, but not a substitute for proper full-device backups (which require root or vendor tooling).

Analyze Your Extracted APKs

Once you've backed up your apps, use our online suite to check their metadata, icons, and permissions.

Start APK Analysis

Frequently Asked Questions (FAQ)

Does extracting an app include my login data?

No. Extraction only copies the application code and resources. It does not include your personal account data, passwords, or settings for security reasons.

Can I extract system apps like YouTube?

Yes. However, some system apps might have deep dependencies on specific OS versions and might not install correctly on other devices.

Where do extracted APKs go?

Most extractor apps save files into a folder named ExtractedAPKs or Download in your phone's internal storage.

Conclusion

Building your own local app repository is the surest way to never lose access to the tools you love. A tap-friendly app and the ADB terminal both get you there, and either way extracting APK files is a safe, practical way to manage your Android device. After you back up your library, take a moment to verify the signatures of those backups so you know they stay untampered over time.