ScreenshotNeo
Sign in Get a free key

BlogGuides

LambdaTest Screenshot pricing: plans, limits, and screenshot costs

See LambdaTest (now TestMu AI) SmartUI screenshot pricing, free allowances, plan limits, and how to estimate visual comparison costs.

By the ScreenshotNeo team4 October 20268 min read

LambdaTest is now branded TestMu AI, and its screenshot comparison product is called SmartUI Visual Regression. The pricing page checked on October 3, 2026 lists a free SmartUI allowance of 2,000 screenshots for the account’s lifetime and a paid SmartUI tier displayed at $199 per month billed annually. That $199 is a plan price, not a universal per-screenshot rate: paid pricing depends on the screenshot-volume tier you select. Confirm the live offer and applicable account terms before buying.

If you mean screenshots captured through browser automation or a screenshot API rather than visual comparisons, those are different workflows. SmartUI pricing is the relevant starting point for comparing page images and detecting visual changes.

1. LambdaTest screenshot pricing at a glance

Option Published detail What to keep in mind
Free SmartUI 2,000 screenshots, valid for the lifetime of the account Includes one month of build history. This is a lifetime allowance, not a monthly refill.
SmartUI Visual Regression $199/month billed annually, as displayed on the pricing page checked October 3, 2026 Paid pricing uses screenshot-volume tiers. The displayed amount is not a per-screenshot rate.
Paid Automation plans 2,000 SmartUI screenshots included to start SmartUI is also described as a separate product; the inclusion does not mean Automation is required to buy SmartUI.

The paid SmartUI tier lists one year of build history, compared with one month on the free tier. These are vendor-published terms; check the official TestMu AI pricing page for the current offer and selected volume.

2. Does LambdaTest charge per screenshot?

The available pricing information does not state one universal marginal price for each screenshot. It says paid SmartUI pricing scales by selected screenshot volume and that cost scales with the visual comparisons generated. Dividing $199 by an allowance would therefore produce a misleading per-screenshot figure: the published plan price is not a stated unit price, and the selected volume affects the suitable tier.

Plan for the number of comparisons your workflow creates, then confirm the matching tier on the live pricing page or with sales. The official page also identifies Smart Ignore and baseline reuse as ways to keep comparison volume efficient; treat those as vendor-described capabilities, not as a guaranteed saving for every project.

3. Estimate your screenshot volume

Start with the work that produces a visual comparison. A page captured at multiple browser, device, or viewport combinations can create multiple screenshots in a build. Repeated builds also add comparisons. The vendor’s pricing FAQ specifically says more browser, device, and viewport combinations increase comparison volume.

  1. List the pages or components you compare in one build.
  2. Count the browser, device, and viewport combinations for each page.
  3. Multiply those combinations by the number of builds you expect in your billing period.
  4. Include any additional comparison workflows your team runs, and ask TestMu AI how its selected volume tier counts them.
  5. Compare your estimate with the current plan terms, history retention, and any account-specific fair-use limits.

This is a planning estimate, not a quoted billing formula. Ask the vendor to confirm exactly which events count toward the selected volume, especially if your workflow uploads externally captured images or uses multiple test configurations.

4. SmartUI, screenshot APIs, and automation screenshots are different

“Screenshot” can refer to several related but distinct things:

  • SmartUI visual regression: images used in visual comparisons and build history. The pricing figures above concern this product.
  • Screenshot API capture: a hosted workflow that creates screenshots for requested browser, operating system, device, resolution, or location combinations. The documented API workflow includes creating screenshot tests and retrieving screenshot details or a ZIP of results.
  • Images uploaded to SmartUI: the SmartUI API documentation describes uploading locally captured images and retrieving build or screenshot status and build screenshots.
  • Automation-run screenshots: screenshots associated with a broader browser automation workflow. Paid Automation plans include 2,000 SmartUI screenshots to start, according to the pricing FAQ.

The API references currently indexed for these workflows are older versions (1.0.1). Use them as evidence that the documented workflows exist, not as a guarantee of current API limits, supported configurations, or plan quotas. Check the current product documentation before implementing against an API.

5. Limits and history to check before you subscribe

  • Free allowance duration: the 2,000 free screenshots are valid for the lifetime of the account; the published page lists one month of build history.
  • Paid history: the displayed paid SmartUI tier lists one year of build history.
  • Paid volume: the selected screenshot-volume tier determines which paid option fits. Do not assume a particular paid allowance from the displayed $199 plan price.
  • Automation inclusion: every paid Automation plan starts with 2,000 SmartUI screenshots, per the pricing FAQ. Verify how the inclusion applies to your account and usage.
  • Fair use: the Acceptable Use Policy says product fair-use limits are communicated when a subscription starts. It discusses time-based and resource-based controls but does not set one universal screenshot-specific cap. Ask for the limits in your order or subscription terms if you expect high volume or an unusual configuration.

