Radiant Optimizer FPS comparison
Calculate changes from numbers you measured yourself. This browser tool cannot scan your PC, run the optimizer or measure a game.
Start with two comparable captures
Enter your average FPS before and after a change. No measurements are filled in for you.
Keep the captures comparable
- Use the same hardware, game scene, resolution and graphics settings for both captures.
- Keep the capture duration and measurement software the same. Record driver changes, game patches and background load separately.
- Repeat each condition rather than treating one unusually fast run as a reliable improvement.
- Change one identifiable thing at a time so you can compare it with the baseline.
1% low FPS describes the slower part of a capture. Enter the value reported by your measurement tool with the same definition for both runs. Average frame time is the average time between frames; it is not an input-latency measurement.
A result here is arithmetic from your inputs, not proof that Radiant Optimizer caused a change. Different capture conditions, random run variation or another system change can also produce a difference.
What happens to your data
Draft fields persist in this browser as you type. Save comparison stores one named capture pair locally; loading it replaces the displayed draft. Reset all clears the draft and saved comparison. The form does not submit measurements to a server.
Keep sensitive information out of test notes. Read the privacy information for analytics and browser storage details.
Before you change settings
Use the feature tour to separate FPS, network and scheduling tasks. For the application itself, use the download guide; purchase questions belong in free versus paid.