If you searched umod oxide or wondered whether they are different, here is a simple map.
Quick Answer
uMod is the plugin website and ecosystem. Oxide is the Rust server plugin framework. In normal Rust server conversations, people often say uMod, Oxide, and Oxide plugins to describe the same plugin workflow: install the framework, then upload .cs plugins.
Oxide
Oxide is the plugin framework that runs on many Rust dedicated servers. It loads .cs plugin files and exposes hooks so plugins can change gameplay, commands, economics, and admin tools.
uMod
uMod (the website umod.org) is the main community hub for downloading Rust plugins, reading documentation, and following updates. People often say "install from uMod" when they mean download an Oxide plugin.
So in daily language:
- "Oxide" = the runtime on the server.
- "uMod" = where most plugins are listed and downloaded.
They are not two competing mod systems in the way Forge vs NeoForge are. They are two names for the same ecosystem.
Oxide vs Carbon in 2026
Carbon is a newer framework that emerged as a faster alternative to Oxide, maintained more actively and patching faster after Rust updates:
| Feature | Oxide | Carbon |
|---|---|---|
| Update speed after Rust patches | 24 to 72 hours | Usually same day |
| Plugin compatibility | Legacy standard | Compatible with most Oxide plugins |
| Performance overhead | Moderate | Lower |
| Community size | Larger | Growing rapidly |
New servers starting in 2026 should consider Carbon as their framework. It is the direction the community is moving. Existing servers on Oxide can migrate when convenient, the transition is straightforward since Carbon supports most existing Oxide plugins.
Installing Carbon
# Download Carbon release
wget https://github.com/CarbonCommunity/Carbon.Core/releases/latest/download/Carbon.Linux.Release.tar.gz
# Extract into your Rust server directory
tar -xzf Carbon.Linux.Release.tar.gz -C /home/rust/
# Start Rust with Carbon loaded (modify your start script)
export DOORSTOP_ENABLED=1
export DOORSTOP_TARGET_ASSEMBLY="$(pwd)/carbon/managed/Carbon.Preloader.dll"
./RustDedicated ...
Plugins downloaded from uMod go into oxide/plugins/YourPlugin.cs on Oxide, or carbon/plugins/YourPlugin.cs on Carbon. The plugin compiles and loads automatically within 5 to 10 seconds of file placement. Space-Node's Rust panel includes a file manager for direct plugin placement without SFTP, drag a .cs file into the plugins directory and it loads automatically.
What you do on a host
- Use a Rust server that supports Oxide (many hosts, including Space-Node, support Oxide / uMod on Rust plans).
- Upload plugins into the
oxide/pluginsfolder (exact path can vary slightly by host). - Restart or reload per plugin instructions.
For server setup and performance, see Rust server hosting and our Rust performance and entity guide.
Frequently Asked Questions
"Is uMod the same as Oxide?"
Mostly yes in conversation: uMod is the platform/site, Oxide is the framework on the server. Players and admins use both words for the same plugin system.
"Do I need both installed separately?"
You need the Oxide layer on the Rust server. You then add plugins you downloaded from uMod (or other trusted sources).
"Does this work on console Rust?"
Console Rust does not give you a full dedicated server with Oxide like PC hosting. This guide is for PC dedicated servers.