Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
You can publish a PC game on Steam without hiring a publisher. You will need to join Steamworks through Steam Direct, complete Valve’s identity, tax and banking checks, pay the $100 USD (or local equivalent) fee per product, prepare a store page and upload a tested build. Plan around two timing rules: a 30-day wait after paying the fee before release and a publicly visible Coming Soon page for at least two weeks before the game becomes playable.
Valve says review generally takes one to five days, but that is not a guaranteed turnaround. A practical launch plan leaves room for review feedback and fixes, and uses a private beta branch to test builds before customers receive them.
What you need before you start
Steam publishing combines legal and payment onboarding, product setup, store-page preparation, build delivery and launch operations. Gather the following before you begin:
- Account and business details: a Steam account, the legal name or company information for the publishing partner, authority to sign Valve’s agreements, tax details, bank information and identity-verification documents.
- Payment: a way to pay the Steam Direct Fee. Steam Wallet funds cannot be used.
- A release-ready game: a working executable and all required files for each platform you plan to support. Test installation, first and later launches, saving, uninstalling and reinstalling, and offline behavior if you claim offline support.
- Store materials: the game title, short and full descriptions, artwork, screenshots, a trailer, feature information, supported languages and platforms, system requirements, content disclosures and pricing decisions.
- A launch schedule: enough lead time for Valve’s review, any requested corrections, the required waiting periods and your own testing.
Valve’s Getting Started guide organizes the work into account setup, SDK access, builds and depots, store presence, pricing and release preparation.
#1 Best Overall
- International (UK) Version
- 7.4” diagonal, HDR OLED, 1280 x 800 x RGB, up to 90Hz Refresh rate, High performance touch, <0.1 ms Response time, 1,000 nits peak brightness (HDR), 600 nits (SDR)
- SteamOS 3.0 (Arch-based)
- 512GB NVMe SSD, 16GB LPDDR5 on-board RAM (5500 MT/s quad 32-bit channels), microSD UHS-I supports SD, SDXC and SDHC
- 6 nm AMD APU, CPU: Zen 2 4c/8t, 2.4-3.5GHz (up to 448 GFlops FP32
How much does publishing on Steam cost?
The mandatory Steam Direct Fee is $100 USD or local equivalent per product. It is nonrefundable, though Valve says it can be recouped once that product reaches at least $1,000 in Adjusted Gross Revenue from Steam Store or in-app purchases. Taxes such as VAT or GST may apply depending on where you are. Check Valve’s current Steam Direct Fee terms for payment and recoupment details.
That fee is an entry charge, not a full launch budget. Development, art, audio, localization, trailer production, QA, legal or accounting advice, marketing, customer support, engine or middleware costs, servers and other services may add to your costs. None is a universal Steam requirement; budget for the services your project actually needs.
Step 1: Join Steamworks through Steam Direct
- Start at Steam Direct and begin Steamworks partner onboarding.
- Sign Valve’s digital agreements using the person or legal entity that will own and operate the product.
- Pay the product’s Direct Fee.
- Submit the required identity, tax and banking information, then complete Valve’s verification process.
- After onboarding, create the product application in the Steamworks dashboard.
An individual can publish; a traditional publisher is not required. But Valve still requires contractual, identity, tax and payment information. The Steamworks partner that owns the app controls its administration and receives payments under the applicable arrangements, so decide whether the individual or company should own the product before setup. If you work with a team, use Steamworks permissions to grant access rather than sharing the account owner’s credentials. For a later change of ownership, consult Valve’s application-transfer documentation; a transfer is a formal process, not simply a change to the login.
Step 2: Understand the Steam app and build terms
- App or application: the Steam product record for your game.
- AppID: the numeric identifier assigned to that product.
- Depot: a logical group of files delivered to users, often separated by operating system or content type.
- Build: an uploaded version of one or more depots.
- Branch: a delivery channel for a build, such as Default or a beta branch. A beta branch can be password-protected.
- Package: an entitlement that determines which users can access or own the application.
SteamPipe creates manifests describing the uploaded files and their metadata. A single-platform game may begin with one depot; a multi-platform game may need platform-specific depots or file mappings. The right structure depends on your platforms and content. Valve explains the terminology and build workflow in its build documentation.
Step 3: Build a store page that accurately sells the game
Treat the store page as part of the product. It should make clear what the player does, what is distinctive about the game and what the shipped build actually contains. Prepare:
Rank #2
- A concise short description and a fuller description of the experience.
- Capsule and library artwork, plus screenshots that show actual gameplay.
- A trailer that communicates the premise with gameplay early. Valve requires a trailer as part of the release process.
- Accurate features, genres and tags, supported languages, operating systems and minimum and recommended system requirements.
- Controller-support details, accessibility information where relevant, and complete content disclosures.
- A clear decision on release date and whether the game is a full release or Early Access.
Use only material you have the rights to publish, including music, images, fonts and other third-party content. Check the current Steam store documentation for page requirements. Store-page content is reviewed before release, so avoid promises, screenshots or feature claims that the submitted build cannot support.
Step 4: Set pricing and choose the release model
Enter pricing through Steamworks, but do not treat it as one US-dollar figure that automatically answers every regional question. Consider your base price, regional pricing, currencies, discount plans and the expectations your price sets for players. The applicable regional values and terms can change; review Steamworks’ current pricing interface and agreements rather than assuming a universal conversion or revenue-share figure.
Decide whether you are shipping a complete game or inviting customers into an evolving one:
- Full release: usually the better fit when the core experience is complete, the feature list is stable and the team can support customers immediately.
- Early Access: can fit a playable game that is still actively evolving, if you can clearly describe what is unfinished, maintain a credible roadmap and communicate and update regularly. It changes customer expectations; it does not remove the need for testing, support or review.
Valve’s Early Access guidance explains the model. Its release-type documentation also describes Coming Soon, Full Release and Pre-Purchase. Pre-Purchase is not a normal self-service option and generally requires Valve involvement.
Step 5: Download the SDK and configure SteamPipe
After onboarding, download the Steamworks SDK from the partner portal and unzip it on the computer or build server you will use for uploads. Keep the SDK’s ContentBuilder directory structure intact. Valve can change SDK package layouts, so treat directory names below as examples and check the documentation that comes with your SDK.
Rank #3
- 【Upgraded】We sells product with professionally upgraded to 2TB SSD. Original Seal is opened for upgrade ONLY.
- 【Stunning 7.4" HDR OLED & 90Hz Motion】 Experience striking contrast and brilliant clarity with the all-new 7.4-inch HDR OLED display. Designed from the ground up for gaming, it features a 90Hz refresh rate for smooth motion and pure blacks. This handheld is capable of delivering an immersive visual experience, ensuring your Steam library looks better than ever with vibrant colors and amazing motion rendition.
- 【30-50% More Battery & Efficient Performance】 Play your favorites longer with up to 50% more battery life. By fitting a larger battery and a power-efficient OLED panel, this device provides extended gameplay sessions. It’s the perfect travel companion for long flights or commutes. The updated AMD APU ensures high-speed performance for AAA titles while maintaining incredible energy efficiency.
- 【3X Faster Downloads with Wi-Fi 6E】 Never wait for a game again. Equipped with Wi-Fi 6E, this Steam Deck OLED offers increased bandwidth and lower latency, delivering downloads up to 3 times faster than previous models. This ensures stable online play and rapid updates, making it the most reliable wireless gaming handheld for modern high-speed home networks.
- 【Responsive Touch & Enhanced Connectivity】 Enjoy a vastly improved touchscreen with higher fidelity and faster haptics. We’ve added a dedicated Bluetooth antenna to improve connections for multiple controllers. Whether using the built-in trackpads or the included external controller, this allows for precision play in everything from FPS to complex strategy games.
- Create a content directory containing only the files customers should install. Leave out source code, editor files, secrets, debug symbols and development-only material.
- In Steamworks, configure the app and create the depot or depots you need. Use the assigned AppID and DepotIDs.
- Create an app build VDF that points to the content root, output folder and depot build scripts.
- Create a depot build VDF for each depot, mapping the intended local files to the depot paths.
- Check that executables, required runtimes and launch files are included, and that paths are correct relative to the scripts.
A simple app build VDF from Valve’s upload workflow looks like this:
"AppBuild"
{
"AppID" "1000"
"Desc" "This is a simple build script"
"ContentRoot" "..\content\"
"BuildOutput" "..\output\"
"Depots"
{
"1001" "depot_build_1001.vdf"
}
}A matching depot script can map the files under the content root:
"DepotBuild"
{
"DepotID" "1001"
"FileMapping"
{
"LocalPath" "*"
"DepotPath" "."
"recursive" "1"
}
}1000 and 1001 are illustrative IDs only: replace them with your own AppID and DepotID. A Windows-only game can often start with one depot; use appropriate platform-specific depots or mappings for Windows, macOS and Linux builds. More complex products may need separate depots for optional content, language packs or dedicated servers. See Valve’s SteamPipe upload instructions for VDF details.
Step 6: Upload a build
A typical Windows upload command is:
toolsContentBuilderbuildersteamcmd.exe +login <account_name> <password> +run_app_build ..scriptssimple_app_build.vdf +quitsteamcmd.exeis the command-line client included with the SDK tools.+loginsigns in with a Steamworks build account.+run_app_buildruns the app build VDF...scriptssimple_app_build.vdfis the path to that VDF; adjust it to your SDK layout.+quitexits after the operation.
Do not put a real password in a shared script or public repository. Use a dedicated build account with only the permissions it needs, protect credentials, and handle Steam Guard securely. SteamPipe checks permissions, scans and chunks files, compresses and encrypts new chunks, uploads them, creates manifests and assigns a BuildID. Uploading creates a build; it does not automatically make that build the version customers receive.
Step 7: Test privately before launch
- Upload a preview build and install it through the Steam client.
- Use a beta branch for testing; set a branch password when access should be limited.
- Test with a clean Steam account or separate tester account, and on every operating system you claim to support.
- Check first and subsequent launches, updates, uninstall and reinstall, save files, controller input and cloud saves if used.
- Test offline behavior if advertised, and verify that the game works from its actual installed path without development-machine dependencies.
- Submit the exact build you intend to ship, then move it to the Default branch only when it is ready for customers.
A development computer can hide missing runtimes, files, environment variables or permissions. A clean install through Steam is a stronger check. After release, setting a build live on Default can update owners, so use a private branch rather than treating the public branch as a casual test environment. Valve documents branches and setting builds live.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #4
- 512 GB NVMe SSD: Fast storage for quicker game load times and space for larger game libraries.
- OLED Display: 1200x800 resolution with deep contrasts and vibrant colors for a captivating visual experience.
- Custom AMD APU: Power-efficient Zen 2 CPU and RDNA 2 GPU for desktop-level gaming performance.
- Expandable Storage: Add more space with a microSD card slot, ensuring you can bring even more games with you.
- Versatile Controls: With built-in thumbsticks, trackpads, and touchscreen controls, you have full control over your gaming experience.
Step 8: Submit the store page and build for review
Valve reviews the store page, proposed pricing and game build. Its review checks configuration, whether the game runs as expected and whether it is doing anything harmful; it is not an editorial selection, quality certification or promise of marketing exposure. Valve states that review generally takes one to five days, but the estimate is not a guarantee. Its Coming Soon guidance recommends submitting for review at least seven business days before the desired page-live date.
Submit early enough to handle a request for changes. Depending on the issue, you may need to revise page text or assets, correct the content survey or fix the build and submit again. A rejected or incomplete submission can add another review cycle. Read Valve’s review process and release process documentation while preparing your submission.
Step 9: Publish a Coming Soon page
A new product must have a publicly visible Coming Soon page for at least two weeks before it can become playable on Steam. The clock begins when the approved page is public, not when you start drafting it. You can post earlier: do so once you can show the game honestly with clear branding, screenshots, a useful description and ideally a gameplay trailer. Publishing too early with weak or inaccurate materials can make a poor first impression.
The page lets people view the game, wishlist it, visit its Community Hub, follow announcements and receive a launch email. Wishlists are useful for launch and discount notifications, but do not assume they guarantee algorithmic visibility or sales. Valve says wishlists are mostly not a direct factor in visibility, with exceptions such as Popular Upcoming; see its current visibility guidance. The Coming Soon page itself must be reviewed and approved before it becomes public. Details are in Valve’s Coming Soon documentation.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →How long does the Steam publishing process take?
Allow for separate steps rather than relying on the shortest estimate. Valve states that there is a 30-day waiting period between paying the app fee and releasing the game. The product also needs a public Coming Soon page for at least two weeks before it becomes playable. Review generally takes one to five days; Valve recommends submitting at least seven business days before the date you want the Coming Soon page live. These periods can overlap where the workflow permits, but review revisions and verification delays can extend the schedule. Do not plan a last-minute launch around the minimums.
Best Value
- Valve is entering the gaming console marketplace with the new Steam Deck, a console geared towards PC gamers. The Steam Deck can be docked to a monitor, and used as a PC, or docked to a TV.
- Players can play a huge variety of games at any time with the comfort of a console and the freedom of a PC. Not anti-glare screen.
- Like the name suggests, the Steam Deck will include upgraded 1TB storage, and will include a carrying case. A micro SD slot will also enable expanded storage.
- Valve partnered with AMD to create a specialized APU optimized for handheld gaming, and Valve says the chip will deliver performance to run AAA gaming titles.
- The Steam Deck is outfitted with a 7-inch touchscreen, and two trackpads under the control sticks that allow gamers to operate games never designed outside of mouse and keyboard capabilities.
Step 10: Release the game
Once Valve has approved the page and build and the timing requirements are met, release is a manual action. Before using the release control, check that the selected Default build is the one tested, the price and release settings are correct, platforms and languages are accurate, and the page describes the shipped version. Prepare an announcement and a way for players to contact you about urgent issues.
- Open the release controls in Steamworks after approval.
- Confirm the release details and intended build.
- Select the publish-now option when you are ready to make the game available.
- Verify the live store page and test downloading and launching the released version.
Valve describes the manual release options in its release-type documentation.
What to do after launch
- Monitor crash reports, customer discussions and support requests; prioritize serious launch blockers.
- Test updates on a private branch, then set the verified build live when ready. Default-branch updates reach owners.
- Post clear patch notes and update the store page if features, requirements or supported platforms change.
- Maintain online services and servers your game depends on, and communicate outages or changes.
- Review sales, traffic, wishlists and conversion data to understand player response; do not treat any one metric as a guaranteed measure of future visibility.
- Plan discounts and community communication around the game’s actual support capacity.
Common upload and launch problems
| Symptom | Likely cause | Recovery |
|---|---|---|
| Permission error | The build account lacks access to the app or depot. | Check Steamworks user permissions and confirm the AppID and DepotID. |
| App information cannot be retrieved | Wrong AppID, missing access or app configuration not published. | Verify the AppID and account access, then publish the relevant Steamworks configuration. |
| Installation is empty | Incorrect ContentRoot, LocalPath or file mapping. | Check paths relative to the VDF scripts and inspect the generated manifest. |
| Windows works but Mac or Linux content is empty | Platform depot or mapping is missing, or the relevant build is not live on the test branch. | Check platform depots and set the correct build live on the branch used for testing. |
| Upload succeeded but users receive an old version | The build uploaded but was not set live for the intended branch. | Select the uploaded build for that branch. |
| Testing changes reach customers | A test build was set live on Default after release. | Use a beta branch for testing; reserve Default for customer-ready builds. |
| SteamCMD login fails | Steam Guard, changed security credentials, network trouble or stored configuration. | Log in interactively, check account security and network access, and protect rather than discard SDK configuration. |
| The build works locally but not through Steam | Missing runtime files, wrong working directory, permissions or Steam-specific launch assumptions. | Install from Steam on a clean machine and test from the actual installed path. |
Valve’s upload documentation and build documentation cover SteamPipe setup and build publication.
Recommended Free Tools
Should you self-publish or use a publisher?
Self-publishing gives you direct control of the store page, pricing, release timing, updates and community communication. It also leaves you responsible for the practical work: tax and legal administration, QA, marketing, localization, customer support and launch operations. Valve review does not guarantee featuring, sales or algorithmic exposure.
A publisher may be worth discussing if you need funding, console or international support, or experienced marketing, localization, QA or community management. Assess the concrete audience, services and rights a publisher brings against the control and responsibilities you would give up. No arrangement fits every game or team.
Quick Recap
Steam launch checklist
- Account: correct person or company owns the Steamworks partner account; agreements signed; identity, tax and banking verification complete.
- Fee and timing: Direct Fee paid; 30-day wait accounted for; public Coming Soon page live for at least two weeks before the game becomes playable.
- Store page: accurate descriptions, artwork, gameplay screenshots, trailer, tags, languages, platforms, system requirements and content disclosures approved.
- Build: correct AppID and depots; customer files mapped; secrets and development-only files excluded; upload assigned a BuildID.
- Testing: Steam installation tested on clean systems for every supported platform; updates, saves, controls and offline claims checked; release build verified on a private branch.
- Review and launch: page, pricing and build approved; correct build selected for Default; release details checked; support and announcement ready.
- After launch: monitor player reports, maintain services, test updates privately and communicate changes.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
