Chrome DevTools shows one device at a time. I built a tool that shows three
A free responsive tester with real viewport sizes, no signup, and side-by-side comparison.

Every responsive check I do follows the same loop.
Open DevTools. Pick a phone. Scroll through the page. Switch to a tablet. Scroll again. Switch back to the phone. Try to remember if that header gap was there before or if I just introduced it.
One device at a time. No way to compare. Just memory and hope.
I've been doing frontend work for a while now, and this workflow never improved. Chrome added more device presets, sure. But the fundamental limitation stayed — you see one viewport, you lose context when you switch, and you repeat the whole cycle after every deploy.
So I built something for it.
What It Does
Responsive Tool loads your site on phone, tablet, and desktop at the same time. Three panes, one screen, real CSS viewport sizes.
You can:
Swap any single pane to a different device — the other two stay put
Refresh one pane after pushing code — no need to reload everything
Enter a custom width if your breakpoint isn't a standard device
Share the URL — it preserves your device setup, so a teammate sees the same comparison
Sync scroll across all three panes with a one-line script snippet
No account. No download. No extension. It runs entirely in your browser. I don't see or store the URLs you test.
The Viewport Data Is Real
This is the part that took the most time, honestly. Every device viewport on the tool and on the reference page is the actual CSS viewport size — not the physical resolution, not a rounded guess.
I cross-checked every single one against multiple sources. Found two outdated specs in common reference sites during the process (iPad Pro 13" and MacBook Air 13" were wrong in several places online). Fixed them with sourced replacements.
There's also a CSS breakpoints reference that maps common breakpoints to real device ranges, with boundary testing at -1px / exact / +1px for each breakpoint. Turns out testing at exactly 768px isn't enough — the bugs hide at 767.
The Iframe Problem
Here's something I learned building this: a lot of websites block being loaded in iframes.
I tested about 60 real sites. 93% of developer portfolio sites loaded fine. But only 44% of framework and marketing sites did — most block via X-Frame-Options: DENY or Content-Security-Policy: frame-ancestors.
There's also a weird edge case with Cloudflare Workers: they don't resolve CNAME chains the way normal DNS does. So sites hosted on GitHub Pages via custom domains were getting falsely flagged as private network addresses. Had to build a hop-following DNS resolver to fix that.
If your site doesn't load in the tool, it's the server blocking iframes, not a bug. Working on a proxy-based fallback for this.
Stack
Next.js 16 (App Router)
React 19
TypeScript
Tailwind CSS v4
Cloudflare Workers
Try It
If you test a site and something breaks or doesn't load right, I genuinely want to hear about it. Still early, still improving.
About the author
- Software Engineer. Fond of music. Problem Solver
Comments
Join the discussionNo comments yet. Be the first to comment.
