Design for the space your content has—not a universal list of phone, tablet, and desktop widths. Start with a fluid layout, resize the browser, and add a breakpoint where the current arrangement stops working well. Then check accessibility reflow separately: WCAG 2.2 uses a width equivalent to 320 CSS pixels as a conformance test for vertically scrolling content, not as a recommended breakpoint.
What screen sizes should you design for?
Design for the available CSS viewport width and for what your content needs to remain readable and usable. A phone, tablet, or laptop label does not tell you exactly how much CSS space a page has: browser controls, window size, zoom, and device scaling all affect the layout viewport. A device’s advertised pixel resolution is therefore not a reliable substitute for the CSS viewport.
There is no universal responsive breakpoint chart required by W3C, MDN, or CSS. A breakpoint is a point where a layout needs to change. The right value depends on the content, font sizes, component behavior, and the width at which the current arrangement becomes cramped or unusable. MDN recommends relative units for media-query breakpoints and notes that flexible grids, relative units, and minimum or maximum sizing can sometimes adapt a layout without media queries.
For example, a navigation bar may need to wrap or collapse before a product-card grid needs fewer columns. A text-heavy article might remain a single column across a wide range of widths, while a dashboard with several panels may need structural changes sooner. Test the actual page rather than assigning breakpoints by device category.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
What are the standard responsive breakpoints?
There are no standard breakpoint values that every responsive site should use. MDN explains media-query fundamentals and responsive design, but its guidance is about choosing behavior for the layout—not adopting a mandatory set of widths. A preset can be a useful initial guess for a project, but it should not replace checking where your own content needs a different arrangement.
Use media queries when the layout needs a structural change, such as switching a grid from multiple columns to one. Before adding one, see whether a fluid layout can do the job with flexible tracks, relative units, and minimum or maximum dimensions. Fewer, purposeful breakpoints are often easier to maintain than a long list of device-specific exceptions.
MDN describes a mobile-first approach in which a narrow, one-column layout is the starting point and columns are added when the viewport has enough room. That is a useful method, not a requirement: you can also start with the layout that best fits the project and adapt it as needed. See MDN’s responsive web design guide and media-query fundamentals.
How do you choose a breakpoint?
- Build a flexible starting layout. Let content and containers use available space rather than assuming one fixed device width. If you choose mobile-first, begin with the narrow layout and add complexity as space allows.
- Resize continuously. Use your browser’s responsive viewport controls or resize its window gradually. Look for the point where a line becomes uncomfortably long or short, columns feel crowded, navigation no longer fits, or controls become hard to use.
- Identify the change the content needs. Decide whether the layout should wrap, reduce its number of columns, move a control, or change how navigation is presented. A breakpoint should enable that change; it is not valuable merely because a device category is common.
- Use a relative breakpoint where practical. MDN advises relative units for media-query breakpoints, which can better accommodate differences in text sizing and available space than a value chosen around one assumed device.
- Check images and neighboring content. Confirm that images stay within their available space and that columns and surrounding material reflow in a useful order.
- Test accessibility reflow separately. Verify the applicable WCAG Reflow condition for the content’s scrolling direction. Passing a typical phone-width check alone does not establish that the page reflows at enlarged zoom.
Keep a breakpoint only if it produces a meaningful improvement. If the fluid layout works across an interval, an extra media query adds complexity without solving a layout problem.
Recommended Free Tools
What is the best breakpoint for mobile?
There is no single best mobile breakpoint. Choose the width where your layout needs to become more compact or change structure, based on observation of the content—not a phone’s product name or a generic chart. If the navigation fits and text remains readable, there may be no reason to change it at a particular preset width. If it fails earlier, make the change earlier.
Rank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
Also distinguish a breakpoint value from a test viewport. A breakpoint is an author-chosen condition in your CSS. A viewport used for accessibility testing checks whether information and functionality remain available under a specified condition. The two values serve different purposes and need not match.
How does the WCAG 2.2 reflow target relate to breakpoints?
WCAG 2.2 Success Criterion 1.4.10, Reflow (Level AA), says: “Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:” the specified width or height conditions, except for content that requires a two-dimensional layout for its use or meaning. For vertically scrolling content, the test is a width equivalent to 320 CSS pixels. For horizontally scrolling content, the corresponding condition is a height equivalent to 256 CSS pixels. W3C explains that 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels at 400% zoom. See the WCAG 2.2 standard and W3C’s understanding document for Reflow.
These are accessibility conformance conditions, not instructions to add a media query at 320 pixels or to design for a device whose physical screen is 320 pixels wide. At high zoom, the CSS viewport can become much narrower than the display’s physical resolution suggests. Test the resulting layout and preserve information and functionality without requiring two-dimensional scrolling for ordinary vertically scrolling content.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →WCAG recognizes that some content genuinely depends on two dimensions for use or meaning. A map, a diagram, or some data tables may need horizontal and vertical movement. That exception does not exempt the rest of the page: surrounding reading content should still reflow. W3C describes the purpose and viewport/zoom relationship in its Reflow guidance.
How should images and columns adapt?
Responsive behavior is not only about changing column counts. Images should fit within their available space instead of forcing the page wider. W3C documents an advisory CSS technique using maximum width and height behavior in C37: Using CSS max-width and height to fit images. This is an example technique, not the only way to meet accessibility needs.
Rank #3
- Clear visuals. Fluid motion: A 144Hz refresh rate and 1ms MPRT deliver smooth, tear‑free motion across work, gaming, and streaming for clearer, more fluid viewing.
- Eye comfort: TÜV Rheinland 3‑star* certification reduces harmful blue light while preserving stunning color quality without compromise. *TÜV Rheinland 3-star eye comfort certification.
- Wide viewing angle: Get consistent views across a wide 178° /178° viewing angle.
- In-Plane Switching (IPS): See excellent color accuracy and consistency across wide viewing angles with In-plane Switching (IPS) technology.
- Ultra-thin bezels: Maximize your viewing experience with thin bezels.
For column layouts, CSS Grid can provide flexible tracks, with media queries where the arrangement needs an explicit change. W3C’s C32 technique shows Grid and media queries to reflow columns. Treat it as an implementation example, not a mandate to use Grid or a particular breakpoint value.
- Check that images do not overflow their containers or obscure adjacent content.
- Check column order and reading order when a multi-column layout becomes a single column.
- Check controls and navigation at narrow widths and enlarged text settings; avoid clipping or forcing horizontal scrolling for ordinary page content.
- Keep essential two-dimensional material usable, while allowing surrounding content to reflow.
W3C also advises checking responsive display across zoom and viewport sizes in its accessibility tips for developers.
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 →How to inspect viewport behavior in a browser
- Open the page in a browser and use its responsive design or device toolbar to set and adjust the viewport. Treat the displayed CSS viewport dimensions as test conditions, not as a definitive list of devices your audience owns.
- Reduce the width gradually, then widen it again. Note when content becomes crowded or a different arrangement becomes clearer.
- Inspect the page at the WCAG reflow-equivalent condition for its scroll direction, including testing enlarged zoom where appropriate. Confirm that users do not lose information or functionality.
- Repeat with representative pages and components: navigation, forms, tables, image-heavy sections, and any content that relies on two dimensions.
- Adjust CSS and test the transition points again. Do not assume that passing one viewport proves every layout state works.
Automate viewport checks with screenshots
A screenshot can help you compare the same page at specific viewport sizes during development or a regression check. It does not decide which breakpoint is right: inspect whether the rendered content remains usable, and test at widths between your chosen values as well. Automated screenshots are evidence of visual output, not proof by themselves of accessibility conformance or functional behavior.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request can return a PNG, JPEG, WebP, or PDF capture. For example, save a WebP screenshot of a page at a chosen viewport (the default viewport can be overridden using the service’s supported parameters):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for authentication and capture options. It accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses include X-Page-Verdict and X-Billed headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to try it without a credit card.
Rank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
Troubleshooting responsive layouts
The page has horizontal scrolling at a narrow viewport
Find the element wider than its container. Check images, long unbroken strings, fixed-width panels, navigation, and tables. Let ordinary content wrap or fit the available width; keep horizontal scrolling only where a two-dimensional region genuinely requires it.
A breakpoint looks right on one device but wrong elsewhere
Do not tune only against a device’s advertised resolution. Check the CSS viewport at different window sizes and zoom settings. Move or remove the breakpoint according to where the content actually stops working, and prefer relative units where appropriate.
The layout has too many media queries
Review whether each query solves a structural problem. Some transitions may work with a flexible grid, relative units, or min/max sizing without a query. Keep explicit breakpoints for changes that cannot be expressed cleanly as fluid behavior.
Columns become too narrow before the breakpoint
Test intermediate widths, not only the narrow and wide endpoints. Change the column arrangement at the point where content becomes cramped, or use a fluid layout that allows fewer columns when available space falls.
The page looks fine on a phone but fails at zoom
Test reflow as an accessibility condition, not as a visual check at a familiar phone preset. At the relevant equivalent viewport, verify information and functionality remain available. W3C’s developer tips discuss responsive display across zoom and viewport sizes: Developing for Web Accessibility.
Best Value
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
Performance, reliability, and cost considerations for screenshot checks
Manual viewport resizing is useful for discovery because it reveals where a layout begins to fail. Repeated screenshots can make visual comparison at selected viewports easier, but they cannot replace inspection between those viewports or interaction and accessibility checks. A screenshot may show clipping or awkward wrapping; it cannot by itself establish that a menu, form, or other control works.
For automated capture, choose only the output and viewport conditions needed for the check, and account for page load failures and dynamic content when interpreting results. ScreenshotNeo identifies page verdict and billing status in response headers; its pricing is available on the product site. Do not treat a successful image capture as a WCAG pass.
FAQ
Does every responsive website need media queries?
No. Flexible grids, relative units, and minimum or maximum sizing can adapt some layouts without media queries. Use a query when the content needs a deliberate structural change.
Free tools Windows power users keep installed
One-click scans. No signup required.
Is 320 CSS pixels a mobile breakpoint?
No. It is the WCAG 2.2 Reflow width condition for vertically scrolling content, expressed as an equivalent CSS viewport width. It is not a prescribed media-query value.
Can a table keep horizontal scrolling?
Some content whose use or meaning requires two dimensions is excepted from the no-two-dimensional-scrolling condition. Keep that exception scoped to the content that needs it; surrounding material should still reflow.
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.
