Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchFor a quick screenshot of a rendered website from Linux or macOS, use Chrome Headless for a single bounded capture, Playwright CLI when you need control over the browser, page or output, and shot-scraper if your workflow is Python-based. Each route needs access to a browser runtime; installing a command-line wrapper does not always install the browser it will use. The commands below capture what a browser renders, not just the page’s original HTML source.
Choose the command-line route that fits
| Route | Best fit | What to know |
|---|---|---|
| Chrome Headless | A one-off capture using Chrome already available on the machine | Direct browser flags keep the command short. A timeout bounds the wait, but does not confirm that a dynamic page is ready. |
| Playwright CLI | Captures that need browser selection, element or full-page scope, output controls, or repeatable browser steps | Install the CLI and its browser runtime. The CLI supports Chromium-based Chrome, Firefox, WebKit and Edge per its reference; check the installed version’s help for current flags. |
shot-scraper |
A Python/pip-oriented command-line workflow | The cited quick start is for release 0.14. Treat its commands as documented for that release, not a guarantee about later versions. |
For a single static page, Chrome’s direct command is often the least setup. When the capture must be reproducible or target a particular part of a page, Playwright CLI offers more documented controls. Choose shot-scraper if its Python installation model fits your environment.
Use Chrome Headless for a one-off capture
Chrome’s Headless command-line interface accepts a URL and a --screenshot flag. For example:
google-chrome --headless --screenshot=page.png https://example.comThe executable name can differ by installation and operating system. If google-chrome is not found, locate the Chrome or Chromium binary installed on your system and substitute its path; do not assume a particular package name. Chrome’s reference documents --timeout as a maximum wait before capture, including when the page is still loading. For example:
#1 Best Overall
- Powerful Linux Laptop: This IdeaPad Slim 3 Laptop comes pre-installed with Ubuntu Linux, offering fast performance, robust security, and a clean, user-friendly experience. Enjoy full customization, seamless hardware compatibility, and access to thousands of open-source apps. Whether you're working, creating, or coding, it's built to keep up with everything you do.
- A Multitasking Master: The latest AMD Ryzen 7 5825U processor (up to 4.5 GHz) delivers powerful performance with 8 cores and 16 threads for smooth multitasking. Integrated AMD Radeon Graphics provide crisp visuals for streaming, browsing, photo editing, and casual gaming. With smart machine intelligence, it adapts to your needs for a fast, responsive experience.
- 15.6" Full HD Display: The IdeaPad Slim 3 boasts an 88% screen-to-body ratio for a floating, edge-to-edge visual experience. TÜV Low Blue Light certification reduces eye strain, making it perfect for long work or study sessions.
- Military-Grade Durability: The smart IdeaPad Slim 3 combines portability and durability, letting you work, study, and play on the go. With a profile 10% slimmer than the previous generation, it's lightweight yet military-grade rugged, ready for anything, anywhere.
- Versatile Connectivity: Enjoy the security of a built-in webcam with a privacy shutter. Connect effortlessly with multiple ports: 2x USB A, 1x USB C, 1x HDMI, 1x SD Card Reader, 1x Headphone/Microphone combo. Bundle comes with Stylus Pen, 256GB Portable SSD and 5-in-1 Docking Station.
google-chrome --headless --screenshot=page.png --timeout=5000 https://example.comThe value bounds the wait; it is not a promise that the page will finish rendering in that time. Modern pages may continue loading images or other content, display a consent dialog, or update after scripts run. If those states matter, use a scripted readiness condition rather than treating an arbitrary timeout as proof of readiness. Chrome’s Headless reference also distinguishes a browser-rendered capture from simply retrieving source with curl: the screenshot reflects the page as rendered in the browser.
Use Playwright CLI for more capture controls
Install the CLI and browser
The documented global installation command is:
npm install -g @playwright/cli@latestPlaywright’s installation page lists Node.js 22.x, 24.x or 26.x, macOS 14 (Sonoma) or later, and Debian 12/13 or Ubuntu 22.04/24.04/26.04 on x86-64 or arm64 among its requirements at the time checked. Those requirements and supported versions can change, so verify the current Playwright installation requirements for your machine before installing. Install the browser runtime required by the CLI as part of its browser-installation workflow; installing the npm package alone may not be enough. See the Playwright CLI guide for the current workflow.
Open a page and take a screenshot
The documented basic sequence is to open a page and then capture the current page:
Rank #2
- Intel Core i5-10210U (up to 4.2GHz) - 1TB PCIe NVMe + 1TB HDD - 32GB DDR4 SDRAM
- 17.3" HD+ (1600x900) Display, Intel UHD Graphics 620
- Built in HD 720p Webcam with Microphone - Bluetooth Version4.2
- I/O Ports: 2x USB 3.1 (Data Only), 1x USB 2.0, 1x HDMI, 1x Headphone/Microphone Combo Jack
- Linux Mint Cinnamon 64-Bit - 6-Row Keyboard w/ Full Numberpad
playwright-cli open https://example.com
playwright-cli screenshotWithout a filename, the documented default is a timestamped file in the output directory, with PNG as the default format. To choose a filename, supply one to the screenshot command:
playwright-cli screenshot --filename=example.pngCheck playwright-cli screenshot --help in the version you installed if an optional flag or filename syntax differs.
Choose full-page, element, format or resolution
The screenshot reference documents page-element targeting, full-page capture, PNG/JPEG/WebP output, a custom filename and --hires for device-pixel output. Consult the current Playwright screenshot and PDF command reference for exact syntax and selector requirements for your installed CLI version.
Rank #3
- Intel Core i5-1335U Processor (12M Cache, 12 Threads, up to 4.6 GHz) - 256GB Solid State Drive - 16GB DDR4 SDRAM
- 15.6" FHD (1920x1080) Non-Touch Anti-Glare Display - Intel UHD 620 Integrated Graphics - Stereo Speakers
- 720p HD Webcam with Privacy Shutter. Integrated Microphone - Intel Dual Band Wireless-AC (2x2) 8265, Bluetooth Version 4.2
- I/O Ports: 2x USB 3.0, 1x USB 3.1 Type-C 3.1, Headphone/Mic Combo Port, 4-in-1 Card Reader, HDMI, Kensington Mini-Lock Slot
- Linux Mint (Cinnamon) 64-Bit - Keyboard with Full NumberPad - Fast Charging
- Viewport capture: captures the visible browser area; use it when the visible fold is what you need to share or inspect.
- Full-page capture: includes the page’s full scrollable extent. Lazy-loaded material may need to be brought into view or otherwise made ready before capture.
- Element capture: targets a page element rather than the entire viewport. The selector must match the intended element in the rendered page.
- Format and filename: select PNG, JPEG or WebP and an explicit filename when downstream scripts expect a particular file.
- High-resolution output:
--hiresaccounts for device pixel ratio. The resulting image dimensions can exceed CSS-pixel dimensions, so pixel coordinates in the image will not necessarily correspond to the CSS-pixel coordinates used for mouse commands.
Playwright CLI runs headless by default. Its documentation also describes a --headed mode for opening a visible browser, which can help inspect what happened during a capture. The CLI reference includes browser selection for Chrome, Firefox, WebKit and Edge; availability depends on the installed version and browser setup.
Make repeated captures more controlled
For a repeatable workflow, separate navigation from the capture and use the CLI’s documented configuration, selection and session commands rather than relying on an implicit default browser state. Decide in advance whether you need the visible viewport, a particular element or the entire scrollable page, and whether image output must use fixed dimensions or a device-pixel ratio. When dynamic content is involved, wait for a meaningful page condition if the tool and workflow support it; a fixed delay can still end before or after the state you intend to capture.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use shot-scraper from Python
The shot-scraper project describes itself as “A command-line utility for taking automated screenshots of websites” in its release 0.14 documentation. That version’s quick start separates installation of the Python package from installation of the browser:
Rank #4
pip install shot-scraper
shot-scraper install
shot-scraper https://datasette.io/The documented example creates datasette-io.png. The cited instructions are specifically for version 0.14; check the shot-scraper 0.14 documentation and the project’s current documentation before relying on option names or assuming current-version behavior. As with the other routes, a wrapper install and browser install are distinct steps.
Plan for page readiness, output and repeatability
Know what the screenshot represents
A command-line browser screenshot records a rendered page state. It is not equivalent to saving the initial HTML response: browser layout, styles and script-driven changes affect what appears in the image. A capture can therefore vary with the browser version, viewport, page state and timing.
Choose a wait based on the page
A page that appears loaded to the browser may still have asynchronous components, animations, lazy images or a consent dialog that has not reached the state you want. Chrome’s --timeout provides a maximum wait, not a readiness test. For pages where correctness matters, use an explicit condition tied to the content or state you need, and keep capture settings consistent across runs.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteBest Value
- 12th Intel Alder Lake N95 Processor – The GMKtec G3 S Mini PC is powered by the 12th Gen Intel N95 processor with 4 cores, 4 threads, 6MB cache and a burst frequency up to 3.4GHz. Compared with N100/N5105/N5100/N5095, the N95 delivers up to 36% overall performance improvement. Perfect for routine tasks, office work, and home entertainment, this compact mini desktop is more convenient than traditional bulky PCs.
- 8GB RAM & 256GB SSD Storage – Pre-installed with 8GB DDR4 memory and a fast 256GB M.2 2242 SSD, the G3 S mini desktop offers quicker startup, smoother multitasking, and faster file transfers. Enjoy seamless performance whether you’re working on multiple applications, browsing, or streaming content.
- Rich Interfaces & Connectivity – The G3 S mini computer comes equipped with USB 3.2 (up to 10Gbps), dual HDMI 2.0 (4K@60Hz), and a 3.5mm audio jack. With support for WiFi 5, Bluetooth 5.0, and Gigabit Ethernet (RJ45 1000MbE), it connects easily with monitors, projectors, printers, office equipment, and other peripherals, making it versatile for both home and business use.
- Dual 4K Display Support – Featuring upgraded Intel UHD Graphics (up to 1000MHz), the G3 S supports 4K video playback and AV1 decoding for a smooth viewing experience. With dual HDMI outputs, you can connect two 4K@60Hz displays simultaneously, enabling efficient multitasking for work and entertainment.
- GMKtec WARRANTY - GMKtec offers a 1-year limited GMKtec's warranty for each mini PC, starting from the date of the purchase. All defects due to design and workmanship are covered. With a professional after sales team always ready to attend to your needs, you can simply relax and enjoy your mini PC.
Match the output to its next use
- Use a stable filename if another command or script will consume the result; a generated timestamp is convenient for manual captures but less convenient for a fixed pipeline.
- Choose PNG, JPEG or WebP based on what the installed tool supports and what the next application accepts.
- Decide whether you need the viewport, an element or the full scrollable page before automating; these scopes produce materially different images.
- Account for device-pixel scaling when comparing image coordinates with browser CSS coordinates.
Keep costs and performance expectations realistic
These local command-line routes do not have a documented speed or accuracy ranking in the cited references. Capture time depends on the page, browser startup and readiness conditions; do not infer a performance guarantee from a short command. If you run captures in CI or repeatedly, include browser installation and version management in the workflow, and use a bounded wait plus an appropriate readiness check so a stalled page does not hold the job indefinitely.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common failures
| Symptom | Likely cause | What to try |
|---|---|---|
command not found |
The CLI or browser binary is not installed, or it is not on the shell’s PATH. | Confirm the package installation completed; use the tool’s documented install steps and call Chrome by its installed path if needed. |
| Playwright starts but cannot launch a browser | The required browser runtime has not been installed or the installed combination is unsupported. | Follow the current Playwright CLI browser-installation workflow and verify the runtime and operating-system requirements on the installation page. |
shot-scraper installs but capture fails |
The separate browser installation step may be missing, or the instructions used may not match the installed version. | Run the browser installation step for the version in use and consult its matching documentation; the cited quick start is release 0.14. |
| The image is blank or missing page content | The page may still be loading, may require script-driven rendering, or may not have reached the intended state before capture. | Inspect the page in a visible browser where supported, increase the bounded wait only as needed, and prefer an explicit readiness condition for dynamic content. |
| The screenshot shows a consent prompt or popup | The page displayed it as part of the state captured by the local browser. | Handle the page’s intended consent state in the browser workflow before capture; do not assume a screenshot flag dismisses site overlays. |
| Image coordinates do not match browser mouse coordinates | High-resolution capture uses device pixels while browser interaction commonly uses CSS pixels. | Account for the device-pixel ratio when mapping coordinates or use a non-high-resolution capture for CSS-pixel alignment. |
Or skip the browser setup
If you want a rendered screenshot without installing and maintaining a local browser workflow, ScreenshotNeo provides a website screenshot API and MCP server for developers. A GET request returns an image or PDF; for example, this cURL command saves a WebP capture (see the API documentation):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo removes cookie and consent banners, newsletter popups and chat widgets before capture; each cleanup step can be disabled. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and response headers report the page verdict and billing status. An MCP server exposes screenshot tools to Claude, Cursor and other MCP clients. 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 with no card.
Which method should you use?
Use Chrome Headless when an installed Chrome binary and a simple bounded capture are enough. Use Playwright CLI when you need documented control over browser choice, capture scope and output, or a repeatable workflow. Use shot-scraper when a Python-oriented CLI suits your setup, while checking which release its instructions cover. If you would rather call a hosted API than install a browser runtime, try ScreenshotNeo first for its clean captures, billing only on clean shots and no-card free tier.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Frequently Asked Questions
Do these commands capture a website’s source HTML?
No. They capture the browser-rendered page state; that can include styling and script-driven changes that are not present in a raw HTML download.
Can I run these tools headlessly in CI?
Playwright CLI runs headless by default, and Playwright documents local and CI use on supported Linux and macOS environments. Check the current installation requirements and browser setup for the exact runner image.
Why can a full-page screenshot still omit images?
A page may load images lazily as they approach the viewport. Make the relevant content load before capture, or use a workflow that explicitly prepares the page for a full-page shot.
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.
Recommended Free Tools
