Which Steam key should I send to each group?

It depends on who receives it and whether the game is out. Valve offers three key types: Default Release, Release State Override and Dev Comp. A Default Release key can be activated at any time, but the game unlocks only after its Steam release. Valve writes that "Release State Override keys are intended for small beta tests and press/influencer access." Dev Comp keys are for your own developers and should never go to customers.

Steam curators need no key at all. Valve describes Curator Connect as a way to send a review copy "directly and immediately through Steam. No need to mess with e-mails or keys." Playtests have their own app: Valve says "Most developers will find using Playtest keys easier and safer to work with than Release State Override keys for their base game."

Giveaways are the case to watch. Valve says "Steam Keys shouldn't be given away for free if you aren't also offering the same deal (i.e., give the game away for free) to Steam customers. This includes giveaways for promotional purposes, unless that giveaway is very small (under 100 Steam Keys)." For a larger giveaway on Steam, Valve asks you to submit a ticket.

Which way to give a copy to each group, with the Valve rule for each. Read in the Steamworks documentation on 19 November 2026.
RecipientWhat to sendValve rule
Press before launchRelease State Override keyFor small betas and press or influencer access; generally limited to 2,500 in total; never sold
Creators before launchRelease State Override keyThe same pool of 2,500 as press
Press and creators after launchDefault Release keyUp to 5,000 for a launching game, then case by case
Steam curatorsCurator Connect copy, no keyOffers to 100 curators, at most 5 copies each; needs a public store page and an uploaded build
PlaytestersSteam Playtest keysStandard Release keys for the playtest app; requests above 50,000 suggest an open signup instead
Giveaway winnersDefault Release keyUnder 100 keys, unless Steam customers get the same free deal
Your own teamDev Comp keyDeveloper use only; never for customers

Sources: Steamworks Steam Keys documentation; Steamworks Curators and Curator Connect documentation; Steamworks Steam Playtest documentation.

How do I request keys in Steamworks?

With the "Request Steam Product Keys" button on the landing page of your app. If the button is missing, your account lacks the "Generate Steam Keys" permission, so ask the account admin to add it. Keys are always requested from a specific Steam package.

A first game has to wait. Valve says "Developers launching their first game on Steam must wait three weeks after the creation of an AppID before they can request Steam keys." Plan the press and creator wave around that date, not around the day you finish the build.

Every request is reviewed, and Valve can say no. It looks at the level of customer interest on Steam, the keys already issued and activated, and the number you ask for. A request can also be denied because it asks for Release State Override keys, which make the game playable as soon as they are activated. Valve also notes that a deal you agree with a partner does not oblige it to provide keys.

When a request is processed, you download the keys as a zip file with a plain text file inside. Valve says "Keys are only available for download by the user that requested them." So the person who sends the keys should be the person who requests them.

  1. Upload a build that press and creators can play, and set up the coming soon page.
  2. Check that your account has the Generate Steam Keys permission.
  3. Open your app in Steamworks and click Request Steam Product Keys.
  4. Choose the package and the key type for this wave: Release State Override before launch, Default Release after it.
  5. Enter a small count and a tag for the channel or campaign, then submit.
  6. Download the zip once the request is processed, and paste the keys into your key log before you send any.

Sources: Steamworks Steam Keys documentation.

How should I split keys into batches?

One batch for each channel or campaign: press for the demo, creators for the launch, a giveaway on one site. Valve says to request keys in small batches and to tag them so you can keep track of them in the future. It gives a country tag for a retail batch as an example, and calls tagging an accountability measure.

Small batches also limit the damage. Valve writes: "In general, you should treat keys like cash." If one batch leaks, you can find it and ban it without touching the others.

Do not expect Steamworks to count activations for you by batch. The Key Stats section shows the total activated and unactivated keys from all packages that include your app, and the keys revoked with the ban tool. The Query Steam Key page looks up one key at a time. Valve documents no report that splits activations by tag, so your key log does that work, and our activation tracking guide shows how.

