ScreenshotNeo

BlogHow-to

How to capture a mobile viewport screenshot with Screenshot.rocks

Capture a mobile viewport with Screenshot.rocks, or use browser DevTools for logged-in pages, custom sizes, and full-page screenshots.

By the ScreenshotNeo team4 October 20265 min read

To capture a mobile viewport screenshot with Screenshot.rocks, open its editor, enter the public page URL under “Or capture a website,” select Mobile, and click Capture. The service documents a fixed mobile profile of 375 × 812 points at 3× pixel density, producing a 1125 × 2436 pixel image. This captures the first screen, not the full scrolling page. Open Screenshot.rocks.

Use this quick online workflow for a public page when a framed mobile preview is enough. Use Chrome or Edge DevTools when you need a logged-in or local page, a custom viewport, or a full-page capture. Use a real phone when the output must match that physical device.

1. Capture a public page with Screenshot.rocks

  1. Open the Screenshot.rocks editor.
  2. Under Or capture a website, enter the page address.
  3. Select Mobile, then click Capture.
  4. Review the first-screen result in the phone frame, choose a background, and export the image.

The documented profile is 375 × 812 points at 3× density, resulting in a 1125 × 2436 pixel image. This is the service’s simulated iPhone X sized profile; it is not a choice of arbitrary real-device models. The guide says URL capture is free and does not require an account.

Before exporting, check that the visible part of the page is the part you want to present. Dismiss cookie banners or app-install prompts if they cover the content, and check dark mode when it matters to the review. The online workflow cannot capture content below the first screen.

2. Capture with Chrome or Edge DevTools

DevTools is the practical fallback for pages your browser session can already access, including authenticated pages and local development servers. It also offers visible-viewport and full-page capture.

  1. Open the target page in Chrome or Edge and open DevTools. Use F12 or ⌘+⌥+I on Mac.
  2. Turn on the device toolbar with Ctrl+Shift+M on Windows, or ⌘+⇧+M on Mac.
  3. Choose a phone preset, or enter a custom viewport width and height. Set the device pixel ratio if you need a higher-resolution output.
  4. Reload the page after changing the dimensions. Some pages choose responsive styles when they load, so changing the viewport without reloading can leave desktop styling in place.
  5. Open the device toolbar’s more-options menu and select Capture screenshot for the visible viewport or Capture full size screenshot for the whole page.

Chrome’s documentation distinguishes viewport capture from full-size capture. A full-size image can be much taller and larger than a viewport screenshot. For a custom width, Screenshot.rocks advises setting device pixel ratio to 2 or 3 when a sharper image is needed. Increasing pixel density also increases output dimensions and file size.

3. Choose the right capture method

Need Best fit Key limit
Fast, framed preview of a public page Screenshot.rocks online capture Fixed simulated profile; first screen only
Authenticated page, localhost, custom dimensions, or full page Chrome or Edge DevTools Emulation does not guarantee the exact behavior or appearance of a physical handset
Faithful capture of one actual handset Screenshot on that phone Requires access to the device and its current browser state

Screenshot.rocks also documents Firefox Responsive Design Mode, Safari Responsive Design Mode, and capturing directly on a phone. For the closest match to a particular physical device, its guide recommends using that real device.

4. Troubleshooting

Problem Likely cause What to do
The online capture cannot open the page The page requires login, uses a local address such as localhost, or blocks automated browsers. Open it in the browser session that has access and capture it with DevTools.
The screenshot shows desktop styling The page selected its layout before the mobile viewport was applied. Set the device dimensions, then reload the page before capturing.
The output looks blurry The custom viewport may be using a low device pixel ratio. In DevTools, raise the device pixel ratio to 2 or 3 and capture again. Expect a larger image file.
A banner or prompt hides the content A cookie consent panel or app-install prompt is over the page. Dismiss it before capturing when using DevTools; in the online flow, follow the service’s available page and styling workflow.
The image ends before the page does The online capture records only the first screen. Use DevTools’ Capture full size screenshot option for a full-page image.
The result does not match a particular phone Viewport emulation is simulated and the online service uses a documented fixed profile. Capture on the target physical phone when device-specific fidelity is required.

5. Quality, reliability, and file size

  • Decide the extent first: label the deliverable as viewport or full page so reviewers know whether content below the fold is included.
  • Reload after changing dimensions: this allows responsive rules and scripts that inspect the viewport at load time to run with the intended size.
  • Control resolution: a higher device pixel ratio gives more pixels, but also larger images and potentially slower sharing or review.
  • Check overlays and theme: dismiss prompts and inspect dark mode if either changes the content under review.
  • Match fidelity to purpose: emulation is useful for review and documentation; a real handset is the more reliable choice for a capture that must reflect that device.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request returns a screenshot or PDF; its 12 device presets and custom viewport options support mobile-sized captures. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Replace the example URL with the page you can access publicly. ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000.

Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month without a card.

FAQ

Does Screenshot.rocks capture a full mobile page?

No. Its online URL capture shows the first screen. Use DevTools’ full-size screenshot option when you need the scrolling page.

Is the Screenshot.rocks mobile result a real iPhone screenshot?

No. The guide describes a simulated 375 × 812 point profile at 3× density. Capture on the phone itself when the actual device matters.

Can I capture a page behind a login with Screenshot.rocks?

The online URL capture cannot access a page behind a login. Use DevTools in the browser session that is already authenticated.

Can I use the online capture for localhost?

No. For a local development page, use browser DevTools on the machine where the local address works.