📱 Online Multi-Device Responsive Preview Tool

Processed locally in the browser · nothing uploaded

Preview one URL live side by side on phone, tablet and desktop viewports: 20 device presets plus custom sizes and rotation; paste or upload local HTML to render it directly. Sites that block embedding get a clear notice with a one-click open-in-new-tab.

① Enter a URL② Pick devices③ Compare side by side

Preview viewports are sandboxed: scripts on the target page run in an isolated origin, cannot read the sign-in state of this site, and cannot break out of the viewport. When a site forbids embedding, its viewport stays blank — use “Open in new tab” in the top control row.

How to use Online Multi-Device Responsive Preview Tool

Follow the steps to get it done

1

Enter a URL and click “Preview”, or switch to local HTML mode and paste code or upload an .html file

Open the page and start — no registration or sign-in needed.

2

Pick a device preset or custom width and height for each viewport; rotation applies live

Settings can be changed at any time; all computation happens in your browser.

3

Compare phone, tablet and desktop in the overlapping device scene — hover or tap a device to bring it to the front — and copy the link so others see the same URL

Copy or download the result when you are done. Nothing is kept on this site.

Page Actions

Mode switch: preview a URL

One of the two mode buttons at the top (selected by default): enter a URL in the input box and click “Preview”, and every viewport loads that URL directly.

Mode switch: local HTML

The other mode button at the top: switch to local HTML mode, the URL input row folds away and the HTML code box appears. Clicking back to “Preview a URL” returns to URL mode, and the code in the box stays on the page.

URL input box

Enter the URL to preview. A missing protocol is completed with https automatically, so example.com previews directly. Pressing Enter works the same as clicking “Preview”. Only http and https are accepted; other protocols are rejected with a note in the status area.

Preview button

Refresh all viewports with the URL in the input box. While loading, the button changes to “⏳ Loading…” and is disabled, and the status line reads “Loading N viewports…”; it returns to “▶ Preview” and reports “Loaded in N viewports” once every iframe has fired its load event. If they have not finished within 8 seconds, the status line warns that the site may block embedding or the network may be down. An invalid URL does not refresh anything, and the status area says why. The last URL you entered is cached in this browser and filled in when you reopen the page; it only loads after you click Preview.

HTML code box

The multi-line code box in local HTML mode: paste complete HTML code. The character count updates live below, with a limit of 200,000 characters; anything beyond it is cut off with a note in the status area. The content lives only on the current page and is never cached or uploaded.

Choose an .html file

In local HTML mode, “Choose an .html file” opens the system file picker and accepts only .html / .htm files up to 2MB. The picked file is read locally into the code box as text, never uploaded, and can be rendered straight away.

Render HTML

In local HTML mode, render the code in the box into all viewports. While rendering, the buttons are disabled and the status line reads “Rendering N viewports…”; it reports the render result when finished, and warns about a timeout after 8 seconds. An empty code box renders nothing, and the status area asks you to paste code or pick a file first.

HTML character count

A persistent small note next to the render button: the current character count against the 200,000 limit, for example 1234 / 200000 characters. When the limit is exceeded it shows the truncated count.

Scrollbar dropdown

A scrollbar switch shared by all viewports: shown by default, so pages can be scrolled inside each viewport. Hiding it removes the scrollbars and also disables scrolling inside the viewports — best for a clean static layout comparison.

Refresh all

Reload all viewports: URL mode revisits the URL, local HTML mode re-renders the current code. While reloading, both Preview and Refresh all are disabled and the status line reads “Refreshing N viewports…”, then reports “Refreshed all viewports” once every load event has fired. After changing the URL there is no need to click it — Preview refreshes everything.

Copy link

Copy a link to this page with a ?url= parameter: opening it previews the same URL automatically. In local HTML mode the button is disabled, with a persistent note beside it saying the share link only works in URL mode.

Open in new tab

The new-tab button in the top control row: URL mode opens the current URL in a new tab; local HTML mode opens the code as its own page. This is how you view a site whose viewport is blank because embedding is blocked.

Device size dropdown (per section)

The dropdown at the top of each device section, listing only that group's presets: 4 phones (iPhone 17 / 17 Pro, iPhone 17 Pro Max, Samsung Galaxy A07, Samsung Galaxy A16 5G), 5 tablets (Huawei MatePad 11.5, iPad 11-inch, Lenovo Xiaoxin Pad Pro 12.7, Xiaomi Pad 7, Honor Pad 9), 8 laptops (Lenovo Xiaoxin Pro 14, Lenovo Legion Y7000P, MacBook Air 13, MacBook Pro 14, Asus Vivobook Pro 15, Asus TUF Gaming, HP Zhan 66, HP Star Book Pro 14) and 3 desktops (1920×1080, 2560×1440, 3440×1440), plus Custom size. Changing it only resizes that section's device frame — no iframe is rebuilt and no viewport reloads.

