Guidefor modders5 min read
Forge version numbers for Minecraft 26.1, 26.2 and 1.21
Forge builds like 65.0.9 carry no hint of the Minecraft version they target. The mapping table for the calendar releases and for the 1.x era.
Why a Forge version number tells you nothing on its own
65.0.9 contains no Minecraft version. Neither does 47.4.10 or 21.1.244. Forge's leading number is a counter that Forge advances as it moves to new Minecraft versions, and the two remaining components track its own releases. Nothing in the string says whether it is for 26.2 or for 1.20.1.
The counter is close to one major per Minecraft version, which tempts people into arithmetic. It does not hold. Minecraft 1.20.3 and 1.20.4 both sit on major 49, at builds 49.0.2 and 49.2.0. Forge also skips Minecraft versions entirely, so the counter jumps: there is no promotion for 1.21.2, and the sequence goes straight from major 52 for 1.21.1 to major 53 for 1.21.3.
This is why the mapping on this site is recorded as declared evidence rather than derived. Forge publishes a file keyed by Minecraft version, so the answer is read from the source rather than inferred from the number. Compare that with how NeoForge encodes the Minecraft version inside its own, where the mapping is a rule.
The promotion channels: latest and recommended
Forge publishes at most two promoted builds per Minecraft version.
| Channel | Meaning | Use it for |
|---|---|---|
recommended | Forge marked this build stable | Servers, modpacks, anything you do not want to babysit |
latest | Newest build published for that version | New Minecraft versions, or when you need a recent fix |
A new Minecraft version starts with latest only. A recommended build appears once the line settles, and some versions never get one. Where both exist, take recommended. Where only latest exists, that is the whole of what Forge offers, and it should be treated as less settled rather than as equivalent.
Mapping table for the 26.x releases
Every calendar version currently carries a latest build and no recommended build. The calendar line is new enough that Forge has not promoted a stable build on any of it yet.
| Minecraft | Forge | Channel available |
|---|---|---|
| 26.2 | 65.0.9 | latest only |
| 26.1.2 | 64.0.14 | latest only |
| 26.1.1 | 63.0.2 | latest only |
| 26.1 | 62.0.9 | latest only |
The counter advanced once per calendar release with no gaps: 62 for 26.1, then 63, 64 and 65. Minecraft 26.2 requires Java 25, and Forge does not change that. The loader runs on whatever the game requires.
Mapping table for the 1.x era
The 1.21 line is where most existing mods still live, and it is the last of the 1.x numbering. 1.21.11 was the final 1.x release before Minecraft moved to calendar versions.
| Minecraft | Forge | Recommended build exists |
|---|---|---|
| 1.21.11 | 61.1.0 | yes |
| 1.21.10 | 60.1.0 | yes |
| 1.21.9 | 59.0.5 | no |
| 1.21.8 | 58.1.0 | yes |
| 1.21.7 | 57.0.3 | no |
| 1.21.6 | 56.0.9 | no |
| 1.21.5 | 55.1.0 | yes |
| 1.21.4 | 54.1.14 | yes |
| 1.21.3 | 53.1.0 | yes |
| 1.21.1 | 52.1.0 | yes |
| 1.21 | 51.0.33 | no |
| 1.20.6 | 50.2.0 | yes |
| 1.20.4 | 49.2.0 | yes |
| 1.20.3 | 49.0.2 | no |
| 1.20.2 | 48.1.0 | yes |
| 1.20.1 | 47.4.10 | yes |
| 1.20 | 46.0.14 | no |
| 1.19.4 | 45.4.0 | yes |
| 1.19.2 | 43.5.0 | yes |
Where the table says a recommended build exists, the number shown is that recommended build. Where it does not, the number is the latest build, which is all Forge published.
Note the gaps. 1.21.2 and 1.20.5 are absent because Forge promoted nothing for them. Note also that 1.20.1 sits at 47.4.10, a fourth digit deep into its own line, because it stayed in wide modpack use long after newer versions shipped. Build depth reflects how long a version was maintained, not how new it is.
Installing the build you picked
Forge ships an installer jar rather than a server jar. The filename carries both versions, in the order Minecraft first, then Forge:
forge-26.2-65.0.9-installer.jar
For a server, run the installer with the server flag in the directory you want the server to live in:
java -jar forge-26.2-65.0.9-installer.jar --installServer
For a client, run the same jar with no arguments and it writes a launcher profile. Download the installer from Forge's own files site, linked from the Forge loader page, and check the size and checksum before running it. Forge's download pages are a long standing target for lookalike sites, and an installer jar is executed code.
Forge compared with NeoForge
Both loaders descend from the same codebase, and both are maintained for current Minecraft versions. The differences that matter when you are choosing a build:
| Forge | NeoForge | |
|---|---|---|
| Minecraft version in the number | No | Yes |
| How the mapping is found | Lookup in the promotions file | Read from the version number |
| Stability signal | recommended channel | Absence of a beta or alpha suffix |
| Calendar era numbering | Counter continued unchanged | Gained a fourth component |
Mods are not portable between them without work. Pick one per instance, and match the loader your mods declare rather than the one you prefer.
Where the mapping comes from
Forge publishes the whole promotions dataset as one small JSON file, keyed by Minecraft version:
curl -s https://files.minecraftforge.net/net/minecraftforge/forge/promotions_slim.json \
| jq '.promos | to_entries | map(select(.key | startswith("26."))) | from_entries'
Keys are <minecraft>-latest and <minecraft>-recommended. Because the Minecraft version is the key, nothing has to be parsed out of the Forge number, which is why this mapping is reliable while reading the number is not.
What could change
Build numbers move constantly, and the recommended column moves with them. The most likely change in the near term is a first recommended build appearing for one of the calendar releases, which would turn a "latest only" row above into a stable answer. A new Minecraft version would add a row and, on past behaviour, advance the counter to 66.
To check, run the curl command above and compare its output against the Forge loader page and the loader section of the Minecraft 26.2 page. If a version you need is missing from the promotions file entirely, Forge does not support it, and NeoForge is worth checking as the alternative.