Paper vs Fabric for Minecraft Servers

Choose Paper when your required server features come from its supported plugin ecosystem. Choose Fabric when you need particular Fabric mods. Both can suit a private Java group, but they run different extensions. A blanket statement that either is always faster or lighter does not establish which configuration supports your project.

Ask three questions first: which extensions are essential, whether players must install client components and how closely your technical builds depend on specific Vanilla behaviour. Then compare the suitable setup under the group's real activity. Extra memory cannot make a Fabric mod run as a Paper plugin.

Paper is the starting selection on this page. Change the configuration if your requirements lead to Fabric. This guide covers the practical differences, installation, meaningful performance checks and the limits of switching an existing world between foundations.

Paper is Java server software with plugin support, its own optimisations and configuration. Fabric is a modloader for compatible Fabric mods. The functions available depend on the extensions actually installed and their required environment.

The Paper migration guide explains the mod boundary. The Fabric installation guide covers matching loader, game and dependencies. A .jar filename does not identify the platform by itself.

Also check whether the essential extension exists for your game version. A release supporting an older version does not prove support for a newer one. Establish a common compatible state before beginning the group world, rather than discovering an impossible combination after players have built in it.

Paper is useful when you want server features through plugins, such as permissions, protected areas or administration. Choose each project for its supported platform and game version. Selecting Paper does not automatically install those functions.

For players using ordinary Java clients, server-side plugins can reduce client setup. Still inspect the particular feature: a plugin may require a resource pack or additional client support for some presentation. Plugin is not a guarantee that every feature is visible without prerequisites.

Paper offers extensive configuration. Avoid applying an entire tuning file from another tutorial without understanding it. Some choices affect entities, farms or other gameplay. A clear baseline is more useful than many undocumented optimisations when investigating a broken mechanic.

If the world depends on a particular Vanilla behaviour, build a small representative test. Run it on the actual Paper version with the intended settings. A software description cannot verify the exact farm your group wants to use, and an old test does not establish every future release's behaviour.

Fabric suits a project requiring specific Fabric mods. Those may provide new content, server-only features or deliberate technical changes. The chosen project determines its supported game version and dependencies; a random loader build does not establish compatibility.

Many Fabric mods require Fabric API. The API is an additional mod, while Fabric Loader supplies the loading foundation. Check both requirements. A missing API error is a dependency issue, not a reason to replace the server with Paper.

Whether friends need mods depends on the declared execution side. Compatible server-only mods may permit ordinary clients. Shared content mods may require matching client installations. A shader or minimap used locally does not establish that the server also needs Fabric.

Fabric does not guarantee unchanged Vanilla mechanics. Installed mods can alter behaviour. For a technical world, record the mod list and test the important farms. A small, identified set is easier to evaluate than a collection of performance promises from unrelated projects.

A player can use a Fabric client for supported local improvements while connecting to an ordinary server. That does not mean the server needs every client mod. Conversely, a content mod on the server can require a particular client installation.

Geyser can translate supported Bedrock connections into a Java server. It does not universally provide arbitrary Java client-mod content to Bedrock. A standard plugin setup and a large Fabric content pack therefore present different crossplay requirements.

Write a list of essential functions and the projects providing them. Assign them to their actual platform. If the list requires incompatible foundations, investigate alternatives or prioritise features. An untested hybrid combination does not establish that both complete sets of requirements will work together.

Record Minecraft version, Paper build or Fabric Loader version, extension releases and required Java runtime. Use the current requirements for the specific chosen release. A runtime recommendation from an older tutorial is not universal.

Paper publishes its runtime table in Getting started. Its current table distinguishes versions through 1.21.11 from 26.1 and later. Select the row for your actual server instead of treating a general Java 21 tutorial as a rule for every release.

For Fabric, compare the game, loader and required mods together. An essential project's supported versions can constrain the choice. Resolve a lack of common support before installation; more resources do not change file compatibility.

For an established world, record its previous working state first. Switching server software and upgrading Minecraft are separate changes. An unchanged import followed by a tested upgrade is easier to diagnose than replacing all the foundations in one operation.

Select Paper and the planned game version. Start the clean foundation, inspect the console and stop before adding plugin files. Use the installation path supported by the hosting configuration.

1. Download the intended plugin from its official distribution.
2. Check supported versions and dependency plugins.
3. Put the correct JAR in the hosted server's plugins directory.
4. Save and remove replaced older releases from the active directory.
5. Restart and inspect the plugin's loading output.
6. Test the function and permissions using an ordinary player account.

The Paper plugin guide explains that workflow and loading failures. A Fabric mod in this directory does not become a plugin. A downloaded archive may need extraction to expose the intended JAR.

Do not give all players operator privileges to make a permission problem disappear. Check the intended permissions and grant the specific access required. An administrator successfully running a command does not establish that an ordinary player can use the feature as planned.

