What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To run a Minecraft Snapshot server, download the server JAR from the official article for the exact snapshot, place it in a new folder, launch it with a compatible Java runtime, accept the EULA, configure server.properties, and make every player use that same snapshot in the Minecraft Launcher. Keep the test server and its worlds separate from release installations: Mojang warns that testing versions can corrupt worlds.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Minecraft Java servers with free DDoS protection and up to three free backups a day.
This guide covers a standalone Java Edition server on Windows, macOS, or Linux, including LAN play, Internet access, backups, configuration, and the errors most often seen when a client cannot connect.
As an Amazon Associate I earn from qualifying purchases.
What a Minecraft snapshot server is
A snapshot is a pre-release testing build for Minecraft: Java Edition. It can contain unfinished features, changing mechanics, and bugs that are not present in a stable release. A snapshot client and a snapshot server are separate components: the Launcher manages the game installed on each computer, while the server is a downloaded Java archive that you start yourself.
The server must run the same snapshot identifier that the players select in their Launchers. A release client cannot normally join a snapshot server, and a client on a different snapshot cannot be treated as compatible merely because both are snapshots.
#1 Best Overall
Before you install: requirements and safety
Software and access you need
- A Minecraft: Java Edition account and the official Minecraft Launcher.
- The official snapshot article for the build you want to test, including its server JAR download.
- A Java runtime that is compatible with that Minecraft version and available from your command line.
- Permission to create files in the chosen server directory and, for Internet play, access to your computer’s firewall and router settings.
- A backup location separate from the test server.
The Java level required by Minecraft can change between versions. Do not assume that the Java installation used by an older server is suitable for a new snapshot. Check the snapshot’s official instructions and verify your installed runtime with java -version.
Protect existing worlds
Do not point a snapshot at the only copy of a release world. Mojang’s warning is explicit: “Testing versions can corrupt your world, so please backup and/or run them in a different folder from your main worlds.” Make a copy before importing any world, and keep the original release-world directory untouched. The safest arrangement is a dedicated folder for each experimental snapshot and a separate backup directory that the server never writes to.
1. Choose and download the exact snapshot
Open the official Minecraft article for the snapshot you intend to test. Snapshot pages explain that snapshots are available for Java Edition, tell you to enable snapshots in the Launcher’s Installations tab, and provide a Minecraft server jar download. Current snapshot announcements use the same workflow.
Record the complete identifier before downloading. Keep that identifier in the JAR filename rather than renaming it to a generic name such as server.jar; the visible version makes it much harder to start the wrong build later. If you download more than one snapshot, use a distinct directory for each one.
2. Create an isolated server folder
Create a new directory such as Minecraft-Snapshot-26.2-7 (replace the example with your actual snapshot identifier). Copy the downloaded JAR into that directory. Do not place it beside a production server’s JAR, world, or configuration files, because the server reads and writes files relative to the directory from which it is launched.
A clean directory normally contains only the snapshot JAR at first. After the first launch, Minecraft creates files including eula.txt, server.properties, logs, and a world directory. Keeping those generated files in the snapshot-specific folder makes backup, deletion, and rollback straightforward.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors3. Verify Java and launch the JAR once
Check the Java command
Open a terminal (Command Prompt or PowerShell on Windows, Terminal on macOS or Linux) and run:
java -versionYou should see a version response rather than a message that Java is unknown. If the command is not found, install the Java runtime required by the snapshot, reopen the terminal, and run the check again. If Java starts but reports an unsupported class version or another compatibility error, replace it with the level specified for that Minecraft release.
Run from the server directory
Change into the folder that contains the downloaded JAR. Then use the exact filename in this command:
java -jar minecraft_server.<snapshot-version>.jarFor a headless server, append nogui:
java -jar minecraft_server.<snapshot-version>.jar noguiThe graphical form omits nogui and may open a server window; the headless form keeps administration in the terminal and is convenient for a machine without a desktop. Substitute the real filename, including its extension. Do not type the angle brackets shown in the example.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →The initial run usually creates eula.txt, server.properties, and world files, then stops because the license has not been accepted. That stop is expected; it is not evidence that the JAR is damaged.
4. Accept the EULA and restart
- Open the
eula.txtgenerated in the same directory as the JAR. - Read the Minecraft End User License Agreement.
- If you agree to it, change the line
eula=falseto exactlyeula=true. - Save the file without changing its name or location.
- Run the same Java command again.
If you do not agree, leave the value false and do not run the server. On a successful second start, the console should continue loading instead of stopping at the EULA check and should create or open a world.
5. Configure server.properties
Stop the server cleanly before editing configuration. In the console, use the server’s stop command, wait for the save to finish, and then open server.properties in a plain-text editor. Values are written as key=value. Save the file and restart when a setting requires a reload.
| Setting | What it controls | Practical snapshot choice |
|---|---|---|
gamemode |
Default mode for new players | Choose the mode appropriate for your test, such as survival or creative. |
difficulty |
World difficulty | Set it deliberately; changing snapshots can make mechanic testing harder to reproduce if this is left accidental. |
pvp |
Player-versus-player damage | Use true or false according to the group testing the build. |
max-players |
Maximum simultaneous players | Set a limit your computer and connection can handle. |
level-seed |
Seed used when a new world is generated | Enter a known seed when repeatable test terrain matters; leave it blank for a random seed. |
motd |
Message displayed in the server list | Identify the snapshot and remind players that the world is experimental. |
spawn-protection |
Protected radius around the spawn point | Adjust it if testers need to build at spawn. |
server-port |
TCP port used for connections | The usual Java default is 25565; change it only when you have a reason and update connection and forwarding details. |
server-ip |
Network interface to bind | Leave it blank unless you specifically need to bind the server to one interface. |
Other properties may appear as the snapshot evolves. Preserve unknown entries unless you understand their effect, and keep a copy of the file before making a large batch of changes.
Free tools Windows power users keep installed
One-click scans. No signup required.
6. Start the configured server
Launch the JAR with the same command used after accepting the EULA. Wait for the console to report that the server is ready before connecting. Keep that console open while testing: it shows joins, disconnects, warnings, and errors, and it is where you issue administrative commands.
For repeatable starts, create a small script in the server folder. On Windows, a batch file can contain:
java -jar minecraft_server.<snapshot-version>.jar nogui
pauseOn macOS or Linux, a shell script can contain:
#!/bin/sh
java -jar minecraft_server.<snapshot-version>.jar noguiReplace the placeholder with the actual JAR name. A script reduces filename typos, but it does not remove the need to update the command when you install a different snapshot.
7. Enable the same snapshot in every Minecraft Launcher
- Open the Minecraft Launcher.
- Open Installations.
- Enable the option that allows snapshot versions.
- Create a new installation or edit an existing one.
- Select the exact snapshot identifier used by the server.
- Save the installation and launch it.
Do this on every player’s computer. The multiplayer guidance from Mojang states that the Minecraft version being played must be the same version the server is running. “Almost the same” is not sufficient: compare the complete identifier displayed in the Launcher with the identifier printed by the server or shown in its JAR filename.
When a player normally uses a release installation, keep that release profile and create a separate snapshot profile. Switching profiles avoids accidentally opening a release world with an experimental client and makes it easy to return to ordinary servers.
8. Connect locally, over a LAN, or through the Internet
Same computer
On the computer running the server, connect to localhost. This avoids guessing the machine’s network address.
Best Value
Same home network
Players on the same LAN should use the host computer’s local IP address and the configured port. If the port remains the Java default, the address has the form local-address:25565. The host firewall must allow Java or the selected port on the private network.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Players outside your network
Remote players generally need the host’s public address and the server port, for example public-IP:25565 when the default is unchanged. Configure both layers:
- Create an inbound firewall rule on the server computer for the selected port and protocol.
- Set a router port-forwarding rule from the external port to the server computer’s local IP and the same internal port.
- Give friends the public address and port, not the private LAN address.
- Check that the server is running and listening before testing the external connection.
Router menus differ by manufacturer, and some Internet providers use carrier-grade NAT that prevents ordinary inbound forwarding. Do not publish the address broadly; give it only to people who need access, and remove the forwarding rule when the test is over.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Snapshot-specific operating practices
Back up before importing or updating
Stop the server, copy the entire snapshot world directory, and label the copy with the snapshot identifier and date. Keep backups outside the active server folder. Never open the only backup in a newer experimental build and assume it can be returned safely to an earlier build.
Keep release and snapshot worlds separate
Use different directories and, ideally, different server profiles for release and snapshot play. A snapshot may change world data in a way a stable release cannot read. If you want to test a release world, duplicate it first and import only that duplicate into the snapshot folder.
Install a newer snapshot as a new test
Download the newer JAR into a new snapshot-specific directory rather than replacing the old file in place. Copy a backup of the test world only when you deliberately want to test an upgrade, and record which version created each copy. This gives you a clean rollback path if the newer build fails or damages data.
Quick Recap
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
Unable to access jarfile |
The terminal is in the wrong directory or the filename does not match. | List the files in the server folder, change to that folder, and copy the exact JAR name into the java -jar command. Check capitalization and the .jar extension. |
| Java is not recognized or not found | Java is not installed, or its executable is not on the command path. | Install the runtime required by the snapshot, reopen the terminal, and confirm with java -version. |
| Unsupported class-version or similar Java error | The installed Java level is incompatible with that Minecraft build. | Check the snapshot’s official requirements and install the compatible Java runtime. Remove ambiguity by running the newly installed Java explicitly if more than one runtime is present. |
| The EULA error returns every time | The wrong file was edited, the value was not saved, or the text is not exactly eula=true. |
Edit the eula.txt beside the JAR, verify the exact value after saving, and launch from that same directory. |
| The server starts but a client is rejected | The client and server snapshot identifiers differ. | Read the server’s identifier, enable snapshots in the client’s Installations tab, select that exact build, and restart the Launcher if necessary. |
| LAN player cannot connect | Wrong local address, blocked firewall, or mismatched port. | Use the host’s private address and configured port, allow the server through the private-network firewall, and confirm that the server is running. |
| Remote friends cannot connect | Missing router forwarding, firewall rule, incorrect public address, or ISP-level inbound restrictions. | Verify the internal server address, forward the selected port, allow it through the host firewall, and test using the current public address. Remove exposure when finished. |
| World behaves strangely or will not load after testing | Snapshot data may be incompatible or corrupted. | Stop the server, preserve the affected directory for diagnosis, and restore the pre-test backup in a separate folder. Do not overwrite the original release world. |
Snapshot server versus a normal release server
| Decision | Snapshot server | Release server |
|---|---|---|
| Purpose | Test upcoming features and changes. | Provide a stable environment for routine play. |
| Client setup | Enable snapshots and select the exact build. | Use the matching release profile. |
| World handling | Use isolated folders and frequent backups because corruption is possible. | Still back up, but compatibility risk is generally lower. |
| Version changes | Builds can change quickly; record every identifier. | Updates are less frequent and easier to schedule. |
| Network setup | LAN and Internet connections use the same firewall and port principles. | The same networking rules apply. |
Final installation checklist
- The server JAR came from the official article for the intended snapshot.
- The JAR, configuration, and world are in a new snapshot-specific folder.
- The required Java runtime responds correctly to
java -version. - The first launch generated
eula.txt; you accepted the EULA by settingeula=trueonly if you agreed. server.propertieshas the desired gameplay settings, andserver-ipis blank unless a binding is intentional.- Every player selected the identical snapshot in the Launcher’s Installations tab.
- A backup exists outside the active folder before any world is imported or upgraded.
- For remote play, the firewall and router forward the selected port (25565 by default) to the correct computer.
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.
