Direct answer
Paper uses a conventional main game tick model. Folia runs independent regions in parallel but requires compatible plugins and benefits most when player activities occupy separated areas.
How to check it
- Inventory every plugin and obtain explicit Folia support evidence from its maintainer; a compatibility label alone does not prove thread safety.
- Test the same representative world and player activity on separate Paper and Folia staging copies.
- Compare regional lag, CPU saturation, memory and plugin correctness; include a densely populated hotspot test, not only dispersed players.
What to change
- Prefer Paper if you rely on many single-threaded plugins, one high-density arena, or features Folia disables.
- Consider Folia when you have high concurrency, ample physical cores and naturally separated gameplay. Keep a verified Paper backup for rollback.
Software and version notes
Compatibility and safety
Folia is not a drop-in Paper replacement. Some Vanilla commands and plugin APIs are limited or disabled, and region ownership affects data access. Check your target build and plugin versions before migration.
Verify the result
Run a realistic peak-player test, including portals, permissions, economies and scheduled events. Adopt Folia only if compatibility and actual workload measurements justify the migration.