Fabric compatibility is a loader question first. At the September 2026 reference point used for this site, the public Tinkers' Construct listing identifies Forge and NeoForge as supported platforms. A Tinkers jar built for those loaders does not become Fabric-compatible simply because the Minecraft version matches; use only a build that explicitly targets the loader in your profile.
Loader APIs are not interchangeable
Forge-style, NeoForge-style, and Fabric-style environments expose different loader APIs and expectations. A jar compiled for one cannot be assumed to initialize correctly on another.
Match the full stack
Compare four items together: Minecraft version, loader, Tinkers build, and dependencies. If any one belongs to a different stack, stop before launching an important world.
Avoid unofficial file-name guesswork
Do not rename jars or rely on a download label that omits the loader. Use release notes or package metadata from the source you trust to establish compatibility.
When an alternative is more practical
If the mod you want is not available for your chosen loader, it can be safer to select a loader-compatible tool-customization mod than to force an incompatible file into the profile.
Test alternatives in a separate profile
Create a clean test instance with a copied world or temporary save. This keeps experimentation separate from your primary modpack and makes conflicts easier to diagnose.