How to Publish a Game on Steam in 2026 [Full Guide]

To publish a game on Steam, you need to join Steamworks, pay the $100 Steam Direct fee for your game, create a store page, upload a working build, pass Valve's review, and release the approved game yourself. You cannot complete the process in a weekend: Valve requires a 30-day waiting period after the fee is paid, and a new game's Coming Soon page must be public for at least two weeks.

The dashboard contains many settings, but the full process becomes manageable when you complete it in the right order. This guide explains each step, what Valve checks, and what you should prepare before choosing a release date.

Steam Publishing Cost and Timeline

The two waiting periods can overlap. You do not always need to add 30 days and 14 days together. However, account verification, asset creation, review feedback, and build fixes can extend the schedule. For a first release, planning six to eight weeks is safer than aiming for the theoretical minimum.

How to Publish a Game on Steam Step by Step

1. Prepare a Game That Steam Can Launch

Before opening Steamworks, prepare a downloadable build that runs on every operating system you plan to list. If your store page says the game supports Windows and macOS, Valve expects the submitted build to launch correctly on both.

Test the game on a clean computer that does not contain your engine, development tools, or local project files. This can reveal missing DLLs, incorrect file paths, absent runtimes, save-data problems, and settings that only work on your own machine.

If your project is still a rough prototype rather than a release candidate, finish the core gameplay loop and reduce its scope before starting the Steam setup. Our guide on how to make an indie game explains how to turn a manageable idea into a small but complete playable build.

If your project currently exists as a browser-based or HTML game, submitting a public URL alone is not enough. Steam needs a downloadable build that it can install and launch on the operating systems listed on your store page.

This is where AI game maker SoonLab can shorten the early development process. Instead of producing only a design concept or static mockup, SoonLab turns your prompt into a playable game with controls, visuals, rules, scoring, and interactive systems. You can play the result immediately and continue improving the gameplay through follow-up prompts. For many small game ideas, the result can already work as a complete game demo.

When the game is ready, SoonLab lets you download it as an HTML file and save it on your device. This gives you a portable version that you can keep, edit, back up, or prepare for distribution outside SoonLab. To release it on Steam, you will still need to package the downloaded HTML game as a desktop application, test the executable, and upload the finished build through SteamPipe. The HTML download is not a Steam-ready executable by itself, but it gives you a working game foundation instead of forcing you to rebuild the demo from scratch.

2. Create a Steamworks Partner Account

Sign in to Steamworks with an existing Steam account and complete the partner onboarding process. You can register as an individual or a legal company, but the name you enter must match the identity and banking documents you use later.

Steam asks you to sign its digital paperwork, provide bank and tax information, and complete identity verification. According to the official Steamworks onboarding guide, this information must be verified before you can fully set up and receive payments for a product.

Use the legal name attached to your bank account. A studio name or public developer name can appear on the store page, but it should not replace the correct legal information during onboarding. Tax verification may also require extra documents, so start this step early.

3. Pay the Steam Direct Fee

Steam charges a $100 USD Steam Direct fee, or its local equivalent, for every new game or application you want to distribute. Taxes such as VAT or GST may be added depending on your country.

The fee is not immediately refundable. Valve states that it is recouped in a later payment after the product reaches at least $1,000 in adjusted gross revenue from Steam Store sales and in-app purchases. Read the Steam Direct fee rules before paying, especially if one person is paying on behalf of a company.

Paying the fee gives the account an app credit that can be activated to create the new product. It also starts the mandatory 30-day waiting period. Pay early enough that this rule does not force you to delay an otherwise finished launch.

4. Create the App and Complete Its Basic Information

Activate the app credit in Steamworks and create your new application. Steam assigns an App ID, which connects the store page, uploaded builds, packages, achievements, pricing, and other settings.

Complete the basic information carefully. Add the game name, supported languages, developers, publishers, genres, tags, supported operating systems, controller support, and features that will actually work at launch. Do not select features you only hope to add later. Valve compares these claims with the submitted build.

You must also complete Steam's content survey. It covers mature content and other material that may affect how the game is displayed. If the game contains pre-generated or live-generated AI content, review the current Steam content survey requirements and disclose the relevant use accurately. You are still responsible for making sure the content is legal and does not infringe another person's rights.

