How to Update an APK File on Android (Without Google Play)

If you installed an app by downloading an APK file instead of getting it from the Google Play Store, you've probably noticed something: it never updates itself. There's no little "Update" button waiting for you, no automatic download in the background. That's expected behavior, not a bug — and this guide walks through exactly how to update apk installations safely, step by step.

Why sideloaded APKs don't auto-update

Google Play tracks every app it installs and periodically checks for newer versions on its own. When you install an APK directly — a process commonly called sideloading — the app is on your device, but it isn't connected to that update system. Android has no built-in mechanism to notify you when a sideloaded app's developer releases a new version. You're responsible for checking and updating it yourself.

This is normal for APKs downloaded from developer websites or third-party app repositories. It doesn't mean anything is broken with your installation.

Step 1: Check your currently installed version

Before downloading anything new, confirm what version you actually have installed. This tells you whether an update is even necessary.

1. Open Settings on your Android device.
2. Tap Apps (sometimes labeled Apps & notifications).
3. Find and tap the app you want to check.
4. Look for App info or scroll down — the version number is usually listed near the bottom of the app details screen.

Write down or remember that version number so you can compare it to whatever you download next.

Step 2: Find out if a newer version is available

Go back to the source you originally trusted for this app — ideally the developer's own site, or a reputable APK distribution site that clearly lists version numbers and release dates. Compare the version number listed there to the one currently on your device. If the listed version is higher, an update is available.

Avoid downloading from a different, unfamiliar source just because it shows up in a search result. Sticking with a source you already trust reduces the risk of getting a tampered file.

How to check for updates without visiting the site every time

Manually revisiting a page every few days to compare version numbers gets old fast, especially if you sideload more than a handful of apps. A few practical habits make this far less tedious:

• Read the changelog, not just the version number. Reputable APK sites publish a short changelog alongside each release — what was fixed, what was added, whether it's a security patch or just a minor tweak. If a changelog mentions a security fix, that's a signal worth acting on quickly rather than waiting for your next scheduled check.
• Look for a "watch" or notification feature. Some APK repositories let registered users follow specific apps and get an email or push notification when a new version is posted, functioning similarly to an RSS feed for that one listing. This isn't universal, but where it exists, it removes the need to check manually at all.
• Subscribe to the developer's own update channel where one exists. Many independent developers post release announcements on a Telegram channel, Discord server, GitHub Releases page, or X/Twitter account before (or instead of) updating a third-party mirror. GitHub Releases in particular can be watched with a "Watch → Custom → Releases only" setting, which sends a notification the moment a new build is tagged — genuinely equivalent to an RSS feed for version updates.
• Set a recurring reminder for apps that matter most. For apps you rely on heavily but that don't offer any notification option, a simple recurring calendar reminder — say, every two weeks — is a low-effort way to make sure you're not running something seriously outdated for months at a time.
• Batch your checks. If you sideload several apps, checking all of them in one sitting once every week or two is far more sustainable than trying to monitor each one individually and constantly.

Version-checking tools for power users

If you sideload regularly, a few tools can take some of the manual work out of tracking versions:

• APKMirror Installer / APKUpdater-style apps. Some third-party installer apps can scan your currently installed apps, compare them against what's listed on a given repository, and flag which ones have newer versions available — essentially replicating Play Store-style update checks for sideloaded software. Vet any such tool carefully before installing it, since it needs a fairly broad view of your installed apps to work.
• ADB for a quick manual check. If you have Android Debug Bridge set up on a computer (see our companion guide on installing APKs for ADB basics), you can query the exact installed version of any package without digging through Settings menus:

  adb shell dumpsys package com.example.app | grep versionName

  This returns the precise version string Android has recorded for that package, which is useful when a changelog references a version number that doesn't obviously match what's shown in the Settings UI.
• Package name lookup. If you're not sure of an app's exact package name (needed for the command above), you can find it under App info on most devices by tapping the three-dot menu and selecting "App details," or by checking the URL of the app's original Play Store listing if it has one.

