Quick answer
Cardboard is bukkit/spigot/paper api implementation for fabric. Allow selected Bukkit-style plugins to run inside a Fabric modded server.
| Developer / maintainer | CardboardPowered contributors |
|---|---|
| Software type | Bukkit/Spigot/Paper API implementation for Fabric |
| Upstream / lineage | A Fabric mod that implements Bukkit/Spigot/Paper APIs; it is not a standalone Paper fork. |
| Current status | Hybrid — test carefully |
| Best fit | Fabric servers that have one or more specific Bukkit plugins they cannot replace with Fabric-native mods, and where those plugins have been tested with Cardboard. |
Who develops Cardboard?
CardboardPowered contributors develops or maintains this project. A Fabric mod that implements Bukkit/Spigot/Paper APIs; it is not a standalone Paper fork.
This matters because “Minecraft server software” covers very different kinds of projects. Some are direct forks of Paper, some are mod loaders, some are compatibility layers, some are proxies, and some reimplement the server from scratch. The lineage above tells you what ecosystem, APIs, and operational assumptions carry over.
What is its main goal?
Allow selected Bukkit-style plugins to run inside a Fabric modded server.
A good reason to choose a server implementation is that its design goal matches a real requirement you have. Switching only because a fork is advertised as faster, more configurable, or more modern usually creates extra compatibility work unless you can name the problem it solves for your server.
How is it different from normal Minecraft?
A Fabric+Cardboard server includes both Fabric modifications and a Bukkit compatibility layer, so it is not equivalent to Vanilla or plain Fabric.
“Vanilla compatibility” can mean several things: the same client protocol, similar gameplay, identical redstone/farm behavior, the same world format, or simply the ability for an unmodified client to join. Those are not equivalent. For technical survival, modded worlds, or long-lived production servers, test the exact behavior you depend on.
How does it differ from its upstream or related forks?
Compared with Fabric alone, Cardboard adds plugin API compatibility. Compared with Paper, it is still fundamentally a Fabric server and cannot promise identical internal behavior.
Fork relationships are especially important for plugins and configuration. A downstream fork usually inherits much of its upstream API, but extra patches can change internals, scheduling, defaults, and edge-case mechanics. The closer a plugin is to undocumented internals, the less useful a generic “Paper-compatible” or “Bukkit-compatible” label becomes.
What type of server is Cardboard good for?
Fabric servers that have one or more specific Bukkit plugins they cannot replace with Fabric-native mods, and where those plugins have been tested with Cardboard.
For a new server, start with the simplest software that meets the requirement. More layers—especially hybrid plugin+mod stacks or multithreaded forks—mean more combinations to test when Minecraft, Java, plugins, or mods update.
Plugin, mod, and ecosystem compatibility
Current project table marks Fabric 26.1.2 active, 1.21.11/1.21.1 low activity, and <=1.20 unsupported. Individual Paper plugins can still rely on unimplemented internals.
Always match extensions to the exact Minecraft version and software family they target. A JAR being Java does not make it universally compatible, and a plugin/mod loading successfully does not prove every code path is safe.
Deployment distinction: Cardboard adds Bukkit-like plugin compatibility to Fabric environments. It is not the same deployment or support promise as installing Paper.
Stability and project maturity
Cardboard is actively developed for a current Fabric line, but compatibility layers necessarily lag parts of the upstream APIs. Test plugin behavior instead of assuming the API name guarantees full parity.
Current version note: The official repository’s version chart currently marks Fabric 26.1.2 as Active.
MSH does not assign a numeric stability score. Release status, maintenance activity, official warnings, supported Minecraft versions, architecture, and ecosystem compatibility are more useful than a single rating. A mature project can still be the wrong fit, while a beta project can be useful for a team that deliberately accepts the risk.
Before switching to Cardboard
Do not build a large plugin stack on Cardboard without testing. Prefer Fabric-native mods where equivalent functionality exists.
If the server contains modded blocks/entities, switching away from the loader or mods that created that data can permanently damage a world. If the change involves proxies or threading models, compatibility problems may appear only when players move between servers or when plugins access data concurrently.
Staging acceptance test: Test the exact Fabric, Cardboard and Bukkit-plugin builds together, including commands, inventories, protection events and world saves; a green startup line is not enough.
Compatibility boundary: Avoid assuming plugins using Paper-exclusive APIs or NMS internals are supported; keep a pure Fabric copy for isolating loader/mod failures.
Official references
These primary project sources were checked on September 23, 2026. Software status changes quickly, so the linked project documentation should win over this article if a newer release changes support or requirements.
Related server software
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.