Responsive Website Tester
Run this utility locally in your browser.
Run this utility locally in your browser.
Enter a URL and the page loads it in frames sized like common devices: a phone at 375×667 CSS pixels (iPhone SE and similar), a tablet at 768×1024 (iPad portrait) and a laptop at 1366×768. Scroll inside each frame to check navigation menus, images, tables and forms at every width without resizing your window.
Many sites forbid being shown inside a frame on other domains with the X-Frame-Options or Content-Security-Policy: frame-ancestors header (Google, GitHub and most banks do). The frame then stays blank. That is a protection, not a fault in your layout. For those sites, and for your own pages on localhost, use the browser's device mode: press F12 then Ctrl+Shift+M in Chrome or Edge, or Ctrl+Shift+M in Firefox.
<meta name="viewport" content="width=device-width, initial-scale=1">; without it phones render a zoomed-out desktop layout.max-width: 100%, an overflow-x: auto wrapper).Frameworks use similar widths: Tailwind sm 640, md 768, lg 1024, xl 1280; Bootstrap 576, 768, 992, 1200. Test just below and above each breakpoint your CSS uses. To convert pixel values to rem for media queries, use the CSS unit converter.
It matches the layout width, which is what responsive CSS responds to, but not touch behaviour, device pixel ratio or mobile browser quirks. Do a final check on a real device.
Your browser loads the site directly in the frames, exactly as when you visit it. Nothing passes through NeatJSON.