About
Gaming fixes that name the actual setting
Most performance advice on the web is a list of vague incantations: "update your drivers", "optimize your PC", "enable game mode". SavePoint exists because that is not enough. A guide should tell you which menu, which value, and what to check afterwards to know it worked.
What we publish
SavePoint covers the practical side of PC gaming: fixing stutter, cutting input lag, managing storage across drives, and keeping a game library under control. The common thread is specificity. Each guide is written around the settings, numbers and step-by-step checks that resolve a problem — and each one names the cases where the fix will not work, because knowing that saves an evening of pointless tweaking.
How we research
Guides start from primary sources wherever they exist: official driver release notes, platform documentation from Microsoft, Steam and the console holders, and the behavior of the software itself on a test machine. Where we describe a menu path, it is the path as the software renders it — and when a setting moves between versions, we say so rather than pretend the guide is permanent.
We avoid quoting benchmark numbers we cannot reproduce. If a claim would be useful but we cannot verify it to a standard we would defend, we either leave it out or describe it as a common report rather than a measured fact.
What we do not do
- No registry "optimizations". Most of them do nothing measurable and a few break installs. If a registry change genuinely matters, we say what it does and how to undo it.
- No paid recommendations. No company pays to appear in a guide, and we do not use affiliate links.
- No placebo tweaks. If a popular setting has no measurable effect, the guide says so instead of repeating it for completeness.
- No invented data. Figures in guides come from reproducible measurements or are clearly labeled as worked examples.
Advertising
This site is supported by display advertising served through Google AdSense. Ads are selected by Google, not by us, and their presence is not an endorsement of the advertiser. Advertising has no influence on which topics we cover or what we conclude — the editorial calendar is set independently of commercial considerations.
Corrections
Games patch weekly and Windows updates move settings; we get things wrong occasionally. If you spot an error, tell us through the contact page and we will correct it. Substantive corrections are noted in the guide itself rather than made silently.
A note on the tools
The frame-time analyzer, storage planner and backlog tracker run entirely in your browser. Nothing you enter is transmitted, logged or stored on our side; the backlog list lives in your browser's local storage and disappears if you clear site data. They are measurement aids, not magic — the point is to replace "it feels laggy" with a number you can compare before and after a change.
Editorial standards and corrections
Who writes this. Every guide is published under the SavePoint editorial team byline. We are an independent publisher, we accept no payment from any company we write about, and there are no sponsored posts on this site. Questions, corrections and removal requests all go to yanli20140223@gmail.com.
How an article is produced. We start from primary sources — official documentation, published research, regulator guidance and the product's own help pages — then prepare a draft, which a person edits and checks against those sources before publishing. We state this openly because it sets the right expectation: our claim is accuracy against the source material, not fieldwork we did not carry out.
What we refuse to do. We do not invent figures, studies or expert quotes. We do not recommend a product because we were paid to. Where a conclusion depends on an assumption, the assumption is printed in the article rather than hidden in a footnote.
Limits you should know. Menu names, setting locations and performance figures differ between game versions, hardware and platforms. We name the version we are describing, but patches move interfaces regularly — treat every path as version-dependent and check the in-game menu if a label has shifted.
Corrections. If a number, a step or a source is wrong, write to us with the page URL and what you found. We aim to reply within 48 hours and to correct confirmed errors within two working days. Substantive changes are noted at the foot of the affected article; typographical fixes are made silently.
How the site is funded. Hosting is paid for by the site owner and partly offset by display advertising served through Google AdSense. Advertisers never see an article before publication and have no influence over what we publish. Cookies and third-party advertising are described in our privacy policy.