Recommended Free Tools
To get a reliable Playwright screenshot, wait for the specific content you need to capture—not just for the browser to report that navigation has started or finished. Navigate with an appropriate waitUntil value, wait for a meaningful locator or assertion to confirm the page is ready, and then take the screenshot.
Use a page-specific readiness check
A browser load event and application readiness are different things. A page can fire load before its API data has arrived, its client-side framework has hydrated, or a transition has displayed the final content. Conversely, Playwright already auto-waits for actionability before most actions, so adding a generic load-state wait before every screenshot is usually unnecessary. The Page API says: “Most of the time, this method is not needed because Playwright auto-waits before every action.”
For a page whose report heading indicates that the relevant view has rendered, a Playwright Test example is:
import { test, expect } from '@playwright/test';
test('captures the report after it is ready', async ({ page }) => {
await page.goto('https://example.com/report', {
waitUntil: 'domcontentloaded',
});
await expect(
page.getByRole('heading', { name: 'Report' })
).toBeVisible();
await page.screenshot({ path: 'report.png', fullPage: true });
});Replace the example URL and heading with a stable signal that represents the content you actually need. If a heading appears before the data is complete, wait for a table row, completed status, or another user-visible indicator instead. The screenshot call should come after that readiness check.
#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
Pick the navigation checkpoint that fits
domcontentloadedwaits for the document to be parsed. It is a useful early checkpoint when the page structure is sufficient to begin checking an application-specific condition.loadwaits for the browser’s load event. Choose it when the capture depends on subresources such as images having loaded, but still verify any client-rendered data separately.commitmeans the response was received and document loading started. It does not mean the page is rendered or ready to capture.networkidlewaits until there are no network connections for at least 500 ms. Playwright’s current Page API labels this state “DISCOURAGED” for testing and recommends web assertions instead.
These navigation options describe browser events or network activity; none inherently proves that the exact business content in a screenshot is ready.
Wait for dynamic content, not an arbitrary delay
For API-driven pages, dashboards, and single-page applications, use a locator that becomes meaningful when the target content is ready. In Playwright Test, web-first assertions retry until their condition passes or times out:
await page.goto('https://example.com/report', {
waitUntil: 'domcontentloaded',
});
const completedRow = page.getByRole('row', { name: /Quarterly revenue.*Complete/i });
await expect(completedRow).toBeVisible();
await page.screenshot({ path: 'revenue.png', fullPage: true });Choose a locator narrowly enough that it cannot match a skeleton, placeholder, or stale version of the content. A visible page title may only prove that the shell is present; a completed status or populated result row may better express the real precondition.
Use locator.waitFor when you need a locator state
locator.waitFor() defaults to waiting for the locator to be visible. It also accepts attached, detached, and hidden. For example, you can wait for a loading indicator to disappear:
const spinner = page.getByRole('status', { name: 'Loading report' });
await spinner.waitFor({ state: 'hidden' });
await page.screenshot({ path: 'report.png', fullPage: true });Only use this as a readiness gate if disappearance of that indicator really means the content is complete. If possible, assert the expected result is visible too; a missing spinner alone could mean it was never rendered or that the page failed.
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
Avoid fixed sleeps as the main readiness strategy
A hard-coded pause such as await page.waitForTimeout(3000) does not identify what the page is waiting for. It may waste time when the page is fast and still take a screenshot too early when the page is slow. Prefer an assertion tied to the target state. A fixed delay is appropriate only when elapsed time itself is part of the behavior being tested, not as a substitute for knowing that content is ready.
Should you wait for networkidle before a screenshot?
Usually, no—not as a general test for readiness. Playwright defines networkidle as no network connections for at least 500 ms, and its Page API explicitly discourages using it for testing in favor of web assertions. Network quiet does not establish that a particular result is correct or visible.
Pages with polling, analytics, long-lived connections, or other background requests may not become idle when expected. Even if they do, an idle network does not prove that the interface finished processing its last response. A locator assertion is scoped to the content you care about and communicates why the screenshot is allowed to proceed.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsUse a network-idle checkpoint only if it serves a deliberate purpose in your workflow and behaves appropriately for that site; do not treat it as a universal replacement for a page-specific condition.
Wait after an action that triggers navigation
When a click or other action starts navigation, Playwright normally waits for the action’s navigation and actionability conditions. If you also need a separate load-state checkpoint, call page.waitForLoadState() after the navigation has been committed:
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 page.getByRole('link', { name: 'Open report' }).click();
await page.waitForLoadState('load');
await expect(page.getByRole('heading', { name: 'Report' })).toBeVisible();
await page.screenshot({ path: 'report.png', fullPage: true });waitForLoadState() resolves immediately if the requested state has already been reached. As with an initial goto, the load state does not establish that application-rendered data is ready; keep the assertion that verifies the target content.
Capture one element instead of the whole page
If you need a component screenshot rather than a viewport or full-page image, use locator.screenshot(). It performs actionability checks and scrolls the target into view before capture:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →const chart = page.getByRole('img', { name: 'Monthly revenue chart' });
await expect(chart).toBeVisible();
await chart.screenshot({ path: 'revenue-chart.png' });The locator screenshot throws if the matched element is detached from the DOM. If the application replaces components during rendering, wait for the stable final locator state and avoid retaining a locator to an obsolete element before capture.
Choose a wait strategy
| Strategy | What it establishes | Reliability for dynamic content | Best fit |
|---|---|---|---|
waitUntil: 'commit' |
The response arrived and document loading began. | Does not establish visible readiness. | Cases where the earliest navigation checkpoint is useful and another readiness condition follows. |
waitUntil: 'domcontentloaded' |
The document structure is parsed. | Does not prove hydration or API data is complete. | Start checking the app’s target state without waiting for every resource. |
waitUntil: 'load' or waitForLoadState('load') |
The browser load event has fired. | Does not prove client-rendered content is ready. | Pages where browser-loaded subresources matter, followed by any needed content assertion. |
waitUntil: 'networkidle' |
No network connections for at least 500 ms. | Can be unreliable with background requests and is discouraged for tests by Playwright. | Not a default screenshot gate; prefer an assertion tied to the captured content. |
expect(locator).toBeVisible() |
The specified user-facing element is visible; the web-first assertion retries until success or timeout. | Strong when the locator represents the final content rather than a placeholder. | Dynamic pages where a heading, result, row, or status signals readiness. |
locator.waitFor() |
The locator reaches the requested state; default is visible. |
Depends on whether the chosen state means the work is truly complete. | Waiting for a specific locator to become visible, attached, detached, or hidden. |
Troubleshoot blank or incomplete screenshots
The screenshot contains the page shell but not its data
Cause: The browser navigation event fired before an API request, hydration, or client-side transition completed.
Fix: Wait for a stable locator representing the final data, such as a populated row or completed status, and then capture. Do not rely on load alone.
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
The wait times out even though the page appears usable
Cause: The assertion may target text or a selector that differs from the rendered interface, or it may wait for a state the application never reaches. A broad selector can also match the wrong element.
Fix: Inspect the locator’s role, accessible name, and expected state. Choose a stable user-facing element and ensure the asserted condition matches what the page actually displays. A specific assertion gives a more useful diagnostic than an unexplained sleep.
The network-idle wait hangs or is inconsistent
Cause: Polling or other persistent background activity can keep the page from reaching network quiet; conversely, quiet can occur before the interface is truly ready.
Fix: Replace it with a web-first assertion for the content to capture. Use network idle only when the page’s traffic pattern and the purpose of the wait make it appropriate.
The element screenshot fails because the element detached
Cause: The application replaced or removed the matched node while the screenshot was being prepared.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteBest 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.
Fix: Wait for the final, stable version of the element, then take the locator screenshot. If the page continually replaces the target, identify a more stable readiness condition before capture.
Images are missing from a full-page capture
Cause: The screenshot was taken before relevant image subresources loaded, or images load lazily only when brought into view.
Fix: Consider waitUntil: 'load' when loaded subresources matter, and verify the actual image or content state you depend on. For lazy content, ensure the relevant area has been brought into view or otherwise loaded before capture; a document load event alone may not mean below-the-fold lazy images have loaded.
Or skip the browser setup
If your goal is simply to obtain a screenshot from a URL, ScreenshotNeo offers a one-request screenshot API. For example, this cURL call saves a WebP image:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/report -o shot.webpSee the ScreenshotNeo documentation for API parameters. ScreenshotNeo accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up free for ScreenshotNeo to try 1,000 screenshots a month with no card.
FAQ
Does Playwright automatically wait before a screenshot?
Playwright auto-waits before most actions, but that does not guarantee that application data is ready. Add an explicit assertion when your screenshot depends on a specific rendered state.
What is the difference between a viewport and full-page screenshot?
page.screenshot() can capture a viewport or, with fullPage: true, the full page. locator.screenshot() is for the matched element.
Which wait is best for a page that uses API data?
Wait for a locator or web-first assertion that represents the final API-driven content rather than selecting a browser load event as a proxy.
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.
