Free tools Windows power users keep installed
One-click scans. No signup required.
A website screenshot is usually cropped because the capture is limited to the visible browser viewport, an explicit clip rectangle, or a selected element. Decide which area you need, then change that capture mode: use fullPage: true for the entire scrollable document, capture a locator for one component, or correct the clip coordinates. Check the page state before capture, because a full-page flag does not guarantee that dynamic or lazy content has finished rendering.
Identify what is being cropped
Before changing code, define the intended deliverable. These are different operations, not interchangeable names for the same screenshot:
| Goal | Capture area | Typical control |
|---|---|---|
| What a visitor currently sees | Visible browser viewport | Default page screenshot |
| Every scrollable section | Full document from top to bottom | fullPage: true |
| One card, chart, or header | A specific DOM element | Element or locator screenshot |
| A precise region | An explicit rectangle | clip with x, y, width, and height |
If the output ends at the bottom of the browser window, you probably captured the viewport. If content is cut on one or more sides, inspect a clip rectangle or element bounds. If the complete page is present but the file has unexpected pixel dimensions, inspect the scale setting rather than assuming content was omitted.
Capture a full page with Playwright
Playwright’s normal page screenshot captures the current viewport. Full-page capture is explicit and covers the full scrollable page, as if the page were displayed on a very tall screen. In JavaScript:
#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
import { chromium } from 'playwright';
const browser = await chromium.launch();
const page = await browser.newPage({ viewport: { width: 1440, height: 900 } });
await page.goto('https://example.com', { waitUntil: 'networkidle' });
await page.screenshot({ path: 'full-page.png', fullPage: true });
await browser.close();Run it with a current Node.js installation and Playwright installed in your project (for example, install the playwright package and its browser binaries). Replace the URL and choose a viewport that matches the layout you need to document. waitUntil: 'networkidle' is a useful starting point, but it is not proof that every application has finished rendering.
Python equivalent
from playwright.sync_api import sync_playwright
with sync_playwright() as p:
browser = p.chromium.launch()
page = browser.new_page(viewport={"width": 1440, "height": 900})
page.goto("https://example.com", wait_until="networkidle")
page.screenshot(path="full-page.png", full_page=True)
browser.close()For a page that renders content after an API call, wait for a reliable selector instead of relying only on a timeout:
await page.goto('https://example.com');
await page.locator('[data-loaded="true"]').wait_for();
await page.screenshot({ path: 'full-page.png', fullPage: true });Use a selector that represents the actual ready state in your application. A fixed delay can be appropriate for a known animation, but it can also be too short on a slow run or unnecessarily slow on a fast one.
Capture one element instead of approximating it
If the requirement is a single component, capture that component directly. Element screenshots avoid guessing page coordinates and remain aligned when the layout changes.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsRank #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
const card = page.locator('.pricing-card').first();
await card.screenshot({ path: 'pricing-card.png' });In Python, the same operation is:
page.locator('.pricing-card').first.screenshot(path="pricing-card.png")Make sure the element is attached and visible. If it is inside a collapsed tab, modal, carousel, or lazy-rendered section, open the relevant UI and wait for the element’s final state before capturing it. An element screenshot is intentionally not a full-page screenshot; selecting the wrong locator can look like cropping when it is actually the requested boundary.
Correct an accidental clip rectangle
A clip rectangle defines the capture’s top-left origin and dimensions. x and y set the origin; width and height set the size. A rectangle that is too small will cut content even when the page itself is fully rendered.
await page.screenshot({
path: 'region.png',
clip: { x: 0, y: 0, width: 1200, height: 800 }
});To diagnose a clipped edge, temporarily remove clip and take a viewport or full-page screenshot. If the edge is no longer cut, calculate the rectangle from the intended element’s bounding box rather than hard-coding values:
const box = await page.locator('#report').boundingBox();
if (!box) throw new Error('Report is not visible');
await page.screenshot({ path: 'report.png', clip: box });Check that the rectangle is in the coordinate space expected by your Playwright version and that its width and height are positive. A clip is a boundary, not a scrolling instruction; it cannot reveal content outside the page area you specified.
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 →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.
Understand scale and pixel dimensions
Scale changes output resolution, not the amount of document content captured. Playwright documents CSS-pixel output as one output pixel per CSS pixel and device-pixel output as one output pixel per device pixel. Device-pixel output can therefore be larger on a high-DPI display.
await page.screenshot({
path: 'device-resolution.png',
fullPage: true,
scale: 'device'
});Use CSS scale when predictable file dimensions matter across machines. Use device scale when you need pixels matching the emulated device density. If text looks soft, compare scale and image metadata; do not “fix” a resolution mismatch by widening an arbitrary clip, because that can add empty space or still omit content.
Dynamic, lazy, and overflowing content
Full-page mode asks the browser for the scrollable document at capture time. It does not establish that a framework has completed every asynchronous render, that an intersection observer has loaded every image, or that an infinite feed has a finite end.
- Wait for a page-specific ready selector after navigation.
- Scroll or otherwise trigger lazy sections when your application requires it, then wait for the images or data to settle.
- Hide or close sticky banners that cover content if they are not part of the deliverable.
- Inspect the captured image against the rendered page at the same viewport width.
- For infinite scroll, define a stopping condition; “full page” cannot capture content that does not yet exist in the document.
There is no universal lazy-loading or browser-limit fix. Verify the behavior of the specific page, browser, and capture tool you operate.
Recommended Free Tools
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
A reliable diagnosis and repair sequence
- Classify the target. Choose viewport, full document, element, or region.
- Remove accidental boundaries. Temporarily remove
clipand element targeting to establish a baseline. - Enable the intended mode. Set
fullPage: truefor the scrollable document, or use a locator for a component. - Wait for actual readiness. Prefer a ready selector or completed network/data state over an arbitrary sleep.
- Check scale. Compare CSS-pixel and device-pixel output when only dimensions or sharpness are wrong.
- Compare at the same viewport. Responsive breakpoints can move or hide content when the screenshot width differs from your browser window.
- Re-run after layout changes. A fixed clip or stale element box can become invalid after fonts, images, or client-side content load.
Common symptoms, causes, and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Image stops at viewport bottom | Default viewport screenshot | Set fullPage: true. |
| Left, right, top, or bottom edge cuts into content | Clip rectangle too small or offset | Remove clip, then recalculate x, y, width, and height. |
| Only a card appears | Element screenshot or locator targeting | Use page-level full-page capture, or intentionally keep the element mode. |
| Everything is present but dimensions are surprising | CSS/device scale or viewport mismatch | Set the desired scale and viewport explicitly. |
| Lower sections are blank or missing | Content had not rendered or lazy-loaded | Wait for a ready selector, trigger loading, and verify the page state. |
| Sticky UI covers the page | Banner, chat widget, or overlay remains visible | Close it in the test flow or hide it with page-specific CSS before capture. |
Performance, reliability, and file-size considerations
A full document can be far taller than the viewport, so it generally takes longer to render and produces a larger image than a viewport shot. Large pages also expose more lazy-loading and memory behavior. Keep the viewport width fixed for reproducible responsive layouts, wait for the smallest reliable readiness signal, and use element captures when a component is all you need. Choose an output format and scale that fit your storage and downstream pipeline; higher pixel density increases dimensions and file size without adding document content.
For regression testing, retain the URL, viewport, scale, readiness condition, and capture mode with each artifact. That metadata makes a future “crop” failure distinguishable from a legitimate responsive-layout change.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
ScreenshotNeo provides a single HTTP request for PNG, JPEG, WebP, or PDF captures. It removes cookie/consent banners, newsletter popups, and chat widgets before the shot; bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers. Its MCP server lets Claude, Cursor, or another MCP client use take_screenshot, get_page_info, and capture_pdf.
See the full parameter list and setup in the ScreenshotNeo documentation. The following calls capture the target URL; add the service’s options for full-page behavior, viewport, selector, waiting, scale, or PDF settings as required by your job.
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://stripe.com -o shot.webpimport 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}`);Every plan includes the features: Free provides 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account to try the browser-free workflow.
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.
FAQ
Does full-page capture include content below an infinite scroll?
Only content that exists and has rendered when the capture runs. Infinite feeds need an application-specific stopping rule and loading sequence.
Should I use a clip or an element screenshot for a component?
Use an element screenshot when the component has a stable locator. Use a clip when you deliberately need coordinates that may include surrounding space.
Why is a high-DPI screenshot larger but not longer?
Device-pixel scale increases pixels per CSS unit. It changes resolution and file dimensions, not the document’s scrollable length.
Frequently Asked Questions
Can I make a full-page screenshot of a page that requires authentication?
Yes, when your browser context has the required session cookies or authentication headers; capture only pages you are authorized to access.
Why does the screenshot differ between my laptop and CI?
Viewport width, device scale, fonts, browser version, and timing can differ. Set these explicitly and wait for a deterministic ready state.
What should I check when a PDF is cut off rather than a PNG?
Check the PDF paper size, margins, orientation, and page-range settings in the capture tool, then compare them with the intended printable area.
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.
