Why choose Fabric?
Fabric is a lightweight mod loader that stays close to vanilla and ships updates for new Minecraft versions within days, often on release day. That speed is why the performance-mod ecosystem, Sodium and Lithium included, targets Fabric first. If you want the newest version with optimization mods, Fabric is usually ready before Forge.
The loader itself adds little overhead. Fabric API, the shared library most mods depend on, is a small server-side jar you install once. Because Fabric does not rewrite large parts of the game the way heavier loaders do, mod conflicts are easier to reason about and startup is quick. The trade-off is compatibility: Fabric and Forge mods use different formats, so a pack built for one will not load on the other.
Server-side vs client-side mods: what runs where?
This is the question that trips up most Fabric buyers. A mod runs in one of three places: server-only, both sides, or client-only. Content mods that add blocks, items or mobs must be installed on the server and on every player's client at the same version. Optimization and visual mods are usually one-sided.
| Mod type | On the server | On each player's client |
|---|---|---|
| Server-side optimization (Lithium, FerriteCore, Krypton, Starlight-class) | Yes | No, nothing to install |
| Content and gameplay (new blocks, items, mobs, recipes) | Yes | Yes, at the same version |
| Client-only visuals and QoL (Sodium, Iris shaders, minimaps) | No | Optional, the player's choice |
Fabric API and the exact Minecraft version have to match on both sides too. A version mismatch is the most common reason a player gets kicked at the loading screen, and it is a client configuration issue rather than a server fault.
Which performance mods should I run?
Four server-side mods do most of the work on a Fabric server, and none of them change gameplay, so players install nothing. Add them before you add content mods, then measure your tick time. They stack cleanly and are safe on production survival and modded servers alike.
- Lithium rewrites game-logic and tick routines to produce the same behaviour with less CPU per tick.
- Starlight-class lighting replaces the vanilla lighting engine to cut the lag spikes that come with chunk loading and large world edits.
- FerriteCore shrinks the memory footprint of block states and world data, freeing heap on large worlds.
- Krypton optimizes the Minecraft networking stack, easing CPU load when many players are connected at once.
We can preinstall this set on request; ask support for the current version-matched build that fits your Minecraft version.
How does DDoS protection work for a Fabric server?
Every Fabric plan sits behind 3.2 Tbps of always-on L3, L4 and L7 filtering at our Frankfurt edge, with detection under one second and no traffic rerouting. We run deep packet inspection tuned for the Minecraft protocol, so malformed and forged game traffic is dropped upstream before it reaches your server.
There is no add-on to buy and no dashboard to arm; protection is active from the moment the server provisions. For the attack background and the software-side hardening that pairs with edge filtering, read how to protect a Minecraft server from DDoS, or route an existing box through us with remote DDoS protection for Minecraft.
What can I do from the panel?
Every server runs on Pterodactyl. You get a one-click loader and jar version swap, so moving from 1.21.1 to 1.21.4 or switching Fabric builds takes seconds. Snapshot backups restore in a single click before a risky mod update, and SFTP plus a file manager handle bulk config edits.
You also get subusers with granular permissions for co-owners and moderators, a free subdomain to hand out, and a dedicated IPv4 with a custom port (native 25565 is an add-on). Java 1.8 through the latest 1.21 is available from the same dropdown, alongside Fabric, Quilt, Paper, Purpur, Spigot and Forge.
How do I get started in three steps?
Under five minutes from checkout to a running server. Pick a plan, deploy Fabric from the panel, then upload your mods. There is no free trial, but a 14-day money-back guarantee covers you if it is not the right fit.
- Order a plan above and complete checkout; the server provisions automatically.
- In Pterodactyl, choose Fabric and your Minecraft version, then start the server so Fabric API and the loader download.
- Upload your server-side mods over SFTP or the file manager, restart, and share the IP and port with your players.
FAQ
Can I run Fabric mods and Bukkit-style plugins together?
Not directly. Fabric does not load Bukkit or Spigot plugins. To run mods and plugins side by side you install a hybrid bridge that adds a Bukkit-style API on top of Fabric, and support and stability vary by Minecraft version. If you only need plugins, Paper is the better base and switches from the panel.
Can I load a Forge modpack on a Fabric server?
No. Forge and Fabric use different mod formats and are not compatible, so a Forge modpack will not start on a Fabric server. Some packs ship separate Fabric and Forge editions; if yours does, install the Fabric build. Otherwise switch the server type to Forge from the Pterodactyl panel.
How much RAM does a modded Fabric server need?
A light performance-mod setup runs on 4 GB. Mid-size curated packs want 8 to 16 GB, and large kitchen-sink packs with many players need 32 GB. Match memory to pack size and player count; our Minecraft server RAM requirements guide gives a sizing table.
Do all players need the server's mods installed?
Only content mods. Server-side optimization mods such as Lithium and Krypton need nothing on the client. Mods that add blocks, items, mobs or recipes must be installed by every player at the same version, with the same Fabric API and Minecraft version as the server, or clients get kicked at the loading screen.