If AI tools helped create your code, visuals, audio, or live game content, our guide to AI games on Steam explains Valve's current policy, disclosure requirements, and the quality concerns that affect AI-assisted releases.

Platform approval and commercial-use rights are separate questions. Before selling the game, check whether an AI-generated game can be used commercially and review the licenses for its code, art, music, and third-party assets.

5. Build the Steam Store Page

Your store page should tell a player what they will do, why the game is interesting, and what the current build includes. Prepare the short description, full description, tags, supported features, system requirements, screenshots, capsule art, library assets, and a trailer if you have useful gameplay footage.

Lead with the playable idea rather than a long story introduction. For example, “Build a moving village while escaping a spreading storm” gives the player a clearer reason to continue than several paragraphs of world history.

Steam has exact dimensions and content rules for each graphical asset. Capsule art must include a readable game name or logo. Screenshots should show real gameplay rather than concept art, award graphics, promotional text, or pre-rendered scenes. Steam currently requires store screenshots to be at least 1920 × 1080 pixels in a 16:9 ratio. Check the current graphical asset specifications before asking a designer to export the final files.

Keep the store page honest. Do not show enemies, levels, multiplayer modes, or other features that are not in the release build. If something is planned for later, label it clearly instead of presenting it as available now.

6. Set the Price, Packages, and Release Date

Choose the game's base price and enter prices for the currencies and regions you want to support. Steam offers suggested currency conversions, but you can review and adjust regional pricing. If a supported currency has no price, customers using that currency cannot buy the game.

Price the game according to its current content, genre, replay value, and nearby alternatives. A low price does not fix a weak store page, while an ambitious price creates expectations for polish, support, and depth.

You can also prepare a launch discount if it fits your plan. Check the latest Steam pricing rules and minimum thresholds before finalizing regional prices or discounts.

7. Submit and Publish the Coming Soon Page

Complete the Store Presence checklist, then click “Mark as ready for review.” Valve normally reviews a store page in three to five business days, but it recommends submitting at least seven business days before you want the page to become public. If the page does not meet the requirements, Valve will send feedback for you to address.

Approval does not make the page public automatically. After it is approved, click “Post as Coming Soon.” A new product's Coming Soon page must remain public for at least two weeks before release.

Do not treat this as an empty waiting period. A public page lets players wishlist the game, visit its Community Hub, and follow development updates. Valve recommends publishing it once the art direction and core feature set are stable enough to represent the final game. Its Coming Soon documentation also notes that wishlisted players receive an email when the game releases.

8. Upload the Game Build with SteamPipe

SteamPipe is Valve's system for uploading and delivering game files. Download the latest Steamworks SDK, create at least one depot for the game's content, and prepare the app and depot configuration files. Then upload the build with SteamCMD or the SteamPipe GUI included with the SDK.

A depot is a group of files delivered under defined conditions. You may use separate depots for different operating systems, languages, or optional content. A simple Windows-only game may need only one main content depot.

After uploading, set the correct build live on a test branch or the default branch, configure the executable and launch options, and install it through the Steam client. The SteamPipe upload guide provides example configuration scripts and the current command format.

Test the Steam-installed version rather than launching the original file from your development folder. Check startup, input, resolution changes, save files, achievements, overlays, multiplayer connections, DLC ownership, and clean uninstallation where relevant.

9. Submit the Build for Review

Once the store page has been submitted, the required build checklist is complete, and a near-final build is on the default branch, mark the build as ready for review. Valve normally takes three to five business days, but asks developers to allow at least seven business days in case changes are needed.

During its review process, Valve checks whether the game launches on every advertised operating system, whether listed features exist in the build, and whether in-game transactions use Steam Wallet. The team also checks that the store page describes the product accurately.

A review is not a full quality certification. Approval does not prove that the game is balanced, bug-free, commercially ready, or appealing to players. You still need your own release testing and feedback process.

10. Release the Game

You can release after the 30-day waiting period has passed, the store page has been public as Coming Soon for at least two weeks, and both the store page and build have been approved.

