How to fix Minecraft lag spikes.

First: spike, FPS, or ping?

Press F3 and watch. Three different problems get called "lag":

• Low FPS — the whole game is sluggish and the FPS counter is low all the time. That's a rendering/CPU problem.
• High ping — FPS is fine, but hits and blocks register late. That's the network. (See lowering your Minecraft ping.)
• A spike — smooth, then a sudden freeze every few seconds or minutes, then smooth again. That periodic stutter is almost always garbage collection or a background process, not your connection.

1. Allocate the right amount of RAM — not the most

The most common self-inflicted spike comes from giving Minecraft too much RAM. People set 8–16 GB thinking more is better; instead the Java garbage collector now has a huge heap to sweep, and when it does, the game freezes for a beat. For vanilla or light mods, 4–6 GB is the sweet spot. Set it in your launcher's installation settings, not as high as it goes.

2. Fix garbage-collection stutter

If spikes line up with the freeze-every-30-seconds pattern, the JVM's default collector is the culprit. Switching to a tuned set of G1GC flags (the widely used "Aikar's flags") smooths allocation so collection happens in small, unnoticeable steps instead of one stall. Paste them into your launcher's JVM arguments. This single change kills most periodic spikes on modded setups.

3. Rein in render distance and chunk loading

High render distance multiplies the work of every frame and causes a spike each time new chunks stream in. Drop it to 8–12, and if you use performance mods, the ones that help are the rendering/chunk optimizers — not the dozens of cosmetic "optimization" packs that change nothing measurable.

4. Clear background CPU contention

A browser with 40 tabs, a game launcher updating, cloud sync, or an antivirus deep-scan will each yank the CPU away mid-frame and read as a spike. Close them before a session, and trim what starts with Windows so they're not running in the first place — the same startup cleanup that makes Windows faster removes a whole class of spikes here too.

5. Rule out the network

If F3 shows your ping jumping around during the freeze, it's jitter, not GC. Get on a cable, stop other downloads, and measure it. CRY Latency reads your real round-trip, jitter, and packet loss from outside the game, so you can tell a network spike from a system one instead of blaming the wrong thing.

What's snake oil

• Allocating 16 GB "to be safe" — it causes the very spikes you're trying to fix.
• Stacks of cosmetic "optimization" mods that duplicate each other and do nothing.
• "FPS booster" downloads that are really adware. The real boosters are open-source rendering mods.

Measure both sides

Spikes are a system-or-network question, and you fix them faster by knowing which. CRY Optimizer handles the Windows side — startup, background services, frame pacing — reversibly, and CRY Latency handles the network side. Neither touches Minecraft's process or memory, so nothing here puts you near anti-cheat.