Oxide vs Carbon: Which Rust Mod Framework to Use?

• Oxide / uMod – the framework the Rust modding scene was built on. It has the largest plugin catalog and the most documentation, and almost every plugin is written for it first.
• Carbon – a newer, open-source framework that’s largely drop-in compatible with Oxide plugins but designed for lower overhead and faster load times, using Harmony and runtime compilation.

Oxide runs Oxide plugins – that’s the whole ecosystem. Carbon is built to load most of those same plugins, so the vast majority "just work." A minority of plugins that hook deep into Oxide internals may need a Carbon-specific build, though the compatibility gap has narrowed a lot. If your must-have plugin only ships an Oxide version and hasn’t been tested on Carbon, that’s worth checking first.

Performance is Carbon’s pitch. It generally boots faster and adds less overhead than Oxide, which can matter on a busy server with many plugins or on modest hardware. Oxide performs perfectly well for most servers, though – for a typical community server you’re unlikely to notice a night-and-day difference, and your config and plugin count affect framerate more than the framework choice.

• Both install by dropping files into your server folder; managed hosts often offer one-click installs for each.
• Both must be updated after Rust’s monthly forced wipe – an outdated framework won’t load until it catches up to the new game build.
• Carbon tends to publish updated builds quickly after a Rust update; Oxide is also usually fast, but on patch day either can lag by a few hours.

Oxide’s maturity means a huge base of battle-tested plugins and answers to almost any problem you’ll hit. Carbon is younger but actively developed with a growing community. Many owners keep Oxide as the safe default and try Carbon when they want the performance edge.

• Pick Oxide if you want maximum plugin compatibility, the most documentation, and a proven default – especially for your first server.
• Pick Carbon if performance is a priority, you’re running lots of plugins, or your hardware is modest and you want the lighter footprint.
• Either way, don’t run both at once – pick one framework per server.