How to Extract an APK File from Android (2026 Guide)

Extracting an APK means copying the installed app’s package file out of the phone, either with an extractor app or with two ADB commands (pm path and adb pull). It works without root for any app you installed, and it gives you a byte-identical backup you can archive, share, or mod later.

Part of the modding hub: How to Mod an APK · Storage: Where APKs Are Stored · Related: Export from Android Studio.

There are two jobs people mix up under this phrase. Copying the package out of a phone is extraction, covered here. Unpacking the archive to read what is inside is a separate task that needs a decompiler instead. Everything below is about copying.

What Does “Extracting an APK” Mean?

Extraction copies the installed package files, base.apk plus any split files, from Android’s app storage to shared storage or a computer; the result preserves the installed version for archiving or inspection, provided you collect every required split and keep the files together.

Getting the APK of an Installed App

Every installed app has at least one APK file on disk. The package manager knows the path, and two tools can read it: a file manager app on the phone, or ADB from a computer. Both are reading the same file.

Unpacking an APK File

Unpacking is different. It means opening the ZIP and extracting classes.dex, the manifest, and resources for inspection. That requires a decompiler such as JADX or APKTool, not an extractor.

Two Different Tasks

If your goal is a backup, a transfer, or a mod base, you want extraction. If your goal is to read the code or change something inside, you want unpacking. Extraction first, then unpack the copy, never the live install.

Method 1: Use an APK Extractor App

An extractor app lists installed packages, lets you select one, and writes its APK files into shared storage; this is a phone-only option when you want to back up a few apps without setting up a computer, cable, or terminal commands.

Step-by-Step

1. Install an extractor from a source you trust.
2. Open it and find the app in the list.
3. Tap the app, choose extract, and pick a destination folder.
4. Confirm the file appears in your file manager with the size you expect.

Where the APK Is Saved

Most extractors default to /storage/emulated/0/ExtractedApks/ or straight into Download/. Check the app’s settings if you cannot find it, and move the file somewhere organized before it gets buried under a hundred downloads.

Method 2: Use ADB

ADB copies files directly from a connected device to an explicit destination, with no intermediate extractor app; use it when you need repeatable commands, visible output paths, or backups of several packages, including split files reported by the package manager.

adb shell pm path

adb shell pm path com.example.app

The output prints package:/data/app/~~random/com.example.app-random/base.apk. That is the path to pull. For split packages, the command prints one line per split file, and every one of them matters. Google’s ADB documentation lists pm path among the package manager commands.

adb pull

adb pull /data/app/~~random/com.example.app-random/base.apk ./app.apk

The file that lands on disk is byte-identical to the installed one. Full ADB setup, including wireless pairing, is in the install APK with ADB guide.

Extract Split APKs

When pm path prints more than one line, copy all of them and keep their names. Reinstalling only the base gives you an app that crashes on launch, because the split that holds the resources for your screen density or ABI never loaded.

List All Package Paths at Once

To pull several apps in one sitting, script the loop instead of clicking through an app list:

for p in com.a.app com.b.app; do
  adb shell pm path $p | sed 's/package://' | while read f; do
    adb pull "$f" "./backups/$p/"
  done
done

Each app lands in its own folder with its full split set intact. A hundred-app backup takes about four minutes on USB 2.0 and roughly half that over a paired Wi-Fi connection.

Method Comparison

An extractor app, ADB, and Android Studio can all copy installed package files, but the right route depends on whether you are using only the phone, already have a computer connected, or need to collect split APKs as a complete set.

All three copy the same bytes. The difference is bookkeeping: ADB makes you responsible for every split file, while the app-based tools collect the set for you.

Method 3: Use MT Manager

MT Manager works as a phone-side extractor: it lists installed apps, shows package details, and writes files to a folder you choose; it is useful when the next step is editing the APK on the same device, with its guide explaining that workflow.

Extract From the App List

Open MT Manager, use the APK list view, find the app, and choose extract. For split packages the tool gathers the set together, which is exactly the case where hand-copying over ADB goes wrong.

Then Edit or Sign

Because MT Manager is also an editor, you can go straight from extraction into modding your copy. Extract first, duplicate the file, and only then open the duplicate in the DEX or Arsc editor. When the edit is done, the signing guide covers the certificate step.

How to Extract an APK From a PC

With USB debugging enabled, a computer can run ADB commands and save package files to an explicit folder; this route suits repeatable backups, while Android Studio offers a graphical path for people who prefer its Device Explorer over a terminal.

