8 Top Minecraft Anti-Lag Plugins for Better TPS

A server that holds 20 TPS when nobody is moving proves almost nothing. The real test starts when 30 players fly in different directions, farms begin running, redstone clocks fire, and someone opens a shulker full of items. The best anti-lag plugins for Minecraft do not magically add CPU power. They help you find, limit, or prevent the specific workload pulling your tick time down.

For most Paper and Purpur servers, the right answer is a small, purposeful plugin stack plus sensible server settings. Installing every "lag remover" you can find often creates new problems: broken farms, deleted items, false bans, and gameplay that feels hostile. Start with the source of the lag, then choose the tool that addresses it.

What anti-lag plugins can actually fix

Minecraft lag is not one thing. A low TPS reading may come from entity-heavy farms, excessive chunk generation, mob AI, a bad plugin task, enormous hopper networks, or a world save stalling on slow storage. Plugins can control entities, pre-generate terrain, adapt view distance, and expose expensive tasks. They cannot make an underpowered CPU handle an overloaded public server forever.

Before installing anything, use timings or a profiler during a busy period. Check MSPT as well as TPS. TPS can still look fine while tick time climbs close to 50 ms, leaving no headroom for a player spike. Once a tick regularly exceeds 50 ms, the server falls below 20 TPS.

The anti-lag plugins worth considering

The plugins below solve different problems. You probably do not need all of them, and compatibility should always be checked against your Minecraft version and server software before deployment.

1. spark: find the real culprit first

spark is the first plugin to install when you do not know why performance is dropping. It profiles CPU activity, tick time, plugin tasks, entities, and chunks so you can stop guessing. A report can reveal that the issue is not "too many players," but one scoreboard plugin running an expensive task every tick or a single area loaded with thousands of villagers.

spark is diagnostic, not a direct TPS booster. That is precisely why it earns the top spot. Removing the wrong thing is worse than having no lag plugin at all. Run a profile while the issue is happening, inspect the hot spots, and make one change at a time.

2. Chunky: prevent exploration lag before launch

New chunk generation is one of the most common causes of stutters on an active SMP. When players explore untouched terrain, the server must generate terrain, structures, caves, lighting, and world data on the fly. That workload can hammer both the CPU and storage.

Chunky pre-generates a selected world border while players are offline or before a season opens. The result is much smoother elytra travel, map exploration, and resource-world activity. It does require planning: pre-generating a massive radius consumes time and disk space. Set a border that fits your actual gameplay instead of generating millions of chunks "just in case." The full method is in our guide on reducing chunk loading.

3. FarmLimiter: keep farms from becoming server-wide problems

A creative iron farm or a mega mob grinder can turn into a TPS problem long before players realize it. FarmLimiter lets administrators define limits around common farm mechanics, such as hopper behavior, mob counts, villagers, pistons, or item movement, depending on its available modules and configuration.

This is a strong choice for public survival servers where players build independently and staff cannot inspect every base. The trade-off is clear: limits must be announced and calibrated. A cap that is too aggressive punishes normal builds, while a cap that is too loose changes nothing. Start with measured data from spark, then apply rules to the mechanics causing actual pressure.

4. ViewDistanceTweaks: preserve TPS when player counts jump

View distance has a direct cost. More loaded chunks mean more entities, block ticking, and data sent to every connected player. ViewDistanceTweaks can dynamically adjust view and simulation distance according to server health, keeping the server playable when a spike would otherwise drag down TPS.

This is especially useful for event servers, public SMPs, and hubs that see uneven traffic. It is less useful for a small private server with a predictable player count, where a well-chosen fixed distance may be all you need. Make the minimum distance reasonable. Players should notice a little less scenery, not a world that constantly pops into view.

5. EntityTrackerFixer: reduce wasteful entity tracking

