Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC 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 & 11There is no mandatory set of screen widths every responsive site must target. Build a flexible layout first, then add a breakpoint where the content needs a different arrangement—such as when navigation wraps awkwardly or columns become too narrow. Use viewport media queries for page-wide changes and container queries when a reusable component should respond to the space its parent provides.
What a CSS breakpoint does
A breakpoint is a condition threshold at which a media or container query becomes true and its CSS rules apply. A minimum-width query, for example, can add columns once there is enough room. The threshold is a design decision, not a standard tied to a particular phone or tablet.
MDN notes that media queries can help with responsive design but are not required: flexible layouts can adapt without a query at every width. MDN’s responsive-design guide and web.dev’s media-query guide both support choosing breakpoints based on content rather than a fixed device checklist.
Choose a breakpoint from the layout
- Start with the content. Identify what must remain readable and usable: text measure, navigation, forms, cards, or columns.
- Use flexible CSS first. Let Grid, Flexbox, and flexible sizing handle ordinary changes in available width.
- Inspect the layout across widths. Look for a specific failure: text becoming cramped, navigation wrapping, columns becoming too narrow, or controls becoming difficult to use.
- Add the smallest necessary change. Put a query at the width where that layout needs a different arrangement, and change only the affected rules.
- Check nearby widths too. A layout should work on both sides of the threshold, not just at the widths of a few popular devices.
For text-led layouts, a relative text unit such as em or ch may express the constraint better than a pixel value. For image-driven content, pixels may be a reasonable fit. The unit and threshold should reflect what is driving the layout; neither a unit nor a sample value is universally correct.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors#1 Best Overall
Use viewport media queries for page-wide changes
A viewport media query responds to the browser window’s available space. In a mobile-first stylesheet, write the narrow layout as the base and add wider arrangements as needed:
/* Base rules: one column when space is limited. */
.cards {
display: grid;
grid-template-columns: 1fr;
}
/* Illustrative threshold only: choose it from your content. */
@media (width >= 42rem) {
.cards {
grid-template-columns: repeat(2, minmax(0, 1fr));
}
}The 42rem value illustrates range syntax; it is not a recommended universal breakpoint. Modern range syntax is one way to express a width condition. A minimum-width form is also common:
@media (min-width: 48rem) {
.layout {
grid-template-columns: 16rem 1fr;
}
}Here too, 48rem is illustrative. Set the actual threshold by checking when the content can use the second column.
Check the viewport declaration
Include this in the document head so mobile browsers use the device-width layout viewport:
<meta name="viewport" content="width=device-width, initial-scale=1">Without an appropriate viewport declaration, some mobile browsers may use a wider virtual viewport, so narrow-width media queries may not match as intended. See MDN’s viewport meta-element reference.
Use container queries for components
A viewport query is the right scope when the page as a whole should change with the window. A reusable component often needs a different scope: a card may sit in a wide desktop page but be placed in a narrow sidebar. A container query lets the component respond to its containing block rather than the viewport.
.card-list {
container-type: inline-size;
}
/* Illustrative threshold: set it from the component's content. */
@container (width >= 32rem) {
.card {
display: grid;
grid-template-columns: 10rem 1fr;
}
}Use container queries when the component’s own available inline space governs its layout; use viewport media queries for page-level decisions. The threshold above is an example, not a standard. For details on query features and syntax, see MDN’s CSS media queries guide.
Width is not the only media-query condition
Media queries can also test features such as height, orientation, aspect ratio, resolution, pointer and hover characteristics, and user preferences including color scheme and reduced motion. Combine conditions with and, or use a query list when alternative conditions should apply the same rules. Use these features when the behavior genuinely depends on them, rather than treating them as substitutes for a content-based layout decision. Examples and syntax are in MDN’s guide to using media queries.
Recommended Free Tools
Avoid common breakpoint mistakes
- Copying device widths as requirements: device sizes change, and the same layout can be used in different contexts. Find the point where your content needs to change.
- Adding queries for every small width difference: flexible Grid and Flexbox can handle many changes without extra rules.
- Using a viewport query for a component constraint: a component placed in a narrow parent may need to adapt even when the viewport is wide; consider a container query.
- Using viewport units alone to set text size: MDN warns that this can make text zoom less effective for users. Prefer a text-sizing approach that preserves user control.
- Testing only a few named devices: check the actual transition and the intermediate widths where wrapping or crowding may appear.
Troubleshoot a breakpoint that does not behave as expected
- A narrow-screen query does not match on mobile: verify the head includes
<meta name="viewport" content="width=device-width, initial-scale=1">. - The layout changes too early or too late: inspect the content near the threshold and adjust the condition to the point where the current arrangement stops working well.
- A reusable component responds to the page instead of its parent: use a container query for a parent-space decision, and establish a query container with
container-type. - Text is difficult to zoom: avoid relying on viewport units alone for font sizing; check the result with browser text zoom.
- Rules work at the threshold but fail nearby: test widths immediately below and above it, then make the base layout flexible enough to cover the interval.
Or skip the browser setup
If you need a rendered screenshot while checking responsive layouts, ScreenshotNeo accepts a URL in one API request and returns an image or PDF. Its documentation is at ScreenshotNeo docs.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe request returns a screenshot; it does not replace testing across widths. ScreenshotNeo removes known cookie and consent banners, newsletter popups, and chat widgets before capture, and those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; response headers report the page verdict and billing status. Its MCP server provides screenshot tools for AI agents. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. See the API documentation for parameters and options.
Sign up for 1,000 free screenshots a month, with no card.
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.
