Publishing a game on Steam is one of those processes that feels like it should be straightforward but really isn't. There are account verifications, tax forms, asset requirements, content surveys, build configurations, and a review process that can trip you up if you don't know what to expect. I've watched developers lose weeks to avoidable mistakes -- uploading the wrong build branch, forgetting a capsule size, or getting stuck on paperwork they didn't know existed.
This guide walks through every step from creating your Steamworks account to pressing the release button. If you're a first-time developer shipping your first game, this is the roadmap. For a quick-reference version of what your store page needs, our Steam store page checklist covers every asset and configuration item.
Step 1: Create your Steamworks account
Everything starts at partner.steamgames.com. This is Steamworks -- Valve's backend for developers and publishers. You'll live here for the duration of your game's life on Steam.
What you need to sign up
You'll need a valid email address, personal identification for tax purposes, and bank account information for receiving payments. If you're registering as a company, you'll need your business details and tax ID. Individuals can register too -- you don't need a formal business entity to publish on Steam.
The signup process involves agreeing to the Steam Distribution Agreement. Read it. Seriously. It covers revenue splits (Valve takes 30% of sales up to $10 million, dropping to 25% up to $50 million, and 20% beyond that), refund policies, and your obligations as a developer. Understanding this upfront saves headaches later. Our Steam revenue share guide breaks down the financial side in detail.
Identity verification
Valve requires identity verification before you can publish. This involves providing personal or business identification documents. The process can take anywhere from a few days to a couple of weeks depending on your situation. Don't wait until the last minute -- start this as soon as you're serious about publishing on Steam.
Step 2: Pay the $100 Steam Direct fee
To create a new application on Steam, you need to pay a $100 app credit fee per title. This is non-refundable upfront, but Valve will recoup it from your first $1,000 in revenue -- meaning you effectively get it back once your game starts selling.
The fee exists to prevent spam and low-effort submissions from flooding the store. It's a one-time cost per game, not a recurring fee. If you're publishing multiple games, you pay $100 for each one.
A common question: should you pay this fee early or wait until your game is closer to release? I'd strongly recommend paying it earlier than you think you need to. Once you have your App ID, you can set up your Coming Soon page and start collecting wishlists immediately. Every month without a Coming Soon page is a month of missed wishlists. Our guide to getting a Steam App ID covers the timing strategy in more detail.
Step 3: Create your application and get your App ID
After paying the fee, you can create a new application in Steamworks. You'll enter your game's name and basic details, and Steam will generate a unique App ID for your title.
Your App ID is permanent. It's the number that identifies your game across Steam's entire ecosystem -- store pages, APIs, community hubs, everything. Choose your game's name carefully at this stage, though you can change it later if needed.
Once you have your App ID, you unlock access to all of Steamworks' tools: store page configuration, build uploading, achievement setup, cloud saves, and more. This is where the real work begins.
Step 4: Complete the content survey
Before your store page can go live, you need to complete Steam's content survey. This is a detailed questionnaire about your game's content -- violence, nudity, language, substance use, and other mature themes.
Answer honestly. The content survey determines which content descriptors appear on your store page and how Steam's parental controls interact with your game. Inaccurate surveys can lead to your page being flagged or rejected during review, and misrepresenting content can cause problems with players and Valve down the line.
The survey isn't pass/fail. Having mature content doesn't prevent you from publishing -- it just ensures the right warnings and filters are in place. Steam sells plenty of games with mature themes. They just want accurate labeling.
Step 5: Set up your store page
This is the big one. Your store page is where players decide whether to wishlist or buy your game, so every element matters. Our Steam store page optimization guide covers the strategy behind each piece, but here's what you need to configure in Steamworks.
Basic information
Fill in your developer name, publisher name, supported platforms, supported languages, genre, and release date (or "Coming Soon"). These fields appear prominently on your store page and in search results, so make sure they're accurate and professional.
Capsule images
You need multiple capsule images at specific dimensions. This is where a lot of first-time developers hit their first rejection. Steam is strict about capsule specs -- wrong dimensions, excessive text, or low-quality art will get sent back.
The required capsules are: Header Capsule (460x215), Small Capsule (231x87), Main Capsule (616x353), Hero Graphic (3840x1240), Library Capsule (600x900), and Community Icon (32x32). For a complete breakdown of every asset with specs, see our Steam page asset requirements guide.
Run all your capsules through our Capsule Validator before uploading. It catches dimension errors, file size issues, and readability problems before Valve's review does -- saving you a round trip that can cost days.
Our capsule design guide covers the design principles that actually drive clicks. Capsules are your single biggest lever for discoverability, so don't treat them as an afterthought.
Screenshots
Upload at least 5 screenshots at 1920x1080 or higher. Aim for 8-10 that show a variety of gameplay moments, environments, and mechanics. Your first screenshot is especially important -- it displays as the default when your trailer isn't playing.
Screenshots should show actual gameplay, not concept art or pre-rendered marketing shots. Players want to know what they're actually getting. For composition tips and ordering strategy, read our screenshot optimization guide.
Trailer
While technically optional, a trailer is practically required for any game that wants to generate wishlists. Upload at least one gameplay trailer at 1080p or higher, ideally 60-90 seconds long. Show real gameplay within the first 10 seconds. End with your game title and a call to action.
Your trailer has more impact on wishlist conversion than any other single asset. Our trailer best practices guide covers what makes trailers convert.
Game description
Write both a short description (up to 300 characters) and a long description for the "About This Game" section. The short description appears in search results and needs to hook immediately. The long description should include a compelling opening, a feature list, world or story context, and development status information if launching in Early Access.
Steam supports basic formatting in descriptions -- headers, bold, lists, and links. Use them to make your description scannable. For a deep dive on writing descriptions that convert, see our Steam description writing guide.
Tags
Apply all 15 developer tag slots. Tags directly feed into Steam's recommendation and discovery systems, determining which players see your game. Order them from most specific to most broad, and make sure they accurately represent your game. Misleading tags waste your slots and attract the wrong audience.
System requirements
Specify minimum and recommended hardware for all supported platforms. Include CPU, GPU, RAM, storage, OS version, and graphics API. Test your game on hardware matching your minimum specs -- guessing leads to angry reviews and refund requests.
Step 6: Upload your game build
Steamworks uses a tool called SteamPipe for uploading builds. You'll download the Steamworks SDK, configure depot and build scripts, and use a command-line tool to push your build to Steam's servers.
Setting up SteamPipe
The process involves creating depots (containers for your game's files), writing VDF configuration files, and running the upload tool. It's not complicated once you understand the structure, but the documentation can be dense for first-timers.
Key concepts: your app has one or more depots, each depot contains a set of files, and builds are uploaded to branches. The "default" branch is what players download when they install your game. You can create additional branches for testing, beta access, and pre-release builds.
Build branches and testing
Before setting your build live, test it thoroughly through Steam. Install it on a clean machine using a test account. Verify that the install process works, the game launches correctly, Steam overlay functions, achievements trigger (if applicable), and cloud saves work (if configured).
Common build issues that delay launches: missing DLL files, incorrect file paths, games that only run from a specific directory, and builds that work in the editor but not as standalone executables. Test the actual Steam build, not your development environment.
Step 7: Configure pricing
Set your base price in USD. Steam will automatically suggest regional pricing based on your USD price, adjusted for purchasing power in each market. Review these suggestions carefully -- the defaults are generally reasonable, but you may want to adjust for specific regions.
Don't set all regions to the same USD equivalent. A $20 game in the US shouldn't cost the equivalent of $20 in countries with significantly lower purchasing power. Steam's suggested pricing accounts for this, and following their recommendations typically maximizes global revenue. Our Steam pricing strategy guide covers pricing psychology, competitive analysis, and how to choose the right price point for your game.
If you're planning a launch discount (and you probably should -- 10-15% is standard), configure it in advance. Launch discounts are a powerful conversion tool, but they need to be set up before your release date.
Step 8: Submit for review
Once your store page, build, and pricing are configured, submit everything for Valve's review. This is a manual process -- real humans at Valve will review your submission.
What Valve reviews
They check your store page assets for technical compliance (dimensions, formats, quality), your content survey accuracy, your game build for basic functionality, your pricing configuration, and your store page content for policy compliance. They're not reviewing your game's quality or commercial viability -- Steam doesn't curate based on game quality. They're checking that your submission meets their technical and policy requirements.
Review timeline
Plan for 3-5 business days for the initial review. If everything is in order, you'll get approved and can set your release date. If there are issues, you'll receive specific feedback about what needs to change.
Common rejection reasons include capsule images not meeting dimension requirements, capsule images containing prohibited content (like review scores or award logos in certain sizes), screenshots that aren't actual gameplay, description containing prohibited formatting or content, content survey inaccuracies, and build issues that prevent the game from launching.
After addressing any issues, resubmit and wait for another review cycle. Each round can add 3-5 business days, which is why it's crucial to get things right the first time. The Capsule Validator and our asset requirements guide exist specifically to help you avoid these delays.
The Coming Soon phase
Once approved, your store page goes live as a "Coming Soon" page. This is when you start collecting wishlists. I cannot overstate how important this phase is -- wishlists are the primary driver of launch-day sales and algorithmic visibility. Our Coming Soon page guide covers how to maximize this period.
Step 9: Prepare for launch
With your Coming Soon page live and wishlists accumulating, the period before launch is about building momentum and preparing your release.
Pre-launch checklist
Verify your final build is uploaded and set to the default branch. Confirm your launch discount is configured. Prepare your launch-day marketing materials -- social media posts, press emails, streamer keys, Discord announcements. Set up your Steam Community hub with discussion categories. Have a monitoring plan for launch day so you can respond quickly to bugs, reviews, and community questions.
Timing your release
Avoid launching during major Steam sales or alongside highly anticipated AAA releases in your genre. Tuesday through Thursday are generally the best days for indie launches. Steam updates at 10 AM Pacific, so plan your marketing around that window. Our guide on the best Steam launch dates covers timing strategy in detail.
Step 10: Release your game
When your release date arrives, you'll need to manually trigger the release in Steamworks (it doesn't happen automatically at midnight). Once you press the button, your game goes live on the store, wishlisted players receive notifications, and your launch discount activates.
The first 48 hours are critical. Steam's algorithm heavily weights early sales velocity, reviews, and engagement. A strong launch creates a feedback loop: good sales lead to more visibility, which leads to more sales. A weak launch is harder to recover from, though not impossible.
Respond to early reviews and community posts promptly. First impressions set the tone for your game's long-term reputation on Steam. Our review management guide covers how to handle feedback -- both positive and negative -- during this intense period.
Common pitfalls and how to avoid them
Rushing the store page
The most expensive mistake is treating your store page as a box to check rather than a marketing asset to optimize. Every element -- capsules, screenshots, trailer, description, tags -- directly affects how many people see and buy your game. Invest time in each one. The Steam store page optimization guide is the single most useful resource for this.
Underestimating the timeline
From account creation to release, the full process typically takes 2-4 months if you already have a finished game. Factor in identity verification (1-2 weeks), store page preparation (2-4 weeks for quality assets), review cycles (1-2 weeks with potential revisions), and Coming Soon wishlist accumulation (ideally 6-12 months). Start the Steamworks process much earlier than you think you need to.
Ignoring regional pricing
Defaulting to the same price everywhere leaves money on the table in wealthy markets and prices you out of developing ones. Take the 15 minutes to review and adjust regional pricing. It meaningfully impacts your total revenue.
Skipping the Coming Soon phase
Some developers try to go from zero to launch without a Coming Soon page. This almost always results in a weak launch because you haven't built an audience. Wishlists are the fuel that powers your launch -- don't skip the phase where you collect them.
Not building an audience before launch
Steam's algorithms reward games that already have momentum. If you rely entirely on Steam's organic discovery without any external marketing, your launch will be underwhelming. Build a community, engage on social media, reach out to press and content creators, participate in Steam events. The work you do before launch matters more than what you do on launch day.
Timeline expectations
Here's a realistic timeline for a first-time developer with a finished game:
Weeks 1-2: Create Steamworks account, complete identity verification, pay $100 fee, get App ID.
Weeks 3-6: Prepare all store page assets -- capsules, screenshots, trailer, description, tags. This takes longer than you expect. Aim for quality, not speed.
Weeks 7-8: Configure store page in Steamworks, upload initial build, complete content survey, set pricing.
Weeks 9-10: Submit for review. Address any feedback. Resubmit if needed.
Weeks 11-12: Coming Soon page goes live. Begin wishlist accumulation and marketing push.
Months 4-12: Build wishlists through marketing, events, demos, and community engagement.
Launch: Release with a launch discount and full marketing push.
If your game is still in development, start the Steamworks process as soon as you have enough polished content to create a compelling store page. There's no minimum completion requirement for a Coming Soon page -- you just need good assets that accurately represent what you're building.
Frequently asked questions
How much does it cost to publish a game on Steam?
The only required fee is the $100 Steam Direct fee per title. There are no monthly fees, listing fees, or hidden costs from Valve's side. The $100 is recouped from your first $1,000 in adjusted gross revenue, so you effectively get it back. Beyond that, Valve takes a 30% revenue share on sales (dropping to 25% after $10 million and 20% after $50 million). Our revenue share guide has the full breakdown.
How long does the Steam review process take?
Typically 3-5 business days for each submission. If your submission is rejected and you need to make changes, each resubmission goes through the same timeline. Getting everything right the first time saves a lot of calendar time. Use our Capsule Validator and follow the store page checklist to minimize revision cycles.
Can I publish a game on Steam as an individual?
Yes. You don't need a registered business entity to publish on Steam. Individuals can sign up for Steamworks, though you'll still need to provide identification and tax information. Many successful indie games are published by solo developers.
Do I need a publisher to release on Steam?
No. Steam's self-publishing tools are designed for independent developers. A publisher can help with marketing, funding, and navigating the process, but they're not required. Plenty of top-selling indie games are self-published.
What happens if my game gets rejected?
You'll receive specific feedback about what needs to change. Common rejections involve capsule image specs, content survey issues, or build problems. Fix the issues, resubmit, and wait for the next review cycle. Valve doesn't reject games for being "bad" -- they reject submissions that don't meet technical or policy requirements. It's a fixable process, not a judgment call.
When should I set up my Coming Soon page?
As early as possible -- ideally 6-12 months before launch. The Coming Soon page is where you collect wishlists, and wishlists directly determine your launch-day visibility and sales. Every month without a Coming Soon page is a month of missed wishlists. See our Coming Soon page guide for the full strategy.
Publishing on Steam is a multi-step process, but none of the individual steps are particularly difficult. The developers who struggle are the ones who rush through it or treat the store page as an afterthought. Take your time with the assets, follow the store page checklist, and start earlier than you think you need to.
Validate your capsules with the Capsule Validator, optimize your visuals with the capsule design guide and screenshot guide, and nail your messaging with the description writing guide. For pricing decisions, our pricing strategy guide gives you data-driven guidance.
Browse our genre-specific optimization guides for strategies tailored to your game type, and check the Steam Page Leaderboard to see how top games optimize their store pages.