Prism Launcher

Last reviewed Aug 26, 2026 · 891 words

Prism Launcher is a desktop program, not a server, and the catalogue is right to flag that. It belongs here anyway, because anyone who hosts a modded Minecraft server for friends ends up doing half the work on the client side: matching mod loader versions, keeping packs in sync, explaining to six people which Java to use. Prism, a 2022 fork in the MultiMC lineage with about 10,200 stars, turns that into one exported file and one import click. Roughly 256 MB of RAM for the launcher itself; the game underneath is another matter.

Where it sits in a self-hosted Minecraft stack

The server half runs on your hardware. The most common way is the itzg/minecraft-server Docker image, which fetches the loader and, if you point it at a Modrinth pack, the pack too:

services:
  mc:
    image: itzg/minecraft-server
    ports:
      - "25565:25565"
    environment:
      EULA: "TRUE"
      TYPE: FABRIC
      MEMORY: 4G
      MODRINTH_MODPACK: https://modrinth.com/modpack/fabulously-optimized
    volumes:
      - ./data:/data
    restart: unless-stopped

If you host several servers or want a web panel with console, backups and scheduled restarts, Crafty Controller is the friendly one and Pterodactyl is the one that scales to a dozen games. For reaching the server without opening port 25565 to the internet, Tailscale on the host and on each friend's PC is the least painful answer, and it keeps the griefer bots out entirely.

Prism is the client half of that picture. Each player installs it, imports the same pack, points it at the server address, and plays. The games category lists the other pieces if you want a wider setup.

One instance per server, without exception

The core idea Prism inherits from MultiMC is the instance: a self-contained Minecraft install with its own version, mod loader, mods, resource packs, saves and settings. Nothing shared, nothing leaking. The discipline I follow is one instance per server I host, named after the server, so "Friday Fabric" and "Big Forge Pack" cannot contaminate each other. When you update the server's pack, you update that one instance, or better, copy it first and test the new version before you touch the working one. Prism copies instances in a couple of clicks, and a copy of a heavy pack is a few gigabytes, so this is cheap insurance.

Ship the pack as one file

Prism imports modpacks directly from Modrinth, CurseForge, FTB, ATLauncher and Technic through its built-in browser, and it exports any instance as a Modrinth .mrpack. That export is how you distribute your server's exact client setup: build the instance, add the client-side extras the server does not need (a minimap, shaders, performance mods), export, and hand out a file that everyone imports in ten seconds. When the server pack changes, you export again. Modrinth-hosted packs are the smoothest because their whole dependency tree downloads automatically; some CurseForge mods have opted out of third-party downloads, and for those Prism opens a browser tab and asks you to fetch the file by hand, which is tedious but works.

The rule that saves the most support messages: the client's loader must match the server's. A Fabric server will reject a Forge client, and a Fabric client with a mod version mismatch will get kicked on join with an error that means nothing to most people. Keep the loader and the shared mod list identical, and put only client-only mods in the difference.

Java and memory are set per instance, not globally

Prism detects installed Java runtimes and, in recent releases, can fetch a matching one for the Minecraft version an instance needs, which removes the "wrong Java" support call that defined the modded scene for a decade. Memory is also per instance: right-click, Edit, Settings, Java, and set a maximum. My defaults are 2 GB for vanilla-ish packs, 4 GB for medium ones, 6 to 8 GB for the 300-mod monsters, on a machine with at least double that installed. Allocating more than the pack needs makes garbage collection stutter worse, not better.

The one thing it will not do

You need a Microsoft account with Minecraft on it, and each player needs their own. Prism handles multiple accounts and switches between them, but it will not launch without a paid one, and it removed the loophole that the original fork was created over. The other thing it is not: a server. Nothing in Prism hosts a world for other people. It is the tool on the desk, and the tools above are the ones in the rack.

What I'd do

Server in itzg/minecraft-server on a box with 8 GB spare, Crafty in front of it if more than one world, Tailscale for access. On the client side, Prism for every player, one instance per server, and a .mrpack in a shared folder that I re-export each time the server pack moves. Fabric where the pack allows it, because its mods update faster and the server starts in a third of the time. That workflow has kept a group of eight playing for years with the only recurring support question being "did you import the new pack", which is the best a modded server admin can hope for.