Folia vs Paper: Is Multithreaded Minecraft Ready?

Minecraft's single-threaded tick loop has been its biggest performance bottleneck for over a decade. Folia, developed by the Paper team, attempts to solve this by splitting the world into independent regions that tick on separate threads. It is the most ambitious change to Minecraft server architecture since Bukkit. But is it ready for production servers in 2026? This guide explains how Folia works, what it breaks, and when you should consider it.

How vanilla/Paper ticking works

In vanilla Minecraft and Paper, the entire server runs on a single thread. Every 50 milliseconds (one tick), the server processes every loaded chunk sequentially: mob AI, block updates, player actions, redstone, hoppers, entity movement. If the sum of all this work exceeds 50 ms, the server drops below 20 TPS and players experience lag. Adding more CPU cores does not help because only one core does the tick work. This is why a 200-player server on a 32-core machine still lags, only one of those cores is running the game loop.

How Folia changes this

Folia divides the world into independent regions based on which chunks are near players. Each region gets its own tick loop running on its own thread. Two players 1,000 blocks apart are effectively on separate single-player servers that happen to share the same world file. This means their tick loops run in parallel on different CPU cores, and one player's lag source (a massive mob farm) does not affect another player's TPS across the map.

Folia also parallelizes chunk loading, entity ticking, and world generation across regions. On a server with many spread-out players, this translates to dramatically better performance because the work is distributed across all available CPU cores instead of bottlenecking on one.

Comparison table

Aspect	Paper	Folia
Threading model	Single main thread	Multi-region, multi-threaded
CPU core utilization	1 core (main thread)	All available cores
Player count scaling	Limited by single-thread speed	Scales with core count (if players are spread out)
Plugin compatibility	99%+ of all plugins	~5-10% of plugins (requires Folia API)
Bukkit/Spigot API	Fully supported	Partially (thread-unsafe calls removed)
Scheduler	BukkitScheduler (global)	Region-based scheduler
Player proximity lag	All players share one tick	Only nearby players share a region
Redstone	Normal	Normal (within a region)
Cross-region interaction	N/A	Handled with thread-safe messaging
Stability	Production-ready	Experimental (improving)
Best use case	All server types	Large survival/SMP with spread-out players

The plugin compatibility problem

This is the biggest barrier to Folia adoption. The Bukkit/Spigot API assumes a single-threaded world. Plugins freely access any entity, any block, any chunk from the main thread. In Folia, this is unsafe because different regions tick on different threads. Accessing a block in Region A from a plugin running on Region B's thread causes race conditions and crashes.

Folia introduces a new scheduling API where plugins must specify which region they want to run code on. This requires plugins to be rewritten. The BukkitScheduler is removed. runTask() does not work. Plugins must use regionScheduler or asyncScheduler instead. As of 2026, only a small percentage of popular plugins have been ported to support Folia. The list includes some essentials (basic teleportation, chat, permissions like LuckPerms), but many complex plugins (economy GUIs, minigame frameworks, hologram plugins) are not yet compatible.

When Folia helps

• Large SMP servers (100+ players): If players spread across the world, Folia distributes tick work across cores. A 200-player server that drops to 15 TPS on Paper can maintain 20 TPS on Folia if players are spread out.
• Multi-core hardware: Folia only helps if you have multiple CPU cores. A 2-core VPS gains almost nothing. An 8-core or 16-core dedicated server sees significant improvement.
• Exploration-heavy servers: Servers where players constantly explore new chunks benefit from parallel chunk generation.

When Folia does not help

• Players clustered in one area: If all 100 players stand in the same spawn area, they share one region and one thread. Folia does not help here.
• Plugin-heavy servers: If most of your plugins do not support Folia, you cannot run them. Period.
• Small servers: Under 50 players, Paper's single-thread performance is almost always sufficient.

The road ahead

Folia is an experimental project and the Paper team is transparent about this. It is not a drop-in replacement for Paper. It is a research platform for multithreaded Minecraft that will gradually mature. Plugin authors are slowly adopting the Folia scheduler API, and each month more plugins gain compatibility. The long-term vision is that Folia's approach (or something like it) becomes the default in Paper itself, but that is years away.

Teleportation and cross-region mechanics

Teleportation is one of the trickiest aspects of Folia. When a player teleports from one region to another, they move between thread contexts. Folia handles this with a ticket system that ensures the destination region is loaded and ticked before the player arrives. Simple teleportation (like /tp or /home) works, but plugins that run code immediately after teleporting a player may crash if they assume the player is still in the same region context. This is why many teleportation and home plugins needed significant rewrites for Folia compatibility. Plugins that do complex post-teleport logic (spawning particles, modifying blocks at the destination, starting a countdown) must schedule those tasks on the destination region's scheduler.

Hardware requirements

Folia is not useful on budget hardware. A 2-core VPS running Folia performs the same or worse than Paper because the overhead of managing multiple regions and thread coordination outweighs the parallelism benefit. To see real gains, you need at least 4 dedicated CPU cores, and the sweet spot is 8-16 cores. Dedicated servers with AMD Ryzen 9 or Intel i9 processors are the ideal Folia hardware. The CPU cores should be fast (high single-thread performance) and numerous. Folia also benefits from fast storage (NVMe) because multiple regions may perform chunk I/O simultaneously.

Should you switch to Folia in 2026?

For most servers, no. Paper remains the correct choice. Consider Folia only if you meet all three conditions: you have 100+ concurrent players, you have multi-core dedicated hardware (8+ cores), and you can operate with the limited set of Folia-compatible plugins. If you are curious, test it on a staging server first. Do not deploy Folia to production without thorough plugin compatibility testing.

Looking for hassle-free hosting? Astroworld Hosting runs NVMe SSDs, Pterodactyl panel, full DDoS protection.