Quick answer
ShreddedPaper is multithreaded single-server paper/purpur-family implementation. Make one Minecraft server process use multiple threads for server work while preserving a single-server deployment model.
| Developer / maintainer | MultiPaper project contributors |
|---|---|
| Software type | Multithreaded single-server Paper/Purpur-family implementation |
| Upstream / lineage | Purpur/Paper-family code with a different multithreading approach from Folia. |
| Current status | Public beta |
| Best fit | Advanced administrators testing multicore scaling on a single server process and developers interested in multithread-aware Paper-style servers. |
Who develops ShreddedPaper?
MultiPaper project contributors develops or maintains this project. Purpur/Paper-family code with a different multithreading approach from Folia.
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?
Make one Minecraft server process use multiple threads for server work while preserving a single-server deployment model.
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?
Its execution model differs from Vanilla because work is distributed across threads. That creates plugin/thread-safety considerations even though the server remains Paper-family.
“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?
Unlike Folia’s region-scheduler model, ShreddedPaper is its own multithreaded implementation. The project includes dedicated guidance for developing multithread-compatible plugins.
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 ShreddedPaper good for?
Advanced administrators testing multicore scaling on a single server process and developers interested in multithread-aware Paper-style servers.
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
Paper-family APIs are present, but plugins that assume a traditional single thread can be unsafe depending on what they do.
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: ShreddedPaper explores a multithreaded server approach; architecture differences can affect plugin scheduling and thread safety even when it resembles Paper.
Stability and project maturity
The official repository explicitly labels ShreddedPaper “public beta” and says things can occasionally break. It currently has a 26.2 branch, so version freshness is better than MultiPaper’s older 1.20.1 line.
Current version note: Current source tracks 26.2. The project’s own public-beta warning should be treated as part of the deployment decision.
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 ShreddedPaper
Use backups and a staging environment. Do not treat “most features work most of the time” as the same guarantee as a mature Paper production build.
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: Before production, verify the release channel, exact supported Minecraft build and plugin compatibility claims from the upstream project. On staging, test a cross-region teleport and plugin data write under load.
Compatibility boundary: Do not infer production stability from a beta or experimental label; compare the current release notes rather than assuming every Paper plugin works.
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.