Steam Page Conversion Rate: What’s Normal? (2026)

Last updated: 2026-07-05 · Reading time: 7 min

Short answer: “Steam page conversion rate” is three different funnels, and most quoted numbers silently mix them up. Capsule CTR (impressions → visits) is mostly a visibility artifact — don’t optimize it. Visit → wishlist runs in the low single digits on resting-week, all-source traffic (documented examples: 2.7% and 4.7%) and several times higher on targeted, high-intent traffic — the median demo player converts at ~16%. Wishlist → sale at launch runs 15–25% by tier. Before you judge any of your numbers, fix which funnel and which traffic you’re looking at.

The three funnels people call “page conversion”

The third funnel has its own guide — Steam wishlist conversion rate — and a calculator that turns a wishlist count into a launch-week sales range. This page is about the first two: what happens before anyone owns a wishlist.

Visit → wishlist: the number that depends on who’s visiting

The most honest published data points come from How To Market A Game’s store-page teardowns, which measured full resting weeks (no promotion, no festival, no discount) across all traffic sources: 4.7% of visitors wishlisted one game, 2.7% another. Low single digits. If you’ve been comparing your Steamworks numbers against a “10–30% page conversion” figure you saw somewhere, that mismatch isn’t your page — it’s the denominator.

Resting-week traffic is dominated by low-intent algorithmic browsing: discovery-queue flips, tag-page scrollers, “more like this” wanderers. Most of them were never going to wishlist anything. Put a high-intent audience on the same page and the rate transforms — the cleanest public measurement is demo players: the median demo converts ~16% of its players into wishlists (30th percentile 12%, 70th percentile 20%). Same store page, different intent, a 3–5× different conversion rate.

Which is why the only benchmark that means anything is your own page against its own history, sliced by source. Steamworks’ traffic breakdown plus a UTM link on your external campaigns gives you per-source visit counts; divide same-window wishlist adds by them and track the trend, not the level. (One caveat when you get to paid campaigns: Steam’s UTM dashboard only credits same-session wishlist adds, which under-reports campaign-driven wishlists by ~75% — judge campaigns on recovered lift, not the dashboard number.)

Capsule CTR: measure it once, then leave it alone

Steam computes click-through rate as page views ÷ capsule impressions, and the same survey of 100+ developers behind that article found CTR only weakly tracks wishlist output. The mechanism is adverse: when Steam’s algorithm trusts your game, it sprays your capsule across low-intent surfaces and your CTR drops while your absolute page views rise. A “bad” CTR is often a symptom of good visibility. The quantities that actually correlate with wishlists are impressions and page views — scale, not efficiency. Make the capsule legible at thumbnail size, make the genre readable at a glance, and then spend your energy on traffic, not CTR decimal points.

Page problem or marketing problem? The diagnostic

The reason to measure visit→wishlist at all is that it splits every “my wishlists are flat” complaint into exactly one of two diagnoses:

• Visits healthy, conversion at or above your baseline, wishlists still flat → marketing problem. The page is doing its job on the traffic it gets; there just isn’t enough of it. More outreach, festivals, streamers, content — a better trailer won’t fix a traffic drought.
• Visits healthy, conversion sliding under your own resting baseline — especially on targeted traffic → page problem. High-intent visitors are arriving and bouncing. That’s capsule↔page mismatch, a trailer that buries the hook, screenshots that don’t communicate the genre, or a first description line that says nothing. Fix the page before buying more traffic to bounce off it.

Run the check on a source you control (your Discord, a newsletter link, a targeted post) rather than on the all-source blend — low-intent algorithmic traffic in the denominator will mask a real page problem behind noise.

What page conversion means for your revenue forecast

Here’s the uncomfortable part: visit→wishlist conversion is private data. It lives in your Steamworks backend, Steam publishes no official averages, and no third-party tool can see it from outside. Any forecast that claims to use “page conversion” for a game the forecaster doesn’t own is making it up. What is public — and what we build on — are the store-page signals themselves (genre, price, tags, followers, review trajectory) and their empirical relationship to launch outcomes across tens of thousands of releases. That’s what a calibrated P10/P50/P90 cone is: the realistic range for a page that looks like yours, without pretending to know your private funnel. For released comps, the Steam revenue calculator works the public side of the same problem from review counts, and how much do Steam games make covers where those outcomes actually land.

Frequently asked questions

Built by Greg C. — senior software engineer with production ML experience in calibrated prediction. Steam Launch Forecaster trains a CQR-calibrated model on a 77K-app Steam corpus. See the methodology →