
Indie Game Festivals 2027: Where to Submit Your Game and When
November 11, 2026
RIDGERUNNERS: A First-Person Mountain Racer Built on Momentum
November 13, 2026How to Run an Indie Game Playtest That Finds Real Problems
A playtest finds real problems when it has one written question per round, testers who have never seen your game, a few numbers you log in every session, and a bug report format that lets you reproduce what went wrong. On Steam, the tool for it is Steam Playtest: it is free, and it runs as a separate app, so a player who only joined the playtest cannot review your game, and joining or leaving it does not touch their wishlist. The signup sits on your main store page. Here is how Steam Playtest works according to the Steamworks documentation, then the plan we would run around it.
How Steam Playtest works
Valve’s Steam Playtest documentation describes a separate “child” app ID that is associated with your game but kept apart from it. The playtest has no store page of its own. Its signup appears as a section on your main game’s page, so a player can request access and still wishlist or follow the real game from the same place.

Steam Playtest, from the Steamworks docs
Free, and kept apart from your game
- Setup: create a Playtest app from the Associated Packages & DLC page of your game. Its review checklist is only capsule images and icons. Its customer-facing name cannot be changed after release.
- Signups: turned on from the Special Settings tab of your main game’s Edit Store Page tools. You can show or hide them at any time.
- Limited signup is the default: you admit players in batches, and Steam picks them at random from the signup pool. You can limit it to certain countries if server latency matters. Open signup admits everyone who requests.
- Keys: you can request Steam keys for a Playtest even before your store page is live. Past 50,000 keys, Valve says the playtest is effectively an open beta and you should open signups instead. It reviews every key request case by case.
- Separate from the real game: someone who has only played the playtest cannot review your game, and playtest playtime has no effect on refunds, trading cards or achievements.
- Not confidential: testers sign no NDA. You cannot charge for access or sell playtest keys.
Two details from the same page are easy to miss. Steam emails players when you grant them access, but it does not email anyone when you set the build to playable, so announce each round with a Steam event. And when you want a completely fresh group, you can reset the playtest, which removes every participant and disables every key. A reset cannot be undone.
If your game is unannounced, Valve’s advice is to announce it first. The alternative the same page describes is release override keys on your main app, limited to 2,500 per app, with your own NDA process. For testing updates inside your team, the Testing on Steam page also covers password-protected beta branches.
Write the test plan before the build
One page is enough. A test plan that fits on one page gets read by the whole team, and it stops a playtest from turning into “tell us what you think.” We would use six lines:
- The question: one per round. “Can a new player finish the first level without help?” is a question. “Is it fun?” is not one you can act on.
- The build: a version number shown on screen, so every report names it.
- The testers: how many, and whether they have played before.
- The session: how long, and where it stops.
- The numbers: what the build logs (next section).
- The channel: where reports go, written on the main menu.
That last line comes from Valve, too. The playtest documentation says collecting feedback is up to you, and suggests telling players what kind of feedback you want and where to post it. It has seen a number of developers add a big feedback button to the main menu.
Pick testers who owe you nothing
Friends and family are kind, and kindness hides problems. Use them for crash testing. For the real question, use people who have never seen the game, such as Steam signups. In a limited playtest, Steam admits them at random from the signup pool, which gives you strangers by default. Keep part of each round for first-time players, because a returning tester already knows where the hidden door is.
What to measure
Opinions tell you how people feel. Logs tell you what they did. Add simple event logging to the playtest build and record the same numbers in every session:

Log these in every session
Five numbers that find problems
- Where each session ends: the last level, room or checkpoint reached. A cluster of quits at one spot is your first fix.
- Time to the first real action: how long from launch to the first jump, shot or build.
- Deaths or failures per section: difficulty spikes show up here before anyone writes about them.
- Crashes per session, tagged with build number and hardware.
- Session length: compare it with the length you planned.
Do not count on Steam for crash data. The Steam Error Reporting page says the feature is nearing its end of life with only limited support, and that it works only for 32-bit Windows applications. Use your engine’s crash reporter or a dedicated tool, and stamp the build number into every report.
After the session, ask a few open questions in this order: What was the game about? What confused you? When did you want to stop, and why? What would you tell a friend about it? Keep yes or no questions out of it. They get polite answers.
How testers should report bugs
A bug you cannot reproduce is a bug you cannot fix. Pin a template in your bug channel and put it in the post guidelines too.

A bug report template testers will fill in
Eight fields, one report
- Build number (shown on screen)
- What happened
- What you expected to happen
- Steps to reproduce, numbered
- How often: every time, sometimes, once
- Where in the game: level, area or menu
- PC or device, operating system, graphics card
- Screenshot, video or log file if you have one
If your community lives on Discord, a Forum channel with required tags (Crash, Gameplay, Visual, Fixed) keeps each report in its own thread. Our guide to setting up a Discord server for your game covers that setup. Steam’s own discussion forums on your store page work as well.
Then triage. Sort reports into crash or blocker, major, minor and cosmetic. Fix what ends sessions first and reply to the person who reported it. When the next build goes up, post a short changelog as a Steam event, because Steam does not email testers when you set a build playable.
Playtest, demo or Early Access
A playtest finds problems. A demo sells the game: our guide to building a Steam demo that turns players into wishlists covers that side. Valve draws the third line itself: its playtest FAQ says that if you are ready to charge money for a work-in-progress version, you should use Steam Early Access. Our article on Steam Early Access covers the rules.
If you would rather hand the testing to people outside your team, our QA and playtesting service is built for that.
Three games on IndiePump.space were testing in the open when we checked in October. Crankles’ Steam page invites players to join its third round of playtest, and its press kit ran a pre-alpha playtest key campaign from September 30 to November 2, 2026. Harbourlight, a cozy diner sim its press kit says is “built slowly by one person,” and Petty Ungodliness both show a playtest signup on their Steam pages.
Games in playtest on IndiePump.space

For developers
Put your game in front of 300+ content creators
Every game on IndiePump.space gets a free press kit page where streamers and writers request review keys, and you decide who gets one.









