Skip to main content
A playtest is a single testing campaign. You build it in the editor, publish it, and share the link. Players join, play, and answer your questions. You get back sessions, submissions, and results.

Playbooks

Single session

One sitting, one survey. First impressions or a feature check.

Survey only

Hand out a build, ask questions, record nothing.

Launch a playtest

Preview, publish, share the link, announce it.

Change a live playtest

Work out whether you need to unpublish at all, then edit safely.

Stages

Every new playtest starts as a draft. Publishing moves it to Published, and from there it can toggle between Published and Unpublished. It never returns to Draft.

Configuring your playtest

Playtests are modular. Start with the core configuration and enable additional features as needed. Each feature adds its own settings to the playtest editor. The Players tab appears automatically once your playtest has a player roster. Announcement and Screening are offered on open playtests only, and Announcement also needs a connected Discord server. Without one the row stays visible but inert, so you can see the feature exists and what it is waiting for.
Two toggles lock the moment you publish. Gameplay Recording sizes the session reservation, and Screening freezes the questions players already answered. To change either one, unpublish first.

Playtest announcements

Writing the message, what publishing it costs, and how the Join button follows a link reset.
Recording is not required. A build plus a survey is a complete playtest, and with Gameplay Recording off, nothing is reserved against your balance.

The player journey

Players move through your playtest in a fixed order, letting you decide which steps are enabled for the players.
1

Before gameplay

Players complete any onboarding requirements you’ve enabled, such as identity verification, accepting an NDA, and player screening.
2

During gameplay

Players receive their game build or game key, read any session briefings, and complete their gameplay session. Session objectives can be shown while they play.
3

After gameplay

Players complete your session survey, if one has been configured.

Session flow

See every screen that players encounter during the playtest experience.

What you get back

Once players complete your playtest, Userplay collects everything in one place.
  • A session contains gameplay recordings, transcripts, highlights, and other session data.
  • A submission represents a player’s overall participation in the playtest.
  • Results aggregate feedback and analytics across all players.

Sessions

Explore gameplay recordings and session data.

Submissions

View each player’s participation across sessions.

Results

Analyze feedback and playtest results.

Next steps

Create a playtest

Walk the create wizard, and see what a fresh draft already has switched on.

Playtest types

Single, multi, or longitudinal, and how many sessions each player runs.

Access

An open share link with a player cap, or a closed email roster.

Preview the flow

See the screens a player gets, before anyone can reach them.

Playtest players

Who is on the roster, and what locks once you publish.

Publishing a playtest

What has to be in place before a playtest can go live.