Choose Fabric and the matching game release. Verify a clean start, stop and add the intended server components. Use mods in the active hosted installation; the client's directory on your computer is a separate location.

1. Select a Fabric file for the exact game version.
2. Match its dependencies, including Fabric API where required.
3. Upload components intended for the server environment.
4. Save and remove duplicate older releases from the active directory.
5. Start and inspect the first meaningful loading error or successful completion.
6. Join with the required client and test the function.

For mods with client components, provide a clearly identified installation to the group. For complete packs, use their supported server and client releases. A roughly similar collection is not a reproducible pack.

Add changes individually or as a clearly related group. Keep the previous working state. Do not remove content mods from an important world merely to see whether the process starts without them; use a test world or copy when that investigation is needed.

A useful comparison holds world, game version, activity and relevant settings reasonably consistent. Two empty servers with different view distances do not establish a winner for a later Survival session. Required functions and gameplay compatibility also remain part of the comparison.

Separate tick processing, memory, network latency and client rendering. One person's low frame rate is not a measurement of server speed. If everyone simultaneously sees delayed actions or pausing entities, a server-side investigation is appropriate.

Normal game simulation targets 20 ticks per second, corresponding to roughly 50 milliseconds per tick. The Paper command documentation explains TPS and MSPT. Averages can hide brief spikes, so observe the problem and record that activity instead of relying only on a single number.

Paper describes its supported spark integration in the profiling guide. On a compatible installation, an appropriately authorised player can start a limited recording, for example:

/spark profiler start --timeout 600

That is not a universal command for every Fabric installation. Fabric needs the appropriate supported profiler distribution. Review reports for private information before sharing and record the activity, duration and settings so a later measurement has a useful comparison.

View distance influences visible loaded areas; simulation distance influences active simulation. Both need to suit the world and group. Reduce an excessive value deliberately and compare the same activity instead of copying an entire optimisation profile.

Test important farms, Redstone behaviour, entities and dimension travel. Paper settings and mods can affect these systems. A statement about Vanilla similarity becomes useful for your build only after the required mechanic works on the actual installation.

Investigate the cause of processing demand: new chunks, entities, an extension or particular loaded areas. Extra memory can resolve memory pressure but does not eliminate arbitrary tick work. Switching loaders alone is also not a guaranteed fix.

Record intentional changes. If a farm behaves differently afterwards, the last setting or component change provides a concrete comparison. For a large technical world, a documented known working state is more valuable than an undocumented configuration described as universally best.

A software switch needs a complete backup and version-appropriate instructions. Check whether the world contains mod content. Paper cannot simply load Fabric's custom blocks, items and dimension data without their required components.

World directory structures also depend on software and version. The current Paper migration guide distinguishes historical paths before 26.1 from newer rules. An old recipe involving separate world_nether and world_the_end directories is not a universal procedure for every modern release.

1. Stop the original server and save the complete state.
2. Record game, software and extension versions.
3. Read the instructions for the exact source and target combination.
4. Investigate directory layout and feature replacements using a copy.
5. Inspect Overworld, Nether, End, player data and special content.
6. Proceed with the intended world only after that route passes.

Do not remove content mods as an incidental performance repair. If performance is the objective, profile the working foundation first. An incompatible migration can produce more serious damage than the original delay, especially without a complete recoverable source state.

Many errors are mismatched platforms or execution sides. Inspect the specific file and its declared requirements before changing the server. Similar project names on different platforms do not prove their files or configuration are interchangeable.

After a failed update, preserve the error and last functioning state. An older server opening an already converted world is not a general recovery method. Restore the saved world and its complete previous software foundation for an actual rollback.

Save world, extensions and configuration before updates. Paper backups need relevant plugin states; Fabric backups need mod and loader versions. Some plugins may store additional data outside the main world, so check their recovery instructions too.

Do not replace server files while the game process runs. Plan stop, update and controlled startup. Test ordinary player permissions, essential functions and a reconnect. The Paper update guide explains the backup and replacement principle for that foundation.

The appropriate choice is the setup whose essential extensions work, clients join reliably and important mechanics function under normal group activity. Neither a loader label nor a RAM display proves those outcomes. Keep the verified version and configuration record for the next change.

If requirements later change, repeat the feature comparison before switching software. A new Fabric content mod or a required Paper plugin can change the decision. Investigate compatibility and recoverability first, then test the intended new arrangement on a copy.

• Paper getting started covers the foundation and runtime.
• Paper plugins covers installation and dependencies.
• Paper profiling and commands cover diagnosis.
• Paper migration explains version-specific world rules.
• Fabric installation and player guides cover its distinct path.

Before choosing the configuration, assign every essential function to a supported project and common release. After setup, check a real login, ordinary permissions, the most important mechanic and a restart. That gives your group a verified Paper or Fabric foundation to build on.