# Playtest survey builder for games

> Pick a playtest type, genre, session length and goals to get a short game playtest survey with answer types. Free, no sign-up: copy it as text or a CSV.

Canonical URL: https://manalens.dev/tools/playtest-survey-builder

This builder writes a short playtest survey for your game: 8 to 12 ordered questions sized to your session, each with an answer type and a time to ask it. Pick the playtest type, genre, session length and goals. Copy the survey as plain text or Markdown, or download a CSV, then paste it into Google Forms or Tally.

## How to use this tool

The interactive tool runs in the browser at https://manalens.dev/tools/playtest-survey-builder. This section describes it for readers who cannot run it.

### Inputs

- Playtest type: First-time user test, Demo before Next Fest, Closed alpha or beta, Steam Playtest, In-person session
- Game genre: Action or platformer (levels), Puzzle (levels), Roguelike or roguelite (runs), Strategy or tactics (matches), RPG or adventure (quests), Simulation or management (days), Multiplayer (matches)
- Session length: Under 15 minutes (up to 8 questions), 15 to 45 minutes (up to 10 questions), 45 minutes to 2 hours (up to 12 questions), Several sessions over days (up to 12 questions)
- Goals (any number): Onboarding and clarity, Fun and core loop, Difficulty and pacing, Controls and UI, Bugs and performance, Willingness to wishlist or buy, Price sensitivity
- Name of your game (optional)
- Add a tester ID question (optional)

### Outputs

- A survey with an intro text, a consent line and ordered questions, grouped by when to ask: during the session, right after the session, a day later
- For each question: the answer type (scale 1 to 5, single choice, multi choice or open text) and the options
- The question count, the target count for the session length and the estimated minutes
- Copy as plain text, copy as Markdown, and a CSV file with the columns question, type, options and when
- Steps to add the survey to Google Forms or Tally

### The question bank (54 questions)

We wrote every question. In a survey, {unit} becomes the unit of the genre, such as level, run or match.

#### General questions

| Question | Answer type | Options | When to ask |
| --- | --- | --- | --- |
| How often do you play games like this one? | Single choice | Most weeks; A few times a year; I tried one or two; Never before this test | Right after the session |
| Overall, how was the game? | Scale 1 to 5 | 1 = very bad; 5 = very good | Right after the session |
| What else do you want to tell us? | Open text |  | Right after the session |

#### Onboarding and clarity

| Question | Answer type | Options | When to ask |
| --- | --- | --- | --- |
| How easy or hard was it to understand what to do in the first minutes? | Scale 1 to 5 | 1 = very hard; 5 = very easy | Right after the session |
| Describe a moment when you did not know what to do next, if there was one. | Open text |  | Right after the session |
| In your own words, what is the goal of the game? | Open text |  | Right after the session |
| How was the amount of explanation at the start? | Single choice | Too little; About right; Too much | Right after the session |
| Which rule or feature did you understand late, or still not understand? | Open text |  | Right after the session |
| How easy or hard was the story to follow? | Scale 1 to 5 | 1 = very hard; 5 = very easy | Right after the session |
| How clear or unclear was it why you won or lost a match? | Scale 1 to 5 | 1 = very unclear; 5 = very clear | Right after the session |
| How often did you know what you wanted to build or do next? | Scale 1 to 5 | 1 = almost never; 5 = almost always | Right after the session |
| What are you trying to do right now? | Open text |  | During the session |

#### Fun and core loop

| Question | Answer type | Options | When to ask |
| --- | --- | --- | --- |
| Which moment do you remember best? Tell us what happened. | Open text |  | Right after the session |
| Where were you bored or annoyed? Tell us what happened. | Open text |  | Right after the session |
| When the session ended, how much did you want to keep playing? | Scale 1 to 5 | 1 = not at all; 5 = very much | Right after the session |
| How would you describe this game to a friend in one sentence? | Open text |  | Right after the session |
| How fresh or repetitive did each new level feel? | Scale 1 to 5 | 1 = very repetitive; 5 = very fresh | Right after the session |
| Since the test, how often have you played the build again? | Single choice | More than once; Once; Not yet, but I want to; Not at all | A day later |
| One day later, what do you remember most about the game? | Open text |  | A day later |
| After a failed run, how much did you want to start a new one? | Scale 1 to 5 | 1 = not at all; 5 = very much | Right after the session |
| How did it feel to solve a puzzle? | Scale 1 to 5 | 1 = I felt nothing; 5 = very satisfying | Right after the session |
| What are you thinking right now? | Open text |  | During the session |

