Use Java Edition snapshots when you want to follow Minecraft’s Java development track on a Windows, macOS or Linux computer. Choose Bedrock Preview on supported consoles, Windows or iOS, or Bedrock Beta on Android, when your target feature is being developed for Bedrock. Neither channel is permanently first: open the dated changelog for the exact feature, then check whether it also needs a world-level experiment. A Windows PC can run both editions; an Xbox can run Bedrock Preview but cannot run Java snapshots. Development builds can damage saves, so test in a disposable world or a backup rather than your main one.
| Name | Best for | Key spec | Platforms | Checked |
|---|---|---|---|---|
| Java snapshots | Testing Java Edition features on a computer | Enabled from Minecraft Launcher → Installations; some features also need a new-world feature toggle | Windows, macOS, Linux | Oct 2026 |
| Bedrock Preview | Testing Bedrock features on supported non-Android devices | Separate Preview testing app or console entry; some features need world Experiments | Xbox, PlayStation, Windows, iOS and other supported Bedrock devices | Oct 2026 |
| Bedrock Beta | Testing Bedrock features on Android | Joined through the Minecraft Google Play listing; beta replaces the normal Android client | Android | Oct 2026 |
Which Minecraft edition should you use to test a new feature?
Match the test channel to the edition named in the feature’s changelog. Java snapshots expose Java-only work on desktop computers. Bedrock Preview and Beta expose Bedrock work on consoles, Windows and mobile devices. A feature announcement is not proof that both editions contain the same implementation, so compare the dated Java and Bedrock notes before creating a world.
Minecraft’s official edition guide distinguishes the two development routes: snapshots are selected in the Java Launcher, while Preview and Beta are Bedrock test clients. Minecraft’s edition guide also explains why a Windows computer is the most flexible single device: it supports both editions, subject to owning the relevant game access.
Choose Java snapshots when
- You play Java Edition on Windows, macOS or Linux.
- The feature appears in a Java snapshot changelog or Java-specific feature-toggle instructions.
- You want the Java mechanics, commands, rendering behavior or mod-adjacent ecosystem represented by that development build.
Choose Bedrock Preview or Beta when
- Your target device is Xbox, PlayStation, Windows, iOS or Android and the feature is listed in Bedrock notes.
- You need to check Bedrock’s cross-device behavior, controller interface or mobile controls.
- You are willing to use a separate test app, or on Android, replace the regular client temporarily with Beta.
What are snapshots, Preview and Beta?
They are different pre-release routes, not alternate names for one universal Minecraft beta. A Java snapshot is a development build selected through the Launcher’s Installations tab. Bedrock Preview is the testing application or console mode for supported platforms. Bedrock Beta is the Android enrollment path distributed through Google Play.
All three channels can contain unfinished changes. The official Bedrock 26.70.22 notes state: “These work-in-progress versions can be unstable and may not be representative of final version quality.” Treat that warning as operational guidance: a test build can crash, change mechanics, or make a world difficult to open in another version.
A development build and an experiment setting are separate decisions. Installing the right build does not automatically activate every announced feature. Read the build notes for required toggles and create a test world with those settings only when the notes instruct you to do so.
How do I enable Java snapshots?
You need Java Edition access and a supported Windows, macOS or Linux computer with the Minecraft Launcher. Keep your normal installation and saves separate from the snapshot environment.
- Open the Minecraft Launcher and select Installations.
- Turn on the option that displays development versions or snapshots.
- Create or select a snapshot installation. Give it a distinct game-directory folder if you want stronger separation from regular worlds.
- Open the snapshot’s dated changelog and search for the feature you intend to test. Note any requirement for a new-world feature toggle.
- Launch the snapshot and create a new disposable world. If the feature requires an experimental option, enable it while creating that world rather than converting your primary save.
- Exit the snapshot before opening your ordinary worlds in the stable installation.
Minecraft’s testing guidance warns that testing versions can corrupt worlds and recommends backing up or running them in a different folder from main worlds. The Java feature-toggle guidance adds that a world created with toggled content might not upgrade safely to future snapshots or releases; keep that save clearly labeled as experimental.
How do I join Bedrock Preview or Beta?
First confirm that your device and account qualify. Preview availability differs by platform, and console ownership conditions can apply. The current Preview guidance names Xbox, PlayStation, Windows and iOS; Android uses Beta instead.
Android: join Bedrock Beta
- Back up worlds before enrolling.
- Open the Minecraft listing in Google Play and use its beta-enrollment control.
- Install the beta update and launch it from the updated app.
- Read the matching Bedrock changelog and create a separate test world.
Android Beta replaces the normal client installation rather than appearing as an entirely separate app. Leave the beta program and reinstall or update the regular release when you need the stable client again; keep a backup because worlds opened in a development build may not behave correctly after switching versions.
iOS: use Preview through TestFlight
On iOS, Preview distribution uses TestFlight and capacity is limited. If no invitation slot is available, you cannot force enrollment; wait for an opening or use another supported device. Once installed, keep Preview worlds separate from your ordinary Bedrock worlds and follow the build notes for experiments.
Xbox: install Minecraft Preview
On Xbox One and Xbox Series X|S, find Minecraft Preview in the Microsoft Store. Preview is a Bedrock route; Xbox cannot install Java Edition snapshots. Check the store and account ownership requirements shown for your console before assuming access.
PlayStation 4 and PlayStation 5: open Preview from Minecraft
Minecraft Help directs digital owners to Settings → Preview on PlayStation 4 and PlayStation 5. Availability can depend on owning an eligible digital edition. Do not delete the stable game or overwrite important worlds while adding the Preview installation.
Windows: select the Bedrock Preview application
Windows can provide both Java snapshots and Bedrock Preview, but they remain separate editions and separate test channels. Start the Bedrock Preview app, not the Java Launcher installation, when checking a Bedrock-only change. Read the Preview notes for the build number and any experiment requirement.
For platform-specific mobile enrollment details, consult Minecraft Help’s Beta and Preview instructions. Menus and eligibility can change, so the current device listing takes precedence over an older tutorial.
Do I need to turn on Experiments or a Java feature toggle?
Sometimes. The build channel tells you which development code is installed; a world-level toggle controls whether certain unfinished content is active in that world.
Java feature toggles
Some Java snapshots expose experimental content during world creation. The toggle is applied to that world, not globally to every save. If you do not see the feature in a new world, recheck the snapshot notes and the world-creation options rather than assuming the installation failed.
Bedrock Experiments
Bedrock places experimental switches in the world’s settings. A feature may require a new world, an existing world with Experiments enabled, or a particular combination listed in the changelog. Bedrock’s official experiment guidance warns that an experimental world cannot be restored to a non-experimental state. Make a copy first and label the copy with the build number and toggles used.
Do not rely on historical toggle names from older guides. The menu changes as experiments graduate, are renamed or are removed; the current build notes are the authority for the switches available in your version.
How can you compare the Java and Bedrock changelogs for one feature?
Use the feature’s exact name, date and edition rather than guessing from version numbers. Open the Java snapshot notes and the Bedrock Preview/Beta notes for the same period, then compare implementation details, prerequisites and known issues.
- Write down the feature you want to test, including its spelling in the announcement.
- Open the dated Java changelog and search for that name.
- Open the dated Bedrock changelog and search again.
- Record whether each note says the feature is available, experimental, limited to a mode, or still under development.
- Check whether either edition requires a new world, a feature toggle or a specific platform.
- Install only the channel that matches the edition you actually intend to evaluate.
A useful October 2026 example shows why dates matter. Java 26.4 Snapshot 6 was published October 27, while Bedrock Beta/Preview 26.70.22 was posted October 28. Both notes discuss snow bricks and the Cold Sulfur Cube. Those shared entries demonstrate how to compare changelogs; they do not establish permanent parity, identical mechanics or a universal lead for either edition. See the Java Snapshot 6 notes and Bedrock 26.70.22 notes for the dated details.
Can I use my main world in a snapshot or Preview?
You should not. Create a disposable test world and back up any save you cannot replace. Minecraft explicitly warns that testing versions can corrupt worlds; its testing article recommends a backup or a separate folder for development versions.
- Java: use a separate game directory or a copied world. A world with experimental feature toggles may fail to upgrade to a later snapshot or stable release.
- Bedrock: duplicate the world before enabling Experiments. Once a Bedrock world is experimental, it cannot be returned to a non-experimental state through the normal settings.
- Android Beta: back up before enrollment because Beta replaces the regular client.
- Preview on consoles and Windows: keep test saves distinct from stable-edition saves and avoid opening the same world alternately in incompatible builds.
Backups should be made while the stable client is closed. Store a copy outside the game’s live save directory, and identify it with the date, edition, build and experiment settings so you know which version can safely reopen it.
Can Java and Bedrock players test together?
Do not assume ordinary Java and Bedrock clients can join the same multiplayer world or server. They are separate editions with different networking and feature tracks. A Java snapshot player and a Bedrock Preview player generally need their own edition-compatible multiplayer setup.
Bedrock participants in a Preview or Beta session need matching development versions. If one player updates and another remains on an older Preview build, joining can fail or the world can be unavailable. Eligible Bedrock Realms subscribers may have a separate testing-Realm option, but it is not a promise that every Realm or account supports development builds.
For a group test, agree on the exact build number, platform and experiment settings before anyone joins. Keep a stable-world copy outside the test session so a failed update does not become the group’s only save.
Which edition fits your device and testing goal?
| If your priority is | Prefer | Reason |
|---|---|---|
| Java mechanics on a desktop | Java snapshot | Snapshots are the Java development route on Windows, macOS and Linux. |
| Console testing | Bedrock Preview | Xbox and PlayStation support Bedrock Preview, not Java snapshots. |
| Android testing | Bedrock Beta | Android’s official enrollment path is Beta through Google Play. |
| Testing both tracks from one computer | Windows with both editions | Windows supports Java and Bedrock, allowing separate edition-specific worlds. |
| Checking controller or mobile behavior | Bedrock Preview or Beta on the target device | The device-specific client is the relevant environment. |
| Playing with friends who use another edition | First verify edition compatibility | Java and Bedrock do not ordinarily share multiplayer sessions, and development builds require matching versions. |
What should you do when a feature is missing or a test fails?
Most apparent failures come from using the wrong edition, an outdated build, or a world without the required experiment. Work through these checks in order:
- Confirm the edition. A Java snapshot will not contain a Bedrock-only change, and Bedrock Preview will not reproduce Java mechanics.
- Confirm the build number. Compare the launcher or app version with the changelog’s exact number and date.
- Check the world requirement. Recreate a test world if the notes require a new world; then enable the named feature toggle or Experiment.
- Check platform eligibility. Preview enrollment, TestFlight capacity and console ownership rules can prevent access even when the feature exists.
- Check multiplayer versions. Every participant should use the same Preview or Beta build and compatible experiment settings.
- Restore from backup. If a world will not open after testing, stop switching versions and restore the untouched copy in the stable client.
If the changelog lists the feature but the menu does not, read its known-issues section before changing unrelated settings. Development builds can intentionally hide, rename or temporarily disable unfinished content.
How we picked the recommendation
The recommendation follows the official edition routes, supported-device guidance, world-safety warnings, multiplayer requirements and dated changelogs. It does not use a performance score or release-speed statistic: official sources provide version identifiers, not a meaningful comparative benchmark. The deciding question is always whether your target feature is documented for Java or Bedrock and whether your device can run that channel.
What is the safest testing setup?
Install the development channel on a supported device, keep the stable installation separate, back up saves, and create a new world with only the required experiment enabled. Record the edition, build number, date and toggles in the world name or a note. When the feature graduates to a release, create a fresh comparison world instead of assuming an experimental save will upgrade cleanly.
For current warnings and procedures, read the official Minecraft testing guidance and the Bedrock Experiments explanation. These pages can change as the menus and channels evolve.
Frequently Asked Questions
Is Minecraft Preview the same as Beta?
No. Preview is the Bedrock testing route used on supported platforms such as consoles, Windows and iOS, while Beta is the Android enrollment route through Google Play. Both are pre-release Bedrock builds, but their installation methods and platform availability differ.
Can I leave Bedrock Beta without losing my worlds?
Leaving the program does not make an experimental world safe to use in every version. Back up before enrollment, then return to the stable client only after confirming that the save was not opened with incompatible experimental content; keep the original backup untouched.
Why do snapshot version numbers not match Bedrock Preview numbers?
Java and Bedrock have separate development pipelines, so their labels use different numbering systems. A shared feature name or nearby publication date is not evidence that the code, mechanics or release schedule is identical.
Does owning Minecraft on Xbox give me access to Java snapshots?
No. Xbox provides Bedrock access and can support Minecraft Preview, but Java snapshots require Java Edition on a supported Windows, macOS or Linux computer. A Windows PC that supports both editions is the practical way to access both testing tracks.