How to Read an FPS Overlay Properly
Setting up the FPS Monitor overlay and reading what the numbers mean, including why average FPS is the least useful figure on screen.
An overlay showing “119” tells you very little on its own. This tutorial covers configuring FPS Monitor so the number on screen is actually diagnostic.
Step 1: Set Up FPS Monitor
FPS Monitor needs two things: permission to draw over other apps, and FPS Engine, which reads the frame data.
- Open FPS Monitor and approve the Display over other apps prompt.
- Start FPS Engine with wireless debugging, Shizuku or one ADB command. The app walks you through it.
If you use Shizuku and it is not running, see the setup guide.
Step 2: Position the Overlay
Drag it somewhere that survives actual gameplay:
- Away from your thumbs. Landscape games put both thumbs at the bottom corners. Use the top edge.
- Away from game HUD. Minimaps, ammo counters and killfeeds all claim the corners. Top-centre is often the only genuinely free space.
- Not in your recordings. If you capture gameplay, remember the overlay is captured too.
Size and colour are adjustable. A smaller overlay in a high-contrast colour reads better than a large one that obscures the game.
Step 3: Read the Numbers Correctly
The average frame rate is the least informative figure available. What matters:
Consistency. A locked 90 feels smoother than a 120 that repeatedly drops to 70. Your eye notices the change, not the height.
Where the dips occur. If frames fall every time you enter a specific area, that is content, and settings will not fix it. If they fall after ten minutes regardless of where you are, that is heat.
The shape over time. Steady from the first minute to the twentieth means you have thermal headroom. A slow decline is throttling. A cliff is usually a background process waking up.
Whether it matches your panel. 120 FPS on a 60 Hz screen is wasted GPU work, wasted battery, and extra heat for zero visible benefit.
Step 4: Run a Real Test
Fifteen minutes of actual gameplay, not a menu screen:
- Start with the phone at room temperature, not straight off a charger.
- Tap the overlay to start recording, then play normally for 15 minutes.
- Tap it again to stop, and in the session’s report compare minute 1, minute 5 and minute 15.
Stable across all three means you have headroom to raise settings. A decline means you are thermally limited, and the fix is lower settings or better cooling, not a higher target.
Why Measured Frames Matter
Some overlays derive frame rate from UI callbacks, which report how often the app asked to draw rather than how often a frame actually reached the screen. Those two numbers diverge exactly when things go wrong: during stutter, which is when you need the reading to be right.
FPS Monitor reads frame timings from Android’s display system, so the figure reflects frames actually presented to your screen. It is the difference between measuring and estimating.
Frequently Asked Questions
Where should I place the FPS overlay?
A top corner outside your thumb zone and away from the minimap or ammo counter. On landscape games the top-centre edge is usually the least destructive position.
Why does my FPS reading fluctuate so much?
The overlay updates once a second, so every dip shows. That is what you want when hunting stutter. For the bigger picture, record the session and read its report.