Why Is My LambdaTest Screenshot Blank or Incomplete?
A blank or incomplete screenshot has several possible explanations. Identify the capture workflow, check its run and artifact, then isolate timing, scope, and retrieval issues.
There is no single verified cause for a blank or incomplete LambdaTest screenshot in the public documentation reviewed for this guide. Start by identifying how the image was produced: a screenshot test, a Selenium automation session, or a report/export. Then check whether that run completed and whether its screenshot artifact exists in the corresponding workflow. LambdaTest documents separate retrieval paths for screenshot-test results and step-by-step session screenshots, but those API references do not identify a particular blank-image cause or guarantee that every run yields a valid image. LambdaTest screenshot API documentation · session screenshot API documentation
1. Identify which screenshot workflow produced the image
Before changing browser settings, establish where the screenshot came from. The likely diagnostic path depends on whether you ran a screenshot test, captured steps from an automated browser session, or downloaded an image embedded in a third-party report.
| Workflow | What to check first | Documented evidence |
|---|---|---|
| Screenshot test | Find the test ID, inspect its details, and verify whether screenshot results are available. | The screenshot API lists operations to start a test, retrieve specified screenshot details, and fetch a ZIP of screenshots. |
| Selenium automation session | Find the session ID and retrieve the step-by-step screenshot artifact for that session. | The automation API documents a session screenshots endpoint that returns a URL for screenshots in ZIP format. |
| Report or export from another tool | Check that tool’s capture settings, report options, and exported artifact. | Settings vary by product. For example, Testsigma documents screenshot capture options in its own reporting workflow; those options do not describe LambdaTest. |
Keep the test or session ID with the original image. If you cannot determine which workflow created it, inspect the test runner, CI job, browser automation code, and report generator that produced the file.
2. Check whether the run and screenshot artifact exist
An image that appears blank in a report may be missing, inaccessible, or different from the artifact you intended to inspect. Check the result through the same workflow that created it before assuming the page itself was captured as white.
- Record the screenshot test ID or browser session ID.
- Open the matching run in the LambdaTest interface and check whether it completed.
- Retrieve screenshot details or step screenshots using the corresponding documented API.
- Confirm that the returned screenshot URL or ZIP can be fetched and that the downloaded file opens as an image.
- Compare the downloaded original with the version displayed in your report or CI output.
For a screenshot test, the documented API exposes GET /{test_id} for test details and GET /{test_id}/zip for zipped screenshots. Its API documentation also lists POST / to start a screenshot test. The exact host, authentication, request fields, and current product labels should be checked in the documentation for your account and workflow; the API reference surfaced for this research is older. See the screenshot API reference.
For a Selenium session, the documented endpoint is GET /automation/api/v1/sessions/{session_id}/screenshots. It uses Basic authentication and returns a URL to the step screenshots ZIP. See the endpoint reference and response schema.
Retrieve step screenshots with cURL
curl --request GET \
--url "https://api.lambdatest.com/automation/api/v1/sessions/SESSION_ID/screenshots" \
--user "USERNAME:ACCESS_KEY"Replace SESSION_ID, USERNAME, and ACCESS_KEY with the values for your session. cURL’s --user option sends Basic authentication. The API response contains a URL; retrieve the ZIP from that URL separately, then inspect the image files inside it. Do not paste credentials into a shared log or commit them to source control.
3. Classify what “blank or incomplete” means
Describe the observed failure precisely. The categories below are a debugging framework, not LambdaTest-confirmed root causes.
| Appearance | What it can tell you | Next check |
|---|---|---|
| No image or missing artifact | The capture may not have produced an artifact, or the artifact may not have been retrieved or displayed. | Run completion, capture settings, API response, download status, report/export configuration. |
| Image exists but is entirely blank | The file may be a valid image whose captured content is blank, or a display pipeline may be showing it incorrectly. | Open the original file; compare with the live session and page state at capture time. |
| Only part of the page appears | The image may reflect a viewport capture, a specific step, or the configured capture scope. | Check the actual workflow’s viewport/full-page support and the selected capture mode. |
| Some content is missing | The page may have changed after capture, or that content may not have appeared in the captured state. | Compare the live session, page readiness, browser/device, and the image from the same run. |
| Image is cropped, scaled, or distorted in a report | The underlying artifact may differ from the report’s preview or export. | Inspect the original dimensions and compare the raw download with the report output. |
4. Reproduce with controlled changes
The public sources reviewed do not confirm timing, viewport, device, or page rendering as LambdaTest-specific causes. Treat these as variables to investigate, changing one at a time so the result remains interpretable.
- Save the baseline. Keep the original file, run ID, session ID, URL, timestamp, browser and OS, viewport or device, and capture method.
- Check what the browser showed. If you have a session recording or can repeat the run, compare the page at the capture step with the screenshot artifact.
- Check readiness. If the page has asynchronous content, wait for a meaningful page condition in your own test before triggering capture. Record the condition used. This is an investigation, not a documented LambdaTest fix.
- Check scope. Determine whether your specific capture mode produces a viewport, a full page, or a screenshot for an individual step. Do not assume one workflow has the same scope as another.
- Repeat the same run. Keep the URL and configuration fixed to see whether the symptom is reproducible.
- Change one variable. Try a different wait condition, capture scope, or browser/device configuration separately. Save each resulting artifact and note the change.
A LambdaTest-hosted legacy Selenium RC example distinguishes an operating-system viewport capture from an entire-page capture and mentions a black-background issue in a particular layout context. It is old, context-specific evidence, so do not treat it as a diagnosis or current behavior for other LambdaTest screenshot products. See the legacy example.
5. Check capture and export settings
Confirm that the relevant workflow is configured to capture screenshots and that the report includes them. Products can have settings that capture on every step, only on failure, or not at all. Testsigma documents such controls for its product; that is a reminder to inspect the configuration in use, not evidence that LambdaTest uses the same options. Testsigma execution documentation.
- Was screenshot capture enabled for this test or report?
- Does the report show the screenshot from the failing step, the final step, or a different artifact?
- Did an export option omit screenshots or use a reduced preview?
- Are you examining the original image file or a thumbnail rendered by another system?
6. Common troubleshooting outcomes
| Symptom | Possible explanation to investigate | Action |
|---|---|---|
| Screenshot API returns no usable artifact | The run may not have completed, the ID may belong to another workflow, or no screenshot may be available. | Verify the ID and run status; use the matching screenshot-test or session endpoint. |
| Session screenshot request returns 401 | Authentication may be missing or invalid. | Use the account’s correct username and access key with Basic authentication; keep credentials private. |
| Session screenshot request returns 404 | The session ID may be incorrect or the resource may not be available at that path. | Confirm the session ID and endpoint against current documentation and the session record. |
| ZIP URL is returned but download fails | The retrieval step may be failing after the API response. | Capture the HTTP status and response from the URL, and retry retrieval while preserving the original API response. |
| Image is valid but white or empty | The captured browser state may have been blank, or the viewer may not be showing the intended file. | Open the original file and compare it with the same run’s browser state or recording. |
| Page looks cut off | The selected workflow or configuration may capture only a viewport or step. | Check the supported scope in that workflow and compare against the live page. |
| Dynamic content is absent | The content may not have appeared before capture. | Reproduce with a specific readiness condition and compare the artifact; treat this as a hypothesis to verify. |
| Failure appears only in a report | The report preview, export, or screenshot-selection setting may differ from the raw artifact. | Download and inspect the original image; review the report tool’s own settings. |
7. A useful support report
If the issue persists, send support a compact reproduction record. This is practical debugging advice, not a stated LambdaTest support requirement.
- Test ID or session ID and the time of the run, including timezone.
- URL, if it can be shared, plus browser, operating system, device, and viewport.
- Capture workflow and scope, relevant settings, and the exact step where the image is taken.
- Original downloaded image and the API response or artifact link, with credentials removed.
- What you expected, what the image actually shows, and the smallest steps that reproduce it.
8. Reliability, performance, and cost considerations
This evidence does not establish LambdaTest pricing, capture latency, or reliability figures, so none are inferred here. For repeatable debugging, preserve run identifiers and original artifacts, avoid comparing screenshots from different browser/device configurations as if they were identical, and change one variable per reproduction. For large test suites, check the product and account’s current limits and pricing documentation rather than estimating from a single run.
9. Or skip the browser setup
If you need a clean image of a public web page rather than a cross-browser test session, ScreenshotNeo offers a one-request screenshot API. ScreenshotNeo is a website screenshot API and MCP server from ScreenshotNeo. Its API and options are documented at ScreenshotNeo docs.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
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)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));Before capture, ScreenshotNeo accepts the cookie or consent banner 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, failed loads, timeouts, and cache hits are not billed, and responses indicate the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots each month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up free for 1,000 screenshots a month, with no card required.
10. FAQ
Does a blank screenshot prove LambdaTest was down?
No. The reviewed API documentation does not establish that a blank artifact indicates an outage or any single cause.
Are a screenshot-test result and a Selenium session screenshot the same artifact?
They are documented through distinct API workflows. Use the test ID or session ID that corresponds to the capture you need.
Can I conclude that the page loaded too slowly?
No. Page readiness is a reasonable variable to test, but the sources reviewed do not confirm it as a LambdaTest-specific root cause.
Should I send credentials with a screenshot artifact?
No. Share the relevant IDs and redacted API response, and remove usernames, access keys, cookies, and authorization headers from logs or attachments.
Evidence note: LambdaTest’s public documentation surfaced screenshot-test result and ZIP retrieval endpoints, plus a separate Selenium session screenshot endpoint. These sources do not document a confirmed cause or universal fix for blank or incomplete screenshots. Diagnose from the artifact and the specific workflow.
