How to Install Sinytra Connector on Fabric (Step-by-Step)

Most failed installs of Sinytra Connector come down to the same thing: a missing companion jar, or a Java version the loader will not accept. Work through the five steps below in order and the setup takes about ten minutes, including the first launch.

Before you start

Sinytra Connector is not a mod loader. It is a compatibility layer that sits inside Fabric and translates the Forge mod API into calls Fabric understands at runtime. That distinction matters, because it means you are still running a Fabric client — you just gain the ability to load a subset of Forge mods alongside your Fabric ones.

Two things must be true before you continue:

Your Minecraft version is one the project actually targets. 1.20.1 and 1.21.1 are the best-supported lines; older releases such as 1.18.2 are not covered.
You are prepared to run a clean, separate installation. Bolting the bridge onto a 90-mod pack you have been growing for two years is the fastest way to a crash log you cannot read.

Step 1 — Install Java 21

Modern Minecraft builds run on Java 21. The launcher usually bundles a runtime, but if you use a third-party launcher, point it at a fresh JDK 21 install. You can confirm what you have from a terminal with java -version. Anything reporting 17 or below will fail with a class-file version error that looks alarming but means only that the runtime is too old.

Step 2 — Install Fabric Loader

Download the Fabric installer, choose your Minecraft version, and let it create a new profile. Launch that profile once, all the way into the main menu, before you add anything. This creates the folder structure the next step depends on and proves the base install works — which is worth knowing before you introduce more moving parts.

Step 3 — Add the two required jars

This is the step people skip. Sinytra Connector on its own will not load a single Forge mod. It needs a companion:

Sinytra Connector — the bridge itself.
Forgified Fabric API — a rebuilt Fabric API that also exposes the Forge-facing hooks the bridge translates against.

Both go into the same mods folder as regular jars. Crucially, Forgified Fabric API replaces the standard Fabric API. If you leave the ordinary Fabric API jar in place, you get two copies of the same classes and the game refuses to start. Delete the old one.

Diagram of a Fabric mods folder containing Sinytra Connector, Forgified Fabric API and a mix of Fabric and Forge mod jars — A correct mods folder: the bridge, the Forgified API, and your mods — with the standard Fabric API removed.

Step 4 — Drop in a Forge mod

Add one Forge mod first. Pick something well-known and content-oriented rather than something that rewrites rendering or world generation — those are the categories most likely to reach into internals the bridge does not cover. Launch, get to the main menu, load a test world.

Why one at a time? If you add twelve mods and the game crashes, you have twelve suspects and no evidence. Adding them in small batches turns a mystery into a two-minute bisect.

Step 5 — Verify the bridge loaded

Open your logs/latest.log and search for the Connector startup lines. You are looking for confirmation that it discovered your Forge jars and finished remapping them. The in-game mod list is the other check: Forge mods that were successfully bridged appear in the Fabric mod menu, usually grouped under the Connector entry.

If the mod list shows only your Fabric mods, the Forge jars were never picked up — which almost always traces back to Step 3.

Where people go wrong

Three failure modes account for the large majority of support threads. The first is the duplicate Fabric API described above. The second is version drift: a Connector build for one Minecraft version paired with a Forgified Fabric API build for another. Match them. The third is expecting universal coverage — the bridge is a translation layer, not a guarantee, and a mod that hooks deeply into Forge's rendering pipeline may simply refuse to work no matter how clean your install is.

Get a minimal setup running first, then grow it. That single habit prevents most of the pain.

Keep reading

These guides pick up where this one leaves off:

Sinytra Connector 1.21.1: Setup, Supported Mods and Known Limits — The 1.21 line moved to NeoForge naming and shifted several internals. Here is what that changes for your mod list — and what to check before upgrading.
Sinytra Connector 1.20.1: The Most Battle-Tested Version — 1.20.1 has the deepest mod catalogue and the most community mileage. If stability matters more than being current, this is where to build.
Sinytra Connector 1.20.4: What to Expect From a Short-Lived Version — 1.20.4 sat between two long-lived releases and never gathered a full mod catalogue. Here is how that shapes what you can realistically build.