Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Back up the world from Minecraft: Java Edition first, then run the snapshot in a separate game directory. In Singleplayer, select the world, choose Edit, choose Make Backup, and confirm that the dated .zip appears through Open Backups Folder. Keep that archive outside the active game directory, preferably with a second copy on removable or off-device storage. In the Launcher, enable the snapshot from Installations and point it at a different game directory or use a temporary test world.
This matters because Mojang’s snapshot warning is explicit: snapshots can corrupt a world. The procedure below is for Minecraft: Java Edition; it does not describe Bedrock Edition saves or Bedrock preview builds.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft | Java & Bedrock Ultimate Collection | Windows Digital Code | $49.99 | Buy on Amazon |
| 3 |
|
Minecraft | Standard Edition | XBOX Digital Code | $19.99 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The safest sequence before you launch a snapshot
Use this order every time you want to test a development build:
- Start the stable Minecraft: Java Edition release that currently opens your world correctly.
- Open Singleplayer, select the world, and choose Edit.
- Choose Make Backup. Java Edition creates a dated
.ziparchive. - Choose Open Backups Folder and confirm that the archive is present and identifiable by its date.
- Copy the archive somewhere outside the active Minecraft game directory. A removable USB drive is a practical second location; an off-device copy gives you another layer if the computer or profile fails.
- In the Launcher, use the Installations tab to enable the snapshot. Configure that installation with a separate game directory, or use it only with a temporary world.
If the snapshot behaves badly, close Minecraft, leave the changed save alone, and restore the pre-snapshot copy while the game is closed. Do not open the modified save in an older release and hope that it will repair the data; use the dated archive as the recovery point.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
What makes snapshots risky
A snapshot is a development build of Minecraft: Java Edition rather than the normal stable release. It can contain unfinished changes to world generation, blocks, entities, data formats, or code that has not received the same compatibility guarantees as a release version. Mojang’s 2021 warning for snapshot 21w19a says: “Snapshots can corrupt your world, so please backup and/or run them in a different folder from your main worlds.” That warning is the reason to treat a snapshot as a separate experiment, not as a routine update.
The danger is not limited to a visible crash. A development build may save changes that a stable release cannot interpret correctly, leave a world broken or unloadable, or alter chunks as they are generated. The Minecraft Wiki’s tutorial likewise advises using a temporary world or a separate game directory when testing development builds. A backup protects the earlier state; isolation reduces the chance that the snapshot ever touches the files you rely on.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteThis guide therefore uses two controls:
- A dated recovery point: the archive made with Make Backup.
- A separate working area: a snapshot installation that does not share the main world’s working files.
Neither control makes a snapshot bug impossible. Together, they make an unsuccessful experiment recoverable.
Before you start: a short preparation checklist
- Confirm that you are working in Minecraft: Java Edition and can see the target world in Singleplayer.
- Close other programs that might be copying, synchronizing, or locking the Minecraft files. The in-game backup should finish before you move the archive.
- Decide which world is the protected original. Give attention to the exact world name; similarly named test copies are easy to confuse.
- Have a second storage location ready. The generated archive is useful only if it remains available after a failed update, damaged profile, or accidental overwrite.
- Know which stable release currently opens the world. Recovery should use that matching release, not an older version selected at random.
- Plan to test the snapshot with a new or disposable world first if you are evaluating features rather than inspecting the protected save.
These checks prevent the most common mistake: creating a backup and then immediately launching the snapshot against the same live save.
Create the official in-game backup
1. Open the world-management screen
- Launch the stable Java Edition installation that normally opens your world.
- Select Singleplayer from the main menu.
- Click the world you want to protect once so it is highlighted.
- Choose Edit. Do not choose Play Selected World yet.
The Edit World screen contains the backup command and keeps the operation tied to the selected save. Selecting the world first is important when several worlds have similar names.
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
2. Choose Make Backup
Select Make Backup and wait for the operation to complete. Java Edition writes a compressed .zip archive whose title includes the backup date. This is preferable to an unlabeled overwrite because the date identifies the recovery point you made immediately before the snapshot test.
Recommended Free Tools
Do not rename the archive in a way that removes the date or the world identity. If you need a human-friendly naming convention for a second copy, retain the original dated name as part of the new name, for example by adding a short note after it.
3. Open the backups folder and verify the file
Return to the Edit World screen and choose Open Backups Folder. This opens the location where Java Edition stores the generated archives. Confirm that a new .zip is present, that its date matches the current backup, and that the file has a plausible size rather than being an empty or obviously incomplete transfer.
The official Help workflow exposes these dated archives through Open Backups Folder. You do not need to guess where the launcher placed the backup. The Java save data itself is conventionally under the .minecraft/saves directory, but the backup archive is easiest to locate through the in-game button.
Store the archive outside the active game directory
Leaving the only copy beside the live installation defeats much of the protection. A snapshot configured to use the same files, a mistaken deletion, or a damaged game profile could affect both the world and the archive.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that is unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world full of surprises.
- SURVIVAL ADVENTURES — Face mysterious foes, travel across varied landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play solo or join friends in local split-screen and cross-platform play across console, mobile, and PC. Online multiplayer supports up to 8 players.
- COMMUNITY PLAY — Connect with players on community servers, or subscribe to Realms Plus (sold separately) to play with up to 10 friends on a private server.
Use two locations when the world matters
- Copy the dated
.zipfrom the backups folder to a location outside the active Minecraft directory. - Keep a second copy on a removable USB storage drive or another off-device location.
- Preserve the date and world identity in both filenames so you can distinguish several recovery points.
- Do not edit the archive contents while Minecraft is running.
A removable drive is a category-level storage choice, not a guarantee: protect it from loss and unplug it safely. An off-device copy adds redundancy, but it is still your responsibility to know which copy is current and usable. The official guidance establishes the dated archive and the corruption risk; it does not mandate a particular storage brand, capacity, or cloud provider.
Keep the original archive until the test is over
Do not replace the pre-snapshot archive with a later backup made after the snapshot has opened the world. The earlier archive is the clean recovery point. If you create additional backups during testing, label them as post-snapshot copies and keep the original separate.
Isolate the snapshot in the Launcher
Enable snapshots from Installations
- Open the Minecraft Launcher.
- Go to the Installations tab.
- Create or edit an installation for the snapshot you want to test, then enable the snapshot option if it is not already visible.
- In that installation’s settings, assign a game directory different from the directory used by your stable installation.
- Save the installation and launch it only after the backup and copy steps are complete.
The important setting is the separate game directory. Minecraft stores saves and other working files relative to that directory, so the snapshot should not share the stable installation’s active saves folder. The exact directory you choose is up to you; the safety property is that it is distinct and recognizable.
Use a temporary world for feature checks
If you want to see a new block, command, mob, or world-generation change, create a temporary test world inside the snapshot installation. This lets you evaluate the build without opening the protected world at all. Keep the temporary world clearly named, such as a snapshot date and build identifier, so it cannot be mistaken for the main save.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →A temporary world is the lowest-risk option for demonstrations. If you must inspect the existing world, use the isolated game directory and the backup you just created; never treat isolation as a substitute for the archive.
Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
Manual folder copies: useful as a second layer
The in-game Make Backup command is the most convenient primary method because it creates a dated archive and exposes it through Open Backups Folder. A manual copy of the world folder can add another recovery option, especially when you want an immediately readable copy of the Java save data.
Copy only while Minecraft is closed
- Exit Minecraft completely, not merely to the title screen.
- Locate the Java data directory and its conventional
.minecraft/savesfolder. - Identify the exact world folder by the name shown in Singleplayer.
- Copy that folder to a separate location without changing the original.
- Label the copied folder with the stable release and date, then keep it apart from the snapshot game directory.
A manual folder copy is not a replacement for the dated archive if you have not verified what was copied. It is a second layer. Copying while the game is closed avoids capturing files during a save operation, when the folder may not represent one consistent point in time.
Free tools Windows power users keep installed
One-click scans. No signup required.
Which approach should you use?
| Approach | Convenience | Isolation | Redundancy | Recovery confidence |
|---|---|---|---|---|
| In-game Make Backup | Highest: one command from the world’s Edit screen | Depends on where you keep the resulting archive | One local archive unless you copy it elsewhere | High when the dated .zip is confirmed and preserved |
| Manual world-folder copy | Lower: requires closing the game and locating .minecraft/saves |
High if the copy is stored outside the active directory | Can supplement the archive with another local copy | Useful second layer when made while the game is closed |
| Separate snapshot game directory | Requires launcher setup before testing | Highest for preventing shared working files | Does not create a backup by itself | Strong when paired with a dated archive |
| Temporary snapshot world | Fastest for testing new features | Highest because the protected world is never opened | Not applicable to the main world | Best for feature checks, not for inspecting existing builds |
The robust combination is not a choice between these rows: make the in-game archive, store it separately, and run the snapshot in its own directory. Add a manual folder copy when the world is especially valuable or you want an additional local recovery layer.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Recover the world after a bad snapshot
Stop before more data is written
If the snapshot crashes, shows missing content, reports errors, or leaves the world behaving unexpectedly, close Minecraft immediately. Do not continue exploring, save again, or open the altered world in the stable release. Every additional save can move the files farther from the state you meant to protect.
Return to the dated archive
- Use the stable Minecraft installation that previously opened the world correctly.
- Ensure Minecraft is closed before changing any save data.
- Open the backups location from the stable installation’s world-management workflow, or use the separate copy you stored outside the game directory.
- Identify the archive dated before the snapshot test.
- Restore the intended world from that archive or copy while the game remains closed. Keep the damaged or post-snapshot files aside rather than deleting them immediately, in case you need to inspect them later.
- Launch the matching stable release and verify that the restored world opens normally.
The critical rule is version alignment: restore the pre-snapshot state, then launch the stable version that created or last opened it successfully. Do not use an older release as a repair tool for a save that a newer snapshot has changed.
Best Value
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Keep the failed test separate
Once the restored world works, leave the snapshot installation and its altered files isolated. If you want to investigate the failure, make a disposable copy of the world and use that copy in the snapshot directory. Never turn the only clean archive into an experiment.
Troubleshooting common backup mistakes
The backup button was used, but no archive is visible
Return to the same world’s Edit screen and choose Open Backups Folder again. Check that you selected the intended world before choosing Make Backup. If the archive still is not present, do not launch the snapshot; make a manual copy of the world folder with Minecraft closed and confirm that the copy exists outside the active directory.
The archive is in the game directory
That is a location problem, not necessarily a failed backup. Copy the dated .zip to a separate drive or off-device location before testing. Keep the original date in the copied filename and avoid deleting the source until the second copy is confirmed.
The snapshot installation opens the main world automatically
Stop at the menu. Recheck the installation’s game-directory setting and point it to a different directory. If you cannot verify the separation, create a temporary world and postpone opening the protected save until the paths are clearly distinct.
The world was opened in the snapshot before the backup
Close the game without making further saves. If a clean archive or manual copy does not exist, there is no guaranteed way to reconstruct the earlier state. The official warning is why the backup must precede the first snapshot launch, not follow it.
The restored world will not load
Confirm that Minecraft is closed, that you restored the pre-snapshot archive rather than a later copy, and that you selected the matching stable release. Do not repeatedly open the same failing save in different versions; preserve the archive and work from a separate copy if further diagnosis is necessary.
A repeatable checklist for every snapshot
- Stable Java installation selected.
- Correct world highlighted in Singleplayer.
- Edit > Make Backup completed.
- Dated
.zipconfirmed with Open Backups Folder. - Archive copied outside the active game directory.
- Second removable or off-device copy made when the world matters.
- Snapshot installation assigned a separate game directory.
- Temporary world used for feature checks whenever possible.
- Stable release identified for recovery.
- Snapshot launched only after all preceding checks pass.
Bottom line
For a Minecraft: Java Edition world you care about, use both safeguards: create the dated archive with Make Backup and run the snapshot from a separate game directory. Keep a second copy outside the computer when practical. If anything goes wrong, close the game, restore the pre-snapshot archive while Minecraft is closed, and return to the matching stable release. This workflow cannot prevent every snapshot bug, but it prevents a test build from becoming the only version of your world.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
