Getting a demo onto Steam involves three main phases: setting up Steamworks and integrating it into Godot, creating a demo depot in the Steamworks backend, and exporting and uploading your build. This guide covers each step in detail, from installing the GodotSteam plugin to getting your demo files live via SteamPipe.
Step 1: Prerequisites — Your Steamworks Partner Account
Before touching Godot, you need the foundational Steamworks setup. All configurations and IDs originate there, so this comes first.
Steamworks Partner Account: Sign up and complete all required paperwork at the Steamworks partner site.
Steam Direct Fee: Pay the US$100 fee per app. This fee is recoupable after your game earns US$1,000 in Adjusted Gross Revenue.
Your App ID: Paying the fee generates your unique App ID. This number is the central identifier for your game on Steam — your store page, depots, and builds all depend on it. You cannot fully integrate Steam features or ship a build without it.
Godot has no built-in Steam support. The standard solution is GodotSteam, an open-source integration that provides a Steam singleton to access the Steamworks API.
Download: Get the GodotSteam GDExtension plugin from the Godot Asset Library or the GodotSteam GitHub releases page. Ensure you pick the version that matches your Godot minor version (e.g., 4.3.x).
Install: Add the plugin files to your project's addons/ folder.
Enable: Go to Project > Project Settings > Plugins and enable the GodotSteam plugin. You may need to restart the editor.
After enabling the GodotSteam GDExtension Updater in your Project Settings, you need to configure your app ID. This tells the plugin which Steam game to export.
Go to Project > Project Settings.
In the left sidebar, scroll down to the Steam section and select Initialization.
Enter your App ID in the App ID field (currently showing 0). For a Demo, you must put in your Demo ID — the Demo ID is separate from the App ID.
Set the App type to Demo if you are exporting a demo. For a final game, the App type should be Game.
Check "Embed Callbacks." This lets GodotSteam handle the calling of frames automatically in the background and prevents a very common bug where Steam features stop working if you pause the game or switch scenes.
Check "Initialize on Startup." This lets GodotSteam start the Steam API automatically before your first scene even loads.
To verify it worked:
i. Make sure the Steam Desktop Client is open and logged into your account (the one with Steamworks access).
ii. Create a simple script on any node in your game to test the connection:
func _ready():
if Steam.isSteamRunning():
print("Steam is running! Logged in as: ", Steam.getPersonaName())
else:
print("Steam is NOT running.")
iii. Run your game from the Godot editor and check the Output panel at the bottom. If it prints your Steam username, you are successfully connected.
Before exporting, make sure you set up the correct icon — by default, Godot games use the Godot icon. You need to change it in two places to cover both the running game and the exported file:
Taskbar/Window Icon (when the game is running): Go to Project > Project Settings > Application > Config. Ensure Advanced Settings are enabled. Find icon and change the path to where your icon is stored.
Exported File Icon (.exe): Go to Project > Export and select your Windows Desktop preset. In the Application section, find the Icon field and select your image.
In Godot, go to Project > Export, then add the preset for Windows.
If you haven't already set up a Windows Desktop preset, click Add... and select Windows Desktop.
Look at the Export Path field near the top — it is currently empty.
Click the folder icon on the far right of that field.
Create a new, empty folder somewhere easy to find (e.g., C:\Builds\DemoGame_Windows\).
Name the file DemoGame.exe and click Save.
Click "Export Project..." at the bottom of the window. (Do not click Export PCK/ZIP.)
A popup will ask: "Do you want to export with debugging enabled?" Click No — you want a Release build for Steam. Then finish the export.
You need to create a Demo page for your game. So you need a page for your main game, and a page for your demo. Take the following steps:
Go to Associated Packages & DLC.
Click the "add demo" button to get the new ID for the demo.
Go to the admin page of your demo. This looks very similar to the admin page of your main game.
To get there:
Look at the top left of your screen, just above "YourGameName Demo." You will see a small path: Steamworks > App Admin.
Click directly on the words App Admin.
Once on the admin page, you will need to go through the same setup steps as were done for the main game. You need an App ID and a Depot ID.
Hover over SteamPipe.
Select Depots from the dropdown.
Click the button to Add a Depot for your demo.
Note the Depot ID that is generated for it — you need this for your upload script.
Crucial: Go to the Publish tab at the far right of that same menu bar, and click Prepare for Publishing to save the new depot.
Note: You can also create your depot by going to your build page at https://partner.steamgames.com/apps/builds/, then hovering over SteamPipe and selecting Depots.
To upload your build, you need to use the SteamPipe Build Uploader. To do this, first you need to get the Steam SDK.
Steamworks SDK: Download this from your Steamworks partner site. It contains the steamcmd tool you will use for uploading builds and the redistributable libraries (like steam_api64.dll) that you will need to ship with your game.
If you are already logged in on the App Admin page, there are two main ways to get it:
Download Page: https://partner.steamgames.com/downloads/list
Direct File Link: https://partner.steamgames.com/downloads/steamworks_sdk.zip
Once the .zip file finishes downloading:
Extract it: Unzip the contents to a short, easy-to-find path on your drive, such as C:\SteamworksSDK\ or C:\steamworks_sdk.
Locate steamcmd: Inside the extracted folder, navigate to the tools folder. You will find steamcmd.exe there, which is the command-line tool you will use later to upload your Godot builds via SteamPipe.
After you have extracted the files, go to sdk > tools > ContentBuilder.
In the ContentBuilder, create a folder for each of your Depots.
Take all the files that you used to build the game from your game engine (Unreal Engine, Godot, Unity, etc.) and paste the files into the folder you just created.
Next, find a zip file called SteamPipeGUI.zip in the tools folder.
Extract all the files from SteamPipeGUI.zip. This can be extracted to the tools folder.
Double-click and open SteamPipeGUI.exe. You will need to fill in some information.
App ID: Enter your Demo App ID, visible in the background under "Apps Included."
Build Description: Enter something like Demo Build v1 (this is just for your own reference).
Depot ID: Enter your Demo Depot ID, visible in the background under "Depots Included."
Build Path: Click "Browse..." and select the folder on your computer that contains all the files for your demo (your .exe and game assets).
Steamworks SDK ContentBuilder Path: Click "Browse..." and locate the ContentBuilder folder inside the Steamworks SDK you downloaded (usually found at ...\sdk\tools\ContentBuilder).
Steam Login / Steam Password: Enter your Steamworks developer account credentials.
31. If this is the first time uploading a game, you need to click the "generate vdfs" button. Then press Upload.
A command prompt interface will open. It will do some updates, then ask you for a Steam Guard code. You will get the code from Steam in your email. Enter the code in the command prompt interface, then press Enter.
The command prompt will eventually disappear, and the SteamPipeGUI will give a message stating that uploading was a success. You can then close the SteamPipeGUI.
32. Go to your builds section: https://partner.steamgames.com/apps/builds/
Go to Installation and tell Steam how to launch your game.
If you are publishing your depot for Windows, make sure to select Windows for the operating system. The rest of the Installation section is self-explanatory.
33. This is the most critical step to make the demo downloadable.
In the "Showing last 50 builds" section at the bottom, locate your new build.
In the "Set build live on branch..." column, click the dropdown and select default.
Click the "Preview Change" button. You'll see a summary; if everything looks correct, confirm the change by clicking "set build to live."
Then go to the Publish tab and publish your changes.
Note: This does not mean everyone can play the demo yet. It only means that those with access rights can play it — and right now, the only person with access rights is you. So only you can access your game.
34. Send your game for Steam to review. You have to wait 3–5 days for this review.
Partner with Impulse Response Enterprises Ltd
Impulse Response Enterprises Ltd, is a technology-oriented economic research organization. We are up to the times; technology has a strong place with policy. We do economic research, econometric and mathematical analysis, strategic plans, action plans, and economic evaluations. We build machine learning models for economic analysis, develop websites and React Native apps, and create games in Unreal Engine 5 and Godot.
👉 Contact us today at impulseresponseenterprisesltd@gmail.com or visit www.impulseresponseenterprises.cc to schedule your consultation and start your journey toward digital excellence!