Core capability
Restore and update skins from the server
Apply account-name skins, refresh an existing choice, offer a visual skin menu, keep favourites and control who can use URL or administrative actions.
Independent Minecraft server resource
Restore player skins with clear server-side control.
SkinsRestorer helps supported Minecraft servers apply named skins, approved skin URLs, custom choices and consistent player appearance. Use this guide to download the supplied package, choose the right platform and configure it safely.
Java 17+ guidancePaper & proxy setupNo account form
/skin & /skinsPlatform-aware setup
What is SkinsRestorer?
A practical identity layer for Minecraft servers.
SkinsRestorer is a server-side plugin and mod project that restores or changes player skins on supported Minecraft server platforms. It is widely used where the default skin pipeline is unavailable or where administrators want controlled skin commands, a selection GUI, URL-based skins and reusable custom choices.
The software focuses on appearance, not authentication. On offline-mode servers, administrators still need suitable login protection and sensible permissions. A correct setup also depends on the server platform, Java runtime, network design and access to required upstream services.
2 modesPlugin and mod platforms
1 commandSimple player skin changes
CentralProxy-aware management
Feature showcase
Player-friendly choices with administrator control.
The App Showcase layout pairs a large product panel with compact feature callouts, keeping the most important capabilities visible without turning the page into a documentation wall.
01
Named skins
Use a player name to select a familiar Minecraft skin.
02
Skin URL
Apply a valid public PNG with classic or slim arm variants.
03
GUI access
Let permitted players browse choices through the `/skins` interface.
04
Network storage
Plan centralized data for proxy networks and larger installations.
How it works
From command to visible skin in four controlled steps.
SkinsRestorer receives a permitted request, resolves or retrieves skin data, stores or reuses the result, and asks the supported server platform to apply it to the player.
Download Now1
Player or admin request
A permitted command selects a player-name skin, URL, custom entry or management action.
2
Validation and resolution
The plugin checks permissions, input format, restrictions and the required skin source.
3
Cache or storage
Resolved data can be reused through local storage or a configured network database.
4
Platform application
The server or proxy integration applies the skin and updates the visible player state.
Compatibility
Choose the build for the platform you actually run.
Do not treat every package as interchangeable. Plugin builds belong in plugin folders; supported mod builds belong in mod folders.
Paper, Spigot & Bukkit
Use the Bukkit-family plugin package and verify the server's Java requirement before startup.
Velocity & BungeeCord
Use documented proxy mode, correct player forwarding and consistent network configuration.
Fabric & NeoForge
Current mod releases target supported modern versions; match loader and Minecraft versions carefully.
Use cases
Where SkinsRestorer adds the most value.
These common scenarios focus on practical server administration rather than decorative extras.
Offline-mode communities
Restore player appearance while keeping authentication and permissions as separate security responsibilities.
Role-play servers
Offer approved custom identities for characters, events and story-based server experiences.
Proxy networks
Keep skin data and commands consistent when players move between connected backend servers.
Creator sessions
Switch controlled appearances quickly for recordings, demonstrations or staged multiplayer scenes.
Default skin replacement
Reduce repeated Steve or Alex appearances by applying configured server defaults where appropriate.
Player self-service
Allow safe named-skin or GUI choices without exposing broad administrative permissions.
Installation & setup
Use a backup-first installation path.
A clean setup is more reliable than adding multiple builds, hot-reloading or changing unrelated settings at once.
A
Identify server software
Confirm Paper, Spigot, Velocity, BungeeCord, Fabric or NeoForge plus the exact Minecraft version.
B
Confirm Java
Use Java 17 or newer, while also meeting the Minecraft server's own runtime requirement.
C
Back up and install
Stop the server, back up configuration and data, then place one matching package in the correct folder.
D
Restart and verify
Perform a full restart, check console output and test one basic command before assigning wider access.
Fast verification checklist
- ✓The server completes startup without disabling the plugin.
- ✓A basic `/skin <name>` test changes the permitted player's skin.
- ✓The `/skins` interface opens only for groups that should use it.
- ✓Proxy players keep the skin when moving between backend servers.
Main downloadDownload SkinsRestorer
Download the supplied SkinsRestorer package.
This button uses the project URL supplied for this build request. It downloads an archive of the `dev` branch, not a guaranteed stable production release.
✓Back up your server before replacing any existing installation.
✓Review the archive and choose the platform-appropriate built package or build process.
✓Test on a staging server before deploying to an active network.
Safety notice
Development packages need controlled testing.
The supplied archive follows a development branch. It can change without a versioned release boundary. Keep a rollback copy and never replace a working production installation without testing.
01Back up plugin or mod files, configuration, skin data and database records.
02Use one matching build; remove duplicate or obsolete copies before restart.
03Restrict URL and admin commands to trusted roles with least privilege.
04On offline-mode servers, add separate authentication protection against name spoofing.
Balanced review
Pros and cons before deployment.
SkinsRestorer can solve a visible player-experience problem, but the surrounding server design still matters.
Pros
- +Restores skins on supported online and offline configurations.
- +Offers player-name, URL, GUI and custom skin workflows.
- +Supports plugin, proxy and selected mod environments.
- +Caching and database options suit growing networks.
Cons
- −Incorrect proxy or permission setup can make commands appear broken.
- −New lookups can depend on reachable external skin services.
- −Development branch archives require extra review and testing.
- −It does not replace authentication for offline-mode servers.
Release information
Download NowMatch stability level to your server risk.
The configured download points to the `dev` branch archive. A live production server should use a tested build with documented compatibility, a rollback plan and a successful staging run.
Troubleshooting
Check evidence before changing configuration.
Start with console output and a minimal test. Random changes often hide the original cause.
Check build and Java
Confirm the file matches the platform, the server sees it in the correct folder, and Java meets requirements.
Check parent permissions
Grant the required parent permission and the specific child action rather than broad admin access.
Check network access
Review firewall, required domains, URL validity, service limits and console messages.
Check forwarding
Verify proxy mode, player information forwarding and consistent configuration across the network.
Set the variant
Specify classic or slim with URL-based skins when automatic detection gives the wrong result.
Refresh carefully
Use the update workflow, review cache behaviour and avoid deleting data without a backup.
Guides preview
Focused help for installation, commands and fixes.
Each guide is a separate static page with its own SEO metadata, feature image, internal links and related reading.
Install on Paper or Spigot
Read Guide
Use Skin URL and /upload
Read Guide
Fix skins not applying
Read GuideFrequently asked questions
SkinsRestorer answers for players and server owners.
Exactly 20 questions are divided into two practical categories. Only one answer remains open at a time.
SkinsRestorer is a server-side Minecraft plugin or mod that lets supported servers restore and change player skins. It is especially useful where normal skin delivery is unavailable, including many offline-mode setups. Players can select account skins, use approved URLs, open a skin GUI, and keep a consistent appearance when the server is configured correctly.
Yes. Restoring skins on offline-mode servers is one of the project's main use cases. Server owners should still secure offline-mode access with appropriate authentication controls because usernames can otherwise be impersonated. SkinsRestorer handles appearance; it is not an account-authentication replacement.
Current official documentation lists Bukkit-family servers such as Spigot and Paper, proxy platforms including BungeeCord and Velocity, and current mod builds for Fabric and NeoForge. Platform and Minecraft-version support can change between builds, so match the package to the exact server software and version you operate.
It can be either, depending on your platform. Bukkit, Spigot and Paper installations use the plugin package in the plugins directory. Fabric and NeoForge servers use a compatible mod package in the mods directory. Do not place a plugin build into a mods folder or a mod build into a plugins folder.
Current installation guidance requires Java 17 or newer. Your Minecraft server version may require an even newer Java release, so verify both requirements before starting. A server that stops during startup with class-version or runtime messages often has a Java mismatch rather than a SkinsRestorer configuration problem.
SkinsRestorer is designed to apply supported skin changes immediately, so a normal change should not require a full server rejoin. Some client, proxy or plugin combinations can delay the visible refresh. When that happens, verify the server log, proxy forwarding and installed build before assuming the command failed.
The `/skins` command opens the available skins interface when the command and permission are enabled. It gives players a visual way to browse or select skins instead of typing every name manually. Server owners can restrict access through the relevant permission nodes and configuration.
Yes. A permitted player can use `/skin url` with a publicly reachable PNG URL. The URL should be quoted, point directly to a valid image, and meet accepted Minecraft skin dimensions. Administrators can restrict allowed domains and grant the URL command only to trusted groups.
The upload workflow converts a local Minecraft skin PNG into a copyable `/skin url` command through the project's upload service. The file should be a genuine PNG, normally 64×64 or legacy 64×32. Keep the generated URL in quotation marks when pasting the command into the game or console.
Yes. URL-based skin commands can use classic or slim variants. Classic is the standard Steve-style arm model, while slim uses the Alex-style narrower arms. When no variant is supplied, the system may attempt detection, but specifying the intended model helps avoid incorrect arm rendering.
Stop the server, confirm the required Java version, place the correct SkinsRestorer plugin file in the `plugins` folder, and restart the server. Watch the console for a successful load message. Then test a basic command such as `/skin <name>` and confirm permissions before opening access to regular players.
Select a plugin-capable server software such as Paper, use the Aternos plugin library to install SkinsRestorer, and restart the server. You do not manually run the plugin file. After startup, test the command and review the Aternos log if the plugin is missing or disabled.
For BungeeCord or Velocity networks, use the documented proxy installation rather than treating every backend as a separate standalone server. The proxy centralizes commands, configuration and skin data. Backend communication and player information forwarding must be correct, and shared storage may be appropriate for larger networks.
Common causes include a blocked required domain, missing permissions, an incompatible build, incorrect proxy forwarding, an invalid URL, or a server startup error. Check the console first, run the status command when available, confirm Java and platform versions, and test with a simple known player-name skin before changing many settings.
The link may not point directly to a public PNG, the image may use the wrong dimensions or format, or URL restrictions may reject its host. Wrap the full URL in quotation marks, verify it opens without authentication, and use a genuine 64×64 or 64×32 PNG rather than a renamed JPG.
Use least privilege. A basic player group may receive the parent player or command permission plus only the specific actions you want, such as setting a named skin or opening the GUI. Keep URL, other-player and administrative controls restricted unless your server rules require them.
Yes. MySQL storage is useful when multiple servers or a proxy network need consistent skin data. Configure the same reachable database details where the documented network setup requires them, use a dedicated database account, protect credentials, and back up the database before migrations or major upgrades.
Cached skin data can help previously resolved skins continue working during temporary upstream outages. New lookups or uncached changes may still depend on external services. Server owners should treat caching as resilience, not a guarantee that every new request will succeed while required services are unreachable.
The configured button on this website downloads an archive of the project's `dev` branch because that is the supplied package URL. Development branch files can change and may not be appropriate for production. Back up your server, review the archive, and prefer a tested stable build for critical environments.
No. This is an independent informational and download-guide website. Minecraft, Mojang, Microsoft, SkinsRestorer and related marks belong to their respective owners. The site does not claim project ownership, does not provide account authentication, and does not collect skin files through a contact form.