Battle Royale · PC GUIDE
Fortnite
Settings & responsiveness.
Compare Performance rendering with your current setup, then check visibility and frame pacing. A different rendering mode can be a better starting point than a long list of launch flags.
Updated · InputLag editorial · English
YOUR MANUAL CHECKLIST
Settings to review.
These are starting points, not a universal best config. Apply changes in the game, compare the result, and mark what you’ve reviewed. Availability can vary by hardware and patch.
6 settings shown
- Try Performance
Epic recommends Performance for competitive play. Restart when prompted and compare the same scene.
- Off as a latency-first starting point
Compare responsiveness and tearing. If you use variable refresh, configure synchronization for your display rather than copying an unrelated setup.
- Start at 100%
Lower it gradually if rendering is too demanding; compare target clarity.
- Low as a baseline
Increase only after checking performance and image quality on your PC.
- Low as a baseline
A lower-detail starting point in Performance mode.
- On while comparing
Track performance during repeatable gameplay, not just in the lobby.
Make the comparison useful.
Check settings after switching modes
Available graphics options depend on the renderer. Compare the options that your current mode actually exposes.
Use a repeatable Creative route
Keep actions and viewpoint consistent, then confirm the result in a match. Do not infer input latency from generated or peak FPS alone.
Change one thing at a time
Keep your resolution, map and test route consistent. Compare several runs and record frame-time spikes as well as average FPS.
Keep a baseline
Save your current settings before changing them. Keep changes that improve your own measurements; a higher peak FPS alone does not mean steadier play.
A SEPARATE BROWSER CHECK
How to read your browser score.
The Responsiveness Lab gives a browser-based score. It does not measure this game’s click-to-photon latency, inspect Windows settings, or predict your rank. Use repeated runs to compare browser test conditions.
Run a browser test ↗See game benchmark methodology ↗
A high result in this browser session. Compare repeat runs under the same conditions.
A solid browser result. Check the individual test results for variation.
Review the individual tests and repeat with background load reduced.
Repeat the test and check browser, display and background activity before drawing conclusions.
Sources & review notes
Official references below support the documented features. The comparison steps are editorial starting points, not measured performance guarantees. No lab benchmark was performed for this guide.
How InputLag handles supported changes →