Yes, absolutely!
The Rust Server Management Tool is completely free and user oriented. There are no hidden costs, subscriptions, ads, or premium versions.
The tool is developed and maintained as a free resource for the Rust gaming community.

No External Programs/Tools Needed. None required — completely standalone.

Rust Server Installation: 10–15 GB minimum for a Rust server installation.

Skin Downloads: Varies. (128 GB* estimated for around 17,500 Skins averaging 8 MB per skin.)

Windows Compatibility: Windows 7 (SP1 – Ultimate), Windows 10 (home + enterprise), Windows 11 (home + enterprise).

The tool itself is lightweight and runs on any modern Windows system capable of hosting Rust dedicated servers.

Yes, RSMT is completely safe and all downloads include VirusTotal scan results for verification.
The tool comes with multiple organized windows to maintain server control and hence the amount of detections.
Microsoft Defender may flag the application — you may need to disable Microsoft Defender or add RSMT to a whitelist.

The tool only makes legitimate changes to your Rust server files as shown by the image of the tool below.

RSMT requires an internet connection for certain features: downloading or updating the Rust server via SteamCMD, fetching plugin updates from uMod, downloading skins, and checking for tool updates.

The core UI and local configuration editing work fully offline. The RCON Tool also functions offline as long as the server is running locally.

Key note: If your ISP blocks rsmt.dev, use the built-in WARP feature under the Network Tool to tunnel through DNS-over-HTTPS.