#### Difficulty and pacing

| Question | Answer type | Options | When to ask |
| --- | --- | --- | --- |
| How easy or hard was the game for you? | Scale 1 to 5 | 1 = much too easy; 3 = about right; 5 = much too hard | Right after the session |
| Which level or moment was the hardest, and what made it hard? | Open text |  | Right after the session |
| How did the pace of the game feel? | Single choice | Too slow; About right; Too fast; It changed a lot | Right after the session |
| When you failed, what did you mostly feel? | Single choice | I knew what I did wrong; It felt like bad luck; It felt unfair; I did not fail | Right after the session |
| How did the length of the session feel? | Single choice | Too short; About right; Too long | Right after the session |
| When you failed, how fair or unfair did it feel? | Scale 1 to 5 | 1 = very unfair; 5 = very fair | Right after the session |
| How fair or unfair did the matches feel? | Scale 1 to 5 | 1 = very unfair; 5 = very fair | Right after the session |
| Right now, how easy or hard is this part? | Scale 1 to 5 | 1 = very easy; 5 = very hard | During the session |

#### Controls and UI

| Question | Answer type | Options | When to ask |
| --- | --- | --- | --- |
| How easy or hard were the controls to use? | Scale 1 to 5 | 1 = very hard; 5 = very easy | Right after the session |
| What did you play with? | Single choice | Keyboard and mouse; Controller; Touch screen; Steam Deck or other handheld; Other | Right after the session |
| Which action did not do what you expected? Tell us what you pressed and what happened. | Open text |  | Right after the session |
| How easy or hard was it to find information on the screen, such as health, goals and menus? | Scale 1 to 5 | 1 = very hard; 5 = very easy | Right after the session |
| How was the size of the text? | Single choice | Too small; About right; Too large | Right after the session |
| Which settings did you look for or change? | Multi choice | Key or button remapping; Audio volume; Graphics quality; Text size or subtitles; Difficulty; Language; None | Right after the session |

#### Bugs and performance

| Question | Answer type | Options | When to ask |
| --- | --- | --- | --- |
| What broke, froze or looked wrong? Tell us where it happened. | Open text |  | Right after the session |
| How many times did the game crash or freeze? | Single choice | Never; Once; 2 or 3 times; More than 3 times | Right after the session |
| What did you play on? For example: a Windows laptop with a GTX 1650, or a Steam Deck. | Open text |  | Right after the session |
| How smooth or choppy did the game run? | Scale 1 to 5 | 1 = very choppy; 5 = very smooth | Right after the session |
| How much did bugs get in the way? | Single choice | Not at all; A little; A lot; I could not continue | Right after the session |
| Which new problems did you find after the first survey? Tell us where they happened. | Open text |  | A day later |

#### Willingness to wishlist or buy

| Question | Answer type | Options | When to ask |
| --- | --- | --- | --- |
| Why did you stop playing? | Single choice | I reached the end of the build; I ran out of time; I got stuck; I got bored; A bug or crash stopped me; Other | Right after the session |
| Which game like this one did you buy most recently? What made you buy it? | Open text |  | Right after the session |
| Which game does this one remind you of? What does that game do better or worse? | Open text |  | Right after the session |
| Think of one person you know who would enjoy this game. What do they like to play? Please give no names. | Open text |  | Right after the session |
| Since the test, which of these have you done? | Multi choice | Added the game to my wishlist; Followed the game or the studio; Told a friend about it; Played the build again; Looked for videos or news about it; None of these | A day later |
| How did the end of the demo feel? | Single choice | It ended too early; It ended at a good point; It went on too long; I did not reach the end | Right after the session |
| Is this game on your Steam wishlist now? | Single choice | Yes, from before the test; Yes, I added it after I played; No; I do not use wishlists | Right after the session |

#### Price sensitivity

