# How to put a GameMaker game on Steam

GameMaker uses YoYo Games' official, open-source Steamworks extension (GMEXT-Steamworks). Import it (the Marketplace build is the recommended one; GitHub has newer, less tested releases), download the Steamworks SDK from Valve's partner site and extract it to a short path, then in the extension's options set the SDK path and your App ID. The extension calls steam_init itself; call steam_update every step from a persistent object and steam_shutdown when the game ends. Run with the Steam client open and signed in, build for Windows (and Ubuntu for a native Linux build), and upload with SteamPipe. Selling commercially needs GameMaker's Professional licence, a one-time purchase; the free tier is for non-commercial use.

Source: https://flockbay.com/blog/gamemaker-steam/ · Updated 2026-10-25

## One extension, maintained by YoYo Games

GameMaker games have shipped on Steam for years, and the engine has a long list of commercial hits behind it. Its Steam support does not live in the IDE itself but in an official extension, GMEXT-Steamworks, which is open source and maintained by YoYo Games. It covers far more than achievements: stats and achievements, leaderboards, lobbies and matchmaking, cloud saves, user-generated content (the Workshop), Steam Input, the overlay, DLC, inventory, networking and more.

The obvious worry with any engine is whether Steam integration is a fragile community add-on. For GameMaker it is not: the extension comes from the engine's own maker, and its setup guide is written for IDE and runtime 2022.6 and later. Most of the work is in Steamworks, not in GML: defining achievements, stats and depots, which is the same for every engine.

