If you want to back up an app before an update, move an installer to another device or inspect a package you already use, you may be searching for how to extract an APK from an installed Android app. Android does not offer a universal “Save APK” button, but there are two practical methods: use a reputable APK extractor app or pull the installed package to a computer with Android Debug Bridge (ADB).
The important detail is that an extracted APK is only the application installer. It does not automatically include your account, settings, messages, game progress or other private app data. Modern apps may also be installed as several split APK files instead of one complete APK.
Can you extract an APK from an installed app?
Yes. A normal user-installed app can often be copied from the device without root access. A dedicated APK extractor offers the simplest interface. ADB gives advanced users a transparent way to find the installed package path and copy the file to a computer.
Extraction is useful for:
- keeping a personal installer backup before updating;
- preserving a working version for testing;
- copying your own app build from a test device;
- examining the package name or signing certificate;
- reinstalling an app on the same compatible device;
- troubleshooting a package with developer tools.
Do not confuse an APK backup with a full app backup. The installer and the app's private data are separate.
What an extracted APK does not contain
Saving an APK from an installed app normally does not copy:
- login sessions and account credentials;
- chats, documents or local databases;
- game progress and in-app purchases;
- app settings and permission choices;
- offline media, maps or expansion data;
- secrets protected by Android Keystore;
- files downloaded after installation.
An extracted APK also does not remove the app from your phone. It simply creates another copy of one or more installation files.
Method 1: Use an APK extractor app on Android
An APK extractor app is the easiest option when you do not want to use a computer.
A typical process is:
- install a reputable extractor from a trusted store;
- open it and allow only the access it genuinely needs;
- select the installed app you want to back up;
- choose Extract, Backup or Save APK;
- find the exported file in the folder shown by the extractor;
- verify the filename, size and app version.
Menu names and storage folders differ between extractor tools. Avoid utilities that request unrelated access to contacts, SMS, microphone, accessibility services or device administration. An APK extractor should not need broad personal-data access simply to list installed packages and save an installer.
Before using an unfamiliar tool, review its developer, privacy information, update history and permissions. Our Android APK permissions guide explains which requests deserve closer attention.
Method 2: Extract an APK with ADB without root
ADB is part of Google's Android SDK Platform Tools. It lets a computer communicate with an Android device over USB or wireless debugging. Google's official ADB documentation includes commands for listing packages, printing an APK path and pulling files from a device.
Step 1: Install Android SDK Platform Tools
Download Platform Tools from the official Android Developers website and extract the folder on Windows, macOS or Linux.
Open Terminal, Command Prompt or PowerShell inside that folder. Using the current official tools avoids many connection and command-compatibility problems.
Step 2: Enable USB debugging
On the phone, open Settings > About phone and tap Build number several times until Developer options are enabled. Then open Developer options and enable USB debugging.
Connect the phone to the computer and approve the debugging prompt on the device. Approve only a computer you trust, and disable USB debugging again when you finish.
Step 3: Confirm that ADB sees the phone
Run:
adb devices
The device should appear with the status device. If it says unauthorized, unlock the phone and accept the debugging prompt. If no device appears, try another data-capable USB cable, USB port or manufacturer driver.
Step 4: Find the app's package name
If you know part of the package or app identity, use Android's package-manager filter:
adb shell pm list packages keyword
For example, replace keyword with part of the expected package name. The result looks like:
package:com.example.app
You can also check the package information displayed on an APKDL app page. Browse the APKDL Android app catalog and compare the developer, version and package name carefully.
Step 5: Find where the APK is stored
Run:
adb shell pm path com.example.app
Replace com.example.app with the real package name. Android returns one or more lines beginning with package: followed by the installed file path.
A single-APK app may return one path ending in base.apk. A split installation can return several paths.
Step 6: Pull the APK to your computer
Remove the package: prefix and use the returned path with ADB pull:
adb pull /returned/path/base.apk ./example-app.apk
Google documents adb pull remote local as the command for copying a file or directory from a device to the computer.
After the copy completes, check that the file exists and has a realistic size. Rename it for identification, but keep the .apk extension.
How to extract split APKs from an installed app
When adb shell pm path returns multiple lines, the app uses split APKs. You might see files such as:
- base.apk;
- split_config.arm64_v8a.apk;
- split_config.en.apk;
- split_config.xxhdpi.apk;
- feature-module APKs.
Pull every path into the same folder. These files form a matched set for that app version and device configuration.
Google explains that App Bundles can produce a base APK, feature APKs and configuration APKs for CPU architecture, language and screen density. Copying only base.apk may produce an installer that fails or opens without required resources. See APK vs XAPK vs APKM for a package-format overview.
Split APKs extracted from one phone are not guaranteed to work on a different phone. The second device may use another CPU architecture, language or screen density. If you need a portable release, prefer an official universal APK when the developer provides one.
Verify the extracted APK
Extraction should preserve the package's existing signature, but it is still sensible to verify the result before archiving or reinstalling it.
Google's apksigner tool can confirm whether an APK signature verifies:
apksigner verify --verbose --print-certs example-app.apk
Record the package version and certificate digest with the backup. This helps you recognize whether a later file belongs to the same signing identity.
See APK Signature Verification and Mismatch Fixes for a safer verification workflow.
Can you reinstall the extracted APK?
A single complete APK can usually be opened on Android or installed with:
adb install example-app.apk
A split set requires a compatible installer or ADB multiple-package installation. Every split must match the same package, version and signing identity.
Installation can still fail because of:
- a different signing certificate;
- an older or rejected version code;
- missing configuration splits;
- incompatible Android requirements;
- the wrong CPU architecture;
- a damaged or incomplete copy;
- device or administrator restrictions.
If Android reports a generic failure, use App Not Installed on Android: 12 APK Fixes. For compatibility checks, see How to Check Your Android Version and App Compatibility.
Use extracted APKs responsibly
Extract packages only when you have a legitimate reason and the right to use them. An app's license and copyright still apply after extraction.
Do not redistribute paid, proprietary or private company apps without permission, bypass licensing, or present another developer's package as your own. For your own app, Google Play Console offers official APK downloads.
FAQ
Can I extract an APK without root?
Yes. Many extractor apps work without root, and ADB can usually copy the installed package files after USB debugging is authorized.
Where are installed APK files stored?
Android commonly stores installed packages under protected paths inside /data/app/. The exact directory is generated by the system and can change after an update. Use adb shell pm path package.name instead of guessing the location.
Does extracting an APK copy app data?
No. It copies the installation package, not private data, accounts, settings or saved progress.
Why did I get several APK files?
The app was installed as split APKs generated for your device. Keep the base and configuration files together.
Final thoughts
The safest way to extract an APK from an installed app is to understand exactly what you are saving. A reputable extractor is convenient; ADB gives you more visibility and handles package paths directly. Neither method creates a full backup of personal app data.
Keep all split APKs together, verify signatures, record the version and respect the developer's license. A well-labeled installer backup can be useful for testing or recovery, but an official current release remains the best choice for normal installation.