How to Take a Full-Page Screenshot with LambdaTest Screenshot
Use LT Browser’s Screenshot Full Page option to capture and save an entire webpage, or choose an API or visual testing workflow for automation.
To take a full-page screenshot in LambdaTest’s LT Browser, open the webpage, choose Screenshot Full Page from the settings menu in the top-left corner, then click the Screenshot icon. When the capture finishes, click Save to keep it in LT Browser, or use the arrow button to download it to your computer. These steps follow the vendor’s LT Browser full-page screenshot guide.
A full-page capture includes content below the visible viewport, as if the entire scrollable page fit on one very tall screen. Use LT Browser for a manual capture in a selected device view; use an API or test integration when you need repeatable captures.
Take a full-page screenshot in LT Browser
- Install and open LT Browser. The official guide lists downloads for Windows, macOS, and Linux.
- Open the page you want to capture. Choose the device or desktop view you need. LT Browser’s guide describes full-page capture for its pre-installed mobile devices, desktops, and laptops.
- Open the settings menu. It is in the top-left corner. Select Screenshot Full Page.
- Start the capture. Click the Screenshot icon. LT Browser indicates that the capture is in progress and then displays a completion confirmation.
- Save or download the result. Click Save to retain it in LT Browser, or click the arrow button to download it locally.
If you are comparing layouts, repeat the capture in the other device views you care about. A full-page screenshot is useful for reviewing long pages, but it is still a static image: it does not show interaction states or prove that every below-the-fold element loaded correctly.
Choose the right workflow
| Workflow | Best for | What it does |
|---|---|---|
| LT Browser manual capture | A one-off screenshot and local saving | Use the settings menu’s Screenshot Full Page option, then save or download. |
| Automated Screenshot API | Programmatic sessions across selected browser and operating system configurations | The vendor documents starting cloud screenshot sessions for a URL and retrieving screenshot details using a test ID. Authentication credentials are required. See the Automated Screenshot API documentation for current compatibility and account details. |
| SmartUI with Selenium | Captures integrated into visual regression tests | The SmartUI Selenium Java guide describes project setup, SDK configuration, a snapshot call in a test, and running it through the SmartUI CLI. Its sample includes an optional wait timeout for lazy-loaded or asynchronous content. |
The API and SmartUI workflows are distinct from the manual LT Browser steps. The vendor’s API examples include older browser and operating system versions, so check current account and API compatibility information instead of treating those examples as a current support matrix. Current pricing, limits, and plan eligibility are not established by the cited guides.
When the screenshot misses content
Some pages load images or components only after scrolling, waiting, or running client-side code. If a full-page image omits content that appears in the live page, first check whether that content had finished loading before capture. For automated Selenium visual tests, the SmartUI guide describes an optional wait setting for lazy-loaded or asynchronous elements. Confirm the current LT Browser controls separately; the reviewed guide does not document an equivalent manual wait setting.
Also check that the selected viewport is the one you intended. A page can use different layouts at mobile and desktop widths, so a full-page capture in one view does not establish how the same page looks in another.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. One GET request can return a screenshot or PDF. Its capture can accept cookie and consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before the shot. Each of those steps can be turned off. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing; response headers report the page verdict and whether the shot was billed. An MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf.
For a full-page capture, use the full_page option described in the ScreenshotNeo API documentation. Replace the example URL with the page you want to capture and use your API key:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -d full_page=true -o shot.webpThe API also accepts the parameter names used by other screenshot APIs to make switching easier. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000, and every feature is available on every plan. Sign up for 1,000 free screenshots a month, with no card required.
Troubleshooting
| Problem | Likely cause | What to do |
|---|---|---|
| Screenshot Full Page is missing | You may be in a different app, menu, or capture mode than the LT Browser workflow in the official guide. | In LT Browser, open the top-left settings menu and look for Screenshot Full Page. Check the current LT Browser guide if the interface has changed. |
| The result stops at the viewport | A regular visible-area screenshot may have been selected instead of the full-page option. | Repeat the capture after selecting Screenshot Full Page. |
| Below-the-fold images or widgets are absent | They may load lazily or asynchronously and were not ready when the page was captured. | Wait for the page to finish loading and try again. For an automated SmartUI test, consult its optional wait timeout configuration. |
| The screenshot is in LT Browser but not on disk | Save retains the capture in LT Browser; it is not the local download action. | Use the arrow button on the results page to download the image. |
| Automated API results differ from the manual capture | The API session may use a different browser or operating system configuration. | Check the current API compatibility information and compare the selected configuration with the LT Browser view. |
Performance, reliability, and cost considerations
- Capture time: Long pages and pages that load content asynchronously can take longer to capture. Let the page settle before a manual capture; automated visual tests may need an appropriate wait configuration.
- Repeatability: A manual capture is straightforward for a single review. For recurring checks, an API or test integration makes capture part of a repeatable workflow, but requires setup and, for the documented API, credentials.
- Cross-device comparison: Capture each device view you need. A screenshot from one viewport cannot stand in for other responsive layouts.
- Cost and availability: The cited LT Browser and automation guides do not establish current pricing, capture limits, or plan eligibility. Check the vendor’s current product and account information before building a workflow around those assumptions.
FAQ
Does a full-page screenshot include content below the fold?
Yes. It captures the scrollable page beyond the initially visible viewport, subject to the page content having loaded.
Can I compare a full page across devices?
Capture the page separately in the device views you want to compare. LT Browser’s guide describes full-page capture across its pre-installed mobile, desktop, and laptop views.
Do I need the Automated Screenshot API for one screenshot?
No. The manual LT Browser workflow is the documented option for a one-off capture. The API is for programmatic sessions and requires authentication credentials.
Is SmartUI the same as LT Browser’s manual screenshot feature?
No. SmartUI with Selenium is an automation and visual testing workflow; LT Browser’s menu-based capture is manual.
