Fabric is a lightweight mod loader for Minecraft Java Edition that is commonly used for performance mods, utility mods, technical servers, and complete modpacks.

This guide explains how to install Fabric on a Down Side Hosting Minecraft Java server, add Fabric mods, and troubleshoot common problems.

Before installing Fabric, determine:

• Your Minecraft version
• The Fabric Loader version required by your mods or modpack
• The Java version required by your Minecraft version
• Whether your mods require Fabric API
• How much RAM your server needs
• Whether you are starting a new world or using an existing world

Important: Your Minecraft version, Fabric Loader, Java version, and installed mods all need to be compatible.

Fabric primarily loads mods from:

mods/

This is different from the Bukkit-style:

plugins/

folder used by Paper, Purpur, and Spigot.

A normal Fabric server should not be expected to run standard Bukkit or Spigot plugins.

If you want a plugin-based Minecraft server instead, see:

Paper vs Purpur vs Spigot: Which Minecraft Server Should You Use?

Fabric Loader is the software that loads Fabric mods.

Fabric API is a separate mod containing common APIs used by many Fabric mods.

Fabric API is not automatically required by every Fabric mod, but many popular mods depend on it.

If a mod requires Fabric API, download a version that matches your Minecraft version and place it in:

mods/

If you are converting an existing Minecraft server to Fabric, create a backup first.

Important files can include:

• Worlds
• Server configuration
• Player data
• Mods
• Mod configuration files
• Server properties
• Other important server files

Do not make major server-software changes without a recovery point.

Open your Down Side Hosting server panel.

Select the Minecraft server and click:

Stop

Wait until the server has completely stopped before replacing server software or uploading mods.

First determine the Minecraft version required by your mods or modpack.

For example, all of these need to agree:

Minecraft version
Fabric Loader version
Mod versions
Java version

A mod made for one Minecraft release should not be assumed to work on another.

If your Down Side Hosting server configuration provides a Fabric installation option, choose the Minecraft version you need and install Fabric through the panel.

If you are performing a custom installation, Fabric provides an official installer and server launcher.

Official Fabric resources:

• Fabric Server Installation
• Fabric Website

Follow the version requirements for your intended Minecraft server.

After the first installation or startup attempt, Minecraft may create:

eula.txt

Open the file and change:

eula=false

to:

eula=true

Then save the file.

By doing this, you are confirming acceptance of the Minecraft End User License Agreement.

Start the server and watch the console.

A successful initial Fabric startup should create the normal Minecraft server files and may create folders such as:

mods/
config/
logs/
world/

Once the server has successfully started, stop it again before installing your mods.

Open the Files section of your Down Side Hosting server panel.

Navigate to:

mods/

Upload your Fabric-compatible mod JAR files.

For example:

mods/
    fabric-api.jar
    lithium.jar
    ferritecore.jar
    ExampleMod.jar

The names above are examples.

Do not extract normal mod JAR files.

A mod may be released separately for:

• Fabric
• Forge
• NeoForge
• Quilt
• Multiple loaders

Make sure you download the Fabric version.

A Forge mod cannot normally be placed into a Fabric server and expected to work.

Fabric mods may require additional mods or libraries.

A mod's download page might list dependencies such as:

Fabric API
Architectury API
Cloth Config
Another library mod

The required dependencies vary by mod.

Install the correct dependency versions for your Minecraft and Fabric environment.

Fabric has many mods that are designed only for the Minecraft client.

Examples can include mods that change:

• User interface
• Rendering
• Graphics
• Client controls
• Local visual effects

A client-only mod generally should not be installed on a dedicated server unless its documentation specifically says server installation is supported.

Other Fabric mods may be:

• Server-side only
• Client-side only
• Required on both client and server

Always check the mod documentation.

Return to the Down Side Hosting server console and click:

Start

Watch the startup log.

Look for messages containing:

ERROR
WARN
Exception
Could not load
ModResolutionException

If the server does not start successfully, the console will usually contain information about the problem.

Once Fabric has successfully started, connect using your Down Side Hosting server address:

dsh.network:YOUR_PORT

Replace YOUR_PORT with the port assigned to your server.

See:

How to Connect to Your Down Side Hosting Minecraft Java Server

It depends on the mods being used.

Some Fabric mods are completely server-side and allow players to connect with an otherwise normal Minecraft client.

Other mods require players to install:

• Fabric Loader
• Fabric API
• The same mod
• Compatible mod versions

Check the documentation for each mod.

If you are using a complete modpack, players will usually need the matching client modpack.

When installing a complete Fabric modpack, use the modpack developer's server pack when one is available.

A server pack may contain:

• Mods
• Configuration files
• Fabric files
• Default configurations
• Scripts
• Server-specific files

Do not automatically upload an entire client modpack folder to the server.

Client installations can include mods and files that do not belong on a dedicated server.

See:

How to Install a Minecraft Modpack on a Server

Common causes include:

• Incorrect Minecraft version
• Incorrect Fabric Loader version
• Wrong Java version
• Missing Fabric API
• Missing mod dependency
• Forge mod installed on Fabric
• Client-only mod installed on the server
• Incompatible mod versions
• Configuration problem
• Corrupted mod file
• Insufficient memory

