How to Publish a Game on Steam: $100 Fee and Steps (2026)
Publishing a game on Steam costs $100 per game (Steam Direct), refunded after $1,000 in sales. Step by step: Steamworks account, build, store page, review, and launch.
By Summer Team

Short answer: publishing a game on Steam costs $100 per game (the Steam Direct fee), and Valve refunds it after the game earns $1,000. You do not need a publisher or an invite. Anyone can publish a game on Steam by paying that fee and following a checklist, and the whole process takes at least three to four weeks because of Valve's required waiting periods.
This guide walks through every step of the process, from creating your Steamworks account to pressing the launch button. No fluff, just what you actually need to do.
{/* IMAGE: Steamworks partner dashboard overview showing the main navigation (store page, builds, analytics tabs). Screenshot, 1200x675. */}
Quick Overview: What It Costs and How Long It Takes
Before getting into the details, here is a summary of the numbers.
| Item | Details |
|---|---|
| Steam Direct fee | $100 per game (refunded after $1,000 in revenue) |
| Valve's revenue cut | 30% (drops to 25% after $10M, 20% after $50M) |
| Tax and bank verification | 2 to 7 business days |
| Wait after paying the fee | 21 days before you can release |
| Coming Soon page | Public for at least 2 weeks before release |
| Review time | 1 to 5 days for the store page and for the build |
| Minimum build requirement | Windows .exe |
| Recommended wishlist period | 2 to 6 months before launch |
Step 1: Create a Steam Developer Account
Go to partner.steamgames.com and create a Steamworks account. You need a regular Steam account first (the same one you use to buy games).
Valve charges a one-time $100 USD fee per game. This is the Steam Direct fee. You get it back as a credit once your game earns $1,000 in revenue. The fee exists to prevent spam, not to block real developers.
Identity Verification
Valve requires bank and tax information before you can receive payments. If you are outside the US, you will fill out a W-8BEN form. This part takes a few days to process, so do it early.
Once approved, you get access to the Steamworks dashboard. This is where everything happens: store page setup, build uploads, analytics, and community management.
Step 2: Prepare Your Game Build
Steam requires a native desktop executable. You cannot publish a web game or browser-based experience. Your game must run as a standalone application.
Platform requirements:
- Windows .exe is the minimum. Most Steam games ship Windows-only, and that covers the vast majority of players.
- macOS and Linux builds are optional. They expand your reach at no extra cost if your engine supports cross-platform export.
- The game must launch without requiring the player to install additional software manually.
Testing Before Upload
Test on a clean machine that does not have your development tools installed. The most common failure is missing DLLs or runtime dependencies that exist on your dev machine but not on a player's PC.
{/* IMAGE: Example of a common Steam build error (missing DLL dialog on Windows). Screenshot, 800x500. */}
Step 3: Set Up Your Store Page
Your store page is the single biggest factor in whether someone wishlists your game or scrolls past. Every element matters.
Required Capsule Art
Steam uses specific image sizes for different placements. You need all of them.
| Asset | Dimensions | Where It Appears |
|---|---|---|
| Header Capsule | 460x215 | Search results, store page |
| Small Capsule | 231x87 | Wishlists, top seller lists |
| Main Capsule | 616x353 | Front page, browse views |
| Hero Graphic | 3840x1240 | Top banner on your store page |
| Library Capsule | 600x900 | Player's Steam library |
| Page Background | 1438x810 | Store page backdrop (optional) |
Every capsule must include your game's name as text on the image. Steam enforces this rule. A beautiful scene with no title will be rejected.
{/* IMAGE: Side-by-side comparison of a good capsule vs. a bad capsule (one with clear title text and strong composition, one cluttered with no readable title). Diagram/illustration, 1200x600. */}
Writing Your Description
Lead with what the player does, not your lore.
- Good: "Build and defend a colony on Mars against sandstorms and rival factions."
- Bad: "In a distant future, humanity has reached the stars and must now face its greatest challenge."
Your description is searchable. If your game is a "roguelike deckbuilder with co-op," those exact words should appear in the text.
Choosing Tags
Tags drive discoverability on Steam. Pick genre tags that honestly describe your game, then add specific mechanical tags (roguelike, base building, co-op, souls-like). Look at similar games in your genre to see which tags they use.
Screenshots
Upload at least 5 screenshots of actual gameplay. Not title screens, not menus. Screenshots need to read clearly at thumbnail size because that is how most people see them first.
Trailer
Games without trailers convert significantly worse. Your trailer does not need professional production. 30 to 60 seconds of gameplay footage with a title card and music works fine. Upload it directly to Steam rather than linking YouTube.
Step 4: Upload Your Build with SteamPipe
SteamPipe is Valve's tool for uploading game files. You can use the command-line tool (steamcmd) or the upload feature in the Steamworks dashboard.
Upload Process
- In Steamworks, navigate to your app's page, then "Edit Steamworks Settings," then "SteamPipe," then "Builds."
- Set up at least one depot (a container for your game files).
- Download the Steamworks SDK, which includes steamcmd.
- Create a build configuration file that points to your game files.
- Run the upload command.
SteamPipe handles delta uploads, so subsequent updates only transfer changed files. The first upload can be slow depending on your game size. After that, patches are fast.
After uploading, set your build as the default branch so reviewers (and later, players) get the correct version.
{/* IMAGE: Steamworks SteamPipe build management interface showing depot setup and branch configuration. Screenshot, 1200x675. */}
Step 5: Set Your Price
You have two paths: free or paid.
Free-to-Play
Skip the pricing step entirely. You can still sell DLC, in-game items, or cosmetics later.
Paid Games
Set a base price in USD. Steam auto-generates regional prices for every other currency using a purchasing power matrix. You can adjust these manually, but the defaults are reasonable.
Pricing Tips for Indie Developers
- First game with no audience? Price at $5 to $15. Building a following matters more than maximizing per-unit revenue.
- Launch discount: Steam allows up to 40% off during your first week. A 10 to 20% discount drives initial sales and pushes you into visibility algorithms.
- Cooldown period: You cannot run another discount for 28 days after your launch discount ends. Plan accordingly.
- Revenue cut: Valve takes 30% of all sales. Factor this into your pricing math.
Step 6: Submit for Review
Valve reviews every game before it goes live. This is not a quality judgment. They check for:
- Legal compliance. No stolen assets, no trademark issues, no illegal content.
- Store page accuracy. Your description and screenshots must reflect the actual game.
- Basic functionality. The game must launch and be playable.
- Content disclosure. Mature content must be properly tagged.
You can (and should) submit the store page for review first, separately from the build. An approved store page lets you start collecting wishlists while you finish development.
Review Timeline
Typical review takes 1 to 5 business days. Do not submit the day before your planned launch. If something fails, Valve tells you what to fix. Most issues are minor: wrong image size, missing content descriptor, or similar small things that take minutes to resolve.
Step 7: Build Wishlists Before You Launch
Do not launch the moment your build is approved. The time between approval and launch is for building wishlists. Every wishlist converts to a notification email on launch day. Those emails drive your critical first-week sales.
How to Get Wishlists
- Post your store link on social media, Reddit communities for your genre, Discord servers, and game dev forums.
- Steam Next Fest. Upload a free demo and get featured alongside thousands of other upcoming games. This is one of the best free marketing opportunities on Steam.
- Content creators. Reach out to small YouTubers and streamers who cover your genre. Many are happy to play indie games if you send a key.
Choosing a Launch Day
| Day | Verdict |
|---|---|
| Monday | Avoid. Competing with weekend releases. |
| Tuesday, Wednesday, Thursday | Best days to launch. |
| Friday | Avoid. Less store browsing over the weekend. |
Step 8: Launch Day Checklist
- Announce across all channels simultaneously.
- Be online and responsive. Players will find bugs. Responding quickly to community posts earns goodwill and better reviews.
- Your first few reviews heavily influence your overall rating. Encourage honest reviews, but never offer incentives for positive ones (Valve prohibits this).
- Monitor your store page analytics in Steamworks. Watch impressions, click-through rate, and wishlist conversion.
{/* IMAGE: Steamworks analytics dashboard showing impressions, visits, and wishlist conversion funnel. Screenshot, 1200x675. */}
Common Mistakes That Kill Launches
1. Bad capsule art. If your header capsule looks amateur, players assume your game is amateur. This is the first thing anyone sees. A freelance designer can create a solid capsule for $50 to $100. It is the highest-ROI investment you can make.
2. No trailer. A store page without a trailer loses a huge percentage of potential wishlists. Even 30 seconds of gameplay with music is better than nothing.
3. Launching with zero wishlists. Steam's algorithm needs signal. If you launch with no wishlists, your game gets no traction and sinks. Spend at least a few weeks (ideally months) with a Coming Soon page before pressing launch.
4. Price too high for a debut. An unknown developer with no audience asking $20+ faces an uphill battle. Build a following at a lower price point first.
5. Ignoring the description. Your store page description is searchable text. Include the keywords players would use to find a game like yours.
Build Your Steam Game with Summer Engine
Summer Engine exports Steam-ready desktop builds directly from the editor. No manual packaging, no third-party export tools. If you are building a game and want to ship on Steam, download Summer Engine and start creating.
Frequently asked questions
- How much does it cost to publish a game on Steam?
$100 per game. The Steam Direct fee is paid once for each new app, and Valve pays it back in a later payout once that game reaches $1,000 in adjusted gross revenue from store or in-app purchases. After release, Valve keeps 30% of revenue, 25% after $10 million, and 20% after $50 million.
- Can I publish a game on Steam for free?
No. Every new app pays the $100 Steam Direct fee, including free-to-play games. The fee is recoupable after $1,000 in revenue, so a paid game that sells makes it back, but a free game without in-app purchases does not.
- How long does it take to publish a game on Steam?
Plan on at least three to four weeks. Tax and bank verification takes 2 to 7 business days, you must wait 21 days after paying the app fee before release, the Coming Soon page must be public for at least two weeks, and store and build reviews take 1 to 5 days each.
- Do I need a publisher to release on Steam?
No. Anyone with a Steamworks account can self-publish by paying the Steam Direct fee and passing Valve's review. Publishers help with marketing and funding, but they are not required.
- What do I need before I submit my game for review?
A working build uploaded through SteamPipe, a complete store page with all required capsule images, screenshots and a description, a price or free-to-play setting, content survey answers including any AI-generated content disclosure, and a Coming Soon page that has been public for at least two weeks before your release date.
- Can I publish a web or browser game on Steam?
Not as a web page. Steam distributes desktop applications, so a browser game has to be packaged as a native Windows, macOS, or Linux build. An engine that exports native builds, like Summer Engine with its Windows and macOS builds, handles that step for you.
Keep reading
All posts- Jun 6, 2026 · 8 min readHow to Publish a Game on PC Gaming Platforms (2026 Step-by-Step)A complete step-by-step guide to publishing a PC game on Steam, itch.io, Epic, GOG, and the Microsoft Store. What each platform costs, what files you need, and the exact order to ship in.

- Jun 6, 2026 · 7 min readAI Enemy Generator for Games: What It Is and How to Use One (2026)What an AI enemy generator actually does, the three layers it should cover (sprite, stats, behavior), and how to build working enemies for your game by describing them in plain language.

- Jun 6, 2026 · 8 min readAI Horror Game Maker: How to Build a Horror Game by Describing It (2026)How to build a real horror game with AI: the five mechanics that actually make a game scary, which template to start from, and a step by step workflow inside Summer Engine where the AI is wired into the editor.
