Last reviewed: 31 July 2026
This page explains how Respawno produces its coverage, where our information comes from, and how to tell us when we have got something wrong.
Who writes for Respawno
Every article carries a byline linking to that writer's profile, which lists their focus areas and everything else they have written for us. We currently have two writers:
- Eren Smith — hardware and build guides
- Yahi Rakh — displays and games
We do not publish anonymous articles.
How we research
Our hardware and troubleshooting coverage is research synthesis: we read primary documentation, manufacturer specifications, independent test results, and support channels, then work out what the evidence actually supports and write it plainly.
We prefer sources in this order:
- Primary documentation — manufacturer specifications, developer interviews, standards bodies, vendor engineering notes
- Independent measurement — publications that test hardware and publish their methodology
- Support channels and community reports — useful for establishing how common a problem is, not for establishing why it happens
Every article ends with a Sources block listing the publisher, title, retrieval date, and full URL for everything we relied on. If a claim is not sourced, treat it as our analysis rather than as established fact.
What we do not claim
We are not currently a testing lab. Where an article does not say we measured something ourselves, we did not. We think that distinction matters more than it is usually given credit for, so we state it here rather than letting layout imply otherwise.
When we describe a procedure — capping a frame rate, measuring stick drift, reading Event Viewer — we are describing a method you can run and verify, not reporting results from our own bench.
Uncertainty and rumour
For unreleased games and hardware, we distinguish between what a publisher has confirmed and what has been reported, leaked, or inferred. Unconfirmed information is labelled as such in the text. We would rather be less exciting than wrong.
Imagery
Most photography on this site comes from manufacturer press assets and published reviews, used for editorial coverage and credited near the end of each article. We do not present third-party imagery as our own original photography. Screenshots of software interfaces are used to illustrate the steps being described.
If you hold rights to an image used here and want it credited differently or removed, email us and we will act on it promptly.
Advertising and independence
Respawno is funded by advertising served through Google AdSense. Advertisers have no input into our editorial coverage, no advance sight of articles, and no ability to influence a recommendation.
Where we recommend hardware, the recommendation reflects our reading of the evidence. If we ever publish sponsored or affiliate content, it will be labelled clearly at the top of the article.
Corrections
We correct errors rather than quietly editing them away.
- Factual errors are fixed and noted on the article.
- Substantive changes to a recommendation update the article's revision date.
- Typos and formatting are fixed without a note.
If you spot something wrong — a number, a mechanism, a claim that does not hold up — email contact@respawno.com with the article and what you believe is incorrect. Corrections from readers with hands-on knowledge are genuinely welcome, and we would rather hear it from you than leave it wrong.
AI use
We use AI tooling as a drafting and research aid. Every article is reviewed, fact-checked against its cited sources, and edited by a named human writer before publication, and the byline reflects who is accountable for it. We do not publish unreviewed generated text.
Contact
Email: contact@respawno.com Location: Detroit, Michigan, United States Response time: usually within 48 hours, Monday to Friday