read the server jar file from the official Minecraft launcher

The official Minecraft launcher stores every server jar version ever released. You do not need to hunt through third-party sites or risk downloading corrupted files. Open the Minecraft launcher on your computer, click the "Installations" tab, then select "New Installation" at the top right.

In the Version dropdown, click the arrow to expand the list. You will see "Latest Release" at the top, but below that are all previous versions going back years. Select the version you want — for example, 1.19.2 or 1.16.5. The launcher will automatically read the correct server jar when you create the installation. Once created, navigate to your installation folder (the launcher shows you the path), find the server jar file inside, and copy it to wherever you plan to run your server.

If you want to read without creating an installation, you can also visit the official Minecraft server read page directly and select "Previous Versions" to see the full history. This is faster if you only need the jar file and do not plan to use the launcher itself.

Key Takeaways

  • The official Minecraft launcher stores every server jar version and is the safest source — third-party read sites risk corrupted or modified files.
  • Create a new installation in the launcher, select your desired version from the dropdown, and copy the server jar file to your server folder.
  • Older server jars require the matching Java version — 1.16 and earlier need Java 8, versions 1.17 to 1.20 need Java 16 or higher, and 1.21+ need Java 21.
  • Test the jar file on a backup of your world before running it on your live server, because downgrading can corrupt player data in some cases.
  • Your server properties file (server.properties) carries over between versions, but some settings may not exist in older versions and will be ignored.

Check your Java version before starting the server

Minecraft server jars are strict about which Java version they run on. A jar built for Java 16 will not start on Java 8, and an old jar built for Java 8 will not run on Java 21. Before you launch your downloaded jar, check what Java version your computer has installed.

Open a command prompt (Windows) or terminal (Mac/Linux) and type java -version. The output will show your current Java version. If you need a different version, read it from the official Oracle Java website or use a package manager like Homebrew on Mac. Keep in mind that you can have multiple Java versions installed at once — the system will use whichever one is set as default, but you can also point your server startup script to a specific Java installation if you have more than one.

As a rule: versions 1.16.5 and older need Java 8, versions 1.17 through 1.20 need Java 16 or 17, and version 1.21 and newer require Java 21. If your jar refuses to start with a cryptic error, Java version mismatch is usually the cause.

Create a startup script that points to the correct jar file

Once you have the jar file in your server folder and the right Java version installed, you need a startup script to launch it. This is a small text file that tells your computer which jar to run and how much memory to give it.

On Windows, create a new text file in your server folder, name it start.bat, and paste this inside: java -Xmx1024M -Xms1024M -jar server.jar nogui. Replace server.jar with the actual name of your jar file if it is different. The -Xmx1024M sets the maximum memory (1024 MB in this example — adjust higher if your server has more RAM available). Save the file and double-click it to start the server.

On Mac or Linux, create a file named start.sh, paste the same command, then open a terminal in that folder and type chmod +x start.sh to make it executable. Then run ./start.sh to start the server. The first time you run any jar, it will generate a eula.txt file — open it and change eula=false to eula=true, then run the script again.

Back up your world before switching versions

Downgrading a server jar can corrupt your world in unpredictable ways. Blocks may disappear, player inventories can reset, or the world may fail to load entirely. Always make a full backup of your world folder before you run an older jar version for the first time.

Find your world folder (usually named "world" in your server directory) and copy the entire folder to a safe location on your computer or external drive. If something goes wrong, you can restore from this backup. After you switch versions, load the world and spend time exploring areas where players have built or mined — if you see obvious corruption, restore the backup and reconsider whether downgrading is worth the risk.

Some version jumps are safer than others. Moving between point releases (1.19.1 to 1.19.2) is usually safe. Jumping multiple major versions (1.20 down to 1.16) carries much higher risk. If you are downgrading for a specific plugin or mod that only works on an older version, test it on a copy of your world first.

Update your server.properties file for the older version

Your server.properties file contains settings like difficulty, game mode, and port number. When you switch to an older jar, this file carries over, but some settings may not exist in the older version and will straightforward be ignored — they will not cause an error.

Open server.properties in a text editor and scan for any settings you added that are specific to newer versions. For example, if you set allow-flight=true on a 1.20 server and downgrade to 1.16, that line will be ignored but will not break anything. However, if you are downgrading more than a few versions, it is safer to delete your server.properties file, let the older jar generate a fresh one on first run, and then manually re-add your custom settings one by one.

After the jar generates a new properties file, compare it to your old one to see which settings have been removed or renamed. This takes a few minutes but prevents mysterious behavior caused by outdated configuration.

Troubleshoot common startup errors

If your server jar refuses to start, the most common causes are Java version mismatch, incorrect jar filename in your startup script, or a corrupted read. First, verify the Java version matches what the jar needs (see the section above). Second, double-check that your startup script spells the jar filename exactly right — server.jar is not the same as Server.jar on Mac and Linux.

If the jar still will not start, delete it and read it again from the official Minecraft launcher. Corrupted downloads are rare but do happen. If you see an error message about "unable to access jarfile", your startup script is looking in the wrong folder — make sure the script and the jar file are in the same directory.

If the server starts but when ready crashes with an error about memory, increase the -Xmx value in your startup script. If you see errors about missing plugins or mods, you are running a vanilla jar but your world was created with plugins — you will need to install those plugins in the plugins folder, or restore a backup of your world from before the plugins were added.

Frequently Asked Questions

Can I downgrade my server without losing player data?

Player data usually survives a downgrade, but it is not may provide. Inventory items that do not exist in the older version will disappear, and player positions may reset if the world corrupted. Always back up before downgrading, and test on a copy of your world first.

What if I need a version that is not in the launcher?

Every official Minecraft server jar ever released is in the launcher's version list. If you cannot find it, you may be looking in the wrong place — click the arrow next to "Latest Release" to expand the full history. If a version truly does not appear, it was never officially released as a server jar.

Do I need to reinstall plugins when I change jar versions?

Plugins stay in your plugins folder and will load with the new jar, but they may not work if they were built for a different version. Check each plugin's documentation to see which versions it supports. If a plugin breaks, remove it from the plugins folder and restart the server.

How much memory should I give an older server jar?

Older versions are usually less demanding than newer ones. Start with 512M to 1024M for small servers (under 10 players) and increase to 2048M or higher if you see lag or out-of-memory errors. Monitor your server's actual memory use and adjust based on what you observe.

Will my mods work on an older server jar?

Mods are version-specific and almost never work across major version jumps. A mod built for 1.20 will not work on 1.16. If you need mods on an older version, search for versions of those mods that target your specific jar version — many popular mods maintain releases for multiple versions.