The Best Minecraft Mods

Two categories dominate the top of any download ranking, and they are worth separating in your head before you scan the table.

The first is libraries. Fabric API is the most-downloaded mod in existence by an enormous margin, but nobody installs it because they want it — they install it because thirty other mods require it. The same goes for Cloth Config and Architectury. These are infrastructure.

The second is performance mods. Sodium, Lithium and Entity Culling sit near the top because they solve a problem almost every player has: Minecraft's rendering is inefficient, and these fix it. On a mid-range machine, Sodium alone routinely doubles frame rates.

Live from Modrinth, sorted by all-time downloads. Loader support is listed because it is the thing you need to check before downloading anything.

For a first modded setup on a current version, this short list gets you most of the benefit with almost none of the risk. All five are Fabric mods, all are actively maintained, and none of them change gameplay — so nothing here can corrupt a world or surprise you later.

Install them together, launch once, and you will have a noticeably faster and more pleasant game before you touch any content mods at all.

For years OptiFine was the default answer to every performance question. It bundled rendering optimisations, shader support, dynamic lighting and zoom into one download, and it worked.

Its problem now is architectural. OptiFine patches the game in ways that conflict with Fabric and, increasingly, with other mods. It is closed-source, updates slowly after new Minecraft releases, and it does not appear on Modrinth at all.

The modern replacement is a stack rather than a single mod: Sodium for rendering, Iris for shaders, and small mods for whatever specific OptiFine features you actually used. The result is faster and considerably more compatible, at the cost of installing three things instead of one.

Download count tells you a mod is popular; it does not tell you it is maintained. Before installing anything, check when it was last updated. A mod whose newest file is two years old will not run on a current version no matter how many downloads it has.

Check the licence too, which Modrinth displays on every project page. Most mods are open-source under permissive licences, but some are all-rights-reserved, which matters if you ever plan to include them in a pack you distribute.

Finally, read the dependency list. A mod that quietly needs three libraries is not harder to install, but it is harder to debug when one of them is missing.

Browsing thirty thousand mods without a filter is how people end up installing nothing. It helps to know that mods sort into a handful of recognisable jobs, and that a good setup usually takes one or two from each rather than fifteen from one.

Performance mods change nothing you can see and everything you can feel. Worldgen mods alter what the map looks like when you walk into unexplored chunks. Tech mods add machines, automation and power systems. Magic mods add rituals and progression built on their own internal logic. Quality-of-life mods fix small annoyances — an inventory sorter, a better recipe viewer, a minimap.

Storage and automation mods deserve a special mention because they change how you play more than almost anything else. Once you have a searchable networked storage system, going back to walls of chests is genuinely difficult.

Certain mods are not really mods so much as shared plumbing, and you will accumulate them whether or not you choose to. It saves confusion to recognise them by name.

Fabric API is required by the large majority of Fabric mods and is the single most-downloaded item on Modrinth for exactly that reason. Cloth Config provides the settings screens that many mods use, so mods with an options menu often need it. Architectury lets an author write one mod and ship it for several loaders. Mod Menu is the mod that gives Fabric an in-game mod list at all — without it you have no interface to any mod's settings.

None of these do anything visible on their own. If you install one out of curiosity and see no change, that is correct behaviour rather than a failed install.

Every project page carries four pieces of information that decide whether a mod will work for you, and they are easy to skim past.

The version and loader chips at the top of the files list are the filters that matter most. Set both before looking at any file, and the list will only show downloads that can actually run in your setup.

The dependencies panel lists what else you need. Required entries are non-negotiable; optional ones add features if present.

The licence is displayed on the right of the project page. Most mods use permissive open-source licences, which matters if you ever distribute a pack containing them.

And the last-updated date tells you whether the mod is alive. Anything untouched for two years will not support a current Minecraft version, however good it once was.

Once a mods folder has thirty files in it, remembering what each one does becomes genuinely hard, and half of them will have filenames that tell you nothing useful.

Mod Menu solves this in-game on Fabric, listing every loaded mod with its version, its description and a link to its settings. On NeoForge the equivalent list is built into the main menu already.

Outside the game, the fastest audit is to list the folder and read the filenames, most of which encode the mod name, the Minecraft version and the loader. A file that does not follow that convention is worth opening on its project page to confirm what it is.

If you find something you cannot identify, do not simply delete it — it may be a dependency that another mod needs. Move it out of the folder, launch, and see whether anything complains.