Learn · frameworks
Quilt vs Fabric: Which Loader Should You Run?
Fabric is the original loader with the biggest mod catalog. Quilt is a fork that runs Fabric mods and adds its own APIs. Here's which to pick.
What is the difference between Quilt and Fabric?
Fabric is the original mod loader maintained by FabricMC. Quilt is a fork of Fabric, started in 2021, that keeps binary compatibility with Fabric mods while layering on its own libraries. Fabric is the foundation; Quilt is a remodel of that foundation with a few extra rooms bolted on.
Both load mods by patching the game with Mixin rather than rewriting Minecraft's code wholesale. That shared lineage is why Quilt can read a Fabric mod folder without conversion. What separates them is ecosystem size, API surface, and which way compatibility points, not how the loaders work mechanically.
What is Fabric?
Fabric is a small, modular loader built by FabricMC. The core is deliberately thin. Most of the useful surface lives in the separately versioned Fabric API, which mods declare as a dependency when they need it.
That split has two consequences worth knowing. Fabric updates to new Minecraft snapshots and releases fast, often within days, because the loader carries little version-specific weight. And it holds by far the largest catalog of performance and utility mods on modern Minecraft, which is why most guides and most clients assume Fabric by default.
If you're setting up from scratch, our Fabric install walkthrough covers the loader and a starter mod set.
What is Quilt?
Quilt forked from Fabric in 2021 after governance disputes inside FabricMC. The project's pitch is "Fabric compatibility plus our own API design." It ships in three pieces:
- The Quilt loader itself, which runs Fabric mods unchanged.
- Quilted Fabric API, a compatibility layer that stands in for the Fabric API so Fabric-targeted mods keep working.
- QSL (Quilt Standard Libraries), Quilt's own set of APIs for mods written specifically against Quilt.
Adoption stays small next to Fabric. The mods that target Quilt exclusively are a short list, and most of what you'd install is a Fabric mod that happens to run fine on Quilt anyway.
Which way does compatibility actually run?
This is the part that decides everything else. Compatibility is one-directional:
- Quilt can load Fabric mods, through the Quilted Fabric API layer.
- Fabric cannot load any mod that depends on Quilt-only QSL features.
So a mod author writing against plain Fabric reaches both audiences at once. A mod author writing against QSL reaches only Quilt users. That asymmetry is why most developers keep targeting Fabric: a Fabric build is a superset of reach, and a Quilt build is a subset.
Quilt vs Fabric at a glance
| Fabric | Quilt | |
|---|---|---|
| Origin | Original loader by FabricMC | 2021 community fork of Fabric |
| Mod ecosystem | Largest on modern Minecraft | Runs Fabric mods plus the smaller QSL pool |
| Own API | Fabric API | Quilted Fabric API (compat) + QSL |
| Loads the other's mods? | No, Quilt-only mods fail | Yes, Fabric mods run unchanged |
| Version support | Fast, often within days | Tracks behind, depends on Fabric upstream |
| Adoption | Very large | Small relative to Fabric |
| Patching model | Mixin | Mixin (inherited from Fabric) |
Which one should you run?
Pick Fabric for the widest catalog
You want the largest mod selection, the quickest support for new Minecraft versions, and the loader that clients and guides assume by default. This covers the vast majority of players.
Pick Quilt for a specific reason
You're running a mod that's Quilt-only, you want a QSL feature, or you back the fork's governance. Your existing Fabric mods come along unchanged, so the cost of trying it is low.
A word on the "performance" question, since it always comes up: neither loader is faster than the other. Quilt inherited Fabric's mixin model, so your frame rate is decided by mods like Sodium and your graphics settings, not by the loader sitting underneath them. If FPS is the goal, the loader choice is a wash, and our performance mod guide is the lever that actually moves the number.
Where does a utility client fit in?
If you run a utility client, the loader question is usually answered for you: it targets Fabric. The reasoning is the same compatibility math developers use. A Fabric build reaches Fabric users and Quilt users; a Quilt build reaches only Quilt users. There's no benefit to cutting your own audience in half.
Terminus is built on Fabric for exactly that reason. You get the broad mod ecosystem, fast version support, and a loader the rest of your modpack already expects, with the client layered cleanly on top instead of fighting it.
FAQ
Yes. Quilt keeps binary compatibility with Fabric and loads Fabric mods through its Quilted Fabric API layer, so an existing Fabric mod folder works without changes. The reverse fails: Fabric cannot run a mod that depends on Quilt-only QSL APIs.
Quilt split off from FabricMC in 2021 after governance disagreements. The goal was a loader that stays compatible with Fabric mods while shipping its own API design through the Quilt Standard Libraries (QSL).
Almost always Fabric. Its user base and version support are larger, and a Fabric build also runs on Quilt for free. Building Quilt-only shrinks the audience with no upside in most cases.
No real difference. Quilt inherits Fabric's mixin patching model, so frame rate and load times come from the mods you install, not the loader underneath them.
Get Terminus
Built on Fabric, ships with the launcher and config cloud.