Start by checking the server console.

Many Fabric mods require Fabric API.

If the server reports that Fabric API is missing:

1. Stop the server.
2. Download the correct Fabric API release for your Minecraft version.
3. Upload it to:

mods/

1. Start the server again.

Do not assume every Fabric API release works with every Minecraft version.

If a mod requires another mod or library, Fabric may identify the missing dependency during startup.

The error may indicate something similar to:

Mod A requires Mod B

Install a compatible version of the required dependency into:

mods/

and start the server again.

Fabric may refuse to start if a mod was built for a different Minecraft version.

For example, verify that all of these match your environment:

Minecraft
Fabric Loader
Fabric API
Individual mods

Check the download page for every mod involved in the error.

Check that the mod is inside:

mods/

and that the file is a valid Fabric mod JAR.

Also verify:

• Correct Minecraft version
• Correct mod loader
• Required dependencies
• Correct Java version
• Whether the mod is server-compatible

If you accidentally place a Forge-only mod into a Fabric server, remove it and download a Fabric-compatible version if one exists.

Forge and Fabric use different modding systems.

A file simply being a:

.jar

does not mean it works with every mod loader.

Different Minecraft releases can require different Java versions.

Using an incompatible Java version can prevent Fabric or Minecraft from starting.

Java-related errors may include:

UnsupportedClassVersionError

If you are unsure which Java version your server should use, check the requirements for your exact Minecraft version or contact Down Side Hosting support.

If the server worked until you added a new mod:

1. Stop the server.
2. Remove the recently added mod JAR.
3. Start the server again.
4. Check whether the problem disappears.

If the server starts normally, check that mod's:

• Minecraft version
• Fabric support
• Dependencies
• Java requirements
• Known compatibility issues

With a large modpack, avoid randomly deleting mods.

Mods can depend on one another, so removing one mod may create additional errors.

Start by checking:

logs/latest.log

and any available crash report.

Look around messages such as:

Caused by:

ModResolutionException

Exception

Failed

Make a backup before changing an established modpack.

For additional help, see:

Minecraft Mod and Modpack Troubleshooting Guide

The main server log is usually located at:

logs/latest.log

Other log files may also be available inside:

logs/

If Minecraft produces a crash report, you may also have:

crash-reports/

The server console should also be checked.

Modded Minecraft servers can require more memory than small Vanilla or plugin-based servers.

The amount needed depends heavily on:

• Number of mods
• Mod complexity
• Player count
• World generation
• Dimensions
• Loaded chunks
• Server activity

See:

How Much RAM Does a Minecraft Java Server Need?

Do not assume every crash is caused by insufficient RAM. Check the server log first.

Fabric itself does not guarantee good performance.

Lag can still result from:

• CPU-heavy mods
• World generation
• Large numbers of entities
• Chunk loading
• High simulation distance
• Large farms
• Mod conflicts
• Insufficient server resources

Performance-oriented Fabric mods may help certain workloads, but compatibility should always be checked before adding them to an existing modpack.

Yes.

However, a modded world may depend on Fabric mods that add:

• Blocks
• Items
• Entities
• Dimensions
• Biomes
• World generation

Make sure the required mods are installed before opening an existing modded world.

See:

How to Upload a Minecraft World to Your Down Side Hosting Server

Possibly, but it can be risky.

Removing a mod may remove or damage content created by that mod, including:

• Blocks
• Items
• Entities
• Dimensions
• Player data
• World data

Create a full backup before removing mods from an established world.

Fabric and Forge are separate Minecraft modding ecosystems.

Fabric is commonly chosen for its lightweight loader, quick version support, performance-focused mods, and Fabric-specific mod ecosystem.

Forge has its own large mod ecosystem and is commonly used by many established modpacks.

The correct choice depends primarily on which loader your desired mods or modpack supports.

For Forge, see:

How to Install Forge on a Down Side Hosting Minecraft Server

Only if one or more of your installed mods require it.

Many Fabric mods use Fabric API, so it is common to have it installed.

Check each mod's requirements.

A standard Fabric server is intended for Fabric mods and does not provide normal Bukkit, Spigot, or Paper plugin support.

If you need Bukkit-style plugins, consider Paper, Purpur, or Spigot instead.

Sometimes.

If all installed mods are server-side and do not require client modifications, a normal compatible Minecraft client may be able to connect.

If your mods require client installation, players need the correct Fabric setup as well.

Normally, no.

Use the version of the mod built specifically for your selected loader.

Yes, especially after the server already has an established world.

Mods can modify world data, player data, dimensions, blocks, items, and other persistent information.

When contacting support, provide:

• Minecraft version
• Fabric Loader version
• Fabric API version, if installed
• Mod or modpack name
• Modpack version
• Relevant console error
• latest.log when appropriate
• What changed before the problem started

Contact Down Side Hosting Support

Down Side Hosting supports Minecraft Java server configurations including Fabric, Forge, Vanilla, Paper, Purpur, and Spigot.

Customers have access to server files, console controls, backups, and server configuration through the Down Side Hosting server panel.

Minecraft Java hosting starts at $2/month.

View Minecraft Java Server Hosting

← Back to Minecraft Java Server Guides