How to Set a Custom Screen Resolution in LambdaTest Screenshot
Set a desktop resolution in LambdaTest Screenshot session preferences. For mobile viewports, use Responsive Testing or LT Browser custom devices.
Direct answer: In LambdaTest’s automated Screenshot workflow, choose a supported resolution in the test-session preferences before you run the screenshot session. The vendor’s guide says this setting applies to desktop devices. For mobile responsiveness, use Responsive Testing or LT Browser custom device viewports instead. The available sources do not establish today’s exact control labels, supported dimensions, or plan limits, so check the live interface for those details. The vendor’s automated screenshot guide documents the desktop-only distinction.
Set a desktop resolution for an automated screenshot
- Open the automated Screenshot test setup in LambdaTest.
- Find the test-session preferences and choose a resolution for the desktop session.
- Run the screenshot session and review the resulting capture.
This is the documented high-level workflow. The reviewed guide does not provide current click-by-click instructions or a numeric list of resolutions. If the setting is missing or named differently, consult the current product interface or help material rather than relying on old button names.
Choose the right workflow for your viewport
| Need | Workflow | What to expect |
|---|---|---|
| Capture a desktop page at a selected size | Automated Screenshot session preferences | The guide describes resolution selection here as desktop-only. |
| Check a mobile layout | Responsive Testing or LT Browser | Vendor material describes mobile device viewports and custom mobile resolutions. |
| Compare several sizes or inspect behavior interactively | Responsive Testing or LT Browser | Vendor guidance describes custom viewports and side-by-side mobile comparisons; LT Browser material also describes interactive debugging features. |
LT Browser product information describes pre-installed and custom mobile viewports, plus custom tablet, laptop, and desktop viewports. It also describes per-viewport DevTools, recording, and bug reports. The responsive testing guide discusses custom devices and comparing mobile views side by side.
Resolution, viewport, and device size
Do not assume that a screen resolution, browser viewport, physical display resolution, device pixel ratio, and browser zoom are interchangeable. The reviewed product sources use “resolution” and “viewport” in describing their workflows but do not specify how device pixel ratio or zoom is handled. If pixel-perfect output matters, confirm the behavior in the current product documentation and inspect the captured result at the intended size.
Practical checks before running
- Decide whether the target is a desktop screenshot or a mobile responsive check.
- Use the Screenshot session preference for the documented desktop resolution workflow.
- For mobile, choose a device viewport or custom resolution in Responsive Testing or LT Browser.
- For multiple breakpoints, capture or compare each viewport you need; one desktop setting does not establish mobile behavior.
- Record the selected dimensions with your results so a later run can use the same configuration.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| The resolution option is unavailable for a mobile device | The documented automated Screenshot resolution preference is described as desktop-only. | Switch to Responsive Testing or LT Browser for mobile viewports. |
| You cannot find the exact menu or preference name | The available guide does not confirm current interface labels. | Look in the test-session preferences in the live setup and consult current vendor help if the control has moved. |
| Your capture does not match a physical device pixel-for-pixel | Viewport dimensions, device pixel ratio, zoom, and physical display resolution may differ. | Verify how the selected workflow handles those settings; the reviewed sources do not define them. |
| You need to inspect a layout while interacting with the page | An automated screenshot run is aimed at capture rather than live responsive debugging. | Use LT Browser or Responsive Testing; vendor material describes interactive debugging capabilities there. |
| A size you need is not listed | The reviewed sources do not provide the supported numeric resolution inventory. | Check the current product interface or choose a custom viewport through the responsive workflow if available for your task. |
Performance, repeatability, and cost
The sources reviewed for this guide do not verify LambdaTest processing times, resolution-specific performance, pricing, plan limits, or capture reliability. Avoid estimating these from the resolution alone. For repeatable visual checks, keep the target URL, chosen viewport, and any other test settings consistent across runs. If your workflow requires comparing devices, use the responsive workflow described by the vendor rather than treating one desktop resolution as a proxy for every device.
Or skip the browser setup
If you need a screenshot file from a URL without setting up a browser session, ScreenshotNeo provides a one-request screenshot API and an MCP server for AI agents. Its clean-shot workflow accepts consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify the page verdict and billing status in headers.
For example, this cURL request saves a WebP screenshot of a URL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpEquivalent Python and Node.js requests are available, along with configuration details, in the ScreenshotNeo API documentation:
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}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);ScreenshotNeo also offers an MCP server for AI agents, including Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for 1,000 free screenshots a month with no card.
FAQ
Can I set a custom mobile resolution in LambdaTest Screenshot?
The automated Screenshot guide describes its resolution preference as desktop-only. For mobile layouts, use Responsive Testing or LT Browser custom device viewports.
Does a custom resolution mean the browser uses a matching device pixel ratio?
The reviewed sources do not specify device pixel ratio behavior. Check current product documentation if that distinction affects your result.
Where can I find the exact supported dimensions?
The sources used here do not list them. Check the current session preferences or responsive viewport controls in the product.
Sources
- TestMu AI: Automated Screenshot Testing features — documents the session-preference resolution setting and desktop-only scope.
- TestMu AI: Check mobile view of a website using LT Browser — describes device viewports and custom resolutions.
- TestMu AI: Responsive testing guide — describes custom viewports and comparisons.
