Skip to main content
Key Distribution lets you provide players with the keys or access codes they need to launch your game. Each playtest has its own key vault, which keeps the keys used for that playtest separate from other tests.

Playbooks

Hand out game keys

Give each player a Steam key or a code of your own as they join.

Stock a key vault

Load Steam keys or your own codes, and pick the right Steam variant.

How it works

When a player reaches key distribution:
  1. Userplay selects an available key from the playtest’s vault.
  2. The key is assigned to that player.
  3. The player can use the key to access your game.
Key Distribution is useful when players need a Steam key or custom code to access a build.

Where it appears in the player flow

Key Distribution runs after players receive the build and before the session briefing. Players:
  1. Access the game build.
  2. Receive their key or access code.
  3. Follow your launch instructions.
  4. Start playing.

Add keys to your playtest

Enable Key Distribution from the Config tab to add the Keys section to your playtest.
1

Enable key distribution

Open the Config tab and enable Key Distribution from Playtest Settings.This adds the Keys section to your playtest.
2

Add keys

Open the Keys section and add your keys using one of these methods:
  • Paste keys to add keys manually, one per line.
  • Import from CSV to upload a list of keys.
  • Import from key vaults to copy keys from an existing vault.
Duplicate keys are automatically skipped.
3

Choose the key type

The first batch of keys creates the playtest vault.By default, it is a Steam key vault. You can change it to a custom key vault or configure the Steam key type based on what the key unlocks.

Key limits

Key limits by plan

How many keys one vault can hold on each plan.
Load more keys than your expected player count. For example, if your player cap is 100, consider adding 200 to 300 keys to avoid running out as more players join.

Playtest key vaults vs studio key vaults

Keys added through a playtest belong only to that playtest. A playtest key vault:
  • Is created specifically for one playtest.
  • Cannot be reused across other playtests.
  • Does not have a public redeem link.
For reusable key pools, create a studio-level key vault instead. Studio key vaults can be shared across playtests and can provide keys through their own redeem links.

Key status

The table shows each key’s status as it moves through the vault. Redeemed means the key was disclosed to the player, not that they clicked toward it. Keys has the full detail on key types, Steam variants, and redeem scopes.

Hand out game keys

Walks the whole job, from an empty vault to a published playtest.

Key vaults

The studio-level vault and how it differs from this one.

Migrate your key inventory

If the keys you need are sitting in a spreadsheet.

Keys

Add, import, and track the keys sitting inside a vault.