Release tracker
Minecraft Updates for Java and Bedrock
Track Minecraft updates by release channel. Find stable versions and hotfixes for everyday play, Java snapshots and Bedrock Preview builds for testing, and Mojang’s announcements for upcoming game drops.
Sources reviewed
Upcoming game drops
Final game drop of 2026
The Deep Freeze
Explore ice caves, meet the frostbite zombie variant, and build with new blocks. Selected features are available to try in Java snapshots and Bedrock Preview or Beta.
First game drop of 2027
Throwing Disc reveal
Mojang revealed the new ranged weapon at TwitchCon alongside expanded off-hand support for Bedrock Edition.
Stable Minecraft updates and hotfixes
Bedrock 26.63
Targets Windows, servers, and PlayStation 5. Fixes include a Windows startup freeze and an issue that could break multiplayer features on the first connection.
Bedrock 26.63 changelogBedrock 26.60
Adds Nintendo Switch 2 support and lets players try selected features from The Deep Freeze through the Drop 4 experiment.
Bedrock 26.60 changelogJava 26.3
Wilderness Bound adds the dappled forest, abandoned camps, poplar wood, straw beds, and cushions.
Java 26.3 changelog
Java snapshots and Bedrock previews
Java 26.4 Snapshot 8
Adjusts the ice ball, fixes aspects of the Ender Dragon’s flight, and adds Javanese and Zamboanga Chavacano language support.
Java Snapshot 8 changelogBedrock 26.70.24
Tests an Invisible Armor world setting and adjusts several features from The Deep Freeze, including brittle ice and ice ball sounds.
Bedrock Preview 26.70.24 changelog
Which Minecraft version should you play?
Match the changelog to your edition and version
Start with the edition you actually play. A Java snapshot, a Bedrock Preview, and a stable release can all appear in the same week. Each answers a different question. If you want to know whether a bug is fixed in your regular world, open the stable changelog for your edition. If you want to try a feature Mojang is still developing, look for the snapshot or Preview that lists it. If you only saw a reveal, look for a changelog before deciding which build to install.
The version number alone can be misleading across editions. Under Mojang’s year-based numbering, both editions use 26 for 2026 releases, while the numbers that follow vary because Java and Bedrock ship on different schedules. Java 26.3 and Bedrock 26.50, for example, both identify Wilderness Bound releases for their respective editions. To compare versions with a friend, first compare edition and release channel, then read out the full version. Read Mojang’s version numbering guide
When you are reading Minecraft updates for changes to terrain, check the notes for any instructions about existing worlds. A screenshot of a new structure or biome leaves open where to find it in a save you already use. If the notes point you to newly explored areas, test that instruction in a world copy before changing your main save.
Stable release notes and platform hotfixes
A stable release is the starting point for ordinary play. Open its changelog and look for the specific feature, fix, or compatibility note that matters to you. If you are waiting for a startup fix, the relevant line may be in a short hotfix post several days after the original game drop. For a major feature, the original release notes usually give more context than the patch notes for a later fix.
Bedrock hotfixes can have a platform-specific rollout. For example, Mojang listed Windows, servers, and PlayStation 5 for the 26.63 hotfix. If a friend on one of those platforms sees a different number, compare the notes’ platform list with the devices you’re using. Then check your device’s regular update channel. A difference in numbers is a reason to check the rollout information before assuming your installation is out of date. Open the official release changelogs
Try upcoming Minecraft updates in Java snapshots
A Java snapshot lets you try development changes before a full release. In the Minecraft Launcher, open Installations for Java Edition and enable snapshots. Choose the build named in the changelog. Give the test installation a separate game directory, and make a backup before opening an existing save in a test version. For a first look at a new block or mob, a fresh test world is often enough.
Read beyond the headline when your world uses data packs or resource packs. The technical section can include changes to pack versions, commands, or world generation that affect a setup even when the headline is about a mob or building block. If a pack stops working, compare the pack’s supported game version with the installation you launched. Test the same feature in a clean world so you can see whether it works before you add your packs. Browse the Java snapshot changelogs
Try Bedrock Preview or Beta on your device
Bedrock players use the Preview or Beta program to try features in development. Follow the directions for your device. On Android, joining the Beta through Google Play can replace your regular Minecraft app, so make a backup before joining. On iOS, Minecraft Preview uses TestFlight and places may be limited. Use the links in Minecraft Help for Windows and console instructions instead of assuming that mobile steps apply to every device. Check Minecraft Help’s Preview and Beta instructions
Keep the full Preview or Beta version handy if you want to test with friends. Minecraft Help says everyone must be on the same testing version to join a multiplayer game. A regular Realm uses the regular game. Check the separate testing Realm instructions if you want to play an early feature with a Realms group. Record the version, platform and world settings when you compare results. That helps you tell a platform difference from a change between two test builds. Browse the Bedrock Preview and Beta changelogs
Check whether a feature needs a world experiment
Some stable Bedrock builds include upcoming features behind a world experiment. Bedrock 26.60 is an example. Its notes identify selected features under the Drop 4 experiment. If the stable game is installed but you cannot find a feature, open that build’s changelog and look for the experiment named beside it. Turn on only the setting the notes specify in a copy of the world, then open the same copy to test.
For a missing item or block, record the exact feature name, the version, and the experiment you enabled before searching for a fix. This will help if a tutorial uses a newer Preview or relies on a community Add-On. When the feature comes from a community project, check the creator’s supported Bedrock build and see the Bedrock Add-On setup guide for pack activation.
Tell a Minecraft game drop announcement from a playable update
A game drop announcement can name a theme, show features and give a release window. A changelog tells you what a specific build contains. The Deep Freeze is Mojang’s final 2026 drop, with selected features available to test through the appropriate builds. The Throwing Disc reveal concerns the first game drop of 2027. Find the name of the feature you want in the release or testing notes for your edition. For the announced weapon itself, see the Throwing Disc release and crafting guide.
Availability can change during testing. Check the changelog for the version you can actually run, even if you already watched a preview video or read an earlier announcement. When a clip lacks a build number, use it to identify the feature and use the notes to find the right version. That also helps when older footage shows behavior that was subsequently adjusted during development.
Before you update a world you want to keep
- Record the working setup. Note the edition, build number, and any packs, add-ons, or mod loader you use. If you share a world, ask the host which version they are running.
- Save a separate backup. On Java, select the single-player world, choose Edit, and select Make Backup. Keep the backup where you can find it again. On Bedrock, follow the backup instructions for your device before changing the release channel.
- Test in a new world or a copy. Verify the feature or fix you care about, and check that your packs and settings work together. Confirm that multiplayer players can connect before updating the main shared world.
- Keep the working copy until you finish checking. If the test breaks something, return to a backup made before opening that save on a newer version. This is especially important if you used a snapshot or Preview.
Minecraft updates FAQ
How do I know if I have the right update? Match the full version on your title screen or launcher profile against the exact changelog. If you play on a server, ask which edition and build the host uses and check that you’re launching the intended profile.
Why is a feature missing after the game updated? Look up the feature name in the changelog for your installed version. Check whether it is limited to a snapshot, Preview, Beta, or named world experiment. If a platform list accompanies the update, check that it includes your device.
Should I switch to a testing build for my main world? Use a fresh world or a copy to try a development feature. Keep the regular save on the stable build you use for everyday play. That gives you a working save to return to if the test version changes world data or breaks a pack.