Methodology

Steam Hardware Review separates official facts, reporting, community signals, reviews, and analysis so readers can see what is known, what is inferred, and what is still unknown.

Source labels

Source labels describe what kind of evidence supports a claim. Launch facts, compatibility claims, review verdicts, tracker status changes, pricing, and availability should point to a source trail whenever a public source exists.

Official: Valve, Steam, Steamworks, product pages, public documentation, or direct publisher/developer material.

Reporting: Reputable third-party coverage, hands-on reporting, interviews, technical testing, or import and certification records.

Community signal: Public user reports, tracker submissions, SteamDB, SteamTracking, Reddit threads, or Steam community context. These can be useful, but they are not official confirmation.

Analysis: Steam Hardware Review interpretation based on the available evidence. Analysis should not be written as if Valve confirmed it.

Rumor: Unconfirmed information that may be newsworthy but needs clear labeling and extra caution.

Unknown: Details that are not yet supported by reliable public evidence.

Confidence levels

Confidence describes the strength of the evidence behind a claim, review verdict, or tracker estimate. It is not a promise. A confirmed launch fact can have high confidence; a thin tracker estimate with only a few recent reports should not.

Tracker confidence is based on usable report count, recency, regional coverage, and whether a state-level result has enough data to stand on its own. Low-data estimates stay labeled instead of being presented as certainty.

Review policy

Reviews separate hands-on testing from source-informed recommendations.

Hands-on verdicts come from direct Steam Hardware Review testing on the named device.

Source-informed verdicts use official compatibility status, reputable testing, store requirements, and public reporting when direct testing is not available.

Unscored verdicts stay gray when there is not enough device-specific evidence for Steam Deck, Steam Machine, Steam Frame, or another target. A positive Steam Deck signal does not automatically prove TV, headset, or streaming behavior on a different device.

Tracker estimate methodology

The community tracker uses anonymous milestone dates. Queue frontier estimates use reports that include both reservation and order-invite dates. Shipment timing uses reported shipping and delivery milestones.

Tracker summaries favor medians and typical ranges over averages because a few unusual shipments can distort a small data set. The queue frontier compares a user's reservation time with the latest reported reservation time that has reached an order invite for the selected product, model, and region.

Tracker estimates are directional. They are not purchase guarantees, delivery promises, or official Valve data.

Tracker privacy boundaries

Public tracker reports should contain product, model, region, and milestone dates only. Submitted reports use random public IDs and private update links. The tracker does not need usernames, emails, order numbers, tracking numbers, addresses, ZIP codes, screenshots, documents, or account identity.

Corrections and updates

Pages are updated when source material changes or an error is found. Material corrections should clarify what changed and why, without hiding uncertainty or implying that Valve has confirmed something it has not.

Image and asset policy

Article artwork may use original editorial art, licensed or user-provided assets, screenshots used as source context, or generated imagery when appropriate. Generated artwork must not fabricate test results, UI states, product details, packaging, availability, or official imagery.