Sources: [GMEXT-Steamworks wiki: Home](https://github.com/YoYoGames/GMEXT-Steamworks/wiki), [GameMaker: Open source extensions](https://gamemaker.io/en/blog/open-source-extensions), [GMEXT-Steamworks on GitHub](https://github.com/YoYoGames/GMEXT-Steamworks).

## Check your licence first

Since GameMaker's November 2023 pricing change, the engine is free for non-commercial use and needs the Professional licence, a one-time purchase (listed at $99.99, with regional pricing), to make money from a game on any platform short of the consoles, Steam included. Console exports need the Enterprise subscription. Developers who bought an older permanent GameMaker Studio 2 licence for a platform can still release commercially with that runtime. Check GameMaker's current terms before you sell; this is general information, not legal advice.

Sources: [GameMaker: November 2023 Pricing/Terms Change FAQ](https://gamemaker.io/en/help/articles/november-2023-pricing-terms-change-faq).

## Setup

1. **Import the Steamworks extension**, preferably from the GameMaker Marketplace; GitHub releases are newer but less tested.

2. **Read the setup guide** in the extension's Included Files (also on its wiki).

3. **Download the Steamworks SDK** from Valve's partner site and extract it somewhere short, such as C:\steamworks\sdk.

4. **Open the extension** in the Asset Browser: set the SDK path in the build options and your App ID in the application options.

5. **Run with Steam installed, running and signed in.**

The extension's wiki notes it is meant for developers already accepted onto Steam, through a publisher or self-publishing with Steam Direct, since the App ID and achievements come from your Steamworks account.

Sources: [GameMaker Help: Steamworks SDK, setting up your games](https://gamemaker.io/en/help/articles/steamworks-sdk-setting-up-your-games), [GMEXT-Steamworks wiki: Setup Guide](https://github.com/YoYoGames/GMEXT-Steamworks/wiki/Guides), [GMEXT-Steamworks wiki: Home](https://github.com/YoYoGames/GMEXT-Steamworks/wiki).

## The three calls that keep it alive

GMEXT-Steamworks splits management into three functions. steam_init is called automatically by the extension when the game starts. steam_update is required: call it every step, from a persistent controller object that exists in every room, so callbacks for achievements, lobbies and the overlay are processed. steam_shutdown is required when the game ends. A missing steam_update is the GameMaker equivalent of a Godot game that stopped running callbacks: everything initializes, and then nothing Steam sends back ever arrives.

Sources: [GMEXT-Steamworks wiki: Management](https://github.com/YoYoGames/GMEXT-Steamworks/wiki/Management).

## What to use first

In rough order of value for an indie game:

Sources: [GMEXT-Steamworks wiki: Home](https://github.com/YoYoGames/GMEXT-Steamworks/wiki).

| Module | What it gives players | Set up in Steamworks first? |
| --- | --- | --- |
| Stats and Achievements | Achievements on the store page and in the library | Yes: define API names, publish |
| Cloud | Saves that follow players between PCs and the Deck | Yes: quota, or Auto-Cloud paths |
| Overlay | Steam's overlay, invites, web pages | No |
| Leaderboards | Scores against friends and the world | Yes, or create from code |
| Lobbies and Matchmaking | Friends joining through Steam | No |
| UGC | Steam Workshop content | Yes: Workshop enabled |
| Input | Steam Input controller configurations | Yes: default configuration |

Modules as the GMEXT-Steamworks wiki lists them, read 18 October 2026; the order is practice.

## Shipping

- **Build for Windows**, and for Ubuntu if you want a native Linux build for the Steam Deck; otherwise the Windows build runs on the Deck through Proton.

- **No DRM wrapper needed**: GameMaker's runner uses Steam's restart-if-necessary check, relaunching through Steam when started outside it.

- **Upload the build with SteamPipe** and set it live; see our [SteamPipe guide](/blog/steampipe-upload-build/).

- **Older projects**: some Steam functions became asynchronous in newer versions of the extension; check its migration notes before upgrading a project mid-development.

- **Test the exported build** from the Steam client on a machine without GameMaker installed.

Sources: [GMEXT-Steamworks: steam_init_new.cpp](https://github.com/YoYoGames/GMEXT-Steamworks/blob/main/source/Steamworks_gml/extensions/steamworks/steamworks_cpp/GMLSteam/steam_init_new.cpp), [GameMaker Help: Steamworks SDK, setting up your games](https://gamemaker.io/en/help/articles/steamworks-sdk-setting-up-your-games), [Steamworks: Uploading to Steam](https://partner.steamgames.com/doc/sdk/uploading), [GMEXT-Steamworks wiki: Setup Guide](https://github.com/YoYoGames/GMEXT-Steamworks/wiki/Guides).

## Steam Deck and controllers

GameMaker's Ubuntu export gives you a native Linux build, which Valve tests first when reviewing a game for Steam Deck compatibility, falling back to the Windows build through Proton. Either way, Verified status depends on the same things for every engine: every menu reachable with the controller, prompts that show controller glyphs while a controller is in use, controller text entry, the smallest text at least 9 pixels tall at 1280x800, and 30 fps at 800p in default settings. Pixel-art GameMaker games usually clear the performance bar easily; text size and menus that assume a mouse are where they fall short. The extension's Input module exposes Steam Input if you want Steam's own controller configurations. See [Steam Deck Verified](/blog/steam-deck-verified/).

Valve's Steamworks documentation: [Steam Deck and Steam Machine Compatibility Review](https://partner.steamgames.com/doc/steamhardware/compat).

## Before you upload: a checklist

- [ ] Professional licence active for commercial release.

- [ ] Real App ID in the extension options, not a test ID.

- [ ] steam_update called every step from a persistent object; steam_shutdown at exit.

- [ ] Achievements, stats and leaderboards defined and published in Steamworks.

- [ ] Windows build tested from the Steam client on a clean machine; Ubuntu build too if you ship it.

- [ ] Controller-only playthrough done, text checked at 1280x800.

- [ ] One depot per platform, with a launch option for each executable.

## When it does not work

- **Steam functions return false or nothing**: the Steam client is not running or signed in, or the App ID is not set in the extension options.

- **Build fails on the extension**: the SDK path is wrong or too long; keep it short and without spaces.

- **Achievements never unlock**: they are not defined and published in Steamworks, or steam_update is not being called.

- **Overlay missing**: the game was not started through Steam; launch it from the Steam client while testing.

Sources: [GMEXT-Steamworks wiki: Setup Guide](https://github.com/YoYoGames/GMEXT-Steamworks/wiki/Guides).

## Where Flockbay fits

Flockbay builds games on the official Godot engine, and its AI can read a GameMaker project's GML and rooms and rebuild it in Godot 4, where Steam features come through GodotSteam. Our [GameMaker to Godot](/gamemaker-to-godot/) page covers that route. Building in Flockbay is free.

## Questions

### Does GameMaker support Steam achievements?

Yes, through YoYo Games' official GMEXT-Steamworks extension, which also covers stats, leaderboards, lobbies, cloud, Workshop and the overlay.

### Do I need a paid GameMaker licence to sell on Steam?

Yes. Since November 2023 GameMaker is free for non-commercial use, and commercial desktop releases need the Professional licence, a one-time purchase. Check the current terms.

### Where do I set my Steam App ID in GameMaker?

In the Steamworks extension's options: open the extension in the Asset Browser, set your App ID in the application options and the Steamworks SDK path in the build options.

### Do GameMaker games run on Steam Deck?

Yes, as an Ubuntu (Linux) build or a Windows build through Proton. Check controller support and text size against Valve's Deck criteria.

Download Flockbay free: Flockbay builds games for free on Godot, and can rebuild a GameMaker project in Godot 4. https://flockbay.com/free-ai-game-maker/

Related: [The indie game publishing guide](/blog/indie-game-publishing-guide/), [Upload a build with SteamPipe](/blog/steampipe-upload-build/), [How to publish a game on Steam](/blog/how-to-publish-a-game-on-steam/), [GameMaker to Godot](/gamemaker-to-godot/)