Custom width (number box)

Appears in that device settings block when the device dropdown is set to Custom: width from 240 to 3840 pixels, applied as soon as you type it, clamped automatically with a note in the status area when out of range.

Custom height (number box)

Appears in that device settings block when the device dropdown is set to Custom: height from 240 to 1600 pixels, applied as soon as you type it, clamped automatically when out of range.

Rotate button (per viewport)

The ⟳ button in each device settings block: swaps width and height (for example 402×874 becomes 874×402); click again to swap back. The custom width and height boxes of that device update to the swapped values.

Bring a device to the front (hover/tap)

With devices overlapping, hovering or tapping the visible part of a device brings it to the front, no longer covered. The last device you touched stays in front until you hover or tap another one; on touch screens without hover, tapping brings it forward just the same. Hovering a device settings block in the settings strip brings its device forward too. Coming forward animates with a slight scale-up and shadow, instead of jumping abruptly.

Fullscreen button

The “⛶ Fullscreen” button at the bottom-right corner of the scene: shows only the device scene fullscreen (the settings strip stays out), scaled to the screen and centred. In fullscreen the button reads “⛶ Exit fullscreen”; click it or press Esc to leave, and the scene returns to its place.

Per-device fullscreen icon

Hovering over a device reveals a “⛶” icon at its bottom-right corner (hidden otherwise): click it to show only that device fullscreen (the others hide), scaled to the screen and centred. Click “⛶ Exit fullscreen” at the bottom-right of the scene or press Esc to leave, and all four devices return side by side. On touch screens, tapping a device reveals its icon too.

Preview summary (persistent)

A persistent line at the bottom of the control panel: the current mode, the viewport count and each viewport size, for example “URL mode · 4 viewports: 402×874 / 800×1228 / 1440×900 / 1920×1080”.

Status (persistent)

A persistent status line at the bottom of the control panel: loading, rendering, refreshing, load complete, the 8-second timeout (the site may block embedding or the network may be down), invalid URL, oversized file, truncated text and copy success are all written here and never disappear. Failures show in red with the reason.

Capture screenshot

The “📷 Capture screenshot” button at the bottom of the left settings strip: in the picker choose “This tab” and allow sharing; the tool grabs one frame of the current page and crops the preview scene out as a PNG. No screenshot extension and no manual selection needed.

Copy screenshot

“📋 Copy” puts the last capture on the clipboard so you can paste it into a chat, an email or a document. When the browser cannot copy images, the status area suggests Download instead.

Download screenshot

“⬇ Download” saves the last capture as a PNG named tool-slug_host.png, for example responsive-preview_example.com.png. Local HTML mode has no URL, so the file is responsive-preview_local-html.png.

Save to cloud

“☁ Save to cloud” stores the last capture in member cloud storage, counted against the cloud storage quota. Signed-out users get the sign-in dialog first. The same filename is not overwritten — saving again adds another copy — and files can be reviewed or cleared under Storage on the account page.

Capture status (persistent)

A persistent small note at the bottom of the capture block: choose “This tab”, the captured filename, copy success, sharing declined, uploading, cloud storage full and other results are all written here. Failures show in red with the reason.

How It Works & Highlights

How it works, and where it fits

