Skip to content

How to put an RPG Maker game on Steam

5 min readBy Eduardo Orellana · · Updated

RPG Maker MZ and MV games ship on Steam as a desktop deployment: use the editor's Deployment for Windows (and macOS if you want it), optionally excluding unused files and encrypting images and audio, test the exported folder on a machine without RPG Maker, then upload it with SteamPipe with a launch option pointing at Game.exe. The game runs on Steam as it is. Steam features such as achievements are not built in: they come from community Steamworks plugins built on Greenworks, which only work with specific NW.js versions, so follow the plugin's own version table exactly. Steam Deck players get the Windows build through Proton.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

An RPG Maker game is a web game in a desktop wrapper

OMORI was made in RPG Maker MV and sold well enough on Steam to reach consoles; RPG Maker games have been on Steam for over a decade. So the obvious question, whether an RPG Maker game can be a real Steam release, was answered long ago. The useful questions are practical: how to package it, how to add Steam features, and how to make a page that does not look like every other RPG Maker game.

The packaging answer follows from how the engine works. RPG Maker MV and MZ games run on JavaScript inside NW.js, a desktop wrapper around Chromium. That makes shipping to Steam easy (deploy the folder, upload it) and makes Steam features a plugin's job, through Greenworks, the community bridge between NW.js and Valve's Steamworks SDK.

Sources: NW.js, Greenworks (Greenheart Games) on GitHub, Wikipedia: Omori (video game).

Which RPG Maker you have changes the route

  • MV and MZ run on JavaScript in NW.js; everything below applies.
  • Older versions (VX Ace, XP, 2000 and 2003) run on their own Windows runtimes rather than NW.js. They ship to Steam as a Windows folder too, but Steam features need tools specific to those runtimes, and Steam Deck players run them through Proton.
  • RPG Maker Unite runs inside Unity, so it ships like any Unity game, with Unity's Steamworks libraries; see Unity games on Steam.

Whichever you use, the Steamworks side, the store page, the fee, the reviews and the upload, is the same for every engine.

Deploying the game

RPG Maker MZ's Deployment exports packages for Windows, macOS and web browsers. For Steam, the Windows deployment is the one that matters; macOS is optional. Its options:

  • Exclude Unused Files shrinks the package by leaving out unused files from the img, audio and effects folders. Files a plugin loads by name can be excluded by mistake; RPG Maker's own MaterialBase plugin can mark them to keep.
  • Encryption of image and sound files, with a key you enter. Encrypted files can no longer be used in the project folder, so keep an unencrypted copy.
  • macOS can ship the exported folder or the Game.app inside it.

Deploy to a clean, empty folder every time, and never upload the project folder itself.

Shipping on Steam, step by step

  1. Steamworks first: pay the $100 Steam Direct fee, create the app, and fill in the store page; a first title waits 21 days after the fee before it can release.
  2. Deploy for Windows to a clean folder, with Exclude Unused Files if your plugins allow it.
  3. Test the deployed Game.exe on a machine that has never had RPG Maker installed, from start to credits, with a controller as well as the keyboard.
  4. Create a depot for Windows and a launch option pointing at Game.exe.
  5. Upload the folder with SteamPipe and set the build live on the default branch. See uploading a build with SteamPipe.
  6. Submit the build for review, which usually takes 3 to 5 business days.

Valve's Steamworks documentation: Steam Direct Fee, Onboarding, Review Process, Uploading to Steam.

Steam achievements and other features

RPG Maker's own achievement plugins track achievements inside the game, not on Steam. For real Steam achievements, the overlay, cloud saves or stats, use a community Steamworks plugin built on Greenworks. Three things decide whether it works:

  • The NW.js version. Greenworks is compiled against specific NW.js versions, and community reports pin some plugins to older NW.js builds. The plugin's documentation names the build to use; replace the deployment's NW.js files with it exactly.
  • The Greenworks binaries for your platform, shipped beside the game as the plugin instructs, with Valve's steam_api library.
  • Steamworks setup: create and publish the achievements and stats in Steamworks before testing them, with API names matching the plugin's calls.

Test from the Steam client with your real App ID; achievements set from a game launched outside Steam may not register.

Sources: Greenworks (Greenheart Games) on GitHub, Steamworks: Stats and Achievements.

Steam Deck and controllers

RPG Maker's deployments have no native Linux build, so Steam Deck players run the Windows build through Proton. RPG Maker MV and MZ support gamepads, which helps, but check Valve's Deck criteria anyway: every menu reachable with the controller, glyphs that match, and the smallest text at least 9 pixels tall at 1280x800. RPG Maker's default fonts at the default resolution can fall short of that; test on a Deck or at that resolution before requesting a review. See Steam Deck Verified.

Valve's Steamworks documentation: Steam Deck and Steam Machine Compatibility Review.

Standing out on the store page

RPG Maker's bundled assets are licensed for games made with the engine, and many Steam games use them. Players recognise them instantly, which is the problem: a capsule and screenshots built from default tiles and characters read as "another RPG Maker game" before anyone reads the hook. Custom key art for the capsule, custom character portraits and screenshots of what is unique about your game do more for the page than anything in the engine. Lead the tags with the specific sub-genre, such as Psychological Horror, JRPG or Narrative, rather than RPG alone.

Mistakes that cost a launch

  • Uploading the project folder instead of a clean deployment, shipping editor files and unencrypted assets.
  • A plugin's files excluded by Exclude Unused Files, crashing on the first map that needs them.
  • A mismatched NW.js for the Steamworks plugin, so the game launches but Steam features silently fail.
  • Testing only on the development machine, where RPG Maker's runtime hides missing files.
  • Default assets on the capsule.

Where Flockbay fits

Flockbay builds games on the official Godot engine, and its AI can read an RPG Maker MV or MZ project's data files and rebuild it in Godot 4, where Steam features come through GodotSteam instead of NW.js plugins. Our RPG Maker to Godot page covers that route. Building in Flockbay is free.

Questions

Can I sell an RPG Maker game on Steam?
Yes. Deploy it for Windows, upload the folder with SteamPipe, and pass Valve's review. RPG Maker games have shipped on Steam for over a decade, OMORI (RPG Maker MV) among them.
Does RPG Maker support Steam achievements?
Not built in. Use a community Steamworks plugin built on Greenworks, with the NW.js version the plugin specifies, and create the achievements in Steamworks first.
Can I use RPG Maker default assets in a Steam game?
The bundled assets are licensed for games made with that RPG Maker, and many Steam games use them. Players recognise them, though, so custom key art and screenshots of what is unique help the page stand out.
Do RPG Maker games run on Steam Deck?
Through Proton, using the Windows build. Check controller navigation and text size at 1280x800 against Valve's Deck criteria before requesting a review.

Flockbay builds games for free on Godot, and can rebuild an RPG Maker project in Godot 4.

Download Flockbay free

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

Flockbay

The free AI game maker for Windows, macOS and Linux.