| Question | Answer type | Options | When to ask |
| --- | --- | --- | --- |
| What did you pay for the last game like this that you bought? Name the game and the price. | Open text |  | Right after the session |
| At what price would this game feel like a great deal? | Open text |  | Right after the session |
| At what price would this game start to feel expensive, so that you would need to think about it? | Open text |  | Right after the session |
| How do you usually buy games like this? | Single choice | At full price near launch; At the first discount; Only at a deep discount; In a bundle or a subscription; I rarely buy them | Right after the session |
| How many hours do you expect a full game like this to last? | Single choice | Under 5 hours; 5 to 10 hours; 10 to 30 hours; More than 30 hours | Right after the session |

## How to use it

1. Pick the "Playtest type", the "Game genre" and the "Session length".
2. Tick the goals under "Goals: what do you want to learn?". Untick them all to get the standard survey.
3. Optional: type the "Name of your game", and tick "Add a tester ID question, to join answers with analytics data".
4. Under "Your playtest survey", read the question count, the minutes and the note. If a goal got no question, pick fewer goals.
5. Click "Copy as plain text", "Copy as Markdown" or "Download CSV", then follow "How to paste this into Google Forms or Tally".

## How it works

The builder picks from a bank of 54 questions that we wrote. Each question has a goal, an answer type (a scale from 1 to 5 with both ends named, single choice, multi choice or open text) and a time to ask it: during the session, right after it, or a day later. Questions made for one genre or one playtest type only appear for that genre or type.

Every survey has the same frame: an optional tester ID, then "How often do you play games like this one?" and "Overall, how was the game?", and at the end the open question "What else do you want to tell us?". The frame asks broad questions before specific ones, which games user researcher Steve Bromley recommends.

The target count depends on the session length: 8 questions for under 15 minutes, 10 questions for 15 to 45 minutes, 12 questions for 45 minutes to 2 hours, 12 questions for several sessions over days. These targets are our practice, not a standard, and the tool shows them as a range from 6 questions to the target. The builder fills the space between the frame questions one goal at a time, in a fixed order (fun, onboarding, difficulty, controls, bugs, intent, price), until the target is full. With no goal ticked, it uses the core questions that work for most playtests.

An in-person session adds up to 2 neutral prompts to ask aloud during play. A demo, a closed test, a Steam Playtest or a test over several sessions can add up to 2 questions for a message one day later. The time is our estimate: 20 seconds for a closed question and 60 seconds for an open one, rounded to whole minutes.

```
questions = frame (2, or 3 with a tester ID) + goal questions + 1 closing question
target = 8 (under 15 minutes), 10 (15 to 45 minutes), 12 (45 minutes to 2 hours), 12 (several sessions over days)
minutes = round((closed questions × 20 + open questions × 60) ÷ 60), at least 1
```

## Worked example

### Example with made-up inputs: a Steam Playtest of a roguelike, 15 to 45 minute sessions

A studio runs a Steam Playtest of a made-up roguelike called Ember Rogue. It picks "15 to 45 minutes", ticks onboarding, difficulty and willingness to wishlist or buy, and adds the tester ID question. The target is 10. The frame takes 4 questions (tester ID, play habits, overall rating, closing question), which leaves 6 for the goals: 2 each.

The builder gives 10 questions. Difficulty gets the roguelike question "When you failed, how fair or unfair did it feel?", and intent gets "Is this game on your Steam wishlist now?", which only appears for a demo, a closed test or a Steam Playtest. 7 questions are closed and 3 are open, so the time is 7 × 20 + 3 × 60 = 320 seconds, about 5 minutes.

## How to read the result

Count the survey against its target. The survey for a session under 15 minutes takes about 5 minutes at 8 questions, and the longest one about 8 minutes at 12. If the note says a goal got no question, the session is too short for all your goals: drop one, or run a second playtest for it.

With 5 to 10 testers, read each answer as a story, not as an average. Jakob Nielsen found that tests with 5 users find about 85% of usability problems, so a small round is enough to find the big ones. To compare ratings between builds, the consumer playtest method from Microsoft Game Studios used 25 to 35 players per test.

On the difficulty question the middle of the scale is the target, not the top. Read it next to how far each tester got. For intent, trust the facts (a wishlist added, the build played again) over any rating.