Entity tracking is the process that determines which nearby entities need to be sent to each player. In crowded bases, item frames, armor stands, mobs, and dropped items can create unnecessary work. EntityTrackerFixer is designed to improve inefficient tracking behavior in compatible Paper-based setups.

It is a targeted optimization, not a replacement for entity limits. If a player has 5,000 villagers loaded, better tracking alone will not make that build cheap. Pair it with practical farm rules and Paper or Purpur entity settings for a more meaningful result.

6. ClearLag: useful, but rarely the first answer

ClearLag is famous because it can remove ground items and run scheduled cleanup tasks. It can help a server that regularly suffers from accidental item floods, TNT debris, or players dropping stacks of blocks in spawn. Used carefully, it addresses a real edge case.

The problem is that blanket item clearing treats symptoms, not causes. It can delete loot before players collect it, disrupt redstone or farm designs, and create a frustrating "the server ate my stuff" reputation. Use it only with clear warnings, sensible exemptions, and a focus on exceptional item buildup. Do not schedule aggressive cleanup every few minutes and call the performance issue solved.

7. LagAssist: automate protection for known spikes

LagAssist offers several automated controls aimed at common lag sources, including entity management and warning systems. It can be useful for communities without staff online around the clock, particularly when you need guardrails against accidental abuse.

Automation should be conservative. Features that cancel events, remove entities, or change gameplay under load need testing in a copy of your world first. A protection plugin that saves TPS but breaks a popular farm may simply move the complaint from lag to Discord.

8. ServerBooster and similar task optimizers: audit carefully

Optimization plugins that promise broad improvements can be attractive, especially for new admins. Some provide useful cleanup or scheduling controls, but they can overlap with the built-in optimizations in Paper and Purpur or conflict with other plugins that touch the same events.

Treat these as optional, not essential. Read every enabled feature, test on a staging server, and compare spark profiles before and after. If you cannot identify what a feature changes, leave it off.

Build a stack around your server type

A private 5-player SMP generally needs spark and Chunky more than a heavy automation suite. Pre-generate the world, set fair simulation distance, and keep an eye on farms as the world matures.

A growing public survival server may benefit from spark, Chunky, FarmLimiter, and ViewDistanceTweaks. That stack handles the usual causes of real-world TPS drops: exploration, uncontrolled farms, and fluctuating player counts. Add item cleanup only if profiling shows item entities are genuinely causing trouble.

For minigames or a hub network, the priorities shift. Fast world loading, clean plugin scheduling, controlled entity counts, and a properly configured proxy matter more than farm limits. BungeeCord or Velocity networks should profile each backend separately, because one overloaded game server can look like a network-wide problem to players.

Plugins need the right foundation

Paper or Purpur should be your baseline for most plugin servers. Their configuration options give you control over mob spawning, hopper behavior, entity activation range, view distance, and more. Change settings gradually and document each adjustment, especially if your players rely on technical farms. If you are still deciding between them, compare Paper and Purpur first.

Hardware still matters. Minecraft leans heavily on single-core CPU speed, while fast NVMe storage helps with chunk loading, saves, and backups. More RAM helps only until the server has enough memory for its player count, plugins, and world. Throwing excessive RAM at a slow CPU can make garbage collection less predictable rather than improving TPS.

At Elysium, that is why Minecraft plans are built around high-performance Ryzen and EPYC hardware, NVMe Gen4 storage, backups, and a control panel that makes profiling, plugin changes, and restarts less of a chore. You should spend your time tuning gameplay, not fighting basic server management.

A safer way to deploy anti-lag plugins

Back up your server, install one plugin, and test it under a realistic load. Check its commands, permissions, default cleanup rules, and config comments before inviting players back. Then use spark to compare MSPT, not just the feeling of lag.

Keep players in the loop when a plugin changes farm behavior, view distance, or item cleanup. The most stable server communities are not the ones with the harshest limits. They are the ones where the rules are clear, the TPS stays predictable, and admins fix the cause before reaching for a delete-everything button.