Android Studio Device Explorer

Open the Device File Explorer, navigate to the app’s folder under /data/app, right-click the APK, and save it. The explorer shows the same paths ADB reports, which makes it useful when you are already deep in a project.

Pull Over USB or Wi-Fi

Same commands as above, run from any terminal where adb is on the PATH. Over Wi-Fi, pair once with adb pair and then work without the cable. The pull step is identical.

How to Extract Split APKs and XAPK

Many modern installs use split packages, with base.apk alongside files such as split_config.arm64_v8a.apk and split_config.en.apk; collect the base and all required splits together because a base-only copy may fail to install or run correctly.

What Split APKs Are

Splits exist so a download contains only the code and resources a given device needs. A phone in one region, on one CPU, in one language downloads a smaller slice of the app than the full universal package would be.

Extract the Whole Set

adb shell pm path lists every file in the set. Pull them all into one folder and leave the names untouched, because the installer matches splits by filename at install time. The same applies to an XAPK, which is an APK bundle with its splits inside a container.

Reinstall as a Set

adb install-multiple base.apk split_config.arm64_v8a.apk split_config.en.apk

Or use a tool that understands the container. Details on installing bundles are in the XAPK install guide.

How to Extract Every App on a Phone

Batch extraction repeats the same path lookup and file copy for each package the device reports; save each output with its package name and version so a large archive remains identifiable when you need to restore one app after a future update.

Keep Versions, Not Just Apps

A backup of one moment in time goes stale the first time an app updates. Record the version code alongside each file, either from dumpsys package <pkg> | grep versionName or from the app’s About screen, so you can tell in a year which build you are holding.

Where to Store the Archive

Local disk is fine for a handful of files. For a full device archive, use a drive you control rather than a cloud folder that re-encodes or strips metadata, and keep two copies if the files matter. APKs are small: a hundred apps usually land between 8 and 15 GB.

Common Extraction Errors

Common extraction failures include denied file access, incomplete split sets, and package paths that changed after an update; identify which condition applies before repeating the copy, since each problem requires a different fix on the phone or computer running the extraction.

Permission Denied

If ADB refuses the copy, the app is in a protected location or the device disallows debug access to it. Extractor apps hit the same wall on system packages. Neither sign means the APK is gone, only that this route cannot read it.

Missing Split APKs

Pulling only base.apk from a split install produces a file that installs and then crashes, or refuses to install outright. Always check how many paths pm path printed, and copy every one.

Wrong File Path

Paths under /data/app contain random suffixes that change on every update. Re-run pm path instead of reusing an old path, and double-check the ~~ characters survive the copy-paste intact.

What to Do With an Extracted APK

An extracted file records the package version installed at the time you copied it, making it useful for a later reinstall, transfer, or inspection; keep the version and date with the backup because the app may have updated since the extraction.

• Back it up: keep dated copies so you can reinstall an old version later. The backup guide turns one-off extractions into a real archive routine.
• Share it: send the file to another phone over Quick Share or a transfer app.
• Inspect it: unpack a copy with a decompiler to see permissions, code, and resources.
• Mod it: duplicate it and start editing, following the modding pillar.

Verify What You Got

Before trusting an extraction, check the size against what the device reports and confirm the file opens as a valid ZIP. A zero-byte file or a truncated pull means the copy failed silently, which is the most common ADB mistake on flaky cables.

Keep the Version Record

Write down the package name, version code, and extraction date next to each file. Six months later, when an app has updated three times, that record is the only way to know which build you are holding. dumpsys package <pkg> prints both numbers on a connected device.

Extraction vs Downloading a Fresh Copy

Extraction copies the package files currently installed on your phone, including required splits, while a fresh download may be a different build or package set; choose based on whether you need to preserve the version you had or obtain the developer’s currently published release.

When Extraction Wins

Rolling back after a bad update, preserving a version that was delisted, or copying an app to a device with no store access. All three need the file you already hold, not a fresh download that may no longer exist.

When Downloading Wins

The installed copy is corrupted, the app was sideloaded from an untrusted source, or you want the universal APK rather than your device’s splits. In those cases pull from the vetted download sites instead of copying what is on the phone.

Backups and restore steps live in the backup APK guide. Start with a single extraction over ADB, confirm the file size matches what the device reports, then build the habit of pulling every package you care about before an update lands.