Skip to main content
Two decisions and one bulk paste. Set the key type before you load anything, since it decides what belongs in the vault. You can change it later from the About tab if you get it wrong.

Take the guided tour

Load a batch of keys into a vault and watch the inventory fill.

What you need first

  • The keys themselves. Steam keys generated in Steamworks, or codes your studio issues.
  • A decision on the kind of vault. A custom vault is studio-level, reusable, and can carry its own redeem link. A system vault belongs to one playtest and cannot be reused. Neither converts into the other.
  • Time for more than one pass. A single import takes 300 keys and a vault holds 1,000, so filling one completely takes four imports.

The playbook

1

Create the vault

Go to Vault in the sidebar.
  • Click Create key vault.
  • Name the vault on the wizard.
  • Click Create key vault again to finish.
Use that playtest’s Keys tab instead. It creates a system vault for you, scoped to that playtest alone.

Key vaults

System vaults against custom vaults, and what each one can do.

Key distribution

The vault a playtest builds for itself, and why it cannot be reused.
2

Set the key type

On the vault’s About tab, open the Key type card and pick Steam key or Custom key.
A custom key is any code you issue outside Steam: a build password, a license string, a launcher invite.
3

Pick the Steam variant and scope

A Steam vault adds two more fields to the same card.
  • Set Steam key type. Steam Playtest is the default and usually the right answer.
  • Set the redeem scope to Game, DLC, or Bundle.
The variants differ in what Valve grants and how many keys Steamworks lets you generate. Choose before you generate anything.

Keys

Every Steam variant, what Valve grants for each, and the quantity caps.

Hand out DLC or bundle keys

Playbook: pick the variant and scope that grants what you intend.
4

Load the keys

On the Keys tab, click Add keys, then pick how the keys come in.
Type or paste keys directly, one per line.
Duplicates already in the vault get skipped, so re-pasting a batch you are unsure about is safe.

Migrate your key inventory

Playbook: bring a pile from elsewhere over in 300-key batches.

Check how many keys were claimed

Playbook: watch the pile drain once it starts handing keys out.

Point the vault at something

A stocked vault does not hand out anything on its own. Pick a distribution route from the vault header or from a playtest.

Give keys away with a redeem link

Playbook: publish the vault and let people claim a key themselves.

Hand out game keys

Playbook: give every player a key as they join a playtest.

How you know it worked

  • The Keys tab lists your keys, each badged Available since nothing has been handed out yet.
  • The vault reads back the key type you set, and for a Steam vault, the variant and what it unlocks.
  • Re-pasting a batch you already loaded adds nothing. It tells you how many were skipped.
  • The Analytics tab appears once you publish the vault. It stays hidden while a custom vault is still in draft.

Keys

Every Steam variant, what Valve grants for each, and how a key’s status moves.

Key vaults

System vaults vs. custom vaults.

Migrate your key inventory

Playbook: bring an inventory over from elsewhere, in batches.

Vault analytics

Watch the pile drain once you start handing keys out.