There is no single correct Figma website size. Choose dimensions according to whether you are creating a Figma Sites breakpoint, a Figma Design frame, or a coded page that must respond to many viewports. A practical Figma Sites starting example is 1,280 px desktop, 800 px tablet and either the documented 340 px mobile example or the 375 px mobile preset shown in Figma’s breakpoint menu. Treat those values as editable starting points, not universal standards.
What “Figma website size” can mean
The question usually combines three different sizing problems:
- Figma Sites breakpoint: a width range at which a published site uses a particular responsive layout.
- Figma Design frame: a canvas with explicit width and height, often based on a device preset or a custom artboard.
- Final webpage viewport: the browser width your HTML and CSS must handle, including widths that were never represented by a single design frame.
These are related, but they are not interchangeable. A 1,280 px design frame does not cause a browser to resize the finished page automatically, and a Figma Sites breakpoint is not a required industry standard for coded websites.
Figma Sites breakpoint sizes
Figma’s current Figma Sites help material illustrates three breakpoints:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems| Layout | Illustrative width | Example range in the documentation | How to interpret it |
|---|---|---|---|
| Desktop | 1,280 px | Widths over 1,280 px | Use as a wide-screen starting point; add a content max-width so text does not stretch indefinitely. |
| Tablet | 800 px | 800–1,280 px | Useful for intermediate navigation, columns and spacing changes. |
| Mobile | 340 px example; 375 px preset shown in the menu | Widths under 800 px | The two numbers are documentation examples, not competing standards. Pick the width that exposes your content’s actual failure point. |
Figma Sites permits custom breakpoint widths. Changing one breakpoint also adjusts neighboring ranges, so review every layout after editing a threshold. The page identifies Figma Sites as an open beta launched at Config 2025; labels and behavior may change as the product develops.
How to choose a breakpoint from content
- Start with the widest layout your content needs, commonly 1,280 px for a desktop exploration.
- Reduce the viewport gradually. Note the first width where navigation wraps, a heading becomes awkwardly narrow, cards become unreadable or controls collide.
- Place a breakpoint near that failure point, then test slightly above and below it.
- Add a mobile breakpoint where the information architecture must change, not merely where a named phone preset begins.
- Preview widths between your named breakpoints. Responsive behavior must remain usable in the intervals, not only at the frames you designed.
Building an adaptive Figma Sites layout
Use stacked section frames
Organize a page as vertically stacked section frames rather than one giant canvas. This makes each hero, feature group, pricing area and footer easier to resize and re-order at different widths.
Apply auto layout
Use auto layout for rows, columns, navigation groups, cards and text clusters. Set direction, gap, padding and alignment on the parent. Let text wrap naturally instead of forcing fixed heights that will break when copy or viewport width changes.
Set the correct width behavior
- Set a full-width background or section frame to Fill container.
- Give the inner content wrapper a maximum width when lines of text or grids should stop expanding on large screens.
- Use fixed widths only for elements that genuinely need them, such as an icon, logo mark or compact control.
- Allow buttons and cards to grow or stack when labels cannot fit comfortably.
Understand breakpoint inheritance
Primary breakpoint changes cascade to secondary breakpoints. A change made only inside a secondary breakpoint remains local to that view. Use the primary layout for shared structure, then add breakpoint-specific overrides only when the content or controls truly need them.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Choosing a Figma Design frame
For ordinary Figma Design, choose a device preset when you are validating a known context, or enter a custom width and height when the layout—not a device name—is the important constraint. Create additional frames for the major responsive states you need to inspect; do not create a frame for every possible browser width.
| Use case | Frame approach | What to inspect |
|---|---|---|
| Marketing landing page | Wide desktop, intermediate tablet and narrow mobile frames | Headline wrapping, navigation, section max-width and call-to-action placement |
| Dashboard | Desktop plus a compact state where navigation collapses | Table overflow, sidebars, density and keyboard-accessible controls |
| Single mobile flow | One device preset or custom phone width | Readable type, tap targets, safe spacing and long-content scrolling |
| Print-like or fixed canvas | Custom dimensions with explicit height | Whether content is intentionally clipped or paginated |
A frame’s bounds are independent of its children. Figma will not automatically resize the frame to fit its contents; use Resize to Fit when you want that result. Conversely, constraints describe how child layers respond when the frame itself is resized. They do not choose the frame’s original size.
Does the published website size itself for every device?
Only if the implementation defines responsive rules. In Figma Sites, breakpoint layouts and responsive properties determine what changes as the viewport crosses a threshold. In a coded site, CSS media queries, flexible grids, intrinsic sizing, images with appropriate sizing rules and accessible navigation perform that work. A Figma frame is a specification and preview, not a guarantee that production CSS will behave correctly.
Check at least the exact breakpoint widths, one or two widths between them, and a very wide viewport. Also test browser zoom and long translated text when those conditions matter to your audience. Look for horizontal scrolling, clipped focus rings, overlapping fixed elements, unreadable line lengths and controls that become impossible to tap.
A practical sizing workflow
- Define the audience and content. Identify the narrowest likely phone viewport, common tablet use and the widest desktop context.
- Sketch structure first. Map sections, navigation, content order and actions before selecting exact dimensions.
- Create three initial states. Use a wide frame around 1,280 px, an intermediate state around 800 px and a mobile state around 340–375 px for a Figma Sites-style exploration.
- Build with auto layout and constraints. Prefer content-driven sizing, Fill container and max-width wrappers over duplicated, manually positioned layers.
- Stress-test the transitions. Drag or preview through widths and record where structure must change.
- Move the breakpoints. Set thresholds where the design fails, not where a device catalogue happens to name a screen.
- Document production rules. Tell developers which wrappers are fluid, which have a max-width, what stacks, what hides and how images behave.
Common sizing mistakes and fixes
Designing only at one desktop width
Symptom: the mobile version is a squeezed desktop page. Fix: decide the mobile information order and controls separately, then connect shared styles through auto layout.
Confusing a preset with a breakpoint
Symptom: a 375 px phone frame is treated as the exact threshold for every phone. Fix: test the surrounding range and choose the threshold from wrapping, overflow and interaction failures.
Using fixed heights for text sections
Symptom: longer headlines or localization are clipped. Fix: use hug-content or flexible heights and verify the tallest realistic copy.
Expecting children to resize a frame
Symptom: adding content leaves the frame too short or too narrow. Fix: use Resize to Fit when the frame should follow its contents; use constraints when children must react to a manually resized frame.
Letting wide layouts grow without limit
Symptom: paragraphs become excessively long and grids lose visual hierarchy. Fix: keep the section background fluid and constrain the inner content wrapper with a max-width.
Previewing and handing off the result
- Preview every named breakpoint and at least one in-between width.
- Check keyboard focus, hover or pressed states, zoom, dynamic text and images with unusual aspect ratios.
- Annotate the intended behavior: “stacks below this width,” “fills parent,” “max 1,200 px,” or “horizontal scroll allowed.”
- Give developers the breakpoint logic and content rules, not just screenshots of three fixed canvases.
Or skip the browser setup
If you need rendered screenshots of a Figma preview or any public URL, ScreenshotNeo provides a one-request website screenshot API and MCP server. It accepts the cookie or consent banner before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be disabled. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and response headers report the page verdict and billing status.
Use the API documentation at https://screenshotneo.com/docs/. Replace the example URL with your published Figma Sites URL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Beyond a basic capture, ScreenshotNeo supports full-page lazy-image loading, CSS-selector element capture, dark mode, 12 device presets plus custom viewports, retina scale, PDF output, custom CSS and JavaScript, clicks, selector or network-idle waits, request and ad blocking, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, configurable caching, signed image links, asynchronous webhooks, bulk capture of up to 100 URLs per call, a usage API and an OpenAPI specification. Parameter names used by other screenshot APIs also work for easier migration.
An MCP server lets Claude, Cursor and other MCP clients call take_screenshot, get_page_info and capture_pdf. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account to try it.
Best Value
Screenshot reliability and cost considerations
For repeatable comparisons, use the same viewport, device scale, wait condition, timezone and authentication state for every capture. A selector wait is generally more meaningful than an arbitrary short delay for pages that render asynchronously. Cache with a TTL when the page is unchanged; disable or shorten caching when validating live content. Inspect X-Page-Verdict and X-Billed headers so automation can distinguish a clean billed capture from a failed or cached response.
FAQ
Should I use 1,366 × 768 because it is a common monitor size?
Use it only if that viewport matters to your audience or product. It can be a useful additional test frame, but Figma’s documented breakpoint example does not establish it as a universal website size.
Can I change a Figma Sites breakpoint after designing the page?
Yes. Figma Sites allows custom widths, but changing a breakpoint can alter neighboring ranges. Recheck inherited and breakpoint-specific properties after the change.
Recommended Free Tools
Is a Figma frame’s height important for responsive web design?
Width normally drives responsive layout decisions. Set height to represent the viewport or content you want to inspect, while allowing real webpages to continue vertically as content grows.
Frequently Asked Questions
Should I use 1,366 × 768 because it is a common monitor size?
Use it only when that viewport is relevant to your audience or product; it is not a universal Figma standard.
Can I change a Figma Sites breakpoint after designing the page?
Yes. Custom widths are supported, but review neighboring ranges and inherited properties afterward.
Is frame height important for responsive web design?
Width usually drives responsive changes; height mainly sets the viewport or content area you want to inspect.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
