This page explains how material on FramesGames is made: what gets published, where the numbers come from, what happens when we are wrong, and who pays for any of it. It is written so that you can check us rather than trust us.
What gets published
Every article has to answer a question a reader actually has. A driver release is not news because it exists, it is news because something in it changes what you should do with your machine.
- We check the claim before the story. If a headline elsewhere says a studio confirmed something, we go to the interview and read what was actually said. More than once the confirmation turned out not to exist.
- We do not retell press releases. A vendor announcement is a source, not an article. What goes on the site is what the announcement means for the person reading it.
- We do not publish numbers we cannot trace. A performance figure without a published test method does not go on the site, no matter how widely it is being quoted.
Where the numbers come from
Specifications come from the manufacturer. Performance figures come from outlets that publish their test setup and their method: TechPowerUp, ComputerBase, PC Games Hardware, GamersNexus, TechSpot, Tom's Hardware, and the primary sources themselves.
We do not lift other people's charts. When a comparison needs a chart, we draw our own from the published numbers and print the source on the image, so it travels with the picture even when the picture is shared somewhere else.
Rumours and leaks
A rumour is labelled as a rumour in the text, not in a line of small print at the bottom. We name who reported it and how far it is from a confirmation. Where a claim cannot be traced to anyone in particular, we say that too, and often that is the whole story.
Estimates and our own calculations
Some material contains figures we worked out ourselves, such as expected frame rates for a build or hours of battery life. These are estimates derived from other people's measurements, and they are marked as estimates wherever they appear, with the source and the date of the underlying test.
The rule behind that is simple. A number printed without a qualifier is read as a promise, and we only make promises we can keep.
Corrections
We get things wrong. When that happens the article is corrected and the correction is stated in the text, not quietly edited away.
- A factual error is fixed as soon as it is confirmed, and a note at the end of the article says what was changed and when.
- A figure that has moved on, such as a price or a driver version, is updated and the date of the update is shown.
- A story that turns out to be wrong at its core is not deleted. It is corrected in place, with the original claim and what actually happened both left visible.
If you have found an error, write to [email protected]. Point at the sentence and, if you have one, the source. Corrections are handled ahead of everything else in the inbox.
Who writes this and who pays for it
One person writes and checks the site. David Freeman is a pen name, and the About page says plainly what is behind it: no newsroom, no industry veteran, someone who builds machines, plays a lot and reads the primary sources.
FramesGames is independent. It is not owned by, funded by or answerable to any hardware maker, publisher or retailer. Nobody buys a verdict here, and no manufacturer sees an article before it goes up.
Where the site links to a shop, the link is there because the reader asked where to buy, and it is marked so search engines do not treat it as an endorsement. If advertising appears on a page, it is separated from the text and labelled. Should any commercial arrangement ever affect a page, that page will say so at the top.
Languages
Every article is published in English, Russian and Dutch. The versions are not machine translations left to their own devices: numbers, names, dates and sources are checked in each one, and a correction in one language is applied to all three.
Questions about any of the above go to [email protected].