

Modrinth · Fabric
Bellows on your Minecraft server
Bellows runs on Minecraft servers with Fabric. Order your server, set the loader in the panel and install the mod with one click in the mod browser.
No-compromises drop-in optimizations for Minecraft Commands/Datapacks.
- Downloads
- 1.7K
- Author
- –
- Loader
- Fabric
- Minecraft
- 26.2 – 26.3
- Updated
- –
Setup
Install Bellows on your server
The server and players need the same loader and Minecraft version. Back up the world before adding or updating mods.
- 01
Configure
4 GB of RAM is preselected. You choose the term and add-ons and pay by credit card or PayPal.
- 02
Set the loader
In the panel, set the server software to Fabric and choose the matching Minecraft version, for example 26.3.
- 03
Install the mod
Search the mod browser for “Bellows” and install the release for your loader. Alternatively, upload the .jar to the mods folder via SFTP. Required dependencies are listed on the project page.
- 04
Connect
Bellows is not needed on the client. Players connect using the server address from the panel.
- On the server
- Required
- On the client
- Not needed
- Loader
- Fabric
- Minecraft
- 26.3, 26.2
- License
- MIT License
The panel
Install mods, find errors.
Real screenshots from the Mado panel. Both come with every Minecraft server.
Mod browser
Modrinth and CurseForge, right in the panel.
The browser filters by your Minecraft version. Install mods with one click, without uploading .jar files.

AI crash analysis
When a mod crashes, the analyzer reads the log.
Mods often fail on a wrong loader version, Java version or missing dependency. The analyzer names a likely cause and suggests a fix.

Releases
Published releases
Pick the file that matches your server’s loader and Minecraft version. The server and players need the same release.
Bellows · Modrinth- Bellows 1.1.3October 29, 2026Minecraft 26.3 · Fabric
- Bellows 1.0.2September 17, 2026Minecraft 26.2 · Fabric
Original description by the project author
Bellows (formally Radon)
Bellows is a no-compromises drop-in Fabric mod designed to apply targeted optimizations for Minecraft commands-- especially in environments with many large datapacks. Do to the targeted nature of Bellow's optimizations, performance gains are somewhat variable. Most large datapacks see a 50-60% reduction in tick time using Bellows. Certain packs like Animated Java can see a 70-90% reduction in tick time.
The following optimizations are used:
- Limiting serialization of NBT data to the requested data instead of all the data, saving massive time on
data get(etc.) operations. For example, if you dodata get entity @s Healthon a player, normally Minecraft would copy & send all of the player NBT data, including the +1000 long array of unlocked recipes. With Bellows, it will copy and send onlyHealthand nothing more. - Deserializing of NBT data is similarly limited to requested data only. This is twice as effective since reading NBT data requires first writing nbt data, which uses the above optimization.
- Entities are cached based on their type (supports type tags) and selector tags. When using @e, the search function will check the caches for valid types and selector tags, and will perform the @e search only on the smallest cache. That is, if you select
@e[type=marker,tag=my_tag]and there are 100 markers, 50 withmy_tag, then the @e will only search the 50 entities withmy_tag. Currently, this does not support type=! and tag=!. Note: As of 1.9.3, Minecraft limits @e searches to specific sub-chunks when using distance= and dx,dy,dz=. Bellows makes no attempt to optimize these searches, it only does global searches. - Fix for MC-168596 "Chunks outside of render distance are not unloaded if 'execute if block' runs on it every tick." While this may not be noticeable in single player, on a server hundreds of chunks can be force-loaded in random players' bases due to custom blocks receiving tickly
if blockchecks.
Special NBT cases:
- "Quick Data:" a type of optimization which pre-compiles an nbt modification and directly updates the entity, bypassing the normal NBT process (even with the other nbt optimization, this can save a lot of time). Currently only applies the transformations, but can be expanded to other data fields.
- The Transformation field on display entities always calculates the matrix form when built, even though the server never uses this form. Bellows disables this construction.
- "data" field on entities uses a standard deep copy instead of a Codec. Reduces time by ~50%.
Usage
If you're setting up a server with a lot of datapacks and you're already using performance mods (i.e. Lithium), or your computer is truly a potato and you need to squeeze out every drop of performance you can get, then definitely give Bellows a try. Just drop it in your mods folder and datapacks will magically perform better.
While Bellows provides drop-in optimizations, it changes optimization rules that apply in vanilla (like no longer needing to reduce @e usage aggressively). In general, it is considered bad practice to develop optimizations for Bellows specifically, but there are some exceptions like:
- You are in a controlled environment, i.e. your own server which is running Bellows
- You are using a pre-compiler which can provide a normal or Bellows build target
In testing, Moonrise (ports some of paper's optimizations to fabric) seems to synergize to Bellows, reducing tick time by significantly more than either alone. Give it a try!
Advanced Features
Want to see the difference for yourself? Bellows supports toggling optimizations on the fly using these commands. You can observe the mspt in f3, or run a profile with f3+L in single player and /perf <start/stop> in multiplayer:
/bellows nbt-optimiations <true/false>/bellows selector-optimizations <true/false>/bellows fix-block-access-forceload <true/false>
Bellows also has a debug mode, which can print potential problems to console if you find your commands aren't running faster or worse are running slower.
/bellows debug <command># this prints debug info from a single command/bellows debug-mode <true/false># this prints debug info for all commands (don't do this with ticking commands running)
Bellows server crashes on startup – what to do?
Common causes: the loader or Minecraft version does not match the mod file, a dependency is missing, or RAM is too low. Check the log (latest.log) for “OutOfMemoryError”, “Mixin” or missing mods. At Mado, the AI crash analysis reads the log and suggests a cause. You can change the loader and version in the panel.
Which loader does Bellows run on?
According to Modrinth, Bellows supports Fabric for Minecraft 26.3, 26.2.
How much RAM does a server with Bellows need?
As guidance, 3–4 GB for a server with this mod. This is an estimate, not a measured minimum. More mods, many players and long view distances need more. The spark profiler shows whether a mod is costing tick time.
Similar mods
Popular mods in the same category
Client only
Sodium
by jellysquid3
A high-performance rendering engine replacement for Minecraft, which greatly improves frame rates and reduces micro-stutter.
Client only
Iris Shaders
by coderbot
A modern shader pack loader for Minecraft intended to be compatible with existing OptiFine shader packs
Client only
Entity Culling
by tr7zw
Using async path-tracing to hide Block-/Entities that are not visible
Server-ready
FerriteCore
by malte0811
Memory usage optimizations
Ready for your server with Bellows?
4 GB of RAM from €8.00 per month. 35% off your first month with MADO35.