Step 3: Download the newer APK

Download the update the same way you downloaded the original app. Most browsers will save the file to your Downloads folder automatically. Make a note of the file name so you can find it easily in the next step.

Step 4: Install the new APK over the existing app

This is the part people worry about most: will updating this way wipe out your data, saved logins, or game progress? In most cases, no — as long as one important condition is met.

For Android to treat the new file as an update rather than a conflicting app, the new APK must have the same package name and the same signing certificate as the version already installed. When that's true, installing the new file over the old one works exactly like a Play Store update: your data, settings, and saved progress are preserved.

1. Open your file manager or browser's download list and tap the new APK file.
2. If prompted, grant permission for that app (Chrome, Files, etc.) to install unknown apps — Android will ask for this the first time.
3. Android will detect the existing installation and typically show an Update or Install prompt instead of a plain "Install" screen.
4. Tap Install and wait for the process to finish.
5. Tap Open or return to your app drawer to confirm the app still launches correctly.

What actually happens to your data during an update vs. a fresh reinstall

It helps to understand what Android is doing behind the scenes, because it explains exactly why some updates preserve everything and others don't.

Every app's private data lives in a dedicated directory under /data/data/<package name>/ — this includes its internal databases (often SQLite files used for local save data), SharedPreferences files (small key-value settings files), and any cached data the app has written. When Android performs a genuine update — meaning the incoming APK's package name and signing certificate match what's already installed — this directory is left completely untouched. The package manager replaces the app's code and resources, but the private data directory is never deleted or reset. This is why login sessions, local save files, and preferences survive an update.

A fresh install following an uninstall is a different story. Uninstalling an app instructs Android to delete that private data directory entirely, along with any data stored in app-specific external storage folders (typically under Android/data/<package name>/ on the device's shared storage, since Android 11's scoped storage changes). Once that's gone, a subsequent install starts the app with a completely empty data directory — functionally identical to installing it for the very first time, regardless of how long you'd previously used it.

There are two partial exceptions worth knowing about. First, if an app explicitly uses Android's Auto Backup for Apps or its own cloud-sync system (a linked account, for example), some or all of that local data can be restored after a fresh install, because it was never solely dependent on the local data directory in the first place. Second, files an app saved to general shared storage outside its own app-specific folder — photos exported to the general Pictures folder, for instance — aren't touched by uninstallation at all, since they were never part of the app's private data footprint to begin with.

When installation fails

If you see an "App not installed" error, it usually means the new APK's signing certificate doesn't match the one already on your device — Android blocks the install to stop a potentially different, untrusted app from silently replacing a legitimate one. It can also happen if the app is still installed for a secondary user profile on the device.

In this situation, your only real option is to uninstall the existing app first and then install the new APK fresh. Keep in mind this will delete local app data unless the app itself backs up your progress to an account or the cloud. Before doing this, check whether the app supports cloud save or account sync so you don't lose anything important.

Also worth knowing: Android won't let you install an older version number over a newer one that's already installed. If you're trying to downgrade, you'll need to uninstall first as well.

Safety notes for manual updates

• Only update from the same trusted source you used for the original install — don't mix sources for the same app.
• Compare the file size and version number against what the source page states before installing.
• Turn off "Allow from this source" for your browser or file manager again after you're done, if you'd rather not leave that permission enabled long-term.
• Be cautious of pop-ups or redirects that appear during download — they're not part of a legitimate update flow.

Final thoughts

Updating a sideloaded app isn't complicated once you understand what Android is actually checking for behind the scenes: a matching package name and signature. Check your current version, grab the new file from a source you trust, and let Android handle the rest. Understanding that a genuine update leaves your private data directory untouched — while an uninstall wipes it — takes a lot of the guesswork out of deciding whether it's safe to proceed. And if it ever refuses with an "app not installed" error, a clean uninstall-and-reinstall will get you back on track.