Responsive testing

Responsive design testing across every screen size

Test responsive layouts by capturing every page at mobile, tablet and desktop widths in one run, then compare viewports and releases side by side.

Updated October 1, 2026

Resizing a browser window one page at a time does not scale. Responsive design testing captures each page at the breakpoints that matter in one run, so overlapping menus, horizontal scrolling and clipped content are visible together.

✓Mobile, tablet and desktop
✓Full-page captures
✓Side-by-side review
✓Every language too
1

Choose viewports from real traffic

Use analytics to pick the widths your visitors actually use, plus each CSS breakpoint boundary. Those edges are where layouts most often break.

2

Capture full pages, not just the fold

Problems often appear far down the page: tables, footers, embedded media. Full-page captures at each width give reviewers the complete picture.

  • Navigation and mobile menus
  • Tables and long content
  • Sticky headers and footers
  • Images and embeds
3

Compare viewports and releases

Review the same page across widths to spot inconsistent behavior, and across releases to catch regressions at one breakpoint that others hide.

4

Combine with localization

Long translations break mobile layouts first. Capturing languages × viewports finds the overflow that a single-language check misses.

Questions

Frequently asked questions

Which screen sizes should I test?

Your top device widths from analytics, plus one width on each side of every CSS breakpoint.

Is this the same as cross-browser testing?

No. Responsive testing varies screen size; cross-browser testing varies browser engine. VisualRunner focuses on viewport coverage in Chromium.

Continue exploring

Related resources

Turn the checklist into a repeatable workflow

Discover your pages, capture the important states and keep a visual history of every meaningful change.

Start free trial