Minecraft modpack server requirements: Java, RAM and server files

The server-requirements answer in one minute

A pack name is not enough to install or size a server. Write down the exact release, Minecraft version, loader build and Java version, then use the matching server pack when the creator provides one. Keep clients on that release unless the creator says otherwise.

A manifest can count the files in a pack. It cannot tell you the perfect amount of RAM, CPU or disk. Players, chunk generation, view distance, entities, machines, backups and extra mods all change the load. Start with advice tested on that release, or measure the world you plan to run and leave some breathing room.

Write these down before choosing hardware

Use the matching server pack, not a copied client folder

NeoForge’s server documentation says a published server pack should be installed as a separate instance and moved into the server game folder. A server pack can exclude client-only projects and include startup scripts or server configuration that an ordinary launcher instance does not have.

If no server pack exists, prepare a separate server instance for the exact Minecraft version and loader. Do not delete mods merely because no side is listed, and do not upload a client instance blindly. Check the pack author’s instructions before removing anything, because visual mods, shared libraries and content mods can fail in different ways.

Modpacks.ch takes you to the exact CurseForge or Modrinth file page, not a raw archive or CDN URL. Choose the server files attached to that same pack release; a similarly named file from another release is not interchangeable.

Match Java to the Minecraft and loader generation

Java is a software requirement, not a guess based on pack size. The current NeoForge user guide documents Java 17 for Minecraft 1.20.2 through 1.20.4 and Java 21 for 1.20.5 through its currently documented releases. Older Forge packs and other loader generations can require a different runtime, so verify the selected target rather than copying a command from a newer guide.

Run the server with the intended Java executable and check its reported version before troubleshooting the modpack. Multiple installed Java versions can leave a startup script pointing at the wrong runtime even when the correct one is present elsewhere on the machine.

Size it for the world you will actually run

There is no honest formula like “this much RAM per mod.” Two packs with the same file count can have wildly different world generation, entities, recipes, scripts and machines. The count tells you how big the pack is, not what server to buy.

Start with advice from the pack creator when it names the release, player count and test conditions. Then watch memory, tick time, CPU and disk while generating chunks and doing the things your group will actually do. Leave room for garbage collection, backups and busy moments; an empty server reaching the title screen is not a load test.

Minecraft’s general client system requirements describe client rendering targets; they are not a modpack server sizing table. A server host does not need the client’s graphics target, while CPU latency, memory pressure, disk latency and network conditions can matter more. Keep client and server requirements separate.

• Concurrent players and how far apart they explore.
• View distance, simulation distance and chunk pregeneration.
• World-generation complexity and new-chunk travel.
• Entity counts, farms, machines, storage networks and scheduled scripts.
• Extra projects or configuration changes beyond the published pack.
• World size, backup retention, logs and update rollback space.

A safe self-hosting sequence

1. 01

   Choose the exact pack release and record its Minecraft version and loader build.

2. 02

   Read the creator’s release notes and obtain the server pack for that same release when available.

3. 03

   Install the documented Java runtime and confirm the startup script uses it.

4. 04

   Create a separate server directory; never work inside the only client instance or world copy.

5. 05

   Run the prepared server once, accept the Minecraft EULA only after reading it, and review the first startup log.

6. 06

   Set access, network and backup controls before sharing the address.

7. 07

   Join with an unmodified client on the same pack release and test a disposable world first.

8. 08

   Generate chunks, build a few real machines and play while watching memory, tick time, CPU and disk.

9. 09

   Back up configuration and the world before importing a real save or adding custom projects.

Keep every joining player on the same tested release

A successful server boot does not mean clients can join. The server and each client must agree on Minecraft, loader and network-relevant mod versions. A published server pack may leave out known client-only mods, but joining players still need the full client pack and its overrides.

Distribute the pack name and exact release, not a hand-written list of individual mods. If one player changes a pinned project, their instance is now a custom fork and should be tested separately before the group’s working setup is changed.

Update the server and clients as one change

Back up the world, configuration and previous server directory before changing the pack. Read the release notes, install the new server pack into a separate directory, and test a copied world with matching updated clients. Keep the last working release until the new one has survived startup, connection and some real play.

Do not update only the loader or a convenient subset of mods unless the pack author documents that path. A partial update can alter dependencies, registries, recipes or network protocols while preserving a deceptively similar folder name.

What a host should be able to tell you

A useful host should tell you which pack release it can install, the loader and Java version it runs, how backups and rollbacks work, and whether you can reach the logs and files. “Supports modpacks” and a big player-slot number are not enough.

Ask what happens during updates, failed starts, world imports and custom configuration. You need the same answers whether you self-host or rent a server. Hosting never changes search order here, so the technical answer cannot be bought.