How to publish your vbgnt game to Steam

Steam does not take the web build. That is the first thing to understand, and it decides most of the work: your game currently exists as a WebAssembly bundle running in a browser, and Steam wants native executables for Windows, and ideally Linux as well. Everything below follows from that.

The good news is that a vbgnt game is an ordinary Godot 4 project, and Godot exports desktop builds from the same project with no code changes. The work is real but it is not a rewrite.

What it costs and how long it takes

Two numbers to plan around. The Steam Direct fee is $100 per product, not per account, and it is recoupable against the payment made once that product has earned $1,000 in adjusted gross revenue. And after you pay it there is a mandatory 30-day wait before you can release, which Valve uses to verify your identity. Both figures were current in August 2026.

So the realistic timeline from "I want this on Steam" to "it is on Steam" is about five weeks, and the per-product fee means shipping every game your studio makes is a habit that gets expensive fast. Pick the one that earned it.

Step 1: get the project onto your machine

In the studio, open the game, go to the Files tab and download the project zip. Install Godot 4 and its export templates, open the project, and confirm it runs in the editor before changing anything. If it runs there, the desktop export is mostly configuration.

Step 2: make it a desktop game

The build was shaped for a browser tab. Four things usually need attention, and none of them are hard:

• Hide the touch controls. vbgnt games show on-screen controls when DisplayServer.is_touchscreen_available() returns true, so on a desktop they should already be hidden. Verify it rather than assume it, because a stray always-visible joystick reads as unfinished.
• Add a way to quit. A browser tab has a close button and a desktop window needs your game to provide one. A pause menu with Quit, and Escape doing something sensible, is the whole fix.
• Handle windowing. Set a sane default resolution, support fullscreen toggling, and make sure the UI survives an ultrawide monitor. The web build only ever had one aspect ratio to worry about.
• Check where saves go. Anything written to user:// works on both targets. Anything that assumed browser storage directly does not.

Leave the renderer alone. vbgnt games export with the Compatibility renderer so they run in browsers, and Compatibility works fine on desktop. Switching to Forward+ for better lighting is a real option, but it is a visual change that needs testing rather than a free upgrade.

Step 3: export Windows and Linux

Add export presets for Windows Desktop and Linux, and export both. The Linux build is worth doing even if you think nobody uses it, because it is what gives you a good story on Steam Deck. A game that runs natively there avoids the entire Proton compatibility question.

Test the exported binaries by running them, not by trusting the export. Missing resources and shader failures show up at launch and nowhere earlier.

Step 4: Steamworks paperwork

Register as a Steamworks partner, then work through the identity, tax and banking forms. This part is genuinely tedious and it is where the 30-day clock starts. Do it early, in parallel with everything else, rather than treating it as the last step.

Then create the app, pay the $100, and complete the content survey that determines your store page's age rating and content warnings. Answer it accurately. Getting caught understating content is a much bigger problem than the warning itself.

Step 5: the store page

This is where most of the actual effort lands, and it matters more than the build. Steam wants a specific set of capsule images at specific sizes (header, small capsule, main capsule, vertical, library art and a page background), at least five screenshots, and a trailer.

Use the cover art the studio generated as your starting point rather than gameplay screenshots. Generated key art tends to read well at capsule size, which is exactly where a screenshot of a small game does not.

Write the short description as the mechanic, not the genre. "You can hold the lamp or use your hands, never both" tells someone whether they want it. "An atmospheric platformer" does not.

Step 6: upload the build

Steam builds go up through SteamPipe, using the ContentBuilder tools in the Steamworks SDK. You define a depot per platform, point a build script at your exported folders, and run it. The first configuration is fiddly; every upload after that is one command.

Set a default branch, install the build on your own account through Steam, and play it from the Steam client before you go anywhere near a release date. Builds that work standalone and fail through Steam are usually a depot path problem.

Do you need the Steamworks SDK in the game?

No, and this surprises people. A game can ship on Steam with no Steam integration at all. It just will not have achievements, cloud saves, the overlay, or rich presence.

If you want those, GodotSteam is the community GDExtension that binds the Steamworks API into Godot. It is well maintained and it works, but it is a genuine addition to the project rather than a checkbox. For a first release, shipping without it is a reasonable decision that you can reverse later.

Steam Deck is worth ten minutes

A vbgnt game is unusually well positioned here, because the studio wires full gamepad support into every game as a requirement. That is most of what Deck compatibility asks for.

The rest is small: make sure text is readable at 1280x800, that the game does not require a mouse for anything essential, and that it launches without a launcher. Ship the Linux build and you are close to a Verified submission for free.

The honest read

Steam is the friendliest of the three real stores to a small generated game. There is no minimum-functionality guideline waiting to reject you, no tester quota, and no Mac required. If your game is finished and yours, it will get on.

What Steam will not do is find an audience for it. The store has more games than anyone can look at, and a page with no wishlists at launch stays that way. The $100 buys you a shelf, not a spotlight.

Which is the argument for shipping to itch.io first. It is free and takes minutes, and if a game does nothing there, the 30 days and the $100 are unlikely to change its mind.