Skip to main content

Browsing Frame Set on Safari

We've turned off Motion auto-play in Safari to keep things stable.

Long scrolls through Motions can slow Safari down — sometimes to a freeze. Here's what we've done to help, and what else you can try.

What we recommend

First and foremost: we've automatically turned off Motion auto-play in Safari. Scroll through your search like normal, and when you find a Motion you'd like to see in action, hover over it to play.

This keeps Safari from getting overloaded while still giving you full access to every Motion in the Library.

Why this happens

After enough scrolling through Motions in Safari (usually around 8–10 pages deep on a Motion-heavy search), the browser starts to lag and may eventually freeze.

This isn't specific to Frame Set. Sites like Giphy and Tenor hit the same wall in Safari. The root cause is how Safari handles decoding and rendering many animated images at once — at some point, it maxes out the browser's CPU and gives up.

We tested a handful of fixes on our end, but none of them solved it cleanly, which is why turning off auto-play and leaning on hover-to-play became our best path forward.

Other solutions

A few other things help:

Refresh the page. A quick reload clears Safari's memory and gets things moving again. You can scroll back to where you were and keep going.

Narrow your search. Filters and more specific search terms mean fewer Motions loaded per page, which pushes back the point where Safari starts to struggle.

Filter to Stills. If you don't need Motions for what you're working on, browsing only Stills is significantly easier on Safari.

Try a different browser. Chrome, Firefox, and Brave handle long Motion-heavy scrolls better than Safari, though no browser is fully immune.


We're still exploring ways to make this experience even better on Safari. If you'd like to share what you were searching when things slowed down, contact our team anytime: help@frameset.app

Did this answer your question?