How to find playtesters for your indie game
Where to find playtesters for your indie game: Discord servers, Reddit, itch.io, jams and tester pools, plus how to ask so people actually show up.
The fastest places to find playtesters for an indie game are genre-specific Discord servers, playtest-swap communities, subreddits that allow feedback threads, itch.io devlogs, and game jam networks. Recruiting works better when you ask for a specific, short commitment ("15 minutes, browser, no download") than when you ask people to "check out my game." The hard part is not finding people, it is removing every reason for them to drop out between yes and actually playing.
Why most recruiting posts fail
Three reasons, in order of how much damage they do.
You asked for too much. "Download the build, make an account, play for an hour, then fill in this form" is four separate decisions. Every one of them loses people. If your ask can fit in one sentence and one click, you will get several times the turnout from the same audience.
You did not say what you need. "Feedback welcome" gives people no idea whether they are qualified or what a good response looks like. "I need five people who have never played a deckbuilder to try the first fifteen minutes" is concrete, and it tells the right person that you mean them.
You went to the wrong room. Posting a horror prototype in a general gamedev server gets you feedback from developers about your code architecture. Posting it in a horror players community gets you feedback about whether it was scary. Both are useful, but only one answers your question.
Where to find playtesters
Genre communities, not gamedev communities
Developers make convenient testers and biased ones. They notice your tech, forgive your UX, and speak in design vocabulary. Players notice that they were bored in minute four. You want mostly players, with a couple of developers for the eye they bring to systems.
Look for Discord servers and subreddits built around your genre, not around making games. Read the rules first, then post in whatever channel is designated for it. In most well-run servers this is a #playtest, #self-promo, or #showcase channel, and posting outside it will get you removed faster than it gets you testers.
Playtest swap communities
Several gamedev servers run reciprocal playtest threads: you test someone's build, they test yours. The quality is high because everyone in the thread knows what useful feedback looks like, and the cost is real time spent on other people's games. Treat that as the price, not as an annoyance. It is also the single best way to learn how a playtest reads from the other side.
Subreddits vary wildly on whether they allow self-promotion, so check the rules and the weekly threads before posting. What tends to work is a post that leads with the specific question rather than the game, includes one short GIF or screenshot, and states the time commitment in the title. What tends to fail is a trailer link with "thoughts?" underneath.
itch.io
If your game is on itch.io you already have a distribution channel, a devlog feed, and a comment section. Devlogs get surfaced to people browsing the platform, and a devlog that ends with a concrete playtest ask converts better than one that ends with a changelog. Point the playtest link at the itch page itself if you like, so you do not have to host anything new.
Game jams
A jam entry is a finished, short, public artefact that hundreds of people may rate in a single week. It is also the cheapest way to build a list of people who have already played something of yours and liked it enough to comment. Ask those commenters directly when you have a longer build. That personal follow-up has a hit rate nothing else comes close to.
Your own list, built deliberately
The best tester source in year two is the list you started in year one. Every time someone gives you good feedback, ask if they want to be told when the next build is ready. Keep the list somewhere boring and reliable, and never use it for anything except playtest invites and launch.
Public tester pools
Some playtesting tools maintain a pool of players who have opted in to try unreleased games. In PlayProbe this is the public tester pool on the Pro plan: your test can appear on the open playtests page, where people browsing for something new to play can pick it up. It is a supplement to your own recruiting, not a replacement, and I would rather say that plainly than pretend a tool can hand you an audience.
The places I would skip
Paid "get 1000 testers" gigs on freelance marketplaces, engagement-swap groups, and anywhere that rewards people per response. Incentives that pay per completed form select for people optimising the form, and you end up reading fluent nonsense that costs you a day to sort through.
What to actually post
Keep it to five lines. This shape works in almost every channel:
- One sentence on the game. Genre, hook, platform.
- One sentence on what you need. How long, in what browser or on what platform, and what you are trying to learn.
- One image or GIF. The most representative five seconds, not the flashiest.
- The link.
- What testers get. Early access, a credit in the game, a copy at launch, or just your honest thanks. Say which. Do not imply payment you are not offering.
A version I would actually post:
Making a small roguelite about repairing a lighthouse. I am trying to find out whether the first run makes sense without any tutorial text, so I would love 15 minutes from people who have never played it. Runs in the browser, no download or account. Link below, and there is a couple of survey questions at the end. Testers get their name in the credits and a key at launch.
Turning a yes into a finished session
This is where most indie playtests leak. Someone says "sure, send it over," and then never plays, because between your message and their session there were four obstacles.
| Obstacle | What it costs you | Fix |
|---|---|---|
| Download and unzip | A large share of casual yeses | Browser build, or point at an existing itch.io page |
| Account signup | Anyone who is mildly curious rather than committed | Use a flow that needs no tester account |
| Unclear time commitment | People who are busy right now and forget later | State the minutes up front and mean it |
| Feedback form arriving separately | Sessions with no data attached | Put the survey in the same flow as the game |
| No deadline | Indefinite postponement | Give a soft window: "this build is up until Sunday" |
That table is essentially the product spec for PlayProbe. You share one link, the tester opens it in any browser with no account and no download, the pre-survey, the game, and the post-survey are one continuous flow, and the answers arrive aggregated rather than as loose messages. You do not have to upload a build either, since a test can embed WebGL or just point at your itch.io page or Steam Playtest.
How many testers should you recruit at once?
Fewer than you think, more often than you think. Small rounds that actually change the build beat one big round that overwhelms you. I go through the numbers and the reasoning in how many playtesters do you need.
The related trap is recruiting the same eight people every time. After the second build they know your map, your controls, and your intentions, and they stop being able to tell you that minute one is confusing. Rotate in fresh testers for anything about onboarding or clarity, and save your regulars for balance and progression questions where familiarity is an asset.
Keeping testers so you recruit less next time
- Reply to every response, even with one line. People who feel heard come back.
- Tell them what changed. "You got stuck on the third room, so I moved the key" is the single most motivating message a tester can receive.
- Never argue with feedback. Ask a clarifying question or say thanks. Debating a tester is how you get a polite tester who tells you nothing next time.
- Give them the build again later, so they can see the game improve. That is genuinely the reward for most people who test unreleased indie games.
- Credit them. It costs nothing and people screenshot it.
Once you have them, ask well
Recruiting is half the job. The other half is not wasting the fifteen minutes you were given, which comes down to what you ask and when. Start with how to playtest your indie game for the session structure, and if you build in Unity, running a playtest for a Unity game covers asking questions during play instead of after.
PlayProbe is free to start with one game, three tests, and twenty sessions per test, which is more than enough for the first few rounds of recruiting described here. The recruiting itself is still on you, and honestly, that part gets easier every build.