An example batch plan for a made-up game before and after launch. Counts are examples, not advice.
Batch tagKey typeKeysWho gets them
press-demoRelease State Override25Writers who cover the genre, before the demo
creators-demoRelease State Override40Video creators you checked by hand
press-launchDefault Release30Reviewers in launch week
giveaway-discordDefault Release20Winners of one community giveaway, under the 100 key limit

Sources: Steamworks Steam Keys documentation.

How do I send the keys?

Choose by who you are reaching. A short list of people you picked yourself works best by direct email: one key in the email, from the batch for that channel, with a tagged link to your store page. Curators get Curator Connect. Inbound requests from creators you do not know are where a key platform helps, because it vets the channel for you.

The order below is our judgment of fit for a small studio that sends its own keys. Each fact comes from the page of the platform, read on 19 November 2026, and we did not run campaigns on any of them. Manalens does not distribute keys, so it is not in the list. Our list of creator platforms compares more options in depth.

Ways to send Steam keys or copies, in our order of fit for a small studio. Facts from each page, read 19 November 2026.
OptionWhat its own page saysOur note
Curator Connect (Valve)Copies go directly through Steam, with no keys; offers to 100 curators, up to 5 copies eachFree and nothing to resell, but it reaches only Steam curators
Direct emailNo platform: you send a key from a tagged batchBest for a short, hand-picked list; you do the vetting
KeymailerSays it has "Full-time anti-fraud staff" and that 2 people review every channel manually; lists a free tierGood for inbound creator requests; we could not open its plan page, so check the price yourself
LurkitSays it manually verifies every creator who signs up; key campaigns on Twitch, TikTok and YouTube; plans say "Contact for pricing" and Quests carry a 20% commissionUseful when you also want paid campaigns; ask for a price first
PressEngineA free Starter account with "Full review key management"; paid plans from £300 per monthUseful when the same tool must reach press as well as creators

Sources: Steamworks Curators and Curator Connect documentation; Keymailer page for publishers; Lurkit key campaigns and pricing pages; PressEngine pricing page.

When should I send keys, and how do embargoes fit?

Send keys once the build is ready to be judged, and early enough for the work to be done before your date. A Release State Override key is playable as soon as it is activated, and so is a Curator Connect copy, even before the game is for sale. A Default Release key sent before launch only unlocks on release day, so it suits a launch review but not a preview.

An embargo is a promise you ask for, not a setting in Steam. Nothing in the key stops a writer from posting early, so put the embargo date and time in the email next to the key, and give the same time to every outlet. Our press coverage guide covers the embargo line and the timing of each pitch.

Two Valve rules affect timing. First, if a player has your game on their wishlist and activates a Release State Override key, Valve says "it will remove your game from their wishlist." A creator who wishlisted early leaves your count when they redeem. Second, a review written from a copy before release is marked as a "Pre-Release Review", and only purchases count in the review score.

Keys for press are allowed under the review rules. Valve forbids offering anything in return for reviews, with one exception: "The exception is sending a copy of your game to press or internet personalities to get previews or reviews." Do not make the key depend on a positive review.

Sources: Steamworks Steam Keys documentation; Steamworks Curators and Curator Connect documentation; Steamworks User Reviews documentation.

How do I check a key request before I answer it?

Reply through the contact listed on the real channel or outlet, never only to the address that wrote to you. Valve warns: "We've heard many reports of fraudsters impersonating journalists or storefronts to acquire keys, and then reselling those keys for profit."

Our practice is a quick check, then one key. Look at whether the channel is active and covers games like yours. If a curator asks by email, send the copy through Curator Connect, where only the real curator can accept it. Our scams guide lists the signs of a fake request in full.

Sources: Steamworks Steam Keys documentation; Steamworks Curators and Curator Connect documentation.

How do I revoke unused or leaked keys?

Use the Ban or Disable Steam Keys page in Steamworks. Valve lists proactively disabling unused keys, ending a closed beta and revoking refunded keys as common reasons. In the second step you choose to ban every key in the batch or only the keys that were not yet activated. You may ban only keys that you have the rights to.

Keys do not expire on their own. Valve says players who activated a beta key before release keep the game, so a press wave from before launch keeps access until you ban those keys. When you end a beta this way, you can mark the reason, so players see a friendly message that their access ended.

