To uninstall a plugin safely, stop the Minecraft server completely, make a full backup, remove or quarantine the plugin’s .jar file from the server’s root plugins folder, decide separately whether to keep its data folder, then restart and inspect the logs. Check dependencies first: removing a library, permissions, or economy plugin can prevent other plugins from loading.
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
What “uninstalling a plugin” actually removes
A Bukkit-compatible server such as Paper, Spigot, or another Bukkit-based implementation normally loads plugins from the server directory’s root-level plugins folder. Each plugin is usually enabled from a .jar file. The executable JAR and the plugin’s stored data are separate things.
![Minecraft: Story Mode – A Telltale Games Series [Online Game Code]](https://m.media-amazon.com/images/I/51R9dPuwNaL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
- Plugin JAR: the code the server loads at startup. Removing it prevents that plugin from loading on the next start.
- Data folder: the plugin’s configuration, messages, databases, caches, player settings, and other stored state inside
plugins. Its name often resembles the plugin name, but not always. - External data: some plugins store information in a separate database, a permissions system, a web service, a world folder, or another location documented by the plugin author.
Deleting only the JAR is usually enough to disable the plugin while preserving its settings. Deleting the data folder is a separate, destructive decision and is not required for a normal uninstall.
Before editing: stop and back up the server
1. Tell players and stop normally
Warn connected players, then use the server console’s normal stop command or your host’s standard Stop button. Wait until the process has fully exited and the console shows that shutdown is complete. Do not edit, move, or delete plugin files while the server is running. Paper’s troubleshooting guidance warns that modifying server files during operation can corrupt them and that only a full shutdown prevents this.
#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).
A restart command is not the same as an opportunity to edit files: wait for the old process to terminate before changing anything. If a panel reports “stopping” for an unusually long time, do not kill the process immediately; first check the console for a plugin that is delaying shutdown. A forced termination can leave world or plugin data incomplete.
2. Make a complete backup
Copy or archive the entire server directory before making the change. Include the world folders, plugins, server configuration, permissions files, scripts, and logs. A ZIP archive of the server folder is a practical minimum, provided it is created after the server has stopped.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Store the backup somewhere outside the live server directory and give it a useful name containing the date and the change, such as server-before-plugin-removal-2026-10-14.zip. Do not overwrite your only backup with a later copy. If your hosting panel offers snapshots or automated backups, create one as well, but retain an independently downloadable archive when possible.
Find the correct server and plugin file
Local or self-managed server
Open the directory that contains the server JAR, the world folders, and the plugins folder. The target file should be directly inside that plugins folder, not inside a backup, a staging directory, or a second server instance.
Plugin filenames can include version numbers, build numbers, or author-specific naming. For example, a file may be named ExamplePlugin-3.2.1.jar while its data folder is simply ExamplePlugin. Match the file using the plugin’s startup log entry or the name shown by the in-game /plugins command rather than deleting a similarly named JAR by guesswork.
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).
Hosted server
Use the provider’s web file manager or connect with SFTP. Open the server’s live root directory, then open plugins. Panel labels differ, but the underlying operation is the same: the JAR must be removed from the active instance’s root plugins folder.
Free tools Windows power users keep installed
One-click scans. No signup required.
Many panels expose multiple instances, templates, or backup directories. Confirm the server identifier, address, or startup command before editing. Removing a JAR from an unused template does not uninstall it from the running server, while deleting a file from the wrong instance can damage an unrelated world.
Choose quarantine or permanent deletion
| Choice | What to do | When it is appropriate | Trade-off |
|---|---|---|---|
| Quarantine the JAR | Move it outside plugins, or rename the extension from .jar to something such as .jar-disabled. |
You are diagnosing crashes, testing whether the plugin causes a problem, or want a quick rollback. | The plugin is not loaded, but the file remains available to restore. |
| Delete the JAR | Remove the target JAR after making the backup. | You are certain the plugin is no longer needed. | Restoration requires the backup or a fresh copy of the exact plugin version. |
For a first attempt, quarantine is safer. Move the file to a directory outside the live server, such as an archive folder beside the server directory. Do not leave a renamed file ending in .jar inside plugins; some server tools or startup scripts may still treat it as a plugin. A non-JAR extension such as .jar-disabled prevents normal loading while preserving the original file.
Remove the plugin JAR
- Confirm the server process is stopped and the backup is complete.
- Open the live server’s root
pluginsdirectory. - Identify the exact JAR associated with the plugin. Check its filename and, if necessary, the previous startup log.
- Move the JAR outside
pluginsfor a reversible uninstall, or delete it for permanent removal. - Do not remove similarly named libraries until you have checked dependencies.
On a Linux-based server, a file operation might look like mv server/plugins/ExamplePlugin-3.2.1.jar server/plugin-archive/. On Windows, use File Explorer’s Cut and Paste or Rename action. These examples describe the location relationship; use the actual path and filename on your server.
Decide what to do with the plugin’s data
After moving the JAR, inspect the corresponding data folder inside plugins. Paper documentation describes plugin configuration files as belonging in the plugin’s data folder within plugins. The folder may contain YAML or JSON configuration, language files, SQLite databases, player-specific records, caches, or generated resources.
Rank #3
![Minecraft Dungeons: Standard Edition – Windows 10 [Digital Code]](https://m.media-amazon.com/images/I/41TayT2RhCL._SL160_.jpg)
- Fight your way through an all-new action-adventure game, inspired by classic dungeon crawlers and set in the Minecraft universe!
- Play with up to four friends or brave the dungeons alone. Battle new-and-nasty mobs across action-packed, wildly varied levels, in a quest to defeat the evil Arch-Illager!
| Data-folder action | Keep it when… | Delete or archive it when… |
|---|---|---|
| Keep in place | You may reinstall, want to preserve settings, or need the records for investigation. | It does not harm anything by remaining after the JAR is gone. |
Archive outside plugins |
You want a clean live directory but still need a rollback copy or historical records. | You are unsure whether the folder belongs to the removed plugin. |
| Delete permanently | You intentionally want a clean reset and have confirmed which data the plugin owns. | Never do this merely because the JAR was removed; plugin-specific data may be irrecoverable. |
Keeping an old data folder usually does not cause the server to load a plugin without its JAR. It does, however, make a later reinstall pick up the old configuration. If you want to test the plugin as though it were newly installed, stop the server, archive the data folder, and let the reinstalled plugin generate a fresh one later.
Do not assume every file with the plugin’s name is safe to delete. A plugin may have created permissions, scoreboard objectives, world files, scheduled tasks, or database records outside its own folder. Read that plugin’s documentation or inspect the backup before removing anything beyond the JAR and its clearly identified data directory.
Check dependencies before restarting
Some plugins provide a feature directly to players; others provide libraries or services that many plugins require. Paper specifically identifies examples such as ProtocolLib, Vault providers, and permission plugins as components that can be needed by other plugins. Removing one of these can leave several apparently unrelated plugins unable to start.
Questions to answer
- Does another plugin list the target as a required dependency rather than a soft or optional dependency?
- Is it a permissions, economy, chat, protocol, library, placeholder, or API plugin used by several others?
- Does the startup log show dependency warnings for the target or for plugins that depend on it?
- Are commands, protections, ranks, shops, or other gameplay systems built around its data?
If the plugin is a dependency, plan the removal as a group. Stop the server, quarantine the target and the plugins that explicitly require it, then restart and inspect the resulting errors. Keep the original files in your archive so you can restore the previous working set.
Recommended Free Tools
Restart and verify the result
- Start the server through the normal script or hosting-panel Start action.
- Wait for startup to finish instead of joining while files are still being generated.
- Open
logs/latest.logand search for the removed plugin name, “error,” “failed,” “dependency,” and “could not load.” - Run
/pluginsin game, orpluginsin the console, and confirm the removed plugin is not listed as enabled. - Check that plugins which should remain active have loaded without missing-dependency messages.
- Test the affected gameplay commands and permissions with an operator account and, where practical, a normal player account.
A removed plugin can still appear in an old log or in a panel’s cached file listing. The authoritative checks are the current startup log and the current /plugins output after this restart.
Rank #4
- 8,800 MINECOINS — Get 8,800 Minecoins to spend on creator-made content in the Minecraft Marketplace.
- MINECRAFT MARKETPLACE — Browse a constantly updating library of content from Minecraft creators, with new content available every week.
- CREATOR-MADE CONTENT — Use Minecoins to get Marketplace content such as skin packs, mash-up packs, mini-games, and adventure maps.
- ACCESS ACROSS DEVICES — Once redeemed and linked to your Microsoft account, your Minecoins and purchases are available on supported devices that run Minecraft, including Android, iOS, Windows, and Xbox.
- A GIFT FOR PLAYERS — Give Minecraft players Minecoins to spend on content in the in-game Marketplace.
Hosted-panel and SFTP workflow
Web file manager
- Stop the server from the panel and wait for the status to change to fully stopped.
- Use the panel’s backup or snapshot function, then download an archive if available.
- Open the live server directory and its
pluginsfolder. - Select the target JAR and choose Move, Rename, or Delete. Moving it to a panel-accessible archive directory is the reversible option.
- Leave the data folder alone unless you have deliberately chosen to archive or delete it.
- Start the server and review the console and
logs/latest.log.
SFTP client
Connect to the server’s assigned SFTP host, port, username, and directory supplied by your provider. Verify that the remote path is the live server root, then perform the same operation on plugins/TargetPlugin.jar. Download the JAR and data folder before deleting them if the panel does not provide a reliable backup.
SFTP transfers can fail partway through or appear delayed in a web panel. Refresh the directory after the operation and confirm the JAR is no longer present before starting the server. Never edit a file while another client or panel process is uploading it.
Safe isolation when a plugin causes crashes
If the server will not start after an earlier change, use isolation rather than repeatedly deleting files. Stop the process, restore the last known-good backup if necessary, and then test in controlled groups.
Single-plugin isolation
Move one suspected JAR out of plugins or rename its extension to .jar-disabled. Start the server and compare the new log with the failure log. If the error disappears, the isolated plugin is a strong suspect; if it remains, stop the server before testing another file.
Group testing
When many plugins are installed, divide them into groups while keeping dependency providers with the plugins that require them. Move one group out, start the server, and narrow the failing group by repeating the process. Keep a written record of each move so you can restore the exact previous arrangement.
Restoring the old state
- Stop the server fully.
- Move the quarantined JAR back into the live
pluginsfolder, or restore it from the backup. - Restore its data folder only if you moved or deleted it.
- Start the server and verify that the original error pattern has returned or that the server is stable.
Do not restore a backup over a live server. Stop first, and preserve the failed state if you need its log for diagnosis.
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 →Paper, Spigot, Bukkit, and vanilla differences
The folder-and-restart procedure applies to Paper and the Bukkit-compatible plugin layout used by Spigot and related servers. Exact file-panel labels vary by host, but the relevant location remains the server’s active plugins directory.
A vanilla Minecraft server does not load Bukkit or Paper plugins, so it has no equivalent plugin-uninstall operation. Forge, Fabric, and other modded platforms use different loaders, directories, metadata, and dependency rules. Remove a mod according to that platform’s procedure rather than assuming a Bukkit JAR can be deleted from a plugins folder.
If you run several server instances on one machine, repeat the identity check for each instance. A shared hosting account can contain multiple roots, and the same plugin filename may exist in more than one of them.
Quick Recap
Common mistakes and their fixes
- Deleting while the server is running: stop it, restore the backup if files changed, and only edit after a full shutdown.
- Removing the wrong JAR: compare the filename with
/pluginsoutput and the startup log; restore the correct file from the backup. - Deleting the data folder automatically: restore or archive the folder before trying a clean reset.
- Removing a shared dependency: read the dependency errors, restore the library or permission plugin, and plan a coordinated removal.
- Leaving a disabled file with a
.jarextension: move it outsidepluginsor use a non-JAR extension. - Checking an old log: inspect the newly generated
logs/latest.logafter the restart. - Editing a template or wrong instance: verify the live server root and startup target before changing files.
- Assuming removal cleans external data: check databases, permissions, worlds, and scheduled resources separately.
Final removal checklist
- Players were informed and the server was stopped normally.
- A complete archive exists outside the live server directory.
- The correct active instance and root
pluginsfolder were confirmed. - The target JAR was quarantined or deleted deliberately.
- The plugin’s data folder was kept, archived, or deleted as a separate decision.
- Dependencies and plugins that rely on the target were checked.
- The server restarted successfully.
logs/latest.logcontains no new missing-dependency or load errors./pluginsor the console’spluginscommand confirms the target is not enabled.- Important commands, permissions, and gameplay features still work.
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.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →
