Battle Royale · PC GUIDE
Apex Legends
Settings & responsiveness.
Use EA’s video recommendations as a starting point, then compare your own frame pacing and visibility. Game settings cannot change the server’s update rate.
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.
7 settings shown
- 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.
- Enabled, on supported NVIDIA GPUs
Use the in-game latency option where available. Compare Boost separately; benefits and power use depend on your system.
- Low or Medium to start
EA recommends a conservative starting budget. Raise it only if your GPU has room and play stays smooth.
- Disabled initially
EA suggests disabling it unless FPS drops are frequent. Compare image clarity if you enable it.
- Disabled
A performance-oriented baseline from EA; compare the visual tradeoff.
- Low
Use EA’s lower-detail baseline when measuring busy scenes.
- Off as a starting point
Keep sensitivity comfortable and compare tracking in the Firing Range.
Make the comparison useful.
Practice, then verify in a match
Use the Firing Range to compare input feel, but also test a real match with combat and movement.
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 →