01 / CLAIM, SOURCE, LIMIT
A description is not a measured result.
These are separate questions: whether a feature is advertised, whether it works as described, and whether it helps a particular PC. Our source check answers the first question.
| Vendor claim or offer | Evidence reviewed | FrameLedger test status | What your test should establish |
|---|---|---|---|
| Free access | Product page and FAQ | Source checked Free workflow not run | Which specific changes you can apply before paying. |
| Paid lifetime edition | Pricing and license description | Source checked Activation and transfer not tried | Whether the setting you need is included and the terms fit your plans. |
| Undo and restore points | Product FAQ | Not tested No recovery exercise completed | Which reversal steps are documented for the exact change. |
| Performance and anti-cheat compatibility | Product claims and FAQ | Not tested No independent benchmark or compatibility test | Repeated results for your own setup; current guidance for the game you use. |
The matrix identifies the source of a claim. It does not verify that the application behaves as advertised.
02 / READ THE EVIDENCE
Ask what would change your decision.
Before downloading
Identify the problem you want to investigate. Low average FPS, uneven frame delivery and network delay require different measurements. A tool's feature list alone does not identify the cause.
Use the download guide to start at the developer's current entry point.
Before paying
Name the specific paid setting or workflow you need. Check its access in the application and read the purchase terms. A larger feature count is not evidence that more settings will help your machine.
Use the edition comparison to prepare those checks.
No expected FPS uplift from us.
We cannot supply an improvement percentage, a compatibility guarantee or an independent safety verdict without the relevant tests. Treat our source review as preparation for a decision, then preserve your own evidence.
03 / MAKE A REVISITABLE TEST
Keep the experiment small enough to explain.
- Define the scene. Choose a fixed replay or built-in benchmark. Record your hardware, game version, settings, driver and capture tool.
- Repeat the baseline. Warm up the game and collect several equal-length runs. Keep the raw captures, including runs that do not look impressive.
- Change one variable. Record the original value and the recovery steps. Run the same scene with the same tool and metric.
- Review and revisit. Compare the spread of results as well as the headline number. Record your conclusion and retest later if the evidence is unclear or your driver changes.
If you are investigating stutter, retain frame-time data rather than treating run-average FPS as a frame-time statistic. Different tools and metrics can produce different numbers; keep them consistent within a comparison.
Record your first testSources and review scope
Checked October 10, 2026: official product page, pricing and FAQ and the linked refund policy. We checked published web information. We have not run the software, verified its installer or measured changes on a Windows gaming PC.
Our test workflow is an editorial method for preserving your own observations. It is not a result obtained by FrameLedger or a guarantee that a particular change is appropriate.