port a game to steam
Port a game to Steam
Steam takes a desktop executable, a depot, and a store page. This is the checklist for getting any game from another platform onto it.
Porting a game to Steam means producing a desktop build of a game you own and publishing it through Steamworks. Steam does not run mobile, console, or browser builds, so the port is a real desktop version, not a wrapper around the old one.
The job has two halves. Engineering: a Windows build at minimum, ideally macOS and Linux as well, with settings, controller support, saves, and stability. Business: a Steamworks partner account, identity and tax verification, a one time app fee, a store page, and a two week minimum between store page launch and release.
Summer Engine builds desktop, mobile, web, and console from one project. Games are written in C++ and GDScript, with C# available on all native targets. You own the project and pay no royalties, so the only revenue share is the one Valve takes.
The Steamworks process in order
Sign up as a Steamworks partner, complete identity verification, tax forms, and bank details. Pay the one time 100 USD app submission fee, which is recoupable once the app earns 1000 USD. Fill in the store page with description, screenshots, a trailer, tags, and system requirements. Submit the store page for review. Create depots, upload a build with SteamPipe, set launch options, and run a build review. Steam requires the store page to be live at least two weeks before release.
What a desktop build has to include
Windowed and fullscreen modes, common resolutions, vsync and frame rate options, audio sliders, and remappable keyboard and mouse controls. Gamepad support through Steam Input, which also covers Steam Deck. Saves written to the user data directory so updates and cloud sync do not destroy them. Graceful handling of alt tab, multiple monitors, and ultrawide aspect ratios. Clean exit and no orphaned processes. These are the items players complain about in reviews when they are missing.
Steam features worth wiring up
Steam Cloud through Auto Cloud keeps saves across machines and costs almost nothing to add. Achievements and stats are defined in the partner site and unlocked from code. Steam Input handles controller remapping, including Deck. Rich Presence, screenshots, and the overlay come mostly for free. Workshop, leaderboards, and multiplayer through the Steam networking APIs are larger investments and should be decided before launch, not after.
Common blockers on first releases
Missing or incorrect tax information delays payment, not release. A store page submitted late pushes the release date because of the two week rule. Builds that write saves next to the executable break for players. Antivirus false positives hit unsigned executables, so code sign Windows builds. Missing controller support draws refunds from Deck users. Plan a closed beta branch on Steam before launch so these show up early.
Frequently asked questions
How much does it cost to publish on Steam?
A one time 100 USD app submission fee per title, recoupable after the game earns 1000 USD. Valve then takes a revenue share on sales. Summer Engine charges no royalties.
How long does Steam review take?
Build and store page reviews typically take a few business days each. The bigger constraint is the rule that a store page must be live at least two weeks before the release date.
Can I put a mobile or browser game on Steam?
Only as a desktop build. You need a real Windows, macOS, or Linux executable, with input, resolution, and session design reworked for desktop players.
Do I need Windows, macOS, and Linux builds?
Windows alone is enough to launch and is where most sales are. macOS and Linux depots can be added later. A Linux build also improves Steam Deck behavior, though Proton runs many Windows builds on Deck.
Does Summer Engine take a cut of Steam sales?
No. There are no royalties and no revenue share. You own the project and the revenue, minus whatever Valve charges.
Keep exploring
More ways to build with Summer Engine
AI game maker
The hub for making complete 2D and 3D games by describing them.
OpenPort a game to Steam Deck
Steam Deck runs your existing Steam build. The port is a compatibility pass: controller first input, readable text, and a power budget.
OpenPort a 3DS game to Steam
Rebuild a 3DS game you own in Summer Engine, then export a Windows, macOS, or Linux build and publish it on Steam.
OpenPort a 3DS game to Steam Deck
Rebuild a 3DS game you own in Summer Engine, then ship a Steam build that plays well on a 1280x800 handheld with gamepad only input.
OpenHow to port a 3DS game
The full process, in order: rights, asset inventory, rebuild, screen and input redesign, testing, export, and store submission.
OpenBring a 3DS game to Steam
The release side of a 3DS port: rights, Steamworks setup, store page, builds, review, wishlists, pricing, and launch day.
OpenPort a Nintendo DS game to Steam
Rebuild a DS game you own in Summer Engine, then export a desktop build for Steam. Mouse covers the stylus, monitors cover both screens.
OpenPort a Wii game to Steam
Rebuild a Wii game you own in Summer Engine, then export a desktop build for Steam. Pointer becomes mouse. Motion becomes a design decision.
OpenPort a PSP game to Steam
Rebuild a PSP game you own in Summer Engine and export a desktop build for Steam. One screen already fits. One analog nub does not.
OpenPlatformer templates
Start from a ready-made project and describe your changes.
BrowseBrowse all game templates
Start from a ready-made project and describe your changes.
BrowseStart building your game now
Download Summer Engine, describe what you want, and watch it come together. Free to start, no coding required.