Skip to main content
Questions that come up often enough to answer here, where the answer is not already a page of its own. For plans and prices, start at billing. If something is going wrong, try studio troubleshooting first.

Getting started

No. The whole flow runs in the browser, and the player needs Chrome, Edge, or Firefox.
No. Userplay makes no changes to your game and needs none from you. Screen and microphone capture happen in the browser, alongside the game rather than inside it.
Any engine, any store. Userplay never touches your build. It hands players a URL you supply, whether that points at Steam, the Epic Games Store, or your own launcher.You can set the game’s platform under Settings > Game: Windows, macOS, or Web.
You bring them. Four ways, and they combine:
  • Publish an open playtest and share its link. Anyone who opens it can join, up to your cap.
  • Seed a closed roster by email, by hand or by CSV.
  • Reuse a player group you built earlier.
  • Announce the playtest to your server through the Discord integration.

Running a playtest

As many as you want, with as many players as you want, on every plan including Free. The only metered thing is recorded gameplay sessions.Fair use limits exist, but they are the same on every plan and are there to keep the platform running, not to sort studios into tiers.
No, but you have to opt out. Gameplay Recording is a toggle in the Playtest Settings card on the Config tab, and it starts on.Turn it off and the playtest still handles everything else: onboarding, an NDA, screening, build and key distribution, briefings, objectives, and a survey. It also costs nothing against your plan, because nothing gets recorded.
No. Screen and microphone have two states, Required and Optional, with no third option. Every session where recording is on captures at least optionally, because both need the player’s explicit consent and the flow is built around asking for it.If you want a session to record nothing at all, turn off Gameplay Recording on Config. That switches the whole feature off for that playtest.

Players

Yes. Paste or upload emails by CSV, either into a playtest’s roster or into a reusable player group you can attach to any future playtest.
Not on their own. The screening verdict sticks to the player, so reopening the link puts them back on the same “Not the right fit this time” screen.If you changed the eligibility rule after they answered, contact support and the team can clear the verdict.

Data and billing

Recorded gameplay sessions, and only when a session actually records something. Playtests, players, invites, surveys, and builds are all free.Publishing reserves the playtest’s full capacity up front: player cap (or roster size) times session count. Unpublishing refunds the gap between what was reserved and what actually recorded.
Recordings are visible only to your studio’s team, and all traffic runs over TLS. Production platform and recording data is hosted in the United States; there is no regional residency option today.Userplay’s security policies, architecture notes, and subprocessor list are published at userplay.io/security.
As long as you tell it to. Every plan sets its own retention window under Settings > Studio, and once a session passes that window, its data is permanently removed.
Yes, one dataset at a time rather than as a single dump. Export from a playtest, from a session, or through the API. The export catalog lists what is available.

Concepts

The model behind studios, games, playtests, and sessions.

Studio troubleshooting

What to check when something is wrong on your side.

Player troubleshooting

What to check when a player says the link is broken.

Contact support

For everything this page did not answer.