"Lag" is a single word people use for three completely different problems, and each has a different fix. Before you change anything, work out which lag you have — otherwise you'll spend an afternoon tuning the server when the real issue was your own graphics card. This guide sorts that out first, then pulls the server-side levers in the order that actually matters.
| At a glance | |
|---|---|
| You need | A Minecraft server, plus its Console, Properties, and Version Changer |
| Plan | Everything works on the free plan; premium is flagged where it genuinely helps |
Step one: which lag is it?
Three different problems wear the same word. TPS ("ticks per second") is the server's heartbeat — a healthy server holds 20.
| Symptom | Type | Fix where |
|---|---|---|
| The whole world slows for everyone at once — mobs freeze, blocks pop back, players rubber-band | Server lag (low TPS) | The panel — the rest of this guide |
| Choppy, stuttery frames on your screen only while friends play fine | Client lag (low FPS) | Your own PC — render distance, graphics, background apps, an optimization mod |
| The game feels delayed just for you, while TPS and FPS are fine | Ping (latency) | Your connection, or a closer region |
Only server lag is worth touching the panel for. The rest of this guide is about that.
The levers, in order of impact
1. View distance and simulation distance
These two are the biggest levers you have, and both are on the Properties page — editable on the free plan.
view-distanceis how many chunks the server sends to players. Higher = more to see, more to transmit.simulation-distanceis how far out the world actually ticks — mobs, crops, redstone, hoppers. This one is heavy, because everything inside it is being simulated every tick.
Drop them and lag usually eases immediately. Try view-distance=7 and simulation-distance=5 on a small server, lower still if it's busy. Save and restart. This one change fixes more Minecraft lag than everything else combined.
💡 Tip: View distance and simulation distance are the biggest levers — this one change fixes more Minecraft lag than everything else combined.
2. Switch to performance-focused software
Some server software is simply built to run lighter. In the Version Changer, Purpur, Pufferfish, and Leaf are optimized members of the Paper family — drop-in compatible with your world and Paper/Spigot plugins, but with more performance options and smarter defaults. Switching to one of these is usually painless and often gives you free frames. See choosing your server software for the full menu.
There's one more software-level knob: the Java flavor, in Settings → Environment. Standard is right for almost everyone, but GraalVM can squeeze extra speed out of a heavy server. (OpenJ9 trades speed for lower memory and some mods dislike it, so test before you rely on it.)
3. Fewer, lighter plugins and mods
Every plugin and mod adds work to each tick. A pile of half-used plugins is a common, invisible tax. Audit what you have on the Plugins or Mods page and remove anything you're not really using. Heavy world-generation, entity, and physics mods are the usual heavy hitters — you don't have to cut them, just know they cost.
4. Pre-generate your world (kept generic)
A lot of lag spikes happen when players explore into brand-new terrain and the server has to generate chunks on the spot. Generating those chunks ahead of time turns that live work into a one-time job, so exploring later is smooth. It's an optional extra step, most useful on servers where people roam far.
5. Understand the RAM reality
🎯 Good to know: You don't need to hand-tune memory flags — Falix's startup already sets the Java heap for you and reserves headroom below your server's limit.
The free plan gives you 2.5 GB of shared RAM, and here's the good news: you don't need to hand-tune memory flags. Falix's startup already sets the Java heap for you and reserves headroom below your server's limit, so the container isn't killed the moment usage spikes. (Editing that startup command is premium-only anyway — but you won't need to.) If your server is being killed for memory, don't just wish for more RAM; read Out of memory to confirm that's really the cause.
6. Stop guessing — profile with spark
When lag persists and you can't see why, don't keep changing things at random. Install spark, a profiler, from the Plugins page (it needs a plugin-capable server like Purpur or Paper). Its commands start with /spark: /spark tps gives a quick health read, and the profiler produces a shareable online report. Read the top of that report — it names the plugin, mod, or task eating the most time. Nine times out of ten it points straight at the real culprit, and you fix that instead of tuning things that were never the problem.
Verify it worked
Watch the server's TPS after each change — via /spark tps, a plugin, or simply whether the world feels smooth with players on. On the Console page, Minecraft servers also show a live player count and resource cards (CPU, RAM), so you can watch load in real time as people join.
The honest limit
Free hosting is genuinely great for vanilla and lightly-modded play with friends. But a big modpack with many players, hundreds of loaded chunks, and heavy simulation asks for more than 2.5 GB of shared RAM can give — and no amount of tuning changes the arithmetic. If you've pulled every lever above and spark keeps pointing at "there's just too much happening," that's not a bug: it's a busy server that needs premium resources. That's a fine place to land.