Our practice for open answers: group them by the moment or feature they name, and count how many testers mention the same one. A problem that 3 of 5 testers name is worth fixing before the next round.

## Decide what you want to learn first

Write down two or three things you need to know about this build before you tick any goal, for example "do new players understand the first run" or "is the second boss too hard". These are your research objectives, and Steve Bromley advises to set them before you write questions. Tick only the goals that serve them. A survey is good at measuring opinions and simple facts. To learn why a tester got stuck, watch them play or look at where they quit in your play data.

## Why the survey is short

We keep the survey short, so that testers still have energy for the open questions. "Keep the survey short" is also one of the tips of games user researcher Steve Bromley. If you pick more goals than a short session can cover, the builder tells you which goals got no question. The target counts and the time estimate (20 seconds for a closed question, 60 seconds for an open one) are our own practice.

## What the survey does not ask

No question asks a tester to predict a purchase, and no question asks the tester to design a fix. Games user researcher Steve Bromley advises to never ask about future behaviour, because it correlates poorly with what players really do, and to ask about things that players did before. So the questions about buying ask for the last similar game the tester bought, for a wishlist that exists today and for the actions after the test.

## When to ask each question

Most questions belong right after the session, when the memory is fresh. An in-person session adds up to 2 neutral prompts to ask aloud during play. A demo, a closed test, a Steam Playtest or a test over several sessions adds up to 2 follow-up questions for a message one day later. Steam does not collect playtest feedback for you: Valve says that collecting feedback is up to you, for example in a forum, on Discord or on your own site.

## Pilot the survey before you send it

Before the playtest, have one teammate or friend fill in the form while you sit next to them, and ask what they think each question means. Five minutes of this catches confusing words and broken answer options. Steve Bromley lists this pilot as a step of its own. Then keep the questions and the scales the same from build to build, so the answers stay comparable.

## Where to put the survey link

Put the link where testers see it at the end of play: on the last screen of the build, in the pause menu, or in the message that sends the build. For a Steam Playtest, Valve suggests a Steam forum, Discord or your own site for feedback, and you can post the link in a community announcement. With the tester ID question, give each tester a link with the ID filled in, as the paste notes above explain for Google Forms and Tally.

## Limits

The builder writes the questions only. It does not host a form, collect answers or analyse them. Paste the survey into Google Forms, Tally or another form tool.

Estimate (20 seconds per closed question, 60 per open one) for the minutes. The count and the minutes also include prompts asked aloud during play and questions sent a day later, which are not part of the same form.

The question bank is fixed and in English. You cannot edit, reorder or add questions in the tool: copy the survey and edit it in your form tool.

Price answers are opinions. Read them as a range that testers accept, not as a sales forecast. No survey answer predicts how many players will buy.

A survey tells you what testers felt and remember, not why they did something. Watch testers play, or compare their answers with their play data, to find the cause.

## Which tool should I use?

Use this builder to write the questions for a test you already planned. Use the Steam Playtest or demo tool to choose the kind of test, the tracking plan generator to choose the events your build sends, and the demo conversion calculator after a demo is live.

