Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Enable Smoother 120Hz Browsing in Safari
- Thread starter MacRumors
- Start date
- Sort by reaction score
Yea, it tanks battery life - apparently.
Tip: Verify 60 or 120 with the Test UFO web page: https://testufo.com/
FYI, system updates frequently reset the Prefer Page Rendering Updates near 60fps setting. You'll need to occasionally verify your setting.
And not only that, why did it take a 20/20 special investigative report to uncover?
At the very least the setting should be available where a somewhat average person can find it.
I’m pretty good at noticing things like refresh rate, but I didn’t really notice anthing when doing this. Reverted back to the default setting.
when I use the vsync option in the Amiga emulator web app https://vamigaweb.github.io and I disable "Prefer Page Rendering Updates near 60fps" then the vAmigaWeb app fps indicator shows 120fps. When I enable it then it shows 60fps.
The vsync logic in the web app is driven by the browser API call window.requestAnimationFrame().
As website scrolling is concerned I can not see any difference between on / off.
So I bet this setting is all about fancy animations which if setting is disabled can become smoother depending how they are implemented by the website. In case of the Emulator this settings makes no sense because NTSC Amiga in the US had a refresh rate of 60 whereas in Europe Amigas had 50fps.
It would be cool if we also could limit the refresh rate to only 50fps. For smooth gameplay on the PAL Amiga or Commodore C64 (see links below)
The vsync logic in the web app is driven by the browser API call window.requestAnimationFrame().
As website scrolling is concerned I can not see any difference between on / off.
So I bet this setting is all about fancy animations which if setting is disabled can become smoother depending how they are implemented by the website. In case of the Emulator this settings makes no sense because NTSC Amiga in the US had a refresh rate of 60 whereas in Europe Amigas had 50fps.
It would be cool if we also could limit the refresh rate to only 50fps. For smooth gameplay on the PAL Amiga or Commodore C64 (see links below)
Even if it is a little worse, we did not buy high-end devices only to disable all the high-end features and live cowering in fear of diminished battery health.
You mean, enabled?
Enabling the setting in question limits the frame rate to "near 60 fps" which would improve battery life, if just slightly.
If you want to compare scrolling at reduced refresh rate, just set your 120hz capable iPhone to low power mode in battery settings and compare scrolling in Safari or anywhere else, it’s cut to half (60hz) the difference is evident, unless you are not sensitive to that, I know some people swear they cannot notice high refresh rates. But I do.
The setting this article is referring to is not about scrolling, that is already working as it should with promotion up to 120hz and to as low as necessary based on the movement happening on screen.
support.apple.com
The setting this article is referring to is not about scrolling, that is already working as it should with promotion up to 120hz and to as low as necessary based on the movement happening on screen.
Save battery life with Power Modes on iPhone
Power Mode reduces the amount of power that your iPhone uses when the battery gets low. It optimizes performance for essential tasks like making and receiving calls, sending and receiving email and messages, and accessing the internet.
Last edited:
I knew what you meant. I can't guarantee everyone reading did.
I swear I saw reviews on YouTube scrolling in Safari and saying how the iPhone Pro is worth it for that feature. I think it was their imagination or they would have mentioned that buried feature.
This feature flag only impacts animations which are rarely over 60fps....this is a non-issue. What is the issue is that on promotion screens full screen streaming video stutters in Safari (26.2) unless you switch the resolution over to a fixed rate - now that would have been a better article looking into this further than something that does nothing and has been around for years.
Will be keeping 120fps on for now, but I'll keep an eye on battery life (17 PM).
For me, the difference between a 60hz and 120hz refresh rate is huge, but in Safari, it still feels like 120fps with it on or off when it comes to scrolling pages.
I use an iPad mini A17 Pro, so the screen is limited to 60fps in Safari on that anyway, and the difference between my 17 PM and that is clearly night and day when it comes to smoothness, even with the iPhone Safari setting on or off.
For graphics rendering in Safari, though, the difference is night and day with that setting as it's not being capped at 60fps.
For me, the difference between a 60hz and 120hz refresh rate is huge, but in Safari, it still feels like 120fps with it on or off when it comes to scrolling pages.
I use an iPad mini A17 Pro, so the screen is limited to 60fps in Safari on that anyway, and the difference between my 17 PM and that is clearly night and day when it comes to smoothness, even with the iPhone Safari setting on or off.
For graphics rendering in Safari, though, the difference is night and day with that setting as it's not being capped at 60fps.
Attachments
Last edited:
Guys… the placebo in this thread is unreal… it’s a requestAnimationFrame setting. It’s very black-and-white what this affects. You probably don’t want to toggle this setting away from default.
120 Hz FTW
The smoothness makes web browsing so much more enjoyable, while worse battery life will push to browse slightly less. It’s a win win in my book ;-)
The smoothness makes web browsing so much more enjoyable, while worse battery life will push to browse slightly less. It’s a win win in my book ;-)
100% this. Comment above suggests it's for javascript animations and not scrolling or the whole view rendering anyway, that seems correct. If it does also somehow impact other layers of the stack, the idea of pro motion in general is to only ramp up to 120 when needed. This setting probably dictates how aggressively safari triggers that system, balancing fluidity and battery life. It probably prefers 60 and only spikes to 120 when really needed, without it, spiking to 120 much more often will cause battery drain the redditors already discovered.
I imagine disabling this is foolish on a number of accounts, and the intention of burying the option is not to "limit your experience" or "safari is just bad" or "apple being dumb" but rather to prevent users from being dumb.
It's a developer option for a reason, not some oversight by the safari team; perhaps they need to test how it works to best optimize the experience for users and toggle it on and off to compare out it works, but too many users on this forum and elsewhere are too foolish to understand that. Claiming, "wow great tip" or "so much better now" just shows they actually can't tell the difference and they are just hurting themselves ultimately, (battery life, etc.) "fixing" things they don't understand, and its sad MR posted such nonsense on their homepage.