Illustration for uMod/Oxide vs Carbon: Install Rust Server Plugins

uMod/Oxide vs Carbon: Install Rust Server Plugins

Compare uMod/Oxide and Carbon, install one Rust framework cleanly, and validate plugins, permissions and updates.

uMod/Oxide and Carbon are server frameworks that load Rust plugins. uMod/Oxide is the long-established ecosystem; Carbon targets Oxide plugin compatibility, a familiar structure and additional optimisations. Do not run both at once. Pick one, back up, and test plugins on a copy.

Choose uMod/Oxide or Carbon

CriterionuMod/OxideCarbon
EcosystemLarge uMod catalogue and extensive legacy documentationLoads most Oxide-targeted plugins and adds Carbon features
InstallationWindows/Linux archive extracted into server rootProduction build for Windows/Linux extracted into root
After a Rust updateReapply a compatible Oxide build after SteamCMDDocumented self-update mechanism tied to branch
Migrationoxide/config/data/lang/plugins structureMigration tooling and compatible layout, still tested per plugin
Conservative choiceStable server whose whole stack is proven on OxideNew or rehearsed migration that needs Carbon features

Compatibility claims cannot guarantee every plugin, especially those using native extensions, removed APIs or a specific game build. Inventory plugins and dependencies before deciding.

Install uMod/Oxide

  1. Stop the server and back up the entire identity folder, oxide/, startup script and server files.
  2. Download the Rust archive for Windows or Linux from uMod.
  3. Extract it into the root containing RustDedicated/RustDedicated.exe, preserving paths.
  4. Start the server and confirm uMod/Oxide messages in the console. The generated oxide/ tree includes plugins, config, data, lang and logs.
  5. Place one compatible .cs plugin in oxide/plugins/ and verify its load and generated configuration before adding another.

SteamCMD restores vanilla server files. Facepunch therefore notes that a compatible Oxide build must be reapplied after a Rust update. Automate Rust update → framework → start, never the reverse.

Install Carbon or migrate from Oxide

1

Create a migration backup

Archive world and player files, oxide/plugins, oxide/config, oxide/data, oxide/lang, permissions and extensions. Keep it off the host.
2

Return to clean Rust files

Update and validate the public Rust branch. Do not launch a mixture of old Oxide and Carbon DLLs.
3

Install the production Carbon build

Download the official build for the server OS and public branch, then extract it where RustDedicated lives. carbon must be a direct subdirectory of that root.
4

Let migration run once

On first boot, Carbon documents migration of Oxide configuration, data, language, permissions and extensions. Read the log and keep the original archive until full validation.
5

Test in batches

Validate permissions, commands and data with a small plugin set. Reintroduce high-risk plugins one at a time, then measure errors and execution time before reopening.

Install and validate plugins

For each plugin, record its source, version, configuration, dependencies and last test date. Install only files published by the author; Rust plugins execute with server privileges.

Pre-launch validation

  • •Framework and game target the same public branch.
  • •Console has no compilation error or missing hook.
  • •Commands work under both player and administrator accounts.
  • •Groups and permissions were migrated or recreated correctly.
  • •Existing data files load instead of being reset.
  • •A full restart preserves config, data and permissions.
  • •A restore point from before the change remains available.

If a plugin fails, disable it, preserve the complete message and check its dependencies first. Do not swap several frameworks and extensions in one test. Use the Rust update guide to make maintenance repeatable.

Host a plugin-ready Rust server

Compare Rust plans with backups, file access and uMod or Carbon installation.

Frequently asked questions

Does Carbon run every Oxide plugin?
Carbon targets broad compatibility and migrates the Oxide layout, but native extensions, old hooks and abandoned plugins still need testing. Never migrate a live public server without a rehearsal environment.
Why do plugins disappear after SteamCMD?
SteamCMD validation restores vanilla Rust files and can replace framework patches. Reapply uMod/Oxide after each update; for Carbon, preserve its documented installation and update order.
Can Oxide and Carbon run together?
No. They serve the same framework role and can conflict. Keep one active stack and store the other only in an offline backup.

Sources: uMod for Rust, Carbon owner documentation, Oxide-to-Carbon migration and the Facepunch Carbon wiki.

Our recommendation

Ready to launch your Rust server?

Here are the best Rust hosting deals right now, promo codes included. Still unsure? Our quiz finds the ideal host for you in under 2 minutes.

My box 12

Minestrator

17.99€/month
-10% with code HOSTMYGAME
Max players:50
Mods:
Yes

Specifications

RAM:12GB(DDR4)

Compatible games

Rust

Features

  • ✓DDoS Protection
  • ✓Backups
See offer

Wood

Shockbyte

12.84€/month
-25% with code LAUNCH
Max players:40
Mods:
Yes

Specifications

RAM:8GB(DDR4)

Compatible games

Rust

Features

  • ✓DDoS Protection
  • ✓Oxide mod support
  • ✓Instant Setup
  • ✓24/7 Support
See offer

Rust

OptiNAS

12.99€/month
-10% with code HOSTMYGAME
Max players:Unknown
Mods:
Yes

Specifications

RAM:16 Go

Compatible games

Rust

Features

  • ✓Environ 30 joueurs
  • ✓Minimum : 6 vCPU et 16 Go de RAM
  • ✓Conseillé : 6 vCPU et 16 Go de RAM
  • ✓Plugins et mods possibles selon le jeu
  • +2 more features
See offer
See all Rust offers