Is it necessary to prioritize responsiveness below 320px width in Webflow, or is it an insignificant number of users who still read on these screens? What is the common wisdom regarding this matter?

Designing for screens smaller than 320px (like older phones, smartwatches, and some edge-case devices) is generally not necessary for the vast majority of Webflow projects.

1. Understand the Mobile Usage Landscape

• 320px is the smallest standard width considered "mobile" by most frameworks, including Webflow's breakpoints.
• The number of users on screens smaller than 320px is extremely small, often less than 0.5% of total web traffic according to global analytics data.
• Nearly all modern smartphones start at 360px or higher screen width.

2. Webflow’s Mobile Breakpoints

• Webflow's default smallest breakpoint is 320px and up (Mobile Portrait).
• Webflow does not provide smaller breakpoints by default, and targeting screen widths below 320px requires custom CSS, which is rarely worth the effort.

3. Common Practice Among Designers

• Most designers and developers ignore sub-320px widths, focusing instead on:

• Desktop (992px+)

• Tablet (768–991px)

• Mobile Landscape (480–767px)

• Mobile Portrait (up to 479px, usually targeting 320px+)

• If a layout still works decently below 320px without major issues, that’s sufficient in most cases.

• Accessibility and readable content should scale down gracefully, but pixel-perfect design is not expected below 320px.

4. Possible Exceptions

• If you’re creating content for:

• Emerging markets with exceptionally small/older devices

• IoT or wearable devices

• A data-heavy audience that tracks engagement in extremely narrow viewports

  ...then it may be worth testing below 320px, but only if analytics validate the need.

Summary

You do not need to prioritize responsiveness below 320px in Webflow unless your analytics show significant traffic from those devices. Standard practice is optimizing from 320px and up, which covers nearly all modern mobile users.