Take care with sold keys. Valve says "You should never ban or disable Steam keys that have been legitimately sold to customers." You may ban keys whose license has expired, such as at the end of a beta, and keys that were stolen or bought fraudulently. A key found on a reseller site points you to its batch through your log.

Two copies cannot be pulled back. Valve says "You cannot revoke a game from a Steam Curator once they have accepted it", though you can expire an offer that was not yet accepted. For a Playtest, "a key, once granted, is not revoked if the Playtest is later marked Not Playable"; a reset of the Playtest disables all its product keys.

Sources: Steamworks Steam Keys documentation; Steamworks Testing on Steam documentation; Steamworks Curators and Curator Connect documentation; Steamworks Steam Playtest documentation.

What should my key log look like?

A sheet with one row for each recipient, filled in on the day you send. Steamworks keeps no field for the person who got a key, so the log is the only place where a key, a person and a result meet.

Fill the Activated column when the person confirms it or a curator accepts the copy, and the Coverage link column when a video or article appears. Valve does not say what a single key query shows, so check it in your own account before you rely on it. The example rows are for a made-up game and made-up people.

A key log template with example rows for a made-up game. Copy the headers into your own sheet.
DateRecipientPlatformBatchKey countCampaign linkCoverage linkActivated
3 FebSam Lee, PC games siteDirect emailpress-demo1utm_source=sam_lee&utm_campaign=demoPreview, 10 FebYes
4 FebA cozy games curatorCurator Connectnone (no key)2noneCurator review, 12 FebAccepted
5 FebA YouTube creatorKeymailercreators-demo1Short link with the Creator field setPendingNo

Sources: Steamworks Steam Keys documentation; our template.

How do I measure the result?

Note the Key Stats totals before and a week after each batch, keep the detail for each person in your log, then read what each recipient sent to your store page. Give every recipient a tracked link: the Steam UTM report counts wishlists, purchases and key activations within 72 hours of a click by a visitor signed in to Steam, and finalizes them 4 days after the visit. Manalens is the analytics and growth engine built for games. A short link for each recipient records every click, and the import of the Steam UTM CSV shows visits, wishlists and activations by source and creator next to those clicks; the automatic Steam sync of all wishlists and sales is in early access.

Sources: Steamworks UTM Analytics documentation; Manalens short links and Steam documentation.

Frequently asked questions

How many Steam keys can I give to press and creators?

Before release, Release State Override keys are generally limited to 2,500 in total, and press, creators and beta testers share that pool. After release, a launching game may receive up to 5,000 Default Release keys, and Valve reviews larger requests case by case. Send one key per person, in small tagged batches.

Should I send a Default Release key or a Release State Override key?

Send a Release State Override key when the person must play before launch, such as for a preview or a review at launch. Send a Default Release key after release, or when the copy can wait for release day, because it unlocks only then. Never sell Release State Override keys.

Can I use Steam keys for a giveaway?

Yes, if it is small. Valve says keys should not be given away free unless Steam customers get the same deal, except for a very small giveaway of under 100 keys. For a giveaway on Steam itself, Valve asks you to submit a ticket. Use a separate tagged batch for each giveaway.

Do I need keys for Steam curators?

No. Curator Connect sends a copy of the game directly through Steam, with no key, to up to 100 curators and up to 5 copies each. It needs a public store page, an uploaded build and the Generate CD Keys permission. Curators do not have to accept, play or review the game.

Can I take back a key after I send it?

You can ban it in the Ban or Disable Steam Keys tool, for the whole batch or only unactivated keys. Valve says never to ban keys that were legitimately sold to customers. Keys do not expire, and a Curator Connect copy cannot be revoked once the curator has accepted it.

Should I use Release State Override keys for a big beta?

No. Valve points larger tests to Steam Playtest, where you can request Standard Release keys for the playtest app and control access with the Playable setting. Release State Override keys are generally limited to 2,500, and Valve says requests above 50,000 Playtest keys suggest opening signups instead.

Sources and implementation