Independent PC coverage · every score comes from a finished playthrough Play log total: 5,180 hours
Pixel Verdict Lab logo Pixel Verdict LabReviews & play logs
Four writers · one rule

We are a small desk that finishes games before writing about them

Pixel Verdict Lab exists because the review cycle rewards speed and we wanted to try the opposite. Everything below explains how that works in practice, including the parts that make us slower than everyone else.

How the desk runs

Four people, no editorial calendar, no launch-day deadlines

Nobody here works to a publisher's embargo. A review is assigned when someone on the desk wants to play the game, and it publishes when that person reaches the end. In practice this means our coverage lands between two days and six weeks after release, and occasionally much later when a game turns out to be enormous.

Every writer keeps a play log from the first launch: hours, patch version, hardware, difficulty, and a running note of the moment the game either clicked or broke. That log is not a formality — it is the raw material the review is built from, and a condensed version of it ships with every verdict so you can see what the score is based on.

  • No score without an ending. If a game cannot be finished, we say so and publish notes instead of a number.
  • Two machines minimum. Everything is tested on both a current build and a six-year-old one.
  • Scores can move. Major patches trigger a revisit, and we mark the date the number changed.
Overhead view of a reviewer's desk with a notebook, controller, stopwatch and coffee
What we will not do

The short list of things this desk refuses

These are not aspirations. They are the constraints the site was built around, and they are the reason it will never be a large publication.

01

No paid coverage of any kind

We do not run sponsored reviews, paid features, affiliate scoring bonuses, or "partner" content dressed as editorial. If a game is covered here, it is because a writer chose to spend their own hours on it.

02

No early-access verdicts

Unfinished games get impressions with an explicit build number and no score. Scoring something that is openly still being made tells a reader nothing useful and pressures developers into premature launches.

03

No rewritten press material

Feature lists, marketing copy and preview-event bullet points do not appear in our reviews. Everything described in a verdict is something one of us saw happen on our own machines.

The writers

Who is behind the scores

We publish under first names and specialisms rather than personal profiles. What matters for a review is what somebody has played enough of to judge fairly.

Marisol

Open world, exploration, immersive sims. Roughly 1,900 logged hours on this site, and the writer most likely to argue that a map should be harder to read.

Teodor

Tactics, grand strategy, anything with a turn counter. Keeps the most detailed play logs on the desk and once wrote 400 words about a supply-line bug.

Aiko

Simulation, cosy games, city and colony builders. Responsible for the house rule that a farm sim must be played for at least two in-game years before scoring.

Rune

Racing, action, platformers, and all hardware testing. Owns the six-year-old machine every game on this site has to survive.

How review copies are handled

We do accept review keys, and we log every one. A key buys a game, not an outcome, and it never changes the timing or the wording of a verdict. When we receive one, the review states it plainly at the top of the play log. Roughly two thirds of the games covered here were bought with our own money because no key existed.

  • 142 reviews published to date
  • 91 games bought at retail price
  • 51 games covered from a supplied key
  • 0 pieces of paid or sponsored content