Skip to main content

Hi all!

 

Just wanted to have some clarify on Figma Sites different breakpoints.

 

I’m currently creating different size breakpoints for my website. 

 

I usually go with breakpoints that are something like:
1600px > 1280px (Figma Preset) > 1024px > 800px > 360px 

Now that I’ve created these breakpoints, it appears that on published site it only shows one breakpoint size on different desktop computer screens, which is 1280px. 

 

Doest the Figma Sites only have that screen breakpoint available on Beta version?

Are the other desktop breakpoints useless?

 

Since the design of the 1280px is too big for smaller laptops and too small for bigger desktops, how can I find a workaround for this?

 

Thank you for advance.

Yes — currently, Figma Sites (Beta) only supports one desktop breakpoint (1280px) for now. Other breakpoints (like 1600px or 1024px) won’t auto-switch based on screen size like in real responsive websites.

Until Figma Sites supports full responsive breakpoints:

  • Try to optimize your 1280px layout so it still looks decent on smaller or larger screens.

  • Keep your layout flexible (use auto-layout, % widths, etc.).

  • Use Figma preview frames to show how the design would ideally look across breakpoints, but know that the published site won’t behave that way yet.

Hi!

 

Thank you for response, good to know this.

 

Since I’m doing the sites for client and it’s meant to be published and showcased on multiple devices, I’m wondering if the Figma Sites Beta version is even good option for this, if the responsiveness is limited to 1280px + the other lacks of features.

 

So can I even make decent websites with Figma Sites Beta version right now or is it just for the prototyping?

 

Regards,

BB01

Hi BB01!

Right now, Figma Sites (Beta) is more for basic site publishing or prototyping — it’s not ideal for full, responsive, production-level websites. If your client needs a fully responsive site across all devices, it’s better to use a proper web builder or hand it off to a developer.

Terms & ConditionsCookie settingsAccessibility statement