Sideloading means installing an Android app from a source outside Google Play, such as the developer’s own download page. This guide walks through a normal single-APK installation, explains the different permission prompts, and shows what to check when an update fails.
Before installing: choose the right download
Start with the project’s official website and follow its Android download link. If the website points to a GitHub release, check that the repository belongs to that project. Note the app version, minimum Android version, and the build the developer recommends for your device. A search result or a file with the right icon is not enough to establish who published it.
For this walkthrough, choose a release APK intended for direct installation. A source-code ZIP is a developer download. An .aab is an Android App Bundle publishing format from which device-specific APKs are generated. A bundle is not interchangeable with a standalone APK, and missing required split APKs can cause installation to fail. If the project supplies a different package format, follow its installation instructions rather than renaming the file. Android’s app-bundle documentation explains the distinction.
Have the phone’s browser or file manager ready and enough free space for the app. If the phone is managed by a school, employer, or parent, its installation policy may apply; use the administrator’s supported route.
Install a single APK
- Download the release. Use the official project link you checked above and wait for the file to finish downloading.
- Open the APK. Tap the completed download, or locate it in your file manager’s Downloads folder.
- Read the installation prompt. If Android asks you to allow this source, open the Settings button in that prompt.
- Allow that specific source. Turn on Allow from this source for the browser or file manager that opened the APK.
- Return to the installer. Confirm the app shown is the one you intended and select Install. Follow any additional device prompts.
- Launch the app. Complete only the setup needed for the feature you want to use.
Google documents the per-source control for Android 8.0 and later. It authorizes a particular installing app; it is not a blanket approval of every downloaded file. Source: Android alternative distribution.
Turn the source permission off when finished
On Pixel, the documented path is Settings → Apps → Special app access → Install unknown apps. Select the browser or file manager and switch off Allow from this source. Other manufacturers may place the setting elsewhere; searching Settings for “Install unknown apps” can help you locate it. You can enable the relevant source again for a future manual update. Source: Pixel installation instructions.
Do not confuse the different prompts
| What Android is asking about | What it means for this guide |
|---|---|
| Allow from this source | Permission for a browser, file manager, or other source to request an installation. |
| Developer verification | A separate check concerning the developer. Follow the specific verification message shown on your device. |
| Play Protect warning or scan | An app-safety check. Read the warning and check the official project’s explanation before proceeding. |
| An app permission after launch | Access to a capability or your data, such as files, camera, or location. |
Google’s current unverified-developer instructions describe a separate advanced flow with a 24-hour security delay. If your device presents that restriction, the ordinary source toggle may not complete the installation. Read the official instructions for that flow and decide whether you trust this developer. This guide does not assume every sideloaded APK encounters it; availability and enforcement depend on the rollout. Consult the official verification FAQ for current applicability.
Keep Play Protect enabled. Google says it checks apps from other sources as well as Play, and may warn about, deactivate, or remove harmful apps. If an install is blocked as harmful, record the exact message and verify the download with the developer rather than disabling protection as a routine troubleshooting step. Source: Google Play Protect.
Check what the app can access
After installation, open Settings → Apps → the app → Permissions. Review the requests in the context of the feature you want: a camera function has a clear reason to request camera access, while an unrelated utility should explain why it needs it. You can revisit individual permissions here. Source: change app permissions.
Accessibility and other restricted settings deserve a separate decision. Google explains that an accessibility-enabled app may read screen content and interact with other apps. A legitimate tool may need that capability, but successful APK installation does not establish that it needs unrestricted access. Read the project’s explanation before enabling a restricted setting. Source: restricted settings.
Plan how updates will arrive
Before relying on the app, find its documented update method: its own updater, its official store listing, or another manual APK download. Bookmark that source and retain any useful export or backup instructions.
For a manual update, get the new release from the same official distribution channel and open it as above. Android checks signing identity when accepting app updates. Builds with different signing arrangements may not update one another, even when their names look identical. An unexplained “not installed” message is not a reason to immediately uninstall the working copy. Check the project’s migration instructions and export important data first. Source: Android app signing.
Common problems and the next useful check
| Problem | Next step |
|---|---|
| The file opens as an archive or will not install | Check whether you downloaded source code, an app bundle, or an incomplete package instead of the release APK. |
| The source permission prompt returns | Check which app is actually opening the file. The browser and the file manager have separate source permissions. |
| An update fails | Read the exact error; check the release’s Android requirements and whether you changed distribution channels. Preserve app data before considering removal. |
| The app installs but a feature cannot access files or the camera | Check that app’s permissions and its own setup documentation. |
| The phone cites developer verification | Use the verification instructions linked above. Treat this separately from the normal source permission. |
| Your menus differ | Use the manufacturer’s instructions for your Android version. Record the actual screen wording when asking for help. |
A useful record is simple: official download URL, app version, Android version, installation source, exact error, and whether an older version is already installed. It makes a specific problem much easier to investigate than “the APK does not work.”
Scope and review date
This guide covers a normal direct APK installation on Android. It does not provide universal steps for split-package installers, device-management restrictions, or every manufacturer’s settings. Official documentation was reviewed October 27, 2026. No firsthand device test is claimed.
Did this guide help?
Your feedback helps decide what to explain or test next.
Suggest a correctionFeedback records an anonymous count. It does not submit your name or contact details.