What Forgified Fabric API works with.
| Platform | Java Edition |
|---|---|
| Loaders | Forge, NeoForge |
| Minecraft versions | 1.20.1, 1.21, 1.21.1, 26.1, 26.1.1, 26.1.2 |
| Environment | Client, Server |
Forgified Fabric API (FFAPI) ports Fabric API's public hooks onto Forge and NeoForge, so a mod built against those hooks can run without a separate Forge or NeoForge rewrite. It is required on both the client and the server whenever an installed mod depends on it. Forge support is frozen at Minecraft 1.20.1, while the NeoForge branch keeps tracking current game versions.
Why Forge and NeoForge mods need Forgified Fabric API
Most Fabric mods are written against Fabric API, the shared library that exposes hooks for particles, biomes, dimensions, and rendering. Forgified Fabric API reimplements those same public hooks on top of Forge and NeoForge's own systems, so a mod that only declares a Fabric API dependency can load without its own Forge or NeoForge build. It is a port, not a universal translator: loader-specific code inside a mod still needs its own handling, and the project only guarantees full compatibility for the public net.fabricmc api packages, not the internal implementation classes some mods reach into anyway.
Forge stops at 1.20.1, NeoForge stays current
Forge and NeoForge split into separate projects after Minecraft 1.20.1, and Forgified Fabric API's release history follows that split exactly. The newest Forge build, 0.92.6+1.11.15+1.20.1 released August 13, 2026, still targets 1.20.1 only. The NeoForge branch has kept shipping through 26.1, 26.1.1, and 26.1.2, most recently on August 23, 2026. A Forge instance cannot move past 1.20.1 and keep this library; NeoForge is the only path forward for anything newer.
- Loaders: Forge and NeoForge. Fabric Loader uses Fabric API instead, not this port.
- Side: required on both client and server.
- Forge ceiling: Minecraft 1.20.1.
- NeoForge ceiling: Minecraft 26.1.2.
- License: Apache License 2.0.
Why it stops working with some mods
Reports of Forgified Fabric API not working almost always trace back to one of two causes. The first is a version mismatch: a build made for one Forge or NeoForge release does not reliably work on a different one, so the installed build has to match the loader and Minecraft version exactly, the same way regular Fabric API does. The second is a mod reaching into Fabric's internal, non-public classes rather than the documented packages Forgified Fabric API guarantees to support. Those internal hooks can change without warning, and they have produced a steady stream of mod-specific crash reports on the project's issue tracker, most fixed per mod rather than by one blanket patch.
Installing Forgified Fabric API
Download the build that matches your loader and Minecraft version, then place the jar in the mods folder the same way any other mod installs. A dedicated server needs the same build as its connecting clients, since Forgified Fabric API runs on both sides. Setting up Forge or NeoForge for the first time is covered in the Forge and NeoForge install guide.
Running Fabric and Forge mods together with Forgified Fabric API
Questions about Forgified Fabric API.
5 questions
What does Forgified Fabric API do?
It ports Fabric API's public hooks, covering particles, biomes, dimensions, and rendering, onto Forge and NeoForge. Mods built against Fabric API can then run on those loaders without a separate Forge or NeoForge build, as long as the mod relies on documented public packages rather than Fabric's internal implementation code.
Does Forgified Fabric API work with Forge?
Yes, but only through Minecraft 1.20.1. Forge and NeoForge diverged as projects after that version, and Forgified Fabric API's Forge branch stopped receiving new game-version ports there. Anything built for a newer Minecraft version needs NeoForge instead of Forge.
Why isn't Forgified Fabric API working with my mods?
Check that the installed build matches your loader, Forge or NeoForge, and exact Minecraft version first, since a mismatch is the most common cause. If versions line up and one specific mod still crashes, that mod is likely calling one of Fabric's internal, non-public classes rather than the documented API, which Forgified Fabric API does not guarantee to support.
Do I still need regular Fabric API?
Only if you are also running Fabric Loader itself. Fabric API and Forgified Fabric API are separate downloads for separate loaders, so a Forge or NeoForge instance needs only the Forgified build, never both at once.
Is Forgified Fabric API safe to use?
It is released under the Apache License 2.0 and distributed by the Sinytra project through Modrinth, CurseForge, and GitHub Releases. As with any mod, install it from one of those pages rather than a third-party rehost.
