Canvas is for large communities that want Folia's regionised multithreading in a more stable, faster-updating package.

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; Folia plugin test boxNo room for region threads on 4 vCores; only for plugin compatibility trials. | 4 vCore Ryzen 9950X · 4 GB DDR5 6000MHz · 50 GB NVMe SSD Samsung 990 PRO | ₺240.00/mo |
| Silver 6GB | Not recommended; development and trialsWorks as a small sandbox for developers building against the Canvas API. | 4 vCore Ryzen 9950X · 6 GB DDR5 6000MHz · 60 GB NVMe SSD Samsung 990 PRO | ₺345.00/mo |
| Gold 8GB | Not recommended; pick Paper at this sizeNo parallel-region gain on 4 vCores; Paper uses the same resources better. | 4 vCore Ryzen 9950X · 8 GB DDR5 6000MHz · 70 GB NVMe SSD Samsung 990 PRO | ₺440.00/mo |
| Platinum 10GB | Not recommended; too few coresMemory is sufficient, but Canvas's region model is cramped on 4 vCores. | 4 vCore Ryzen 9950X · 10 GB DDR5 6000MHz · 100 GB NVMe SSD Samsung 990 PRO | ₺530.00/mo |
| Diamond 12GB | Not recommended; step before CanvasAn interim tier for growing on Paper before a planned move to Canvas. | 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 Canvas's parallel regions pay off; grow as you test. | 6 vCore Ryzen 9950X · 16 GB DDR5 6000MHz · 120 GB NVMe SSD Samsung 990 PRO | ₺840.00/mo |
| Xtreme 32GB | 150+ players, SMP or skyblock (12 vCore)Our best fit for Canvas, with ample headroom for region threads and networking. | 12 vCore Ryzen 9950X · 32 GB DDR5 6000MHz · 200 GB NVMe SSD Samsung 990 PRO | ₺1520.00/mo |
The cores and file access you need to use what Canvas adds on top of Folia, with the limits spelled out.
Canvas splits the world into independent regions and ticks them in parallel like Folia, and its 80-plus region-threading fixes aim to improve stability and vanilla consistency.
The modified spark bundled with Canvas breaks CPU load down by region. One report shows which island or base is stretching tick times, so you fix the problem at its source.
Canvas keeps Folia's patches in its own repository and pulls updates straight from Paper, aiming to deliver new versions and fixes sooner than waiting on Folia itself.
Emerald 16GB comes with 6 vCores and Xtreme 32GB with 12. Only on these plans can Canvas's region threads, networking and chunk workers all run comfortably at once.
Canvas doesn't loosen Folia's thread-safety rules, so only Folia-compatible plugins load. The restriction can feel limiting, but it exists to prevent data corruption between regions.
Canvas adds settings under a vanilla-compatibility-first, performance-second philosophy. Every config file is reachable through the panel's file manager or over SFTP.
Our CanvasMC server hosting begins at $6.00 a month and installs Canvas, a community fork of Folia, on Ryzen 9 9950X cores and NVMe SSD as soon as payment clears. Canvas keeps Folia's architecture of splitting the world into regions that tick in parallel, then adds more than 80 stability fixes to region threading, performance work aimed at high player counts and a modified spark that profiles load region by region. Folia's plugin rules still apply: only Folia-compatible plugins run. Hosting is in our Istanbul datacenter; because Canvas inherits Folia's appetite for cores, only Emerald (6 vCores) and Xtreme (12 vCores) make sense for a live server.
CanvasMC, or simply Canvas, is a fork of Folia: it builds on Folia's regionised multithreading and layers its own changes on top. The project describes its goal as fixing gameplay inconsistencies and bugs in Folia while adding further performance improvements to the dedicated server. To get there, Canvas ships more than 80 fixes to region threading and aims to make busy servers both steadier and smoother.
Its development model differs too. Canvas bundles Folia's patches in its own repository and upstreams directly from Paper, which lets it pick up new versions and fixes without waiting for Folia's official releases. It also comes with a modified spark that can profile per region, and it aims to offer plugin developers a comprehensive API that makes supporting region threading easier.
The core idea is the same as Folia's: there is no single main thread, and each region ticks in parallel on its own loop. Everything you know about Folia, especially its plugin restrictions and appetite for cores, applies to Canvas as well.
In the project's own words, Canvas is not a drop-in replacement for Paper, Purpur or any non-Folia fork; it's meant for setups already running Folia or committed to moving there. That makes the decision order clear.
First, ask whether you need Folia at all. For most servers under a hundred players, a well-tuned Paper server with its far wider plugin choice is the smarter option. Region threading starts to pay off when you're aiming for a spread-out SMP or skyblock with hundreds of players.
Second, Folia or Canvas? Folia is PaperMC's official project and moves cautiously. Canvas is a community-developed alternative that updates faster and targets the region-threading bugs people hit on Folia. If you're seeing unexplained instability on Folia, or you want to reach new versions sooner, Canvas is worth a try. Because it's built by a smaller team, a closed test with your own plugin set before going live matters even more than usual.
Canvas sticks rigidly to Folia's threading rules and, for safety reasons, doesn't allow them to be bypassed. In practice, only plugins marked as Folia-compatible, meaning those with folia-supported: true in their plugin.yml, will load. Most classic Paper and Spigot plugins lack that marker and won't start on Canvas.
There's a reason for the restriction. Regions are processed on different threads at the same time, so a plugin written around a main-thread assumption can corrupt data or crash the server when it touches an entity or block owned by another region. Rather than accept that risk, Canvas keeps incompatible code out from the start.
Before installing, list your plugins and check each one's Folia support. Widely used tools like LuckPerms and spark do support Folia. Since Canvas aims to give developers extra APIs for region threading, some plugins may add Canvas-specific improvements over time, but the baseline test is always Folia compatibility.
Canvas shares Folia's architecture, so its hardware needs look similar: besides region threads, it needs cores for networking, chunk workers and garbage collection. Folia's documentation recommends at least 16 physical cores as ideal. With 12 vCores, Xtreme 32GB is our largest plan: it gives Canvas real parallelism for a mid-sized to large community that spreads across the map, though it isn't sized for deployments in the thousands.
On the 4 vCore plans, Bronze through Diamond, there's almost nothing left for region threads, so we recommend them for Canvas only for plugin testing or development. Emerald 16GB's 6 vCores are a reasonable start, and Xtreme 32GB is the most comfortable option.
On the Java side, Canvas requires Java 25 or newer, which also signals that the project targets current Minecraft releases. The memory rule doesn't change: on busy servers, loaded chunks per player add up quickly, so keep view-distance balanced and pre-generate your world.
On a region-threaded server, a classic TPS reading can mislead, because each region ticks at its own rate. Players on one side of the map can enjoy smooth gameplay while a giant farm elsewhere slows only the people near it. Canvas's modified spark exists for exactly this: it splits the profile by region, showing which region, entity or task the problem comes from.
Common scenarios mirror Folia's. When players gather in one spot, their regions merge and that region lands on a single thread; spreading big events across different parts of the map shares the load. An incompatible or poorly written plugin can misbehave during cross-region operations, so check the console and a spark report after adding anything new.
Be careful with updates. Canvas aims for a quick release cycle, which means frequent new builds. Before each one, take a manual backup in the panel, test in a closed session first and only then let players back in. Once a world has been opened on a newer build, there's no safe way back to the old one.
Canvas loads only Folia-compatible plugins; don't start the setup until you've confirmed Folia support on the page of every plugin you'll use.
Canvas's region threads need at least 6 vCores, so run a live server on Emerald 16GB or Xtreme 32GB and keep the 4 vCore plans for plugin trials.
Canvas is installed automatically once payment clears. Start the server for the first time from gamepanel.hostingmerkezi.net to generate its config files and open the console.
Transfer your Folia world folder and Folia-compatible plugins over SFTP in the same layout; if you're coming from Paper, weed out incompatible plugins first.
Keep the threads assigned to regions below 80% of your cores and measure load with a per-region spark report during a closed session.
Once testing goes smoothly, share the IP:port from your panel; players don't need to install anything on their side.
Questions to settle before choosing CanvasMC: how it differs from Folia, plugin support, hardware and Java.
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