Open the product landing page in Steamworks and click the green “Release App” button. Steam will show the packages and changes that are about to go live. Review them, follow the confirmation steps, and choose the final option to publish the game.

The game does not release automatically when the review is approved or when the date arrives. A user with the necessary permissions must complete this action. The official Steam release process explains the permissions and final release controls.

Steam Release Checklist

• The Steamworks partner identity, bank details, and tax information are verified.
• The $100 Steam Direct fee has been paid, and the 30-day waiting period has passed.
• The store page describes only current or clearly labeled future content.
• Capsule art, screenshots, descriptions, tags, and system requirements are complete.
• The content survey, including any relevant AI content disclosure, is accurate.
• Prices are entered for every region where the game should be sold.
• The Coming Soon page has been public for at least two weeks.
• The Steam-installed build launches on every listed operating system.
• All advertised features work in the submitted build.
• The store page and build have both passed Valve review.
• The correct build and packages are selected for release.
• A team member with release permissions is available to click “Release App.”

Common Steam Publishing Mistakes

Waiting Until the Game Is Finished to Create the Store Page

A Coming Soon page is required for at least two weeks, but its larger value is collecting wishlists before launch. Prepare the page when the game's visual direction and main promise are stable, not the night before release.

Advertising Features That Are Not in the Build

Valve expects every supported feature selected on the store page to exist in the submitted game. Remove unfinished features or explain clearly that they are planned for a later update.

Testing Only from the Development Folder

A local build may depend on files that are not included in the Steam depot. Install the game through Steam on a clean test machine and use the same branch that Valve and customers will receive.

Leaving No Time for Review Feedback

The usual review time is not a guaranteed deadline. Submit the store page and build early enough to correct rejected artwork, launch problems, inaccurate feature claims, or missing configuration.

Treating Approval as a Marketing Plan

Passing Valve's review only makes the game eligible for release. It does not guarantee visibility. Use the Coming Soon period to collect wishlists, share a useful demo or trailer, contact relevant creators, and show the game to players who already enjoy its genre.

FAQs About Publishing a Game on Steam

Can anyone publish a game on Steam?

Individuals and companies can apply to become Steamworks partners. You must complete the required legal, identity, tax, and banking steps, pay the Steam Direct fee for the game, follow Steam's content rules, and pass the store page and build reviews.

How much does it cost to publish a game on Steam?

The Steam Direct fee is $100 USD or the local equivalent for each new product, plus any applicable taxes. Valve recoups the fee after the product reaches at least $1,000 in adjusted gross revenue from Steam Store sales and in-app purchases. Development, localization, art, ratings, marketing, and business costs are separate.

Can you publish a game on Steam for free?

No. Even if the game will be free to play, you generally still need to pay the Steam Direct fee for its app credit. The fee applies to submitting the product, not only to selling it at a paid price.

How long does Steam take to approve a game?

Valve says store page and build reviews usually take three to five business days each, but recommends allowing at least seven business days for each submission. Your full timeline must also account for the 30-day waiting period and the required two-week Coming Soon period.

Can I publish an HTML game on Steam?

You cannot use a hosted browser link as the complete Steam build. The product needs downloadable files and a configured application that Steam can launch. If you are still creating the browser version, our guide on how to make a web browser game covers the HTML5, JavaScript, no-code, and AI-assisted development options. Before publishing it on Steam, you will still need to package the game in a desktop wrapper, include its dependencies, and test it on every operating system listed on the store page.

Do I need to use the Steamworks SDK inside my game?

You need Steamworks tools to configure and upload the release, but not every game must implement every Steamworks feature. Only advertise features such as achievements, cloud saves, multiplayer, or controller support when they are correctly implemented and tested.

Conclusion

The safest way to publish a game on Steam is to separate “the game is playable” from “the game is ready to release.” A Steam-ready launch also needs verified account information, accurate store assets, regional pricing, an uploaded and tested build, two Valve approvals, and time to collect wishlists.

Pay the Steam Direct fee and prepare the Coming Soon page before the final development rush. Then submit a near-final build at least a week before your planned release. That buffer gives you time to fix real problems instead of moving the launch date at the last minute.