Key takeaways
- A recipe viewer shows you what a modded item is for, which vanilla’s recipe book cannot do – it only knows vanilla.
- JEI is the compatibility standard, EMI is the feature-rich newcomer with zero dependencies, and REI sits between them.
- EMI and JEI can run together, with JEI hidden and its recipes shared, which solves the mod-support gap in one step.
Install thirty mods and you will have four hundred new items. Some are crafting intermediates, some are tools, some are ingredients for a machine you have not built yet, and the game will tell you nothing about any of them. Vanilla’s recipe book only knows vanilla recipes.
That is the problem recipe viewers solve, and it is why a recipe viewer is the first mod in almost every modpack. The three that matter are JEI, EMI and REI. Here is how they differ and which to pick.
What a recipe viewer does
The core function is two keystrokes. Hover an item and press one key to see how it is made; press another to see what it is used for. That is it, and it is enough to make a modpack playable.
Everything beyond that is convenience:
- A searchable item list in the inventory sidebar.
- Recipe chains, so you can walk backwards from a goal to the raw materials.
- Cheat modes for creative, giving items directly.
- Integration with mod machines so a furnace-like block from a mod shows its recipes properly.
That last point is the real differentiator between the three. A recipe viewer is only as good as the mods that have written integration for it.
JEI
Just Enough Items has been the default for years and its advantage is entirely about ecosystem. Almost every mod that adds a machine or a custom crafting process ships JEI integration, because JEI is what everyone assumed you would be running.
Strengths: universal mod support, extremely stable, familiar to everyone, lightweight.
Weaknesses: the interface has aged. Search syntax is powerful but unfriendly, the recipe browsing flow requires more clicks than the alternatives, and the feature set has not moved much.
Pick it if your pack is large and old, if mod support is your binding constraint, or if you simply know it already.
EMI
The newer option and the one with the most interesting design. The project describes it as a featureful and accessible item and recipe viewer, and accessibility is a genuine design goal rather than a line in a readme.
Strengths:
- Zero dependencies. Outside the standard Fabric or Quilt API it requires nothing at all. That is unusual and it makes pack assembly simpler.
- Recipe tree browsing. EMI will show you a full crafting tree for a target item, including what you are missing. This is the feature people switch for.
- Better default interface. Fewer clicks to the same information.
- Runtime JEI compatibility. Install JEI alongside EMI and the two share recipes – JEI hides itself and hands its integrations over.
That last point deserves emphasis because it resolves the main objection. You do not have to choose between EMI’s interface and JEI’s mod support. Run both, get both.
Weaknesses: fewer mods write native EMI integration, which is what the JEI compat mode exists to cover. Version support is also the thing to check – EMI’s listed game versions top out lower than JEI’s at the time of writing, so confirm before planning a pack around it.
REI
Roughly Enough Items sits between the two. It arrived as the Fabric answer when JEI was Forge-only, and it built a real ecosystem in that window.
Strengths: strong Fabric mod support, a cleaner interface than JEI, and a mature feature set.
Weaknesses: it depends on Cloth Config and Architectury, which is two more libraries in your pack. Our notes on that library chain cover why those keep appearing.
Pick it if your pack already depends on Architectury for other reasons, or if a mod you need ships REI integration specifically.
How to choose
A short decision path.
Building a new pack on a current version? EMI, with JEI alongside for compatibility. Best interface, widest coverage, and the two-mod install costs almost nothing.
Running an existing large pack? Whatever it shipped with. Swapping recipe viewers in a pack that has integration written for one of them is a way to lose information for no gain.
Playing a lighter setup where you just need recipes? JEI alone. It is the smallest, the most stable, and the extra features of the others only matter when the pack is complex.
Already deep in the Architectury ecosystem? REI, since the libraries are already there.
Our stable modded setup guide covers the broader question of pinning a version and sticking to it, which matters more than this choice does.
What none of them fix
Worth saying. A recipe viewer tells you how to make something. It does not tell you why you would want it, what progression gate it sits behind, or what order to do things in. That is what a quest book or a guide mod is for, and a large pack without one is still confusing with a perfect recipe viewer installed.
They also do not help with vanilla mechanics. Our anvil cost guide and brewing guide cover two systems where knowing the recipe is the easy part.
Our read
The EMI plus JEI combination is the answer most packs should land on, and the fact that it works at all is the interesting part. Two mods that solve the same problem, where the newer one detects the older one and absorbs its data rather than conflicting with it – that is a deliberate piece of cooperation in an ecosystem where the normal outcome is an incompatibility report.
It also quietly ends the argument. For years the EMI-versus-JEI discussion was interface quality against mod support, and the answer turned out to be that you do not have to pick. Our mod installation guide covers getting both in place, and it is two jars in a folder.
Images: Vanilla Experience+ project gallery.