# What does fps mean exactly in show stats?

**URL:** https://forum.makecode.com/t/what-does-fps-mean-exactly-in-show-stats/955
**Category:** Arcade
**Created:** [December 28, 2019, 12:01am UTC](https://forum.makecode.com/t/what-does-fps-mean-exactly-in-show-stats/955 "2019-12-28T00:01:23Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![kjw](https://avatars.discourse-cdn.com/v4/letter/k/e79b87/32.png) [@kjw](https://forum.makecode.com/u/kjw)
#### Post date: [December 28, 2019, 12:01am UTC](https://forum.makecode.com/t/what-does-fps-mean-exactly-in-show-stats/955/1 "2019-12-28T00:01:23Z")

</div>

What does the `fps` value mean, the one that appears when `show stats` is toggled on from the menu? The value can be 2000fps for a simple game in the simulator on a desktop browser and 67fps on a PyGamer.

The [Game Loop](https://arcade.makecode.com/developer/game-loop) documentation states the screen is updated once per game loop and as I understand this the current implementation aims for an approximate 50Hz rate and only slows if the processing becomes too lengthy for the loop, i.e. \> 20ms.

I see @richard refers to this value as the “uncapped FPS” in [Need help in rendering loop](https://forum.makecode.com/t/need-help-in-rendering-loop/408). Is this value an estimate of the maximum fps that could be achieved and only becomes the real screen update rate if it drops below 50 fps?

---

<div class="post-metadata">

### Author: ![kjw](https://avatars.discourse-cdn.com/v4/letter/k/e79b87/32.png) [@kjw](https://forum.makecode.com/u/kjw)
#### Post date: [December 28, 2019, 6:28pm UTC](https://forum.makecode.com/t/what-does-fps-mean-exactly-in-show-stats/955/2 "2019-12-28T18:28:14Z")

</div>

I noticed it mentions 60 fps in [https://github.com/microsoft/pxt-arcade/blob/master/docs/examples/jumper.md](https://github.com/microsoft/pxt-arcade/blob/master/docs/examples/jumper.md)

Is the target/maximum update rate for game loop / screen 50 or 60Hz?

---

<div class="post-metadata">

### Author: ![mmoskal](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/mmoskal/32/20_2.png) [@mmoskal](https://forum.makecode.com/u/mmoskal)
#### Post date: [January 1, 2020, 1:42pm UTC](https://forum.makecode.com/t/what-does-fps-mean-exactly-in-show-stats/955/3 "2020-01-01T13:42:06Z")

</div>

Your understanding is correct - if the screen didn’t have its own update rate this is what you would get. On desktop the limit is usually 60Hz but often we don’t manage that and only hit 30Hz (probably due to that 20ms sleep). On hardware the screen can refresh at around 40Hz but it depends on configuration and chip.
