Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

To capture a page behind a login with LambdaTest, save a login profile containing the sign-in page URL, form locators, and authorized credentials. Then enable that profile and enter the separate URL of the page you want to capture. The login URL tells the browser where to sign in; the screenshot URL tells it what to capture after sign-in.

Set up a saved login profile

  1. Sign in to your TestMu AI/LambdaTest account and open Visual UI Testing > Screenshot Testing.

  2. Create a new login profile and enter the website’s login-page URL. Do not put the post-login destination here.

    Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  3. Inspect the live login form with your browser’s developer tools. Identify the username or email field, password field, and submit control.

    #1 Best Overall
  4. For each control, choose a locator that uniquely matches the intended element. The support guide lists ID, Name, TagName, CSS Selector, XPath, Class Name, Link Text, and Partial Link Text. If a class matches more than one element, use a more specific locator, such as an XPath that identifies the correct submit button.

  5. Enter credentials authorized for the test, give the profile a recognizable name, and save it. The profile is retained in your account for later runs.

The documented flow loads the login URL, locates and fills the username and password fields, activates the submit control, waits for the next page to render, and then navigates the screenshot driver to the target URL. Incorrect or ambiguous locators can prevent the login step from succeeding. See the TestMu AI instructions for taking screenshots of pages behind login.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Run a screenshot against the authenticated page

  1. Return to Screenshot Testing and enable the saved login profile.

  2. Enter the distinct URL of the page you want to capture. This is the post-login target, not the login-page URL saved in the profile.

  3. Start one test session first. Confirm that sign-in succeeds and the destination page renders as expected.

  4. After verification, run the browser and device configurations you need. The vendor describes bulk, full-page captures; its support page states that a test session can include up to 25 screenshots. Check the current product documentation for the limit applicable to your account and configuration.

    Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Authentication cases to check before relying on a capture

The documented profile workflow covers filling standard username and password fields and activating a submit control. It does not establish that every authentication flow is supported. In particular, the cited instructions do not provide universal steps for MFA, CAPTCHA, SSO, expiring sessions, or client-side navigation that does not follow the documented sequence. Verify your specific flow against the current support instructions or with TestMu AI support before scaling up.

For a locally hosted site, the TestMu AI blog describes using its testing tunnel to provide access. Tunnel setup screens and connection steps can change, so follow the current vendor documentation for the tunnel rather than assuming a fixed UI sequence: TestMu AI’s overview of automated screenshot-testing features.

Troubleshoot failed or incorrect captures

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Or skip the browser setup

ScreenshotNeo takes a screenshot or PDF with one GET request. It is a separate option from LambdaTest: the API can capture a URL, while its pre-capture steps accept consent banners and remove known overlays that may obscure a shot. The API also marks bot checks, blank pages, timeouts, failed loads, and cache hits as non-billable in response headers. An MCP server provides screenshot tools for AI agents, including Claude, Cursor, and other MCP clients.

cURL example, saving a WebP capture of the authenticated destination URL where that URL is publicly reachable or otherwise accessible to the service:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/account -o shot.webp

See the ScreenshotNeo API documentation for authentication and capture options. A server-side API request does not inherit a browser login profile; use the service’s supported authentication parameters where applicable, and do not assume it can reproduce an interactive login flow.

ScreenshotNeo offers 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.

Frequently Asked Questions

Does the login profile URL point to the page I want to screenshot?

No. It points to the sign-in page; enter the post-login destination separately in the screenshot test.

Can I capture a page that requires MFA or CAPTCHA?

The cited vendor instructions do not establish universal support for MFA or CAPTCHA. Check your specific flow with current TestMu AI documentation or support.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.