How to Set Up a Steam Playtest

Running a playtest on Steam can feel complicated the first time, but using the Steam Playtest functionality makes the process smoother, more flexible, and easier to control. This guide explains why Steam Playtests are recommended, clears up common misconceptions, walks through how to set them up in Steam and then shows how to use FirstLook to distribute keys and manage tester access.

Why Use Steam Playtest Apps?

Steam Playtests are the preferred way for studios to run playtests because they offer more flexibility, fewer risks, and fewer limitations than traditional key-based approaches.

Advantages of Steam Playtests

• Distribute up to 50,000 keys, compared to the standard 2,500 limit on Release Override Keys.
• Players with Playtest Keys can still wishlist, purchase, and review your game normally.
• You can toggle playability on/off without revoking or reissuing keys.
• No need for a completed or public store page - Playtest Apps can remain minimal and hidden.

Common Myths About Steam Playtests

”Playtest Apps shouldn’t be used for confidential testing.”

Not true.
Steam Docs make it sound risky to release a playtest app since there is not an NDA in place for play testers. While it is true Playtest Apps do not include NDAs by default, FirstLook easily adds NDA requirements during onboarding.

”You need a fully completed Store Page before you can use Playtest Apps.”

Not true.
A Store Page technically exists but does not need to be public or complete. You only need capsule images and minimal assets for review and using a codename is common practice.

”The Request Access button must be visible on your store page.”

It doesn’t.
You can hide the Request Access button entirely and distribute access solely through FirstLook.

Setting Up a Steam Playtest

Follow these steps inside Steamworks:

1. Create a Playtest App
   Go to your base game’s Associated Packages & DLC section and add a new Playtest App.

2. Add Required Assets
   At minimum, upload Library Capsule and Community Capsule images.
   Tip: The Playtest App name cannot be changed after publishing, so if you want to change it - change it now.

3. Complete the Review Process
   Your app must go through a lightweight Store and Build review. This review typically only checks capsule images and icons.

4. Configure Playtest Behavior
   Once approved, visit Manage Your Steam Playtest to set visibility and launch permissions:

   • Playtest Status
     • Playable: Players can launch the build
     • Not Playable: Access stays in the library but cannot be launched
   • Store Visibility
     • Visible: Request Access appears on your main game’s store page
     • Hidden: The playtest stays invisible
   • Signup Type
     • Open: No approval needed
     • Limited: Players must request access

5. Request Playtest Keys
   Go to Manage Keys → generate the number of keys you need → download and import them into FirstLook.
   Need more than 50,000? Submit a Steam support ticket.

6. Publish Your Playtest App
   Select:
   See Release Steps → View Release Options → Prepare for Release → Publish Now

7. Start Your Playtest
   Once published, your Playtest App is live.

8. Turn Off Access Afterward
   No need to revoke keys—just change Playtest Status to Not Playable until the next test.

---

Connecting Steam Playtests to FirstLook

Once your Playtest App is ready, FirstLook helps you manage access, distribute keys, and guide players through onboarding.

1. Create a Key Type
   Add a new Steam key type in Keys and import your Playtest Keys.

2. Configure Your Flows
   Set up Flows to control your player journey through FirstLook.

3. Connect Keys to Roles
   Assign the Steam key type to the appropriate Flow Role.

4. Invite Players
   Use FirstLook’s Invite tools to bring players into your playtest.

   When they complete onboarding, their Steam Playtest Key is assigned automatically.

Removing Steam Playtest Keys (If Needed)

In rare cases, you may need to revoke or cycle keys. If so:

Key Removal Workflow

1. Delete keys in Steam (you can upload a list exported from FirstLook).
2. Tag relevant players in FirstLook for tracking.
3. Revoke the keys in FirstLook (contact support for large batches).
4. If using a new batch of keys from the same pool you are all set. Otherwise, create a new key type and make sure to add that into your flow and remove the old keys.
5. Manually assign keys to previously onboarded players. New players will receive them as part of the standard flow.
6. Key changes do not trigger automatic emails. We recommend using Announcements to notify players of the key change.

Summary

Using Steam Playtests gives you more control, more keys, and fewer risks while FirstLook handles onboarding, NDAs, Discord Access, and key distribution.

This combination gives studios a clean, scalable playtesting workflow with minimal operational overhead.