Carbon vs Oxide in 2026: An Honest, Tested Comparison
Carbon and Oxide both compile C# plugins for Rust and share an API — but they differ on performance, update speed, and momentum. Here's an honest, tested comparison and a clear recommendation.
Most "Carbon vs Oxide" articles are generic feature rewrites, often outdated on how far Carbon has come. This is a current, practical comparison — what actually matters when you're choosing a framework for a server you have to keep running.
The short version
For a new server in 2026, install Carbon. It runs the same plugin ecosystem, performs better, and gets its post-wipe update out faster — which is the single thing that hurts most when it lags. Oxide is still perfectly usable and some long-running servers have no reason to switch, but the momentum is with Carbon.
What they have in common
It's easy to overstate the difference. Both:
- Compile C# plugin
.csfiles at runtime — no precompiling. - Use the same hooks, the same
[Info]attribute, the same permission system, and the same JSON config/data formats. - Run essentially the same library of community plugins.
Because Carbon implements the Oxide API, a plugin written for one almost always runs on the other — see how to make a Rust plugin for what that shared API looks like in code.
Where they differ
| Factor | Carbon | Oxide / uMod |
|---|---|---|
| Performance | Generally lighter; dynamic hook system only subscribes to hooks in use | Stable but heavier; all hooks always active |
| Post-update speed | Typically updated within hours of a Facepunch update | Slower in recent cycles |
| Plugin compatibility | Runs Oxide plugins via API shim; rare internal-dependent ones fail | The original target — everything written for Oxide |
| Hot-reload & tooling | Strong file watcher, good console commands (c.*) | Functional (o.*), less actively developed |
| Maturity | Newer, but well past "experimental" | Years of production hardening |
| Momentum | Where new development and most admin attention is going | In maintenance mode; uMod site itself is largely static |
The update-cadence point is the real one
Everything above matters, but in practice the deciding factor is this: Rust force wipes on the first Thursday of every month, and the update under it breaks plugins. Whichever framework gets itscompatible build out first is the framework whose servers are back online first. Lately that's consistently Carbon. A server that's down for fresh-map evening loses players that don't come back.
When Oxide still makes sense
- An established server that's stable on Oxide, with an admin who knows it cold — "don't fix what isn't broken" is legitimate.
- A plugin you depend on that explicitly only supports Oxide (rare, but check before switching).
Recommendation & next steps
New server: Carbon. Existing Oxide server that's working: consider switching at a wipe boundary, not mid-wipe, and only after confirming your critical plugins are green on Carbon (each plugin's page in our directory carries a tested verdict).
Ready to go? Install Carbon, then keep it current with how to update Carbon. The full server build is in the Rust server setup guide.