Minecraft without a main thread: Folia splits the world into independent regions and ticks them in parallel, built for large, spread-out SMP and skyblock servers.

Select from our wide range of optimized game servers. Each server is configured for maximum performance and comes with DDoS protection.







Compare recommended use, plan hardware and monthly prices.
| Plan | Recommended for | Hardware | Monthly price |
|---|---|---|---|
| Bronze 4GB | Not recommended; plugin testing onlyNo cores left for regions on 4 vCores; suits developers testing Folia support. | 4 vCore Ryzen 9950X · 4 GB DDR5 6000MHz · 50 GB NVMe SSD Samsung 990 PRO | ₺240.00/mo |
| Silver 6GB | Not recommended; dev environmentWorks as a test box if you write Folia plugins; run a live server on Paper. | 4 vCore Ryzen 9950X · 6 GB DDR5 6000MHz · 60 GB NVMe SSD Samsung 990 PRO | ₺345.00/mo |
| Gold 8GB | Not recommended; Paper is faster hereWith the same resources, Paper carries more players and far more plugins. | 4 vCore Ryzen 9950X · 8 GB DDR5 6000MHz · 70 GB NVMe SSD Samsung 990 PRO | ₺440.00/mo |
| Platinum 10GB | Not recommended; 4 vCores is too tightMemory is fine but there are no spare cores for parallel regions. | 4 vCore Ryzen 9950X · 10 GB DDR5 6000MHz · 100 GB NVMe SSD Samsung 990 PRO | ₺530.00/mo |
| Diamond 12GB | Not recommended; pre-Folia stepping stoneA tier for growing on Paper before a planned Folia move, not for Folia itself. | 4 vCore Ryzen 9950X · 12 GB DDR5 6000MHz · 110 GB NVMe SSD Samsung 990 PRO | ₺617.50/mo |
| Emerald 16GB | 80–150 players, spread-out SMP (6 vCore)The first plan where Folia makes sense; allocate about 4 region threads. | 6 vCore Ryzen 9950X · 16 GB DDR5 6000MHz · 120 GB NVMe SSD Samsung 990 PRO | ₺840.00/mo |
| Xtreme 32GB | 150+ players, spread-out SMP or skyblockOur best fit for Folia; about 8 region threads give genuine parallelism on 12 vCores. | 12 vCore Ryzen 9950X · 32 GB DDR5 6000MHz · 200 GB NVMe SSD Samsung 990 PRO | ₺1520.00/mo |
The cores and config access you need to benefit from Folia's parallel regions, with its limits stated plainly.
Folia groups loaded chunks into independent regions and ticks each on its own loop inside a thread pool, so players at distant bases don't share each other's lag.
Emerald 16GB offers 6 and Xtreme 32GB offers 12 Ryzen 9 9950X vCores, enough to feed Folia's region threads alongside networking and chunk workers.
Folia refuses to load any plugin whose plugin.yml lacks folia-supported: true. You pick tools that support it, like LuckPerms and spark, and verify the rest before installing.
The threaded-regions.threads value in the global config decides how many threads regions get, and how much headroom you keep for networking, chunk generation and GC.
Each region keeps its own tick counter, so a heavy farm in one place slows only the players in that region while people on the far side of the map play at their own pace.
Take a manual backup from the panel before moving from Paper to Folia, and roll back if a plugin turns out incompatible. Automatic backups keep running on schedule too.
Folia server hosting at TheCrewHost starts at $6.00 a month, with PaperMC's regionised multithreading server installed automatically on Ryzen 9 9950X cores and NVMe SSD after payment. Folia divides the world into regions that tick independently and processes them at the same time on different cores, so hundreds of players spread across the map are no longer squeezed through one main thread. The trade-off is plugin compatibility: only plugins explicitly marked as Folia-supported will load. Your server runs in our Istanbul datacenter, and to get real value from Folia we recommend the Emerald and Xtreme plans with 6 and 12 vCores.
Folia is a Minecraft Java server developed by the PaperMC team and derived from Paper. Vanilla, Paper and Spigot process each world sequentially on a single main thread; as player counts rise, that thread becomes the bottleneck, and extra cores can't help the core game loop. Folia changes that model at the root.
Folia groups loaded chunks by proximity into independent regions. Each region has its own tick loop and scheduler, and regions are ticked simultaneously on a thread pool. According to the official docs, as long as the pool isn't fully saturated, every region whose tick takes 50 ms or less holds 20 TPS. When players move close together their regions merge, and when they drift apart the regions split again.
The upshot is that Folia has no main thread in the traditional sense; each region acts as its own. That makes the architecture far more scalable, but it also breaks most plugins that rely on Bukkit's single-thread assumptions. Choosing Folia means trading a large part of the plugin ecosystem for performance.
Folia's developers point to server types that naturally spread players out, skyblock and SMP, as the ones that benefit most. When each player spends time on their own island or base, regions stay separate and the cores genuinely work in parallel.
Servers that pull everyone into one spot gain little. A lobby where everybody waits at spawn, a minigame where players fight in the same arena, or a roleplay server centered on a single city effectively forms one big region, and that region is still ticked on one thread. In those cases, Folia's plugin restrictions buy you nothing.
Folia is also usually unnecessary for small and mid-sized servers. Up to around 50–100 players, a well-tuned Paper server does the same job with a far wider choice of plugins. Consider Folia when you're a large community that wants hundreds of players in one world and you're prepared to build your plugin list from Folia-compatible options.
Folia only loads plugins that their authors have explicitly marked as compatible. The marker is a folia-supported: true line in the plugin's plugin.yml; without it, the plugin never starts. PaperMC is clear that you should expect no backward compatibility with Paper plugins.
The technical reason is scheduling. Classic Bukkit plugins send work to the main thread through the BukkitScheduler. Folia has no such thread, so plugins must be rewritten around new APIs: the RegionScheduler, EntityScheduler, GlobalRegionScheduler and AsyncScheduler. Code that touches an entity or a location must run on the thread that owns that entity's or location's region.
In practice, work in this order: list the plugins you need, check each one's page for Folia support, and only then commit to Folia. Widely used tools such as LuckPerms and spark support it, but many classic economy, minigame and command plugins do not. Modrinth's platform filter lets you list Folia-compatible plugins.
Folia's documentation recommends at least 16 physical cores as ideal hardware, because networking (Netty), chunk system workers and garbage collection need cores alongside the region threads. To be upfront: our largest plan, Xtreme 32GB, gives you 12 vCores. That's enough to run Folia meaningfully for a mid-to-large community that plays spread out, but it isn't an environment built for multi-thousand-player deployments.
The Bronze through Diamond plans come with 4 vCores. After reserving cores for networking and chunk workers, almost nothing is available for regions, so Folia gains nothing over Paper and only brings its restrictions. We recommend those plans for Folia purely for plugin development and compatibility testing.
Emerald 16GB's 6 vCores are a reasonable starting point for Folia. On the memory side, Folia typically runs busy servers, so loaded chunks per player add up quickly; keeping view-distance balanced and pre-generating the world still applies here.
Folia uses Paper's config files and adds Folia-specific sections. The most important setting is threaded-regions.threads in the global config, which sets how many threads regions get. Folia's guide suggests keeping total thread allocation below 80% of available cores to leave room for plugins' unpredictable thread use. As a rough rule, about 8 region threads on 12 vCores and about 4 on 6 vCores is a sensible starting point; then tune by measuring with spark.
Moving a world from Paper is usually painless because the world format is the same. The real risk is plugins. The safe path: take a manual backup in the panel, remove or replace plugins without Folia support, start the server on Folia, read the console for plugins that failed to load, and play a closed test session first. If something goes wrong, restore the backup and carry on with Paper.
Players and commands also follow region logic in Folia; operations such as teleporting between regions happen asynchronously behind the scenes. Custom scripts and plugins that don't account for this can behave unexpectedly.
Look for Folia support on the page of every plugin you plan to use; if a critical one lacks it, staying on Paper may be the better call.
Pick Emerald 16GB with 6 vCores or Xtreme 32GB with 12 vCores to benefit from parallel regions; the 4 vCore plans are suited only to testing.
Folia installs itself once payment clears; the first start from gamepanel.hostingmerkezi.net creates the familiar Paper config files along with Folia's region settings.
Set threaded-regions.threads in the global config so total threads stay under 80% of your cores, then restart the server.
Transfer your world folder and only plugins marked folia-supported over SFTP, then check the console for any plugin that refused to load.
Measure region load with spark during a closed session; once it looks healthy, share the IP:port from your panel with your community.
What to know before choosing Folia: core counts, plugin compatibility and who it's really for.
Our İstanbul datacenter runs on Ryzen 9 hardware, delivering low latency to players in Türkiye and good connectivity to Europe, the Middle East and the Caucasus.
Turkey
Everything your project needs — from game servers to VPS, dedicated servers, web hosting and Discord bot hosting.
Connect with our community of gamers and developers
Get instant support, share experiences, and stay updated with the latest news