6. A practical buying checklist

  1. Confirm that you need visual regression comparisons, rather than only a one-off screenshot capture.
  2. Estimate comparisons per build using your pages and browser, device, and viewport matrix.
  3. Estimate how many builds you run in the billing period.
  4. Decide whether one month of free build history is enough or whether you need the one year listed for the paid SmartUI tier.
  5. Check whether your team already has a paid Automation plan that includes 2,000 starting SmartUI screenshots.
  6. Ask which volume tier matches your estimate, what counts as a screenshot or comparison, and what account-specific fair-use terms apply.
  7. Recheck the official price and plan details immediately before purchase; prices and packaging can change.

7. Troubleshooting pricing and quota questions

Problem Likely cause What to do
The estimate from $199 divided by screenshots looks too low or too high. The displayed price is a plan price, not a universal per-screenshot charge. Use your expected comparison volume to select a tier and request the applicable price. Do not derive a unit rate from the headline amount.
The free screenshots appear to run out sooner than expected. A build may compare many page and browser/device/viewport combinations; the free allowance is lifetime, not monthly. Review the number of comparisons your builds generate and confirm how the account dashboard counts them.
Your Automation subscription does not appear to cover all SmartUI usage. The published inclusion is 2,000 SmartUI screenshots to start, not an unlimited allowance. Check the current plan terms and ask how additional comparison volume is priced.
You cannot find a universal maximum screenshot cap. The AUP communicates fair-use limits through subscription terms instead of specifying one public screenshot cap. Review your order terms or ask the vendor to confirm the applicable time-based and resource-based limits.
An old API example does not match the current service. The indexed API references are older versions and may not reflect current support or limits. Use current official documentation and verify supported configurations before relying on the example.

8. Performance, reliability, and cost considerations

Budget around the comparison workload rather than a raw page count. Adding browser, device, or viewport variants raises the number of comparisons, while repeated builds multiply that work. If the team can reuse a baseline and use Smart Ignore appropriately, the vendor says these can help keep volume efficient; validate the effect against your own workflow.

Keep enough build history to investigate regressions. The published difference is one month for free and one year for the paid SmartUI Visual Regression tier. If your review or release process needs older build evidence, include retention in the plan decision.

For reliability, document which configurations are required for release checks and confirm your account’s actual limits. The AUP describes fair-use controls but does not publish a universal screenshot cap. For high-volume or unusual setups, get the applicable limits and volume treatment in writing before committing.

9. ScreenshotNeo as an alternative to try first

If your immediate need is to capture clean website screenshots through an API or MCP server rather than run a visual-regression comparison suite, ScreenshotNeo is an alternative to evaluate. It accepts a URL in one GET request and returns PNG, JPEG, WebP, or PDF. Its API and MCP server are for screenshot capture; they are not a claim of SmartUI-style visual comparison.

For a straightforward HTTP capture, see the ScreenshotNeo API documentation alongside this example:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
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}`);

ScreenshotNeo removes known cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, with response headers indicating the page verdict and billing status. It also provides an MCP server with screenshot, page-info, and PDF tools for AI agents. One thousand screenshots per month are free without a card; paid plans start at $5 for 3,000 screenshots. All listed features are on every plan. Consider it when you need screenshot capture and predictable billing for clean results; choose a visual-regression product when comparison and build history are the requirement. Sign up free for 1,000 screenshots a month, with no card required.

10. FAQ

Is LambdaTest still the product name?

The current pricing page calls the service TestMu AI (formerly LambdaTest). SmartUI is the name used for its visual-regression product.

Do the free 2,000 screenshots renew monthly?

No. The published allowance is valid for the lifetime of the account.

Does every paid Automation plan include SmartUI?

The pricing FAQ says each paid Automation plan includes 2,000 SmartUI screenshots to start. Check the live terms for your plan.

Can I calculate a definite cost per screenshot?

Not from the published headline price alone. The paid tier depends on selected screenshot volume, and the page does not state one universal per-screenshot rate.

Should I choose SmartUI or a screenshot API?

Choose based on the job: SmartUI is the documented visual-comparison product; a screenshot API is for requesting captures. Confirm current capabilities and plan terms for the exact workflow.

Sources

Keep reading

7 min read

LinkedIn Open to Work Image

Learn what LinkedIn’s Open to Work photo frame means, who can see it, how to add or remove it, and how to choose the right privacy setting.