Valve does not publish sales numbers. They never have, and they almost certainly never will. So if you want to know how many copies a Steam game has sold -- whether it is a competitor you are researching, a comparable title you are benchmarking against, or a game in a genre you are considering -- you need to estimate. And the most widely used estimation method in indie game development is the Boxleiter method.
This guide explains exactly how the method works, where it came from, how to apply it correctly, and -- just as importantly -- when it breaks down and you should not trust it.
The origins of the Boxleiter method
The method's history matters because understanding where it came from helps you understand its assumptions and limitations.
Simon Carless and the original observation
The roots of the Boxleiter method go back to Simon Carless, the founder of GameDiscoverCo and a longtime industry analyst. Carless observed that there appeared to be a roughly consistent ratio between the number of Steam reviews a game had and its total unit sales. He published early estimates suggesting that each review represented approximately 20 to 50 sales, depending on the game.
This was not a revolutionary statistical breakthrough -- it was a practical observation. Steam reviews are public. Sales are not. If you can establish a reliable ratio between the two, you have a free, fast way to estimate something that would otherwise be invisible.
Jake Birkett's refinement
Developer Jake Birkett (known for games like Shadowhand and Regency Solitaire) took Carless's observation and refined it significantly. Birkett had access to his own real sales data from Steamworks, which meant he could compare his actual unit sales against his review counts and calculate the true multiplier for his games. He then surveyed other indie developers, collecting their real multipliers, and published the aggregated results.
Birkett's work established the commonly cited range of 20 to 60 sales per review, with a central estimate around 30x for typical indie games. The method became known as the "Boxleiter method" -- a playful name that stuck in the indie development community. His contribution was turning a rough observation into something with enough data behind it that developers could use it with reasonable confidence.
Why the name matters less than the method
You will sometimes see this called the "review multiplier method," the "Carless-Birkett method," or just "the reviews-to-sales ratio." They all refer to the same core idea. The name Boxleiter caught on, and it is what most developers use when discussing it, so that is what this guide uses. What matters is understanding the mechanics, not the naming history.
How the Boxleiter method works
The formula is deceptively simple.
The core formula
Estimated units sold = Number of Steam reviews x Multiplier
To estimate revenue:
Estimated gross revenue = Number of reviews x Multiplier x Price
That is it. Three numbers multiplied together. The challenge is not the math -- it is choosing the right multiplier.
Why the multiplier exists
Most people who buy a game on Steam never leave a review. This is true across all genres, price points, and audience types. The question the Boxleiter method tries to answer is: for every person who does leave a review, how many total buyers does that person represent?
If a game has 1,000 reviews and a true multiplier of 30x, then approximately 30,000 people bought the game. Only one in thirty bothered to write a review. The other twenty-nine played the game (or didn't), formed an opinion (or didn't), and moved on without ever clicking the review button.
The multiplier range: 20x to 60x
The multiplier is not a fixed number. It varies based on several factors, and choosing the right value is where the Boxleiter method either gives you a useful estimate or leads you astray.
Lower multipliers (20-30x) apply when
- •The game targets a niche, engaged audience that reviews at higher rates (think hardcore strategy, simulation, wargames)
- •The game is PC-first with an audience that lives on Steam and is comfortable with the platform's review system
- •The price point is higher ($19.99+), which makes buyers feel more invested and more likely to leave feedback
- •The game has a small, passionate community rather than a broad casual audience
Mid-range multipliers (30-40x) apply when
- •The game is a typical indie title in a mainstream genre (roguelites, platformers, action games)
- •The price is in the $9.99-$14.99 range
- •The audience is a mix of dedicated and casual players
- •The game has a normal review rate without unusual factors pushing it up or down
Higher multipliers (40-60x) apply when
- •The audience is casual and less inclined to leave reviews
- •The price is very low ($4.99 or under), where buyers feel less compelled to review
- •A large portion of the player base is non-English-speaking, since non-English players leave reviews at lower rates
- •The game went through free weekends, large bundle distributions, or giveaways that brought in players who never intended to review
Step-by-step calculation examples
Let me walk through several examples at different price points and genres so you can see how the method works in practice.
Example 1: Indie roguelite at $14.99
A roguelite with 800 reviews. Roguelite audiences are engaged and review at moderate rates. I would use a multiplier of 28-35x.
- •Conservative (28x): 800 x 28 = 22,400 units. Revenue: 22,400 x $14.99 = $335,776 gross
- •Mid estimate (32x): 800 x 32 = 25,600 units. Revenue: 25,600 x $14.99 = $383,744 gross
- •Optimistic (35x): 800 x 35 = 28,000 units. Revenue: 28,000 x $14.99 = $419,720 gross
After Steam's 30% cut, the developer nets roughly $235,000 to $294,000. That is a meaningful range, but it is narrow enough to be useful for planning. You can model these scenarios instantly with our Revenue Calculator, which applies genre-adjusted multipliers automatically.
Example 2: Casual puzzle game at $4.99
A puzzle game with 300 reviews. Casual audiences review less frequently. I would use 40-55x.
- •Conservative (40x): 300 x 40 = 12,000 units. Revenue: 12,000 x $4.99 = $59,880 gross
- •Mid estimate (47x): 300 x 47 = 14,100 units. Revenue: 14,100 x $4.99 = $70,359 gross
- •Optimistic (55x): 300 x 55 = 16,500 units. Revenue: 16,500 x $4.99 = $82,335 gross
Developer net: roughly $42,000 to $57,600. Notice how the lower price amplifies the impact of the multiplier choice. At $4.99, the difference between 40x and 55x is about $15,000. That is why getting the multiplier approximately right matters more for cheaper games.
Example 3: Strategy game at $24.99
A complex strategy game with 2,000 reviews. Strategy audiences are highly engaged reviewers. Use 22-28x.
- •Conservative (22x): 2,000 x 22 = 44,000 units. Revenue: 44,000 x $24.99 = $1,099,560 gross
- •Mid estimate (25x): 2,000 x 25 = 50,000 units. Revenue: 50,000 x $24.99 = $1,249,500 gross
- •Optimistic (28x): 2,000 x 28 = 56,000 units. Revenue: 56,000 x $24.99 = $1,399,440 gross
Developer net: roughly $770,000 to $980,000. The higher price point and lower multiplier range produce a tighter estimate band, which makes the method more useful here.
Example 4: Survival crafting game at $19.99 (Early Access)
A survival game in Early Access with 1,500 reviews accumulated over 18 months. This one is trickier -- Early Access games accumulate reviews differently than traditional launches. Use 30-45x, leaning toward the higher end because Early Access titles often attract players who play without reviewing during the development period.
- •Conservative (30x): 1,500 x 30 = 45,000 units. Revenue: 45,000 x $19.99 = $899,550 gross
- •Mid estimate (38x): 1,500 x 38 = 57,000 units. Revenue: 57,000 x $19.99 = $1,139,430 gross
- •Optimistic (45x): 1,500 x 45 = 67,500 units. Revenue: 67,500 x $19.99 = $1,349,325 gross
For a detailed breakdown of how different genres perform on Steam, check our revenue by genre benchmarks.
Using the Boxleiter method for market research
The Boxleiter method is not just for satisfying curiosity about a single game. Its real power is as a market research tool before you commit to building something.
Step 1: Identify comparable titles
Find 10-15 games that are similar to what you want to build. Match on genre, scope, art style, and price point. Be honest -- compare yourself to games at your production level, not to the genre's outlier successes.
Step 2: Estimate each game's revenue
Run the Boxleiter calculation for each comparable title. Use genre-appropriate multipliers. Our Revenue Calculator does this automatically, but you can also do it by hand with a spreadsheet.
Step 3: Build the distribution
Sort your estimates from lowest to highest. Look at the median, the 25th percentile, and the 75th percentile. This gives you a realistic range for what a game like yours might earn.
Step 4: Set your target
Where in that distribution do you think your game will land? Be conservative. Most developers overestimate their position relative to comparables. If the median comparable earned $80,000 gross, planning around $60,000-$100,000 is reasonable. Planning around $200,000 because "my game is better" is how people get hurt.
Step 5: Validate against your budget
Compare your revenue estimate to your development costs. If the median comparable in your genre earns $80,000 and your game will cost $150,000 to make, the math does not work unless you have strong reasons to believe you will outperform the median significantly. Our indie game revenue data guide covers realistic benchmarks by genre to help you set expectations.
Limitations and when the method breaks down
The Boxleiter method is useful precisely because it is simple. But that simplicity means it ignores a lot of real-world complexity.
Regional pricing distortion
A game listed at $19.99 in the US might sell for $8-$12 equivalent in major markets like Brazil, Turkey, and Southeast Asia. If 35-40% of sales come from lower-priced regions, the actual average revenue per unit is significantly below the listed USD price. The Boxleiter method has no way to account for this. Your revenue estimate will be inflated, sometimes by 20-30%.
Bundle and key distribution
Games that have appeared in Humble Bundle, Fanatical, or other key distribution channels may have thousands of additional owners who paid $1-$3 per game as part of a package. These owners often still leave reviews, inflating the review count without proportional revenue. If you are estimating a game that has been in multiple bundles, your revenue figure will be too high.
Free-to-play games
The method simply does not work for free-to-play games. The price variable is zero, and revenue comes from microtransactions that have no relationship to review counts.
Review manipulation and anomalies
Review bombing, astroturfing, and other unusual review patterns break the method's assumptions. If a game received 500 negative reviews from a controversy that brought in people who never bought the game (through Steam's changed review access policies, or from key giveaways), the review count no longer correlates with organic purchases.
Very new games
Games in their first week or two have unstable review counts. The initial surge of reviews often comes from the most engaged early buyers, who review at a higher rate than the overall buyer base. Applying the Boxleiter method to a game that launched three days ago will usually underestimate its eventual sales.
Very old games
Games that have been on Steam for 5+ years have accumulated reviews through multiple pricing regimes, bundles, free weekends, and Steam algorithm changes. The lifetime review count represents a composite of very different buying conditions, making a single multiplier less reliable.
Comparing the Boxleiter method to other estimation approaches
The Boxleiter method is not the only way to estimate Steam sales. For a full comparison, see our Steam revenue calculator comparison guide, but here is a quick summary.
vs. SteamSpy
SteamSpy uses ownership data scraped from Steam profiles (heavily degraded since Valve's 2018 privacy changes). It provides ownership ranges rather than point estimates. The Boxleiter method is generally more useful for revenue estimation because SteamSpy gives you owners, not revenue, and its ranges are often extremely wide (200K-500K). However, SteamSpy is useful as a cross-reference -- if your Boxleiter estimate and SteamSpy's ownership range are in the same ballpark, you have more confidence.
vs. VGInsights
VGInsights is a paid platform that uses multi-factor modeling (review data, player activity, pricing history, machine learning) to estimate revenue. It is more accurate than the Boxleiter method for most games, particularly for games with complex pricing histories. But it costs money, and for quick competitive scans, the Boxleiter method is faster and free.
vs. developer postmortems
Nothing beats real numbers from the developer. When developers share their actual Steamworks data in GDC talks, blog posts, or social media, those figures are ground truth. The problem is that only a small fraction of developers share this data, and they tend to share when they have either a success story or a cautionary tale -- not a boringly average result. Use postmortems to calibrate your multiplier assumptions, not as your primary estimation tool.
The triangulation approach
The best practice is to use multiple methods and look for convergence. Start with the Boxleiter method for a quick baseline, cross-reference with SteamSpy for a sanity check, and use VGInsights if the stakes are high enough to justify the subscription. Our guide on how to estimate Steam game sales walks through this triangulation process in detail.
Advanced considerations
Adjusting for discount history
A game that has been on sale 15 times at 50%+ off will have a different revenue profile than one that has maintained its price. The Boxleiter method assumes full price for every unit, which is never true in practice. You can partially adjust for this by reducing your price variable to an estimated average sale price. If a game at $14.99 has been discounted 40% of the time at an average 35% discount, your effective price might be closer to $12.
Adjusting for DLC revenue
The base game's review count tells you about base game sales. If a game has significant DLC, total franchise revenue could be substantially higher than what the base game estimate suggests. Some games earn 50-100% of their base game revenue from DLC alone. The Boxleiter method does not capture this.
Adjusting for platform
If a game is also available on consoles, Epic, or GOG, the Steam review count only reflects Steam buyers. Total cross-platform revenue could be significantly higher. Console ports can add 30-100% to a game's total revenue depending on the genre and how well the port is marketed.
Frequently asked questions
What multiplier should I use for the Boxleiter method?
Start with 30x as a baseline for a typical indie game. Adjust down to 22-28x for niche genres with engaged audiences (strategy, simulation, wargames). Adjust up to 40-55x for casual genres, very low price points, or games with large non-English player bases. If you are unsure, use our Revenue Calculator, which applies genre-adjusted multipliers automatically so you do not have to guess.
How accurate is the Boxleiter method compared to real sales data?
When developers have compared their actual Steamworks data against Boxleiter estimates, the method is typically accurate within 30-50% if the multiplier is chosen reasonably. Genre-adjusted multipliers narrow this range. The biggest sources of error are regional pricing (which inflates revenue estimates) and bundle sales (which inflate unit estimates). For most indie developers doing competitive research, this level of accuracy is sufficient for decision-making.
Can I use the Boxleiter method for games with very few reviews?
You can, but the estimate becomes very unreliable below about 50 reviews. With only 20 reviews, a small change in the multiplier produces wild swings in the estimate. At 20 reviews with a 25x multiplier, you get 500 units. At 40x, you get 800 units. The true number could be anywhere in that range or outside it entirely. For games with very few reviews, look for developer-reported data or use VGInsights if you need a more reliable figure.
Does the Boxleiter method work for AAA games?
It can provide a rough ballpark, but it is less reliable for AAA titles. AAA games have complex pricing structures (multiple editions, pre-order bonuses, bundled DLC), large marketing-driven purchase spikes, and significant console revenue that the Steam review count does not reflect. VGInsights is a better tool for AAA estimation.
How often should I re-run Boxleiter estimates during market research?
For active market research, re-estimate your key comparables every 3-6 months. Review counts grow over time, and games you estimated six months ago may have meaningfully different numbers now. This is especially important for games in Early Access, where review counts grow steadily as the game develops.
Ready to run the numbers on your competitors or comparable titles? Use the Revenue Calculator with genre-adjusted Boxleiter multipliers -- it is free and instant. Then read our full guide to estimating Steam game sales for the triangulation approach, check our indie game revenue data for benchmarks by genre, and review the genre-specific revenue breakdown to see where your game type falls in the revenue distribution.
Browse our genre-specific optimization guides for strategies tailored to your game type, and check the Steam Page Leaderboard to see how top-performing games structure their store pages.