Steam Deployment | ECOSYSTEM Research

1. Decide whether you need Steamworks API integration You can ship on Steam without Steamworks API integration, but the API is recommended for things players expect: overlay behavior, achievements, leaderboards, invites, lobbies, Steam Cloud, etc. Valve explicitly says Steamworks API integration is not required to ship, but is highly recommended for Steam-specific interactions. ([Steamworks][1]) For Bevy, you have two main options: Option A — Bevy 0.18: use bevy-steamworks The latest bevy-steamworks docs I found show version 0.16.0, depending on bevyapp ^0.18 and bevyecs ^0.18, so it is a clean fit for Bevy 0.18 projects. ([Docs.rs][2]) The plugin docs say it adds a Steam Client as a Bevy ECS resource and automatically runs callbacks every tick, which is why this route is convenient. ([Docs.rs][3]) Option B — Bevy 0.19+: use steamworks directly Bevy 0.19 was released on June 19, 2026, while the plugin docs above still show Bevy 0.18 dependencies. ([Bevy][4]) For a Bevy 0.19 project, I would integrate the lower-level steamworks crate directly until your chosen Bevy Steam plugin catches up. The steamworks crate is the Rust binding layer for the Steamworks SDK, and Valve’s API docs also note that callbacks should be pumped regularly, ideally once per render frame. ([Docs.rs][5]) 2. Local Steam testing When running outside the Steam client, create this file next to your executable: Contents: Use 480 for Valve’s SpaceWar test app during early local testing, then replace it with your actual AppID. Do not ship steamappid.txt in your Steam depot; Valve says it is for development, and Steam supplies the AppID automatically when launched through Steam. ([Steamworks][1]) Your local test folder should look roughly like this: For Linux: For macOS, prefer a proper .app bundle if you are shipping macOS; Steam’s docs note that launching a macOS app bundle is generally preferred, especially for correct behavior on Apple Silicon. ([Steamworks][6]) 3. Build Bevy for release In Cargo.toml, use release optimizations similar to Bevy’s official setup guidance: Bevy’s docs recommend release-mode optimization like codegen-units = 1 and lto = "thin" for better runtime performance, with longer compile times as the tradeoff. ([Bevy][7]) Build: Do not ship Bevy’s dynamiclinking development feature unless you intentionally want to package the Bevy dynamic library. Bevy’s docs specifically say shipping with dynamiclinking is not recommended because it requires including libbevydylib, prevents some optimizations, and can increase game size. ([Bevy][7]) 4. Package your Bevy assets correctly Bevy’s AssetServer defaults to loading from an assets folder, and the file asset reader’s base path is normally the executable’s parent directory. ([Docs.rs][8]) So your Steam depot should usually include: If you need a different layout, configure AssetPlugin::filepath; Bevy exposes that field for changing the default asset path. ([Docs.rs][9]) 5. Create Steam launch options, depots, and packages In Steamworks, configure these before uploading: 1. General Installation Settings: add at least one launch option pointing to your executable. 2. Depots: create one depot per platform if needed, for example Windows, Linux, macOS. 3. Packages: make sure your depots are included in the Developer Comp package and any public store packages, or testers/customers will not be able to download them. Valve’s SteamPipe setup docs explicitly call out launch options, depots, publishing changes, and adding depots to packages as required setup steps. ([Steamworks][6]) A simple depot strategy: Steam depot OS filtering can be set per depot: OS, language, architecture, and DLC rules are configurable on the Depots page. ([Steamworks][10]) 6. Upload with SteamPipe In the Steamworks SDK, put your files under tools/ContentBuilder/content, and your build scripts under tools/ContentBuilder/scripts. Valve’s docs describe ContentBuilder/content as the place for game files and ContentBuilder/scripts as the place for depot/app build scripts. ([Steamworks][6]) Example appbuild1234560.vdf: Upload: Valve’s example uses the same steamcmd +login ... +runappbuild ... +quit flow and explains that, after upload, Steam creates a build ID you can set live on a branch. ([Steamworks][6]) 7. Test on a private branch first Use a password-protected beta branch for internal testing. Steam branches are specific public or private builds of your app; testers can opt into them through the Steam client, and you can set uploaded builds live for a chosen branch. ([Steamworks][11]) Recommended branch setup: For unreleased games, Steam also supports Steam Playtest and release override keys for external testing. ([Steamworks][12]) 8. Steam Deck / SteamOS checklist for Bevy For a Bevy game, test these early: Valve’s Steam hardware compatibility criteria include controller support, correct glyphs, controller-friendly text input, playable default performance, no blocking launchers, and Steam Deck resolution/text re…