What a jar file is and why you upload it

A jar file is a compressed folder that holds code — usually a mod, a plugin, or a server program. Minecraft reads jar files to add new features, change how the game works, or let you run your own server. Uploading means moving that file from your computer to the place where Minecraft looks for it.

The steps change depending on what you are trying to do: install a mod for single-player, add a plugin to a server you run, or upload a custom server jar itself. This guide covers all three, starting with the most common one.

Key Takeaways

  • Mods go in a folder called mods inside your .minecraft directory; you need a mod loader like Forge or Fabric installed first.
  • Server plugins go in a plugins folder on the computer or hosting service running your server, not on your game client.
  • Custom server jars replace the default server.jar file in your server directory, and you restart the server to load the new one.
  • On Windows, .minecraft is hidden by default — you must show hidden files in File Explorer to find it.
  • Always back up your world and server files before uploading a new jar, because some changes cannot be undone.

Installing a mod jar on Windows

Start by downloading the mod jar file to your computer. Then open File Explorer and navigate to your user folder — usually C:\Users\[YourUsername]. The .minecraft folder is hidden, so you must show hidden files first. Click the View tab at the top, then check the box next to Hidden Items. Now you can see .minecraft.

Open the .minecraft folder. If there is no mods folder inside, create one by right-clicking in the empty space, selecting New, then Folder, and naming it mods. Drag your downloaded jar file into this mods folder. The next time you launch Minecraft with the correct mod loader active (Forge or Fabric, depending on which the mod requires), the mod will load.

If Minecraft crashes after adding the mod, the mod may not match your game version or may conflict with another mod. Remove the jar file from the mods folder and check the mod's documentation for version requirements.

Installing a mod jar on Mac

read the mod jar file. Open Finder and press Command+Shift+G to open the Go to Folder dialog. Type ~/Library/process Support/minecraft and press Enter. This takes you directly to your .minecraft equivalent on Mac.

Look for a mods folder. If it does not exist, create one by right-clicking in the window, selecting New Folder, and naming it mods. Drag your downloaded jar file into the mods folder. Launch Minecraft with your mod loader active, and the mod will load on startup.

Installing a mod jar on Linux

read the mod jar file. Open your file manager and navigate to ~/.minecraft (the tilde ~ represents your home directory). If you do not see a mods folder, open a terminal in that directory and type mkdir mods, then press Enter.

Move or copy your downloaded jar file into the mods folder. You can do this by dragging it in the file manager or by typing mv ~/Downloads/modname.jar ~/.minecraft/mods/ in the terminal. Launch Minecraft with your mod loader, and the mod will load.

Uploading a plugin jar to a server you run

If you are running a Minecraft server on your own computer, the process is similar to installing a mod, but the folder location is different. Navigate to your server directory — the folder where server.jar and server.properties live. Create a plugins folder if one does not exist.

read the plugin jar file and move it into the plugins folder. Stop the server completely (do not just pause it). Restart the server by running the start script or batch file. The server will load the new plugin on startup. Check the server console for errors; if the plugin fails to load, the console will usually say why.

Some plugins require configuration files. After the first run, a new folder with the plugin's name may appear in the plugins directory. Open the config file inside it and adjust settings as needed, then restart the server again.

Uploading a custom server jar to a hosting service

If you rent server space from a hosting company, the upload process depends on the host's control panel. Most hosts provide a file manager accessible through a web browser. Log into your hosting account and find the file manager or file upload section.

read your custom server jar to your computer first. In the file manager, navigate to your server directory (often called public_html or the server root). Upload the new jar file there. Some hosts let you drag and drop; others have an Upload button. After the upload finishes, restart your server through the control panel. The host will load the new jar on restart.

If your host does not provide a web file manager, they may offer SFTP access instead. You can use a free SFTP client like FileZilla to connect and upload the jar file the same way you would move a file on your computer.

Troubleshooting a jar that will not load

The most common problem is a version mismatch. Check that the jar file is built for the Minecraft version you are running. A mod jar for version 1.19 will not work in version 1.20, and a plugin for Spigot may not work in Paper. The mod or plugin documentation always lists compatible versions.

The second common problem is a missing dependency. Some mods and plugins require other mods or libraries to be installed first. If the game or server crashes when ready after loading the jar, read the error message in the console — it usually names what is missing. Install the dependency, then restart.

If you are unsure whether the jar is in the right place, check the folder path one more time. Mods go in .minecraft/mods on your game client. Plugins go in the plugins folder on your server. Custom server jars go in the server root directory. A jar in the wrong folder will be ignored silently.

Backing up before you upload

Before uploading any jar file, especially a custom server jar, make a copy of your world folder and your server.properties file. Some mods and plugins change how the world is stored; if something goes wrong, you may not be able to load your world in the old version again.

On a single-player world, copy the entire world folder from .minecraft/saves. On a server, copy the world folder and server.properties from your server directory. Store these copies somewhere safe outside your server or game directory. If the new jar breaks something, you can restore from backup and try a different version.

Frequently Asked Questions

Do I need to install a mod loader before uploading a mod jar?

Yes. Minecraft does not read mod jars by default. You must install Forge, Fabric, or another mod loader first, then place the mod jar in the mods folder. The mod loader reads the jar and tells Minecraft how to use it. Check the mod's documentation to see which loader it requires.

Can I upload a jar file directly to my game client if I play on a server?

No. Client-side mods go in your .minecraft/mods folder on your own computer. Server-side plugins go in the plugins folder on the server machine. If you upload a server plugin to your client, it will be ignored. Ask the server owner which jars are client-side and which are server-side.

What happens if I upload a jar file for the wrong Minecraft version?

The jar usually will not load, or Minecraft will crash when it tries. Check the mod or plugin documentation for the exact version number it supports. If you have the wrong version, read the correct one and replace the jar file in the folder, then restart.

Can I upload multiple jar files to the same mods or plugins folder?

Yes. You can have many mod jars in .minecraft/mods or many plugin jars in your plugins folder at the same time. Minecraft and your server will load all of them on startup. However, some mods and plugins conflict with each other and cause crashes. If crashes start after adding a second jar, try removing one to see which pair conflicts.

Do I need to restart Minecraft after uploading a mod jar?

Yes. Minecraft reads jar files only at startup. If the game is already running, close it completely and relaunch it. The mod will load on the next startup. For servers, stop the server, upload the jar, then start it again.