How Many Steam Keys Should You Send to Influencers?

The short answer, by launch size

There is no universal number, but these ranges hold up for a typical solo-to-small-team Steam launch where you are personalizing every pitch: a quiet first launch with a small wishlist base needs 30-50 keys total; a launch with an active demo, a Next Fest appearance, and a warm press list needs 60-100; a well-hyped launch with a publisher or an established following can justify 100-200. Above that you are almost certainly mass-dumping rather than curating.

These totals are per campaign, not per creator, and they cover creators plus curators plus a small reserve for last-minute yeses. The number is deliberately far below Valve's 5,000 default cap. Keys are cheap to generate; the scarce resource is the personalized outreach behind each one and the attention it asks for.

If you are tempted to send 500 keys 'to be safe,' stop. A pile of unsent keys costs nothing to hold in reserve, and a pile of sent-but-untracked keys is how leaks, gray-market resales, and zero-accountability campaigns happen.

What Valve actually lets you generate

Per the Steamworks documentation, a game launching on Steam may receive up to 5,000 Default Release Steam Keys without any individual review. After that threshold, all Steam Key requests are reviewed case-by-case, and Valve is explicit that there is no guarantee you will be provided additional keys.

Pre-release access is separate and tighter. Release State Override (beta) keys — the ones that unlock your game before its public launch, ideal for pre-launch creator previews — are generally limited to 2,500 total, and Valve states it is never OK to sell them. If you need large-scale pre-launch testing, Valve points you to the Steam Playtest feature instead of burning override keys.

Two rules shape how you request keys. First, Valve reviews requests against customer interest on Steam and the number of keys already issued and activated — a request looks bad if it is disproportionate to your actual Steam sales. Second, you must not give Steam customers a worse deal than key purchasers; requests are rejected when there is an imbalance versus what Steam buyers are offered. Neither rule bites a normal 30-100-key creator campaign, but both are why 'generate 5,000 and blast them out' is a bad habit.

Budget keys by creator tier

Match key volume to fit, not to follower count. A workable split for a first campaign, from a shortlist of 40-60 researched creators:

Nano and micro creators (roughly 1k-50k subscribers/followers): this is the core of an indie campaign. Send 20-40 keys here, one personal pitch each. Small, engaged channels are far likelier to actually play a niche indie than a channel with a million subscribers, and they convert to genuine coverage more often.

Mid-tier creators (roughly 50k-500k): send 8-15 keys, and only to creators who demonstrably cover games like yours. These take more personalization and patience, and a lower share will respond, so keep the batch tight.

Curators and press: use Steam Curator Connect for the curator side — it lets you reach up to 100 curators with a maximum of 5 copies each, directly on Steam, and copies delivered this way don't spend your CD-key allocation. Reserve a separate handful (5-15) of direct press/outlet keys.

Add a small reserve — 10-15 keys — for opportunistic yeses, a creator who replies asking for a couple of copies for a giveaway, or a mid-campaign discovery. Everything above these buckets is speculative; hold it back until a real recipient exists.

Phase the send: preview batch vs launch-week batch

Do not send every key on launch day. Split the campaign into two or three timed waves so coverage lands when it moves wishlists and sales, not a week after everyone has moved on.

Preview batch (2-4 weeks before launch): send Release State Override keys to your 10-20 highest-fit creators and to curators via Curator Connect. This buys them time to play, record, and schedule. One published outreach playbook recommends having a build ready 2-3 weeks before release and doing beta-stage outreach 2-6 months out for larger creators who plan further ahead. Ask for an embargo through your launch day if you want the coverage to cluster.

Launch-week batch (day-of through the first few days): send the remaining creator keys plus a fresh follow-up to anyone from the preview batch who went quiet. This is also when to release giveaway keys — the Xsolla playbook suggests adding 10-15 giveaway keys to a creator's email so they can run a community giveaway alongside coverage.

Optional third wave (post-launch): hold a small reserve for creators who surface after launch or for a discount/update spike. Keys don't expire, so an unsent reserve loses nothing by waiting.

Coverage reality: most keys will never turn into a video

Set expectations before you count keys. A meaningful share of sent keys never produces coverage — creators get busy, the game isn't a fit after they try it, or the pitch never got read. This is normal and is exactly why you send keys to a curated shortlist with follow-ups rather than one identical blast.

Follow-ups matter more than volume. Outreach research consistently shows a single follow-up materially lifts reply rates, and disciplined senders use a short sequence (initial email plus 2-3 follow-ups) rather than one-and-done. Sending twice the keys with no follow-up will underperform sending half as many with a two-touch sequence.

Because the hit rate is low, over-send slightly at the tier level (a few extra micro-creator keys) rather than globally (hundreds of untargeted keys). The former costs you a bit more personalization; the latter costs you control and invites abuse.

Protect your keys: don't mass-dump, and watch for resale

Open 'request a key' forms are the fastest way to leak keys to resellers and low-effort accounts. Early in a campaign, when each key represents a real relationship, hand-pick every recipient. Gated or public request forms only make sense once you have keys to spare and a way to vet requests.

Steam gives you enforcement levers if a key is abused. Keys can be banned or disabled from the Steamworks Ban or Disable Steam Keys page — common cases include proactively disabling unused keys, revoking closed-beta access, and revoking keys that were refunded. If a key you sent to a specific creator shows up on a gray market, you can act, but only if you know which key went to whom.

That traceability is the whole point of tracking. A key sent into a spreadsheet cell labeled 'batch 2' is untraceable; a key logged against a named creator, a send date, and a status is auditable and revocable.

Give every key an owner and an outcome

The most common and most expensive mistake is losing track of who holds which key and whether it produced anything. Tag every key with the creator it went to, the date sent, and its current pipeline status. That converts a pile of keys into a measurable funnel: how many were sent, viewed, replied to, and turned into coverage.

CreatorScout is built for exactly this loop. It finds YouTube and Twitch creators who already cover games comparable to yours, relevance-ranks them so your shortlist is real, and surfaces contact emails so the outreach step isn't a research project. Then its outreach CRM tracks each creator through Not Contacted, Key Sent, Key Viewed, Replied, and Covered — so the tiered budget and phased waves above stop being a spreadsheet you forget to update.

Each key lives in a masked Steam-key field on that creator's record, with a per-creator outreach history logging every touch and status change. That masked field means keys aren't sitting in plain text in a shared sheet, and the timeline gives you the audit trail you need if a key is misused or if you simply want to know, three weeks post-launch, which of your 60 keys actually earned a video.

Frequently asked questions