topic Spotify changing refresh-rate on primary screen in Desktop (Windows)

Frame Rate capped at 60hz

Raaandooom — Thu, 11 Apr 2024 15:05:48 GMT

Plan

Premium Duo

Country

France

Device

PC, Desktop App

Operating System

Windows 10 64-Bits

My Question or Issue

Hello, since the last interface update it seems that the desktop app has been capped at 60hz.

Animations and scrolling are slow and seem a bit split, I'm pretty sure it's 60hz.

Btw: I have a 165 Hz monitor.

Best regards.

Re: Frame Rate capped at 60hz

MateusM — Thu, 11 Jul 2024 11:43:15 GMT

Hi there @Raaandooom! Thanks for posting in the Spotify Community.

Sorry for the late response!

We'll check if the desktop app has a specific monitor Hz rate. In the meantime, we recommend you follow some troubleshooting to see if you notice any difference:

Check if the hardware acceleration is enabled in Settings > Compatibility > Enable hardware acceleration.
Clear the cache.
Try heading to the app settings and toggle the option Local Files on > toggle off all the sources that appear there > toggle Local Files back off.

Keep me posted on how this goes.
/Mateus

Re: Frame Rate capped at 60hz

Ayshndood — Wed, 08 Jan 2025 14:09:55 GMT

I have the exact same problem. Especially noticeable when scrolling through spotify.

Spotify changing refresh-rate on primary screen

Isakf — Tue, 02 Dec 2025 22:09:48 GMT

Plan

Premium

Country

Norway

Device

Desktop

Operating System

Win11/Win10

My Question or Issue

Especially when playing CS2 in fullscreen mode, and spotify with hardware acceleration on, on the secondary screen, it changes the refreshrate on my primary screen. It goes from 240hz to 60hz. Turning off hardware acceleration fixed the issue, but this should be investigated.

Re: Spotify changing refresh-rate on primary screen

Amay — Wed, 03 Dec 2025 13:28:43 GMT

Thanks for the feedback @Isakf. This seems to occur due to the interactions between the Spotify app's Hardware Acceleration and the GPU adaptive sync technologies. For the time being, as you and @MateusM have mentioned, disabling hardware acceleration is the way to fix this behaviour.

@Ayshndood, sorry for the radio silence here! Tagging you in case you're still experiencing this issue 🙂