How to Take a Mobile Website Screenshot with WebPageTest
Use WebPageTest’s mobile emulation to capture a site at phone size, then inspect its visual output. Learn what the capture represents and how to compare runs reliably.
To take a mobile website screenshot with WebPageTest, open its Site Performance test, enter the page URL, select a mobile or emulated mobile browser configuration, and run the test. Then inspect the visual result, filmstrip, or video capture. The mobile preset configures the test as a mobile browser run; it is not a crop of a desktop screenshot.
1. Configure and run a mobile test
- Open WebPageTest’s Site Performance test and enter the full URL of the page you want to capture, including its scheme, such as
https://example.com/. - Choose a mobile browser or device preset in the browser and device controls. The current interface snapshot in the research lists Chrome on an emulated Motorola G (gen 4). Advanced configuration also offers browser, location, and device choices.
- Choose test conditions that match your question. You can set a test location, connection profile, number of runs, and first-view or repeat-view behavior. Leave unrelated settings consistent if you plan to compare results.
- Submit the test and open its visual output. WebPageTest documents video capture and visual comparison; the results can include a filmstrip or video, and the test interface offers a full-size video capture setting. Exact result-page labels can change, so look for the visual or video output rather than relying on a fixed button name.
Save the selected browser or device preset, location, connection profile, view type, run count, and capture type with your notes. These settings describe the context of the screenshot and help make later comparisons meaningful.
2. What a mobile-emulated screenshot represents
A mobile-emulated run uses a mobile browser configuration. A WebPageTest staff explanation describes mobile emulation as changing the user agent to mimic the selected phone, resizing the browser window to match the device, and throttling CPU accordingly. That means the output reflects more than a narrow viewport: browser identity and processing conditions may differ from a desktop run.
Describe the result as an emulated mobile capture when that is the configuration you chose. The documented workflow does not require you to own a physical phone. The available research does not establish WebPageTest’s current inventory or regional availability of physical-device agents, so do not assume a particular real-device option is available.
3. Make useful comparisons
When you compare two screenshots, hold the test context steady. Otherwise, a visual difference may come from the configuration rather than a page change.
| Setting | What to keep consistent |
|---|---|
| Rendering configuration | Mobile browser or device preset and emulation behavior |
| Network and geography | Test location and connection profile |
| Load selection | First view or repeat view, plus the number of runs |
| Capture output | Visual result or filmstrip versus full-size video capture |
For a layout check, use the same mobile preset and test settings before and after your change. If you are investigating loading behavior, preserve the location and connection profile too, since those conditions are part of the run.
4. When WebPageTest is the right fit
Use WebPageTest when you want a mobile-configured performance test and a visual record of what rendered under the selected test conditions. Its visual features include video capture and visual comparison, which can help review how the page appears during a run. If you only need a returned image file from a URL, a screenshot API may fit that narrower workflow better.
5. Troubleshooting
The screenshot looks like desktop
Cause: A desktop browser configuration may have been selected, or the mobile preset was not applied to the run.
Fix: Select a mobile or emulated mobile browser/device option before submitting a new test. Do not assume resizing a desktop result afterward is equivalent to a mobile-emulated run.
The page differs between two captures
Cause: The browser/device preset, location, connection, first-view or repeat-view selection, run count, or capture type changed.
Fix: Match these settings and rerun. Record them alongside each capture.
The result is a video or filmstrip instead of one obvious image
Cause: WebPageTest’s visual output can include video capture and filmstrip views, and the exact result-screen labels may change.
Fix: Open the visual results and inspect the relevant frame or full-size video capture option. The research does not verify a stable, exact sequence of result-page button labels.
You cannot find the old mobile emulation control
Cause: The interface may list emulated mobile devices in the main browser dropdown rather than exposing a separate checkbox. A staff response in 2023 described that arrangement; the current interface may differ.
Fix: Check the main browser/device choices for mobile presets and confirm the selected configuration before running the test.
You need a physical-device result
Cause: Emulation represents a configured browser environment, not proof of behavior on a particular physical handset.
Fix: Use a physical device for validation that depends on actual hardware or device-specific behavior. WebPageTest’s current physical-agent availability is not established by the sources used here.
6. Performance, reliability, and cost considerations
The screenshot is tied to a test run, so the selected location, connection, browser/device configuration, and view behavior affect what you observe. For repeatable checks, keep those conditions fixed and retain the run settings with the image or video. The available source material does not provide benchmark figures, capture-time guarantees, or a complete current pricing breakdown, so none are stated here. WebPageTest Pro describes API access, bulk testing, premium locations, experiments, and private tests for advanced or repeated testing needs.
Or skip the browser setup
ScreenshotNeo returns a screenshot or PDF from one GET request, with options for mobile device presets, custom viewport dimensions, and full-page capture. Its API uses the parameter names other screenshot APIs use, which can make switching easier. 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.webpimport 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}`);Before capture, ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. An MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for 1,000 free screenshots a month, no card required.
FAQ
Does a mobile WebPageTest screenshot require a phone?
No. The documented emulated workflow selects a mobile browser/device configuration in WebPageTest.
Is mobile emulation the same as testing on a physical phone?
No. Emulation changes browser identity, viewport size, and CPU behavior according to the selected configuration; it does not establish how a particular physical handset behaves.
Can I use the screenshot as a fair before-and-after comparison?
Yes, if you keep the browser/device preset, location, connection, view selection, run count, and capture type consistent.
