How to Tell If a PC Game Discount Is Actually Good

Before you click buy, learn how to check whether a game discount is genuine or just clever marketing — using price history, historical lows, and a few key signals.

The problem with percentage discounts

A game shown at 75% off sounds impressive — but off what? Publishers set the “original” price (MSRP), and that number can be changed at will. A game that launched at $30, quietly bumped to $40 eighteen months later, then put on “50% off sale” is really $20 — exactly what it cost at launch. The discount is real on paper and meaningless in practice.

This pattern is especially common with mid-tier titles that want to appear more premium than they are. The sale badge does the marketing work. The actual price is unchanged.

What the historical low actually tells you

The most useful number when evaluating any deal is the all-time low — the lowest price the game has ever reached, across every store. A game currently at $9.99 with an all-time low of $4.99 is not a great deal, even if the banner says “60% off.” A game at $14.99 that has never gone below $19.99 before is worth real consideration.

Historical low data separates genuine bargains from cosmetic discounts. Any serious price-tracking tool compares across stores and keeps a record over time — single-store comparisons miss deals that happened elsewhere.

How to read a price history graph

A price history graph shows every price change a game has gone through, on which stores, over time. Here is what each pattern means:

• Flat line near launch price: The game rarely discounts. When it does, it is genuinely notable.
• Regular seasonal troughs: The game hits the same low every major sale. If you are not at a trough right now, wait.
• Declining trend over time: Common in older games. If a five-year-old game is still at $29.99, it may have reached its floor.
• Price spike just before a sale: The clearest sign of a fake discount. Check whether the “original” price was higher 30–60 days ago. If it was bumped right before the sale window, the discount is manufactured.

Spotting inflated base prices

The sharpest signal of a manufactured discount is a price increase in the weeks before a sale event. Check whether the base price changed recently. On Steam, SteamDB’s price history tab shows this clearly. If there is a spike in the three to eight weeks before a major Steam sale, treat the resulting “discount” with skepticism.

Also watch for games that launched at a reasonable price, got negative reviews, raised their price, and then “went on sale” back to the original launch price.

Will this go lower?

For most games you can predict the price floor based on publisher behavior:

• Major publisher AAA titles (EA, Ubisoft, 2K, Bethesda): typically reach 75–90% off within two to three years of launch, often sooner.
• Mid-range indie games ($15–25): Often hit 80% off eventually, but timing is less predictable. Some stay at 50% as a floor for years.
• Cult titles with stable audiences (Hollow Knight, Terraria, Stardew Valley): publishers hold prices deliberately. These may never go below 50% off.
• Live-service games: Pricing is tied to the game’s health. A declining live-service game can crater to 90% off quickly. A thriving one may never drop the base price.

A practical decision checklist

Before clicking buy, answer four questions:

1. Is this price at or near the all-time low across all stores?
2. Has the base price been bumped recently — did the publisher inflate before this sale?
3. Is a major sale season coming in the next 4–6 weeks where it might go lower?
4. Will I actually play this within the next month?

If the answer to (1) and (4) is yes: buy without hesitation. If (3) is yes and (4) is no: wait. If (2) is yes: skepticism is warranted regardless of the headline discount number.

GameHotDeals tracks price history across 30+ stores so you can answer these questions in seconds. The all-time low list shows which games are currently at the lowest price ever recorded. Every game detail page includes a full price history graph — check it before you commit.