Unknown author · Developer Tools
3 items
Preview any page on true-to-size iPhones, Android phones and tablets — a mobile simulator for responsive testing. A mobile simulator that lives in the tab you are already in. One click puts the page you are working on inside a realistic phone or tablet on a lit table, and the address bar stays your site's URL. Chrome's own emulation engine drives the device, so the page really believes it is on a phone. WHAT IT DOES • One click, one device: the framed light table opens in the current tab. The site keeps its own URL; the light table's URL field shows where the device is. • A real tab when you want one: "Real tab (no frame)" turns the tab itself into the device, with the browser's own address bar following the site. • 49 device presets: iPhones (including the 2026 iPhone 18 Pro, 18 Pro Max and the foldable iPhone Duo), Android phones, foldables, tablets and desktop sizes. Search by name, size or pixel ratio. • Boards: up to four devices side by side on the same page, one shared navigation. • Rotate, fit or 100%, reload, and a URL field that navigates the device. • Capture the viewport or the full page, framed or frameless, at the device's native pixels. An iPhone 17 Pro capture is 1206×2436 for a 402×812 viewport. • A readout that says exactly what is emulated: touch, mobile UA, client hints, hover:none / pointer:coarse, device pixel ratio. When something is not applied, it says so instead of staying green. • Live device (optional): run the page on a real WebKit or Chromium engine on a relay you host yourself. It leads with "run it on local Chrome, nothing to install"; true Safari is the quiet advanced path. No account, nothing hosted by us. HOW IT WORKS The extension uses Chrome's DevTools emulation layer (the same one behind DevTools device mode) through the debugger API: mobile user agent and client hints on every request, touch events, hover:none and pointer:coarse, and the device's true pixel ratio. Captures come out at native device resolution. HONEST LIMITS • Chrome shows its own "started debugging this browser" bar while a device is emulating. It takes 40 to 56 pixels of height; Cancel on that bar stops emulation. • Browser pages, the extension store and file:// pages cannot be debugged. The stage opens as its own tab for those, or for file:// when file access is allowed. • Cross-site iframes inside the tested page keep the desktop pointer and hover; the readout reports the page's own top document. • Full-page captures stop at 32,767 device pixels tall. • The first navigation of a device can lose a race with its own debugger session and show ERR_BLOCKED_BY_RESPONSE; the engine retries that load automatically. • In the framed mode the site runs inside the frame, so the browser address bar stays on the entry page while the device navigates inside. The overlay is dropped when the host tab reloads or navigates. Free. No account. No tracking. No remote code. The only network connection the extension makes is to a relay endpoint you configure for Live device (loopback by default); everything else happens in your browser.
Oct 29, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.