This tool uses no server-side proxy. In URL mode the browser loads the target site directly into 4 sandboxed iframes, each sized to the CSS pixel width and height of the chosen device, wrapped in the matching frame of its device group (phone, tablet, laptop and desktop — custom sizes use their group's frame too), and then the whole device scene is scaled to fit the scene column width. Changing a section's device, size or rotation only recomputes that section's frame size and scale: no iframe is rebuilt and no viewport reloads. The sandbox carries neither allow-same-origin nor allow-top-navigation, so scripts on the target page run in an isolated origin: they cannot read the sign-in state of this site and cannot break out of the viewport. In local HTML mode the code is written into the srcdoc of the iframe and rendered directly, with no request sent. When the target site sends a header that forbids embedding, the browser blocks it outright and the viewport can only stay blank — a browser security rule this tool cannot work around.

Highlights

  • ✓ 20 device presets for phone, tablet and desktop, each in its matching device frame for a multi-device view at a glance, with custom width and height and rotation that apply live
  • ✓ 4 devices in an overlapping scene, live — hover or tap to bring one to the front, click links and scroll pages right inside each device
  • ✓ Paste or upload local HTML and render it directly, no deploy needed to check a landing page
  • ✓ Zero-proxy direct loading: the URL never passes through the servers of this site, sandboxed, with a clear notice when embedding is blocked
  • ✓ Free, no sign-in; share links let others view the same URL side by side
  • ✓ One-click capture of the four-device scene: the cropped PNG can be copied, downloaded or saved to member cloud storage

Tips

  • 💡 Check the phone viewport first: most traffic to an independent store comes from phones, so fix the phone layout before tablet and desktop
  • 💡 Type widths near breakpoints such as 360, 768 and 1024 in the custom size boxes — layout breaks show up there first
  • 💡 Do not keep refreshing a blank viewport: click open in new tab first to confirm the URL itself loads, then check whether embedding is blocked

FAQ

Privacy, format limits, and usage tips

Usually not. Many sites send X-Frame-Options or a CSP frame-ancestors header that forbids embedding on other pages, and the browser blocks them outright, leaving the viewport blank. Click “Open in new tab” in the top control row to view the site normally. If it is your own site, remove the embedding restriction or add this site to the frame-ancestors allowlist.
Close, but it is not a real device. The preview only simulates CSS pixel width, height and zoom: real device pixel ratio, touch gestures, system fonts and browser differences are not simulated, and code that branches on touch or pixel ratio follows the desktop browser path here. Check the final version on a real device.
Not reliably. Viewports are sandboxed and do not share cookies with signed-in tabs in your browser, and the target site sign-in cookie can also be blocked by third-party cookie partitioning, so the session may not hold. To check pages behind sign-in, open them in a new tab, or preview public pages that need no sign-in.
No. Each viewport is an independent page instance, and cross-origin security rules stop one page from reading or changing the scroll position and clicks of another site. A link clicked or a page scrolled in one viewport affects only that viewport. Changing the URL or clicking refresh updates all viewports together.
Local HTML renders exactly the code you paste or upload. Relative paths such as images/logo.png or style.css have no site root to resolve against, so the browser has nowhere to fetch them from. Use full http/https addresses instead, or write the styles directly into the HTML.
No. In URL mode the browser loads the target site directly, without going through the servers of this site, and this site does not record the URL you enter — but the target site sees a normal visit. Local HTML lives only on the current page and is destroyed when you close it. The last URL you entered is cached only in your own browser, filled in when you reopen the page, and never uploaded.
No. In URL mode the browser loads the target site directly, without going through the servers of this site, and this site does not record the URL you enter — but the target site sees a normal visit. Local HTML lives only on the current page and is destroyed when you close it; an .html file is only read locally, never uploaded.
Any recent browser works (Chrome, Edge, Firefox, or Safari from the last three years). It works on phones too, but batch file handling and table checks are more efficient on a large screen.
When a preview is blank, click “Open in new tab” in the top control row first to confirm the URL itself loads: if it opens, the site most likely forbids embedding; if it does not, the URL is wrong or the site is down. If a button does nothing, refresh the page and try again. If it still fails, send the steps to reproduce via 「Feedback」 in the top bar.
4 viewports, one per device group (phone, tablet, laptop, desktop). Custom width 240 to 3840 pixels and height 240 to 1600 pixels, clamped automatically when out of range. URLs are limited to http/https and 2,048 characters. Local HTML is limited to 200,000 characters, and .html files to 2MB. A site that forbids embedding shows a blank viewport — open it in a new tab. The preview only simulates CSS pixel width and height, not real device pixel ratio or touch, and sign-in state does not hold inside a viewport. Capturing needs permission to share “This tab”; the capture is one frame of the current page cropped to the preview scene, and cloud storage takes files up to 50MB each.
No. You cannot enter several URLs at once; one URL can be shown in 4 viewports side by side, and changing the URL or clicking refresh updates all viewports together.
1 to 4 live preview viewports side by side, clickable inside each viewport. A URL can be shared as a ?url= link so others view the same page. Capture screenshot at the bottom of the left settings strip saves the preview scene as a PNG you can copy, download, or store in member cloud storage after signing in, named tool-slug_host.png.
URL mode needs a network connection. Local HTML mode works offline once the page has loaded successfully (it relies on the browser cache); clearing the cache or switching devices means loading it online again.
No. Favorites and recent-use records only store tool names, never your files or text. When you are not signed in, favorites are kept only in your browser's localStorage; after signing in they sync to your account and work across devices. Recent-use records stay on your own machine.
First check that the input is complete and the format matches the hints on the page — you can click the example on the page to verify quickly. If it is still wrong, refresh the page and send us the steps and a screenshot via the feedback form.
Send your question or suggestion via 「Feedback」 in the top bar. Describe the use case and the outcome you want, and we will assess it before updating the tool and the page.

Related tutorials

Step-by-step guides for this tool on our blog