- [Steam Playtest or demo?](https://manalens.dev/tools/steam-playtest-or-demo)
- [Game tracking plan generator](https://manalens.dev/tools/game-tracking-plan-generator)
- [Demo to full game conversion calculator](https://manalens.dev/tools/demo-conversion-calculator)

## Frequently asked questions

**How many questions should a playtest survey have?**

We aim for 8 questions after a session under 15 minutes and up to 12 after a long one. By our estimate, that takes about 5 to 8 minutes. This is our practice, not a standard. A short survey with open "why" questions gives better answers than a long form, because testers rush the end of a long one.

**What questions should I ask in a playtest survey?**

Start broad: how often the tester plays games like yours and an overall rating. Then ask about your goals, such as the first minutes, difficulty or controls, with both ends of each scale named, for example "easy or hard". Add open questions about the best and the worst moment. Ask about past actions, not future plans, and end with an open question.

**How many playtesters do I need?**

To find the big problems, a small round is enough: Jakob Nielsen found that 5 users find about 85% of usability problems. Fix them and test again. To compare ratings between two builds with some confidence, you need more: the consumer playtest method from Microsoft Game Studios used 25 to 35 players per test. Recruit players of your genre, not only friends.

**Does Steam Playtest have a built-in feedback survey?**

No. Valve says that collecting feedback from players is up to you. Steam handles signups and access to the playtest build, but not questions or answers. Make the survey in a form tool, then share the link in the build, in a Steam community announcement, in a Steam forum or on Discord. A tester ID lets you join the answers with play data.

**Should I ask testers if they would buy my game?**

No. Answers about future behaviour correlate poorly with what players really do, as games user researcher Steve Bromley notes. Ask about facts instead: is the game on their wishlist now, which similar game they bought last and why, and, a day later, what they did since the test. Those answers say more about real interest than a promise to buy.

**Why is there a tester ID question?**

It is optional. With an ID, you can put the answers of a tester next to what that tester did in the build, for example in Manalens after identify() with the same ID. Without an ID, you can read the answers but cannot join them to play data. Send each tester a link with the ID filled in.

## Sources

- [Steve Bromley, "How to write a playtest survey", Games User Research, 12 January 2022.](https://gamesuserresearch.com/how-to-write-a-playtest-survey/), read 2026-11-19
- [Valve, Steamworks documentation: Steam Playtest ("Collecting feedback from players is up to you").](https://partner.steamgames.com/doc/features/playtest), read 2026-11-19
- [Jakob Nielsen, "Why You Only Need to Test with 5 Users", Nielsen Norman Group, 18 March 2000.](https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/), read 2026-11-19
- [John P. Davis, Keith Steury and Randy Pagulayan, "A survey method for assessing perceptions of a game: The consumer playtest in game design", Game Studies 5(1), October 2005.](https://gamestudies.org/0501/davis_steury_pagulayan/), read 2026-11-19
- [Google Docs Editors Help: Choose a type of question for your form.](https://support.google.com/docs/answer/7322334), read 2026-11-19
- [Google Docs Editors Help: Publish and share your form with responders ("Send a form with pre-filled answers").](https://support.google.com/docs/answer/2839588), read 2026-11-19
- [Tally Help: Input blocks.](https://tally.so/help/input-blocks), read 2026-11-19
- [Tally Help: Bulk insert option lists.](https://tally.so/help/bulk-insert-option-lists), read 2026-11-19
- [Tally Help: Hidden fields.](https://tally.so/help/hidden-fields), read 2026-11-19

Last reviewed 2026-11-19. The survey is built in your browser. We do not send your choices anywhere.

## Related guides, tools and terms

### Guides

- [Playtest survey questions: what to ask your playtesters](https://manalens.dev/blog/playtest-survey-questions)
- [How to run a Steam Playtest](https://manalens.dev/blog/how-to-run-a-steam-playtest)
- [Playtest analytics: what to measure](https://manalens.dev/blog/playtest-analytics)
- [Best playtest and feedback tools for indie games](https://manalens.dev/blog/best-playtest-tools-indie-games)

### Tools

- [Steam Playtest or demo?](https://manalens.dev/tools/steam-playtest-or-demo)
- [Game tracking plan generator](https://manalens.dev/tools/game-tracking-plan-generator)
- [Demo to full game conversion calculator](https://manalens.dev/tools/demo-conversion-calculator)

### Glossary

- [What is a Steam Playtest?](https://manalens.dev/glossary/steam-playtest)
- [What is drop-off in game analytics?](https://manalens.dev/glossary/drop-off)
- [What is a funnel?](https://manalens.dev/glossary/funnel)

## Next step

Call identify() with the same tester ID in your build, and Manalens shows each tester's profile with their event feed and activity, so you can read the survey answers next to what that tester did. [See player profiles](https://manalens.dev/features/user-profiles)

## Guides that use this tool

- [itch.io for playtesting: restricted pages and keys](https://manalens.dev/blog/itch-io-playtesting)
- [In-game feedback surveys: join survey answers to player data](https://manalens.dev/blog/in-game-feedback-survey-player-data)

[Explore more game tools](https://manalens.dev/tools)

Interactive tool: https://manalens.dev/tools/playtest-survey-builder
