What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Capture each meaningful page state separately: navigate to the flow, perform one action, wait for a visible or URL-based signal that confirms the next state, then save a clearly named screenshot. Repeat for each step. A full-page capture shows the whole document at the current state; it does not move the flow forward.
Capture each flow state in sequence
The example below uses Playwright Test and TypeScript. Replace the routes, accessible names, and readiness checks with those in your application. It illustrates the documented APIs; it has not been run against a real checkout.
import { test, expect } from '@playwright/test';
test('captures the checkout flow states', async ({ page }) => {
await page.goto('/cart');
await expect(page.getByRole('heading', { name: 'Your cart' })).toBeVisible();
await page.screenshot({ path: 'artifacts/01-cart.png' });
await page.getByRole('button', { name: 'Continue to delivery' }).click();
await expect(page).toHaveURL(//delivery/);
await expect(page.getByRole('heading', { name: 'Delivery' })).toBeVisible();
await page.screenshot({ path: 'artifacts/02-delivery.png' });
await page.getByRole('button', { name: 'Continue to payment' }).click();
await expect(page).toHaveURL(//payment/);
await expect(page.getByRole('heading', { name: 'Payment' })).toBeVisible();
await page.screenshot({ path: 'artifacts/03-payment.png' });
});
Each screenshot records the state after its readiness assertion. Locator interactions wait for actionability, while Playwright Test assertions retry until they pass or time out. Prefer meaningful page signals over a fixed delay. See the Playwright locator guidance and Page API.
Choose what to capture
Visible viewport
page.screenshot({ path: 'step.png' }) captures the visible viewport by default. Use this when the relevant state fits on screen or when you want a consistent viewport-sized artifact.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
Full scrollable page
page.screenshot({ path: 'step-full.png', fullPage: true }) captures the full scrollable document at that moment in the flow. It does not activate later steps. For long pages with lazy-loaded images, ensure the content you need has loaded before capture; consult the current Playwright screenshot documentation for version-specific details.
One element
To save one component rather than the page, call the locator screenshot method, for example: await page.locator('header').screenshot({ path: 'header.png' }); Choose a selector that identifies the intended element in your application.
Save or reuse the image data
Providing path writes an image file. Without a path, page.screenshot() returns a buffer you can attach to a report or pass to another processing step.
Wait for the next state, not an arbitrary timer
Use a condition that demonstrates the new state is ready: a heading becomes visible, a confirmation message appears, or the URL changes. For URL transitions, an assertion such as await expect(page).toHaveURL(//delivery/) is often clear; page.waitForURL() is another option.
Rank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- Do not routinely use
page.waitForTimeout()to synchronize production tests. Playwright says timer-based waits are flaky and advises waiting for an event or condition instead. - Do not treat
networkidleas a general test-readiness signal; the Page API discourages it for tests. - Avoid
waitForNavigation()for navigation synchronization: it is documented as inherently racy. UsewaitForURL()when you need to wait for a URL change.
These recommendations and API details are documented in the Page API. Documentation can change; check the documentation matching the Playwright version installed in your project.
Use visual assertions for regression testing
If the goal is to detect visual changes rather than simply keep images, use Playwright Test’s toHaveScreenshot() assertion at each state, for example await expect(page).toHaveScreenshot('01-cart.png');. It requires the Playwright Test runner. The assertion captures repeatedly until two consecutive screenshots match, then compares the result with the reference image. On first execution, the runner creates the reference; review and version-control approved baselines rather than accepting updates automatically. Details are in Playwright’s visual comparison guide and the PageAssertions API.
Keep comparisons stable
Rendering can vary across operating systems, browser versions, settings, hardware, power source, and headless mode. Generate and compare baselines in a consistent environment. For changing regions, supported screenshot options such as masks or a custom stylesheet can help control dynamic content; use the options documented for your installed version.
Attach screenshots to named test steps
For diagnostic evidence in a Playwright Test report, take a buffer inside test.step and attach it with the step’s attachment API:
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
- Clear visuals. Fluid motion: A 144Hz refresh rate and 1ms MPRT deliver smooth, tear‑free motion across work, gaming, and streaming for clearer, more fluid viewing.
- Eye comfort: TÜV Rheinland 3‑star* certification reduces harmful blue light while preserving stunning color quality without compromise. *TÜV Rheinland 3-star eye comfort certification.
- Wide viewing angle: Get consistent views across a wide 178° /178° viewing angle.
- In-Plane Switching (IPS): See excellent color accuracy and consistency across wide viewing angles with In-plane Switching (IPS) technology.
- Ultra-thin bezels: Maximize your viewing experience with thin bezels.
await test.step('capture delivery state', async (step) => {
const screenshot = await page.screenshot();
await step.attach('screenshot', {
body: screenshot,
contentType: 'image/png',
});
});
Playwright Test copies the attachment to a reporter-accessible location. See the TestStepInfo API.
Or skip the browser setup
If you need a screenshot from a URL without writing a browser flow, ScreenshotNeo returns an image or PDF with one GET request. This is a URL capture, not an automated multi-step interaction: use Playwright when you need to progress through application states.
Install the Python dependency with python -m pip install requests, then run:
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)
See the ScreenshotNeo API documentation for setup and options. It removes cookie banners, consent prompts, newsletter popups, and chat widgets before capture; those steps can be turned off. Bot checks, blank pages, timeouts, and failed loads are not billed, and cache hits cost nothing. Its response identifies the page verdict and billing status in headers. ScreenshotNeo also provides an MCP server for AI agents, with screenshot, page-info, and PDF-capture tools. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000.
Sign up free for 1,000 screenshots a month—no card required.
Rank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
Troubleshoot missing or unreliable captures
The screenshot shows the previous step
The capture may be happening before the application has transitioned. After the click, wait for a distinctive heading, message, or expected URL before calling screenshot(). If the interface updates without changing the URL, assert on the new visible content.
The test times out waiting for a locator
Check that the locator matches the rendered accessible name or content, and that the preceding action actually leads to that state. Use a role-based locator when practical; it makes the intended control explicit. If the application has a genuine slow transition, adjust the relevant assertion timeout deliberately rather than inserting a fixed sleep.
The full-page image omits content
Full-page capture covers the scrollable document at the point of capture, but content that has not yet loaded may not appear. Wait for a relevant element or application signal before capturing, and verify the result in the same browser and version used by your test suite.
Recommended Free Tools
Visual tests fail despite no intended change
Check whether the comparison ran in a different operating system, browser version, rendering mode, or other environment. Identify dynamic content and consider supported masks or a custom stylesheet. Review any baseline update before committing it; do not use a new baseline merely to silence an unexplained difference.
Best Value
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
Navigation wait behaves inconsistently
Replace a racy navigation wait with an expected URL condition using waitForURL() or a URL assertion. If the flow is a single-page interface, wait for the content that proves the new state instead of expecting navigation.
Frequently Asked Questions
Does full-page capture take screenshots of every step automatically?
No. It captures the whole scrollable document for the current state only; the test must perform each action and capture each later state.
Can I use toHaveScreenshot outside Playwright Test?
No. The screenshot assertion is part of the Playwright Test runner; use page.screenshot() for standalone image capture.
Quick Recap
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.

