How do I update a plugin without losing its config? — Minecraft

Q: Will my settings reset when I update?

No — as long as you replace only the .jar and leave the config folder in place, your settings are preserved. Most plugins migrate their config forward on first launch.

Updating a plugin is usually as simple as swapping one file. Because a plugin's settings live separately from its .jar, you can drop in the new version and keep all your configuration exactly as it was.

How plugin files are organised

Each plugin's configuration lives in its own folder at plugins/<PluginName>/, completely separate from the plugin's .jar in the plugins folder. That separation is what lets you update the code without touching your settings.

Step-by-step

Stop the server from the Console and wait for Offline.
In the Files tab, open the plugins folder and replace only the plugin's .jar with the new version — leave its plugins/<PluginName>/ config folder alone.
Start the server and check the Console; the plugin migrates its config automatically if the new version needs to.

Tip: Back up the config folder first — select plugins/<PluginName>/, Archive it to a .zip, and download it. That way you're covered if the new version changes the config format.

Frequently asked questions

Will my settings reset when I update? No — as long as you replace only the .jar and leave the config folder in place, your settings are preserved. Most plugins migrate their config forward on first launch.

The new version changed the config format — what happens? Well-made plugins update the file automatically and note it in the Console. If something looks off, restore your backup copy and check the plugin's changelog for config changes.

Do I need to update dependencies too? Sometimes. If the Console warns about an outdated dependency after the update, grab the matching version of that plugin as well.