You can download directly from the website, or use iex (irm https://rsmt.dev/rsmt) in PowerShell to install the latest version without a browser.
Simply download the ZIP and extract to a folder — no external tools are required (besides SteamCMD, which is automatically installed for you).
Rust Server Management Tool is ready to go when you are.

Yes, of course!
RSMT can work with existing Rust server installations, AUX01 staging branches, and even outdated versions.
Just point the tool to your existing Rust Server Path at the top of the application, and it will integrate with your current server setup.

No — RSMT will not update your server automatically. It can update to the latest version on command, so be aware of mod support when doing so.
RSMT provides one-click server updates and installations, but the timing is always your choice.
You maintain full control over when updates are applied to your server.

RSMT includes a dedicated Oxide Install tool accessible from the main interface.

To install Oxide for the first time, click the Oxide install button — RSMT downloads and injects the latest Oxide build directly into your server directory. Your server must be stopped before installing.

To update Oxide after a Rust update, use the Oxide Update button. This fetches the latest uMod build and replaces the existing files.

Key note: Always update Oxide after each Rust server update, as outdated Oxide versions will cause crashes or plugin failures on a newer server build.

The Skin Downloader allows you to view, save, download, and fetch information for skins in Rust.

Usage:
1. Open Skin Downloader from the main window.
2. Check Save to Client if you want skins saved locally for use in-game.
3. Click Fetch All and wait for the fetch to complete — this queries the Steam Workshop for all available skins.
4. Click Download All Fetched to save them to disk. Be aware this is a very lengthy process.

After downloading, run in client console: graphics.itemskintimeout -1
This forces the game to load your locally stored skins.

To spawn an item with a specific skin: inventory.giveto PlayerName rifle.ak 1 889710179

Key note: Skin Downloader does not have Steam backend access, so fetching all 17,500+ skins takes significant time. You can also use the SkinBox or Skins plugins as an alternative, as they include all Skin IDs by default.

RSMT includes a Plugin Update Tool that connects directly to the uMod API to download and update your installed Oxide plugins.

Usage:
1. Ensure Oxide is installed on your server.
2. Open the Plugin Manager tab in RSMT.
3. RSMT reads your /oxide/plugins/ folder and checks each plugin against uMod.
4. Click Update to pull the latest version of any outdated plugin.

Key note: There is currently no in-app plugin browser — you must already have plugins installed in your plugins folder for RSMT to update them. Only uMod is used as the source, ensuring reputable and verified plugin downloads.

The backup feature creates a snapshot folder of your server contents. You choose what to include:

Backup options: World data, player data, Oxide data, or the full server directory.

Usage:
1. Open the Backup tab in RSMT.
2. Select the components you want to back up.
3. Click Backup — a timestamped folder is created with the selected data.
4. To restore, select a previous backup from the list and click Restore.

Key note: After restoring a world, update the server to the matching client version or ensure both are on the same Rust build to avoid connection issues. Backups are also useful for archival in case of corruption.

The RCON Tool allows you to send commands to your running Rust server without being in-game, using WebSocket RCON.

Usage:
1. Start your server with +rcon.web 1 +rcon.port 28016 +rcon.password yourpassword.
2. Open the RCON Tool in RSMT.
3. Enter the IP, port, and password. For local use, set IP to localhost or 127.0.0.1.
4. Click Connect. The console shows live server output and accepts commands.

LAN access: Use your device's LAN IP (e.g. 192.168.1.x) — find it with ipconfig in cmd.exe.

New in v1.7.2: Auto-connect on launch, online map view of the connected server, and FTP support alongside RCON.

The Server Config Editor is a visual interface for editing your Rust server's startup parameters and configuration files without manually editing text files.

It covers: server name, description, max players, world seed, map size, tick rate, RCON and network parameters, and more.

New in v1.7.2: The Server Config now includes Deepsea server parameters following the Deepsea content update.

Key note: Changes are written to your server's startup batch file and server.cfg. Always restart the server after changes for them to take effect.

The World Config tab lets you set world parameters such as seed, size, and biome settings. The World Editor provides prefab management for placing or removing objects in the world.

New in v1.7.2: New Deepsea prefabs and road placement options are now available in the World Editor.

Key note: Changing the world seed or size wipes the existing map. Always back up your world data before making world config changes if you want to preserve player progress.

The Network Tool helps diagnose and manage your server's network connectivity. It includes port checking, verifying RCON and game ports are accessible, and the built-in WARP integration for ISP-level bypass.

WARP is a DNS-over-HTTPS service that encrypts your DNS queries through a secure tunnel. If your ISP blocks rsmt.dev or prevents the installer from downloading, enabling WARP resolves most connectivity restrictions.

Key note: The Network Tool runs elevated (as administrator) in a separate process to safely modify network adapter settings without affecting the rest of the tool.

Usually antivirus flags RSMT and deletes the executable. Ensure it is added to your antivirus exclusion list, or temporarily disable your antivirus and re-extract from the ZIP.
Try running the application as administrator, as some features (Network Tool, server installation) require elevated permissions.
If you receive a specific error message, please report it via the contact link so it can be investigated.

Certain ISPs block rsmt.dev or prevent the RSMT tool from downloading updates. There is always a solution.

Rust Server Management Tool includes WARP — a DNS-over-HTTPS service that encrypts your DNS queries through a secure HTTPS tunnel, bypassing ISP-level DNS blocks while preserving tool integrity.

Enable WARP from the Network Tool within the application, then retry the download or update.

After downloading skins with the Skin Downloader, you must tell the Rust client to load locally stored skins instead of fetching them from Steam in real time.

Run this command in your client console: graphics.itemskintimeout -1

This removes the skin loading timeout, forcing the client to use all locally downloaded skins.

To spawn an item with a specific skin ID: inventory.giveto PlayerName rifle.ak 1 889710179

Key note: Skins downloaded via the Skin Downloader are stored in the Steam skins cache folder. If you clear skin caches or reinstall, you will need to re-download.

After each Rust server update, Oxide typically needs to be updated as well, as the game's internal assemblies change and Oxide hooks break.

Steps to fix:
1. Stop your server.
2. Use the Oxide Update button in RSMT to pull the latest Oxide build from uMod.
3. Use the Plugin Update Tool to update all installed plugins to their latest versions.
4. Restart the server.

Key note: If a specific plugin is still broken after updating, it may not yet support the new Rust version. Check the plugin's page on uMod for update notes from the plugin author.

Basic tools hide raw plaintext — anyone who suspects a carrier can read the message directly. Project Static hides encrypted, authenticated ciphertext. Even if an analyst extracts the hidden bits, they see AES-256 ciphertext indistinguishable from random noise. Without the key, the message is impossible to recover.

Out-of-band key exchange means an attacker must compromise both channels simultaneously. The image alone is useless; the key alone is meaningless.

Example: Send the image via Signal or Discord. Send the key via SMS or email. Each channel independently reveals nothing.

No. AES-256 has no backdoor, and the keyspace is astronomical. Without the exact 64-character hex key, the encrypted data is permanently unrecoverable. Always copy and store the key before closing or regenerating.

No. Project Static is completely offline. It uses only built-in .NET cryptography and has no network telemetry, update checks, or external calls of any kind.

Because the carrier is pure random noise (not a natural photograph), standard steganalysis techniques fail. There is no original image to compare against, and the payload itself is cryptographically random.

No — never. JPEG's lossy compression alters pixel values, corrupting the LSB layer where the payload is embedded. Use PNG, BMP, or TIFF only.

Static images: Saving as JPEG, taking a screenshot, resizing, cropping, uploading to social media that re-encodes images, or applying any filter.

GIFs: Using any GIF optimizer or compressor, re-encoding the file, or uploading to platforms that reprocess GIFs.

Safe sharing: Direct file transfer, email attachment, Telegram/Signal as a file, Discord direct upload.

Use the formula: (width × height × 3) ÷ 8 minus 36 bytes overhead.

256×256 — ~24 KB usable capacity
512×512 — ~96 KB usable capacity
1024×1024 — ~384 KB usable capacity

Possibly, due to its cryptographic operations and random data generation. The app has no installer, no registry writes, and no network activity. If flagged, add it to your antivirus exclusion list.

Project Breakaway is a C# 5.0 Windows utility that allows you to run applications at the Windows 10 and 11 lock screen, and perform elevated operations using SYSTEM-level privileges — all on your own device.

It is designed for white, grey, and red hat engineers who want full control over their own machine, including browsing the file system, changing passwords, updating backgrounds or avatars, watching media, and booting to recovery environments, all from the lock screen.

Key note: Breakaway operates entirely on your local machine using standard Windows APIs. It does not communicate over the network and leaves no permanent changes unless you explicitly make them through the app.

Windows 10 and 11 use anachronistic code. Core Win32 infrastructure from the XP era still underpins modern architecture, while newer layers such as UWP, WinRT, and modern UI frameworks are stacked on top. The lock screen is a separate Windows session (Session 0 / Secure Desktop) that runs independently of user sessions, which is why most user-mode applications cannot reach it without a specific injection or patch method.

Breakaway exploits the existing Debugger registry key mechanism and available SYSTEM process tokens to bridge this gap without modifying protected OS files.

The Patching Tab modifies Windows registry items to redirect specific system executables (such as Utilman.exe, sethc.exe, osk.exe, or Narrator.exe) to run a target application instead.

Usage:
1. Under Source Executable, select one of the four available system targets.
2. Under Target, click Browse and select the executable you want to run at the lock screen.
3. Click Patch.

Example output:
Patching...
Source: C:\Windows\system32\Utilman.exe
Target: C:\Users\Brent\Desktop\Breakaway.exe
Set Debugger and UseDebugger
Patch successful

Key note: The original executable data is safely backed up internally. You can restore at any time using the Kernel Tab.

Utilman.exe — The accessibility icon (bottom-left on the PIN/Password screen). Recommended for most users.
sethc.exe — Sticky Keys, triggered by pressing Shift five times.
osk.exe — On-Screen Keyboard.
Narrator.exe — Windows Narrator.

The Kernel Tab provides restoration and advanced privilege tools:

Restore: Undo patches made in the Patching Tab.
SAM Hash Dump: Extract NTLM password hashes from multiple local accounts for auditing.
Password Reset: Send a network-level reset command by entering a username.
Boot Options: Directly boot to Windows Recovery Environment (WinRE), UEFI firmware settings, or Advanced Boot Options.

Project Breakaway uses standard Windows APIs for elevation and process creation. Antivirus software may flag it heuristically due to token borrowing and registry modifications. If flagged, add it to your exclusion list.

Fix: Press Alt+Tab to bring Breakaway back to the foreground. To prevent this, enable the Always on Top (AoT) checkbox before editing background, avatar, or transparency settings while on the lock screen.

UWP-ADU (Universal Windows Platform Application Downgrade Utility) lets you download, install, downgrade, restore, reinstall, and version-target Microsoft Store applications on Windows 10 and 11.

It fetches app packages directly from Microsoft's delivery servers, bypassing the Store update mechanism entirely. This lets you install older builds, restore a working version after a bad update, or install newer builds on older Windows versions.

Key note: UWP-ADU must be run as Administrator for installs to succeed. Developer Mode must be enabled and MsixMgr installed for sideloading packaged apps.

Newer updates sometimes remove features, change behavior, introduce bugs, or silently update without notification. Common reasons to downgrade include a feature you relied on being removed, visual or functional regressions, or unwanted major updates.

UWP-ADU prevents and mitigates forced UWP application updates by allowing you to install and stay on any specific version you choose.

For sideloading and deploying packaged Store apps outside the Microsoft Store, Developer Mode generally needs to be enabled. MsixMgr helps unpack and install .msix and .appx packages correctly.

UWP-ADU detects whether both are present and offers a one-click install for each if missing.

To enable Developer Mode manually: Run ms-settings:developers in the Run dialog or Settings.

UWP-ADU handles installing the following file types:

.msix — Modern packaged app format.
.appx — Older packaged app format.
.msi — Windows Installer packages.
.exe — Standard executable installers.

After downgrading, the Microsoft Store may detect the version mismatch and auto-update the app back to the latest version.

To prevent auto-updates:
1. Open the Microsoft Store.
2. Click your profile icon (top right) and select Settings.
3. Toggle App updates to Off.