Published: July 30, 2026 · Reading focus: installation
A reliable SkinsRestorer installation starts with platform identification, a complete backup and one matching plugin build. This guide explains the local steps without relying on an installer, external form or hidden script.
Before you install
Confirm that the server is actually running a Bukkit-family platform such as Paper or Spigot. Current SkinsRestorer guidance requires Java 17 or newer, while your Minecraft server may require a newer runtime. Record the server version, Java version and existing plugin list before changing files.
Back up the server
Stop the server fully. Copy the world, the `plugins` directory, configuration files and any SkinsRestorer data from an earlier installation. A file-level backup is the fastest way to return to a known working state if the new package fails to load.
Place the plugin correctly
Use a plugin build that matches your supported server version. Put one SkinsRestorer `.jar` file in the server `plugins` directory. Do not unpack the jar, do not put a Fabric or NeoForge mod in the plugins directory, and remove duplicate older copies before starting.
Useful command examples
Test a known player-name skin.
/skin NotchOpen the skin selection interface.
/skinsCheck SkinsRestorer status when supported by the installed build.
/sr statusRestart and read the console
Start the server normally and watch the startup log. A successful installation creates or loads the plugin configuration without disabling itself. If the log reports an unsupported Java class version, missing dependency or incompatible server mapping, correct that specific issue before changing permissions.
Verify the first command
Join with an administrator account and run a simple named-skin test. Then open the skin menu and confirm that the expected commands are registered. Test with one account before granting access to a full player group.
Set player permissions carefully
Use the parent command permissions and only the actions your players need. Named skins and the GUI can be suitable for regular groups, while URL skins, setting other players and administrative database actions should remain restricted unless your rules require them.
Rollback plan
If the server stops loading or player data behaves unexpectedly, stop it, restore the previous plugin and configuration from backup, then reproduce the issue on a staging copy. Avoid hot reloads because they can leave plugins in a partial state.
Related SkinsRestorer guides
- SkinsRestorer Skin URL and /upload Guide
- SkinsRestorer Commands and Permissions Explained
- How to Set Up SkinsRestorer on Aternos
This guide is an independent resource. It does not replace the documentation shipped with the exact build you install. Return to the SkinsRestorer guide library or review the download safety notice.