Architectury API — the Library That Makes Cross-Loader Mods Possible
Fabric · Forge · NeoForge · Quilt · 351M downloads

Architectury API: one codebase, four loaders

Architectury API is the layer that lets a single mod codebase compile for Fabric, Forge, NeoForge, and Quilt. If a mod supports more than one loader, the odds are good it depends on Architectury — it is arguably the most important single library in the modern modding ecosystem after the loaders themselves. It adds no content, no HUD, and no config screen. Its only visible effect is that other mods load when they otherwise would not.

Fabric / Forge / NeoForge / Quilt Minecraft 1.21.4 Library / API Verified source

Quick facts

CategoryLibrary / API
LoadersFabric, Forge, NeoForge, Quilt
Minecraft1.21.4 and older supported versions
SourceCurseForge
Downloads351.0M (CurseForge, Nov 2026)
SideClient and server (depends on dependent mod)

Source status

Verified

The download below is the file listed in our catalogue. Metadata last checked November 2026.

View on CurseForge →

Opens CurseForge in a new tab. CurseForge's terms apply.

Minecraft Mod

One codebase, four loaders

Architectury API loaded in a mod list alongside several cross-loader mods that depend on it, with no separate content visible in-game
Architectury API in a Fabric mod list, sitting between the loader and the mods that depend on it. The library has no content of its own — it exists so the mods around it can share one codebase across Fabric, Forge, NeoForge, and Quilt.
External link

Get Architectury API

One JAR file per loader. Drop into mods for Fabric, Forge, NeoForge, or Quilt — steps below.

Visit Architectury API

File: architectury-api.zip · External — creator's site · No redirects, no ads

What Architectury API actually does

Minecraft has two major mod loaders — Fabric and Forge — plus NeoForge, a newer fork of Forge, and Quilt, a newer fork of Fabric. A mod that wants to support more than one of them normally has to maintain separate codebases. Architectury API solves that by providing a shared abstraction layer that all four loaders understand. The mod writes to Architectury; Architectury writes to the loader.

For players, the effect is simple: one mod download works on whichever loader you happen to be running. For mod developers, the effect is structural — the mod is written once instead of three or four times, and the loader-specific code lives in Architectury instead of being duplicated in every mod. You will never see Architectury in your inventory, your creative menu, or your config screens. It is infrastructure, and it is invisible by design.

The scale is hard to overstate. Hundreds of mods across the community use Architectury as their cross-loader layer. It is arguably the most important single library in the modern modding ecosystem after the loaders themselves — and it is the reason so many mods can ship for both Fabric and Forge on the same day.

What it provides to dependent mods

Architectury is not a single feature — it is a set of abstractions, each of which replaces a piece of loader-specific code that would otherwise have to be written twice:

  • Event system. Mods register events through Architectury, and the library routes them to the right loader's event bus. The mod's event code is identical on Fabric and Forge.
  • Registry abstraction. Blocks, items, entities, and other game objects are registered through a unified interface. The loader-specific registration is handled by Architectury, not by the mod.
  • Networking layer. Packet handling that works on every supported loader without loader-specific code — the mod sends and receives packets through one API.
  • Quilt support. Architectury runs on Quilt as well as Fabric, Forge, and NeoForge — the broadest loader coverage of any abstraction layer in the ecosystem.

What the library changes (and doesn't)

1
One codebase, four loadersFabric, Forge, NeoForge, and Quilt all understand Architectury, so the mod ships once.
2
No content of its ownNo blocks, no items, no HUD. Architectury is infrastructure that other mods depend on.
3
Negligible overheadThe abstraction cost is small — its purpose is to eliminate duplicated loader-specific code, not to add features.
4
Dependency, not a feature modInstall it because a mod told you to. Remove the dependent mod, and Architectury can go too.

How to install it (loader and version must both match)

Architectury is a standard mod JAR, but there are two matching problems that catch people out — the loader and the Minecraft version. Both must match the dependent mod exactly, or the game will crash on startup.

  1. Download the JAR matching your loader — Fabric, Forge, NeoForge, or Quilt. The JARs are not interchangeable. A Forge JAR dropped into a Fabric profile will not work.
  2. Download the JAR matching your Minecraft version. Architectury ships separate builds per MC version. Loading the wrong one will crash on startup, usually with a message about a missing method or an incompatible class version.
  3. Drop the JAR into .minecraft/mods (or your launcher's mods folder for the profile you are using).
  4. Launch the game. If a dependent mod was failing before, it should load normally now. If it still says Architectury is missing, re-check the loader match — that is the most common cause.
Dependency, not a feature mod. Architectury adds nothing visible to the game. If you are installing it because a mod told you to, that is the only reason you need it. Remove the dependent mod, and Architectury can be removed too.

Compatibility at a glance

Every value below comes from the creator's official source page. Where the creator doesn't state a field, we mark it "Unknown" rather than guess.

FieldValue
CategoryLibrary / API
LoadersFabric, Forge, NeoForge, Quilt
Minecraft versions1.21.4 and older supported versions
SideClient and server (depends on dependent mod)
SourceCurseForge
Downloads351.0M (CurseForge, Nov 2026)
Last verifiedNovember 2026

Frequently asked questions

Is Architectury API required for every mod?
No. Only mods that explicitly list Architectury as a dependency need it. Many single-loader mods don't use it at all.
What's the difference between Architectury and Balm?
Architectury is a broad framework used by dozens of authors across the community. Balm is a smaller, more focused layer used primarily by one author's mods. They solve the same problem at different scopes.
Which loaders does Architectury support?
Architectury supports Fabric, Forge, NeoForge, and Quilt. The exact loader availability depends on the Minecraft version you are running.
Do I need Architectury on the server?
It depends on the mod that requires it. Most mods that use Architectury need it on both client and server, because the abstraction layer handles networking and registry sync.
Will Architectury slow down my game?
No. Architectury adds no gameplay content. The overhead is negligible — its job is to let mods avoid duplicating loader-specific code.

Why this listing exists

Most resource sites either dump hundreds of unverified links with no context, or hide downloads behind fake countdown timers and redirect chains. This page follows a different approach: it shows the resource's real metadata, links to the creator's original page, and states clearly what we have and have not verified.

If you find a broken link, an incorrect version, or a download that goes somewhere unexpected, report it using the contact form. If you are the creator and want this listing removed or changed, see Copyright / DMCA.

Related mods

Report a problem with this page: contact form. If you are the creator and want this listing changed, see Copyright / DMCA.