Download Minecraft APK for Android
Download Latest Version Minecraft Bedrock
Why Download Minecraft APK from mcpedl.gg
Every Minecraft APK on this site is checked before it goes live. The file you install on Android matches what Mojang ships — not a modified, repackaged, or unofficial version.
What we verify on every build:
- Official package name
com.mojang.minecraftpeand Mojang Studios digital signature - SHA-256 checksum confirmed before publication
- Test install and stable launch on real Android devices
- New Minecraft Bedrock releases added within 24 hours of Mojang’s rollout — Release, Beta, Preview, and Hotfix builds
Choose a Minecraft PE Version
Minecraft Bedrock for Android is split into numbered branches. Each branch matches a major content update — 1.21 Tricky Trials, 1.26 Tiny Takeover and Chaos Cubed — and contains multiple patches, hotfixes, and Beta builds inside.
The right APK for you depends on what you want from the game. The newest features. The best stability for your device. Compatibility with a Realm or server. Support for a specific add-on.
Pick the branch that fits your situation, then grab the latest patch within that branch. Every active branch has a dedicated page with every patch, Beta, and Hotfix listed.
- Minecraft PE 1.26 (26.x) — Tiny Takeover and Chaos Cubed. Year-based numbering, redesigned baby mobs, craftable Name Tags, Sulfur Caves, and Cinnabar. Latest Release and Beta builds.
- Minecraft PE 1.21 — Tricky Trials. Trial Chambers, Mace, Breeze, Crafter, plus all 2024–2025 feature drops. Latest patch 1.21.132.
- Minecraft PE 1.20 — Trails and Tales. Cherry Grove, Sniffer, Camel, Archaeology, and Armor Trims. Latest patch 1.20.81.
- Minecraft PE 1.19 — The Wild Update. Deep Dark, Warden, Allay, and Mangrove Swamp. Final patch 1.19.83.
- Minecraft PE 1.18 — Caves and Cliffs Part 2. Expanded world height -64 to 320. Final patch 1.18.32.
- Minecraft PE 1.17 — Caves and Cliffs Part 1. Introduced the RenderDragon engine. Final patch 1.17.41.
- Minecraft PE 1.16 — Nether Update. The lightest modern branch for older Android devices. Final patch 1.16.221.
Version Numbering — How to Read a Minecraft APK Version
Minecraft Bedrock uses a layered version number written as MAJOR.MINOR.PATCH.BUILD. A typical Release looks like 1.21.81 or 1.20.81. A Beta or Preview build adds a fourth segment, such as 1.21.130.22.
The first number (MAJOR) has stayed at 1 throughout Bedrock history. The second number (MINOR) identifies the major update — 1.21 is Tricky Trials, 1.20 is Trails and Tales, 1.19 is The Wild Update.
The third number (PATCH) marks a stable release inside the same branch. 1.21.0 is the original Tricky Trials drop, 1.21.50 is The Garden Awakens, 1.21.80 is Mounts of Mayhem.
The fourth segment, when present, identifies the exact build. Numbers ending in .20 through .29 are typically Beta or Preview builds inside that patch line. A file labeled 1.21.130.22 is a Beta inside the 1.21.130 patch chain. Public Release builds usually end at .0x or have no fourth number.
Starting with version 1.26, Mojang introduced a parallel year-based notation written as 26.x. This is the same APK as 1.26.x — the file 26.13 and 1.26.13 are byte-for-byte identical, just written in two valid formats. Both notations appear across changelogs, websites, and add-on creators.
The rule of thumb when picking a build — higher patch numbers within the same MINOR branch are more stable. Pick the latest patch of the branch you want, unless you specifically need an earlier build for server, Realm, or add-on compatibility.
Build Types — Release, Beta, Preview, Hotfix, and Patch
Mojang ships Minecraft Bedrock through a fixed release cycle. Knowing what each build type means helps you pick the right APK for your situation.
| Build Type | When to Pick It |
|---|---|
| Release | Default choice for everyday play. Works with Realms, Featured Servers, and most add-ons. The Latest Release hot-button at the top of this page points here. |
| Beta | You specifically want to test pre-release features. Distributed through Google Play opt-in on Android. Cannot connect to Realms. |
| Preview | Same as Beta but on Windows, iOS, and consoles. On Android, the Beta channel remains the standard testing route. |
| Hotfix | Recent Release caused crashes or UI issues on your device. Hotfixes are small urgent updates that fix critical bugs without adding features. |
| Patch | Incremental update inside the same branch (1.21.50 → 1.21.60 → 1.21.70). Often adds named feature drops while preserving compatibility with worlds and add-ons. |
Stability progresses through the release cycle: Beta or Preview → Release → Hotfix or Patch. For everyday Android play, the latest Release or Hotfix of the branch you need is almost always the right pick.
Beta and Preview builds cannot connect to Realms by design. If Realms is your main use case, never install a Beta APK — install the latest Release from the version page that matches your branch.
What is Minecraft Bedrock Edition?
Minecraft Bedrock Edition is the cross-platform version of Minecraft built for Android, iOS, Windows 10/11, Xbox, PlayStation, and Nintendo Switch.
When someone searches for a Minecraft APK download, they are looking for Bedrock — APK is the Android installation format, and the only Minecraft edition that ships as an Android APK is Bedrock. Every download on this site is a Bedrock APK.
Minecraft PE (Pocket Edition) is the original name of the mobile version, and today it is fully integrated into Bedrock. The terms are used interchangeably. “Minecraft PE 1.21” and “Minecraft Bedrock 1.21” on Android refer to the same game, the same APK file, and the same set of features.
The defining feature of Bedrock is cross-platform play. An Android player can join the same world as a friend on Xbox, PlayStation, Switch, iOS, or Windows 10/11, as long as everyone runs a compatible Bedrock version.
This is what version-matching means in practice — Bedrock unifies all these platforms under one engine and one update schedule.
Minecraft Java Edition does not run on Android. Java is a separate product, built on different technology, and runs only on PC, Mac, and Linux. It has no Android APK and never has. It cannot connect to Bedrock servers, cannot use Bedrock add-ons, and shares no save format with Bedrock.
Bedrock is developed by Mojang Studios, owned by Microsoft. Mojang manages the version cycle, signs the APK files, and publishes the official changelogs.
One side note — Minecraft Dungeons is a separate game from Mojang and is not related to Bedrock APK downloads. If you came here looking for Dungeons, that is a different product with a different Android app.
Official Sources and APK Authenticity
Minecraft Bedrock for Android is officially distributed through two channels — Google Play and direct APK files signed by Mojang Studios.
Google Play is the default for most users. It auto-updates the game, verifies file integrity at install time, and ties the install to your Google account for easy reinstalls.
Manual APK installation is the alternative, and it exists for cases where Google Play cannot serve what you need. The Play Store only delivers the latest Release of the current branch.
If you want a specific patch — for add-on compatibility, server matching, or device performance — or if you want to install a Beta build outside the Play Store enrollment, you need an APK file. Manual install is also the only option in regions where Google Play does not list Minecraft, or on Android devices without Google services.
How to verify an installed Minecraft APK is authentic:
- Open Settings → Apps → Minecraft → App Info
- Confirm the package name is
com.mojang.minecraftpe - If the package name is anything else, the file is not the official Mojang build — uninstall it
Beyond the package name, Android performs digital signature verification on every APK at install time. Official Minecraft builds are signed by Mojang Studios, and Android checks this signature against any existing Minecraft installation on the device.
A file that claims to be Minecraft but is signed by someone else fails to install or triggers a security warning.
Signature verification is also why “App not installed” appears so often when switching between Minecraft sources. If you have Minecraft from Google Play installed and try to install an APK from a different source on top, Android sees two different signatures for the same package name and blocks the install.
The fix is to uninstall the existing Minecraft first (back up your worlds — see the Older Versions section below), then install the new APK. From that point, stick to one installation source for that device.
How to Install Minecraft APK on Android
Once you have picked a build from one of the version pages and downloaded the APK, the install takes about a minute. Menu paths differ slightly between Android versions and manufacturer skins, but the steps are the same everywhere.
- Open Android Settings. On Android 8–9, go to Security → Install unknown apps. On Android 10 and later, open Apps → Special app access → Install unknown apps. On Samsung One UI, the path is Settings → Biometrics and security → Install unknown apps. On Xiaomi MIUI, it is Settings → Privacy protection → Special permissions → Install unknown apps.
- Find the browser or file manager you used to download the Minecraft APK and enable “Allow from this source” for that app.
- Open the downloaded APK from your Downloads folder or directly from the browser, and tap Install.
- Wait for installation to finish, then launch Minecraft from the app drawer.
- After install completes, turn off “Install unknown apps” for your browser to keep the permission scoped to a single use.
If Android shows “App not installed”, a parse error, or a signature conflict during step 3, jump to the Troubleshooting section below — these are the three most common install errors and each has a known fix.
Android Compatibility — RAM, Processor, World Saves
Minecraft Bedrock APK runs on a wide range of Android devices, but performance and feature support vary by Android version, processor architecture, and available RAM.
Java Edition does not run on Android in any form. There is no Java APK, no mobile port, and no plan for one. On Android, Bedrock is the only option — every APK on this site is a Bedrock build.
The minimum supported Android version depends on the branch. Older branches like 1.16 and 1.17 still launch on Android 7. The newest 26.x branch requires Android 9 or later for stable performance. Most current Minecraft branches target Android 8 as the baseline.
Processor architecture matters as much as Android version. Modern Minecraft builds require a 64-bit ARM (arm64-v8a) processor, which covers virtually every Android phone made since 2018.
Older 32-bit ARMv7 devices can run earlier Minecraft branches (1.16 through some 1.20 patches) but are no longer supported on the newest releases.
RAM is the practical limit on which version runs smoothly.
| Branch | Recommended Device |
|---|---|
| 1.16 and 1.17 | 2 GB RAM minimum, Android 7+ |
| 1.19 and 1.20 | 3 GB RAM works, 4 GB feels comfortable, Android 8+ |
| 1.21 and 26.x | 4 GB RAM minimum, 6 GB recommended for dense scenes, Android 9+ |
Storage requirements have grown alongside features. Current builds need around 1 GB of free space for the game, worlds, and cache.
World compatibility follows the version cycle. Worlds created in an older branch open and convert in a newer branch — but the conversion is one-way and permanent. A 1.20 world loaded in 1.21 can no longer be opened in 1.20 afterward.
Worlds created in a newer branch usually cannot be opened in an older branch at all, because the newer branch contains blocks, mobs, or world-generation features that the older engine cannot read. Patches inside the same branch (1.21.50 → 1.21.81) are mutually compatible and worlds move freely between them.
If a Minecraft build does not launch on your device, the cause is almost always one of three things — Android version too old for that branch, RAM too low for the build’s content load, or a 32-bit device trying to run a 64-bit-only APK. Switching to an earlier branch (or a lighter patch within the same branch) usually solves it.
Add-ons and Mods Compatibility
Bedrock Edition does not use Java-style mods. Instead, it has a parallel system called add-ons, distributed as .mcaddon or .mcpack files.
An add-on is a packaged combination of a behavior pack (which changes how mobs, items, or game logic behave) and a resource pack (which changes how things look and sound). On Android, you install an add-on by tapping the .mcaddon file — Minecraft opens automatically and imports it into your library.
This is one of the most common reasons players download a specific Minecraft APK rather than the latest from Google Play. Add-ons are version-locked to the engine they were built against.
An add-on made for 1.21.50 may break, fail to load, or crash the game on 1.21.80 or 1.26.x because internal APIs, entity formats, or scripting hooks changed between versions. Popular add-on creators usually update their packs after a Minecraft release, but the gap can be days or weeks — and some smaller add-ons never get updated at all.
The practical rule — match the APK to your add-on, not the other way around. Before installing a new Minecraft version, check which game version the add-ons you use support. If they support 1.21.x, install the latest 1.21 patch rather than jumping to 26.x. Patches inside the same branch usually preserve add-on compatibility, while jumps between branches frequently break things.
Some character, mob, and gameplay add-ons require Experimental Gameplay enabled in world settings. If you install an add-on, load a world, and the new content is missing or appears broken, open the world’s settings and turn on the experimental toggles the add-on requires.
If an add-on stops working after a Minecraft update, the diagnostic order is — confirm the add-on supports your installed Minecraft version, verify the experimental toggles, then try downloading the previous Minecraft patch from the relevant version page on this site to restore the working setup. Browse the full Mods category for the latest free add-ons compatible with current Bedrock builds.
Multiplayer, Realms, and Cross-Platform Play
Multiplayer in Minecraft Bedrock depends on one core rule — everyone needs a compatible version. The APK you install on Android has to match the version your friends, your server, or your Realm is running.
When versions don’t match, Bedrock blocks the connection with a generic “outdated client” or “incompatible version” error and gives no further detail. That is how strict the version match is.
Cross-platform play is the headline feature of Bedrock. An Android player on the right version can join Xbox, PlayStation, Nintendo Switch, Windows 10/11, and iOS players in the same world. The catch is that all of those platforms also need to be on a compatible Bedrock version.
When Mojang releases a new Release, platforms update at slightly different times. Android typically updates within hours through Google Play, while console platforms can lag by a day or two. During that window, cross-play between platforms can break temporarily until everyone is on the new version.
There are three multiplayer routes on Android, each with its own version requirements.
| Multiplayer Route | Version Requirement |
|---|---|
| Featured & Marketplace Servers (Lifeboat, Mineplex, CubeCraft, The Hive) |
Latest Release only. Beta and Preview builds are rejected. Microsoft sign-in required. |
| Realms (Mojang’s subscription service) |
Latest stable Release only. Beta and Preview clients cannot connect by design. |
| Personal & community servers (BedrockConnect, custom IP) |
Depends on the server. Some stay on a specific older patch (1.21.30, 1.20.81) for stability. |
A free Microsoft account is required for almost all online play — Featured Servers, Realms, Marketplace, and friend invites. Single-player and local LAN play work fully offline without an account, so if you only play solo, no sign-in is needed.
If multiplayer fails after install, the troubleshooting order is — confirm you are on the same exact version as the server or your friends, confirm you are on a Release build (not Beta), confirm you are signed in with Microsoft for any online feature, then check network permissions and that the device’s date and time are correct. A clock skew of more than a few minutes blocks the Microsoft sign-in.
Looking for an Older Minecraft Version?
Most players download the latest Release because newer is usually better — newer features, fewer bugs, active server compatibility. But there are real situations where an older Minecraft APK is the right choice, and this site keeps every patch of every branch online specifically for those cases.
The most common reason to download an older version is add-on compatibility. If your favourite character pack, gameplay overhaul, or texture set was last updated for 1.20.81 and breaks on 1.21 or 26.x, the cleanest fix is to install the exact APK the add-on was built against.
The second reason is server or Realm version matching. Some community servers stay on a specific patch for stability or to keep their add-on chain working — 1.21.30, 1.20.81, and 1.19.83 are common stable anchors. If you cannot connect to a server you used to play on, the cause is usually a version mismatch.
The third reason is device performance. Newer Minecraft branches add features that increase rendering load and RAM usage. The 1.21 Trial Chambers, the 26.x Static Colored Lighting, and the Sulfur Caves visuals all run noticeably heavier than 1.20 or 1.19.
On a 3 GB or 4 GB RAM device that struggles with the newest branch, dropping to 1.20.81 or 1.19.83 often restores smooth gameplay without losing the parts of Minecraft you actually use.
The fourth reason is preserving worlds. World saves convert one-way — a 1.20 world opened in 1.21 cannot be opened in 1.20 ever again.
Always back up your worlds before switching versions. On Android, world saves are stored at /sdcard/games/com.mojang/minecraftWorlds/. Copy this folder to another location on the device or to cloud storage before installing a different Minecraft APK. To restore, place the folder back at the same path after the new install.
Worlds created in a newer Minecraft cannot be opened in an older Minecraft. If your world was created or opened in 1.26, going back to 1.21 will fail with a “world is incompatible” error or, worse, render the world with missing blocks shown as purple “unknown block” tiles.
Test the rollback on a copy first, and keep the original world folder backed up.
Troubleshooting — Common Errors and Fixes
Most Minecraft APK problems on Android fall into three groups — install errors, launch crashes, and performance issues. Each has a small set of known causes and fixes.
“App not installed” or signature conflict. This happens when you install a Minecraft APK on top of a different Minecraft build with a mismatched signature. Android blocks the install to prevent silent app replacement.
Fix — uninstall the existing Minecraft first (worlds remain on the device if you backed up /sdcard/games/com.mojang/minecraftWorlds/), then install the new APK. After that, keep using the same source for future installs on that device.
“Parse error”. Android cannot read the APK file. The three common causes are — the file is corrupted (redownload it), your Android version is older than what the build requires, or the APK is 64-bit only and your device is 32-bit. Use the version pages on this site to pick a build compatible with your hardware.
Game crashes on launch. Open Settings → Apps → Minecraft → Storage and tap Clear cache — not Clear data, which would delete your worlds. Reboot the device and launch again. If the crash continues, uninstall and reinstall the APK.
On Samsung One UI and Xiaomi MIUI, manufacturer overlays sometimes interfere with the first launch. Disabling battery optimization for Minecraft (Settings → Apps → Minecraft → Battery → Unrestricted) often resolves it.
Game crashes on specific content. Crashes that only happen in Trial Chambers, Sulfur Caves, the Pale Garden, or other heavy biomes are usually GPU-related. Lower the Render Distance to 8 chunks, disable Fancy Graphics, and turn off Smooth Lighting in Video settings.
If the crashes continue, switch to an earlier patch within the same branch — heavy visuals in the newest patches sometimes need a hardware refresh that your device cannot deliver yet.
Low FPS or stuttering. Close background apps, free up storage, and reduce Render Distance to 8–10 chunks. On 4 GB RAM devices, switching from a Beta build to the latest Release of the same branch often improves performance significantly. Beta builds are not optimized to the same level as Release.
“Not enough storage”. Minecraft needs roughly 1 GB free during install, plus space for worlds and cache afterward. Clear unused apps, photos, or downloads, then retry. On low-storage devices, prefer a lighter Minecraft branch (1.20 or earlier) over the heaviest 26.x builds.
How to Read Minecraft Changelogs
Every Minecraft Bedrock release comes with an official changelog from Mojang, published on minecraft.net and inside the in-game What’s New screen. The changelog is the only reliable source for deciding whether to update — it lists exactly what changed, what was fixed, and what might break.
A typical Mojang changelog has three core sections — New Features, Changes, and Fixed Bugs. Larger releases also have an Experimental Features section for content that requires the Experimental Gameplay toggle, and a Technical Changes section for add-on creators describing API changes that may break existing add-ons.
When deciding whether to update, the most important sections to read are Fixed Bugs and Technical Changes. Fixed Bugs tells you whether the issues you have been hitting are addressed in this build. Technical Changes is where compatibility with your current add-ons is at stake.
A few specific phrases in changelogs should make you pause before updating:
- “World generation changes” — newly generated chunks will look different from old chunks at the boundary, creating ugly seams in long-running worlds.
- “Breaking changes” or “Removed features” — something that worked before no longer works. Mojang flags these deliberately.
- “Experimental” next to a major feature — the feature is still in testing, may behave incorrectly, change, or get removed entirely. Worlds using experimental features cannot be uploaded to Realms.
- “Beta”, “Preview”, or build numbers ending in .20–.29 — this is not a Release. Skip unless you are specifically testing.
For minor patches that only list bug fixes and no Technical Changes section, updating is almost always safe and worthwhile. For major patches that introduce new features, new biomes, or new mobs,