# How to Screenshot a Full Web Page to PDF (and Automate It) Source: PageCrawl.io Blog URL: https://pagecrawl.io/blog/screenshot-webpage-to-pdf --- A competitor quietly drops their headline price from $49 to $39, runs the promotion for six days, then puts it back. You remember seeing it. You cannot prove it. The page looks exactly like it did before, and your word against a cached marketing claim is worth nothing in a pricing dispute, a chargeback, or a conversation with your own legal team. A full-page screenshot saved as PDF fixes this. It captures the entire page, top to bottom, including the parts below the fold you would normally have to scroll to reach, and freezes it into a single portable file with a date attached. Unlike a clipboard screenshot of whatever happens to fit on your monitor, a page-to-PDF capture preserves the whole document: every price, every clause, every disclaimer. This guide covers every practical way to screenshot a full web page to PDF, from the print dialog already built into your browser to command-line tools to fully automated, scheduled captures that build an archive while you sleep. By the end you will know which method fits a one-off save versus a compliance program that needs a timestamped record every single day. ### Why save a web page as a PDF instead of a regular screenshot? A PDF captures the whole page in one file, not just the slice visible on your screen. A standard screenshot freezes whatever fits in the viewport, so a long product page, a multi-section policy, or a pricing table that runs past the fold gets chopped off. PDF keeps the complete document, stays searchable, and prints cleanly. The practical differences matter more than they sound. A clipboard screenshot is a flat image: you cannot select text from it, search inside it, or extract a quote without retyping. A web page saved to PDF keeps the text layer intact in most browsers, so you can highlight a clause, copy a price, or run a find-in-document search months later. PDFs also embed the URL and capture date in the header or footer by default, which turns a casual save into something closer to a record, and the format opens identically on any device years from now. If your real goal is keeping defensible copies of pages over time, read our primer on the [web evidence layer](/blog/web-evidence-layer-definitional) and how durable captures differ from throwaway screenshots. ### How do you screenshot a full web page to PDF in your browser? Every major browser can save a full web page to PDF through its built-in print dialog, with no extension required. Open the page, trigger print (Ctrl+P on Windows, Cmd+P on Mac), and choose "Save as PDF" or "Microsoft Print to PDF" as the destination instead of a physical printer. The browser renders the entire page, not just the visible part. This is the fastest method for a one-off capture and it works on every operating system. The output quality depends on the page, so a few settings make a large difference. #### Chrome and Edge In Chrome or Edge, press Ctrl+P (Cmd+P on Mac) to open the print dialog. Under "Destination," select "Save as PDF." Expand "More settings" and adjust these for a clean full-page capture: 1. Set "Paper size" to A4 or Letter depending on your region. 2. Turn on "Background graphics" so colors, banners, and shaded price boxes are preserved instead of printing as white. 3. Set "Margins" to "None" or "Minimum" to avoid cropping wide layouts. 4. Use the "Scale" option (try "Fit to printable area" or a custom percentage near 70-90 percent) if the right edge of the page is being cut off. Click "Save," choose a filename, and the entire scrollable page is written to a single PDF. Note: descriptive filenames that include the date, such as `competitor-pricing-2026-10-29.pdf`, save you enormous time when you have dozens of captures. #### Firefox Firefox works almost identically. Press Ctrl+P, then choose "Save to PDF" in the destination dropdown. Firefox exposes a handy "Pages" range and a "Shrink to fit" option that solves most cut-off-edge problems. As with Chrome, enable "Print backgrounds" under "More settings" so styled elements and color-coded sections survive the export. #### Safari On Mac, Safari handles this through the standard print sheet. Open the page, press Cmd+P, then click the dropdown at the bottom-left of the print dialog (it may read "PDF") and choose "Save as PDF." Safari also offers File then "Export as PDF," which captures the full page in one continuous document. Reader mode (the icon in the address bar) strips navigation and ads before you export, which is ideal for archiving long articles cleanly. ### How do you capture a full-page screenshot without using print? If you want an image-style screenshot of the entire page rather than a paginated PDF, browsers have a hidden full-page capture and extensions fill the gaps. In Chrome and Edge, open Developer Tools (F12), press Ctrl+Shift+P to open the command menu, type "screenshot," and choose "Capture full size screenshot." The browser scrolls and stitches the whole page into one PNG automatically. This built-in command is the cleanest no-extension way to get a single tall image of an entire page, including content far below the fold. Firefox makes it even easier: right-click anywhere on the page, choose "Take Screenshot," then "Save full page." Both produce a PNG you can later convert to PDF if you need the portable format. Browser extensions add convenience for people who do this often. The well-known full-page capture extensions let you click a toolbar button to grab the entire page, annotate it, and export to either PNG or PDF. They are fine for occasional manual use. The catch is that every capture is still a manual action you have to remember to perform, which is exactly the problem that breaks down the moment you need a capture from last Tuesday and nobody took one. For changes you actually want to compare visually over time, a purpose-built [visual regression monitoring](/blog/visual-regression-monitoring-detect-ui-changes) approach beats a folder of loose PNGs. ### How do you screenshot a web page to PDF from the command line? Developers and technical teams can generate a full-page PDF without opening a browser window using a headless command. The widely used approach is Chrome's headless mode: run `chrome --headless --print-to-pdf=output.pdf --no-margins https://example.com` and Chrome renders the page and writes a PDF without any visible UI. The older `wkhtmltopdf` tool does the same for simpler pages. This is the right tool when you want to script captures or wire them into a build pipeline. A minimal loop that reads URLs from a text file and writes one dated PDF per URL is only a few lines of shell. The headless approach handles modern JavaScript-rendered pages because it uses the same rendering engine as the visible browser, whereas `wkhtmltopdf` predates a lot of modern web standards and struggles with dynamic content, custom fonts, and lazy-loaded images. The honest limitation: a command-line script captures a page at the instant you run it and nothing more. It does not know when the page changed, keep a history, or notify anyone. You still have to schedule it, store the output durably, handle pages behind logins, and build your own way to compare today's capture against last month's. That is a real project, and it is the seam where dedicated monitoring earns its keep. For the broader build-versus-buy tradeoff, see our [complete guide to monitoring website changes](/blog/how-to-monitor-website-changes-guide). ### Why does manual page-to-PDF capture break down at scale? Manual capture fails the moment you need consistency over time rather than a single file today. One person, one page, one save works fine. But evidence, compliance, and competitive tracking all depend on capturing the same page repeatedly, on a reliable schedule, without gaps, and nobody remembers to print a PDF every morning for ninety straight days. The specific failure modes are predictable. You forget a day, and the one capture you needed is the one you missed. Different people use different settings, so your archive is inconsistent. The page changes at 2 a.m. and your 9 a.m. capture misses the version that mattered. You end up with a folder of hundreds of similarly named PDFs and no quick way to see which two differ or what changed between them. And pages behind a login, or pages that only render their important content after JavaScript runs, defeat a naive script entirely. What turns a pile of screenshots into something useful is detecting when a page actually changed and capturing automatically at that moment, with the date and the difference recorded. That is monitoring, not screenshotting, and it is the difference between a drawer of paper and a system of record. The same logic applies whether you are watching prices, [tracking document and PDF changes](/blog/online-pdf-monitoring-document-changes), or building a legal archive. ### How do you automate full-page web captures on a schedule? You automate captures by setting up a monitor that visits the page on a fixed schedule, saves a full-page screenshot every time, and keeps each capture in a dated history you can browse and compare. Instead of remembering to print a PDF, you configure the page once and the system builds the archive for you, flagging the checks where something actually changed. [Image: PageCrawl change diff for Competitor Pricing Page Archive, highlighting the added and removed text] PageCrawl does this with screenshot history turned on. Every check stores a full-page capture, so over weeks and months you accumulate a timeline of exactly how a page looked on each date, with the changes between captures highlighted automatically. Here is how to set it up. #### Step 1: Add the page you want to capture Paste the URL into PageCrawl. It loads the page in a real browser, renders JavaScript, and shows you a preview of the full page exactly as it will be captured. This matters for modern sites: a simple HTTP fetch would miss content that only appears after scripts run, but a browser-rendered capture sees the page the way a human does. #### Step 2: Enable screenshots and full-page capture In the monitor settings, turn on screenshots so each check stores a visual capture. New monitors in PageCrawl already default to screenshots enabled, plus automatic removal of cookie banners and overlays so those popups do not obscure your archived image. Choose full-page (rather than viewport-only) so the entire scrollable page is recorded top to bottom. #### Step 3: Choose what counts as a change Decide what should trigger a fresh, flagged capture: any visible change to the page, a change to a specific section you select, or a movement in a tracked value like a price. Targeting a specific region cuts noise dramatically, so a rotating ad banner does not flag every check while a buried clause change does. Our [CSS selector guide](/blog/css-selector-guide-target-elements-monitoring) covers how to target one element precisely. #### Step 4: Set the capture frequency Pick how often the page is checked and captured. Daily suits policy pages, terms of service, and compliance records. Hourly suits competitor pricing and promotions. Every few minutes suits fast-moving inventory or flash sales. On the free tier you get checks every 60 minutes, which is plenty to validate the approach on your most important page. #### Step 5: Set up notifications Choose how you want to hear about a change: email, Slack, Discord, Microsoft Teams, Telegram, a webhook into your own system, or browser push. You get the alert and a side-by-side comparison the moment a capture differs from the last one, so you are not scrolling a folder of PDFs hunting for the difference. #### Step 6: Browse and export your capture history Open the monitor's history to see every dated capture in one timeline, with changed checks highlighted. You can open any individual capture, compare two dates visually, and export the record when you need a portable file for a dispute, an audit, or your records. The archive builds itself from here on. ### What makes a captured page actually hold up as a record? A capture holds up when it is complete, timestamped, and consistent: the full page, the exact date and time it was taken, and an unbroken series rather than a single convenient screenshot. A lone PDF someone produced after the fact is easy to question. A continuous, automated history showing the page on dozens of consecutive dates is far harder to dispute. Three properties separate a record from a screenshot. First, completeness: the entire page, including the fine print below the fold, not a cropped view. Second, an objective timestamp tied to each capture rather than a date you typed into a filename yourself. Third, regularity, because an automated daily capture that ran whether or not anyone was watching tells a credible story about what the page showed and when. This is why teams handling defamation, false advertising, or contract disputes lean on systematic capture. Our guide to [preserving internet evidence](/blog/preserving-internet-evidence-defamation) goes deeper on what makes web captures defensible, and regulated firms with formal retention duties should read about [SEC 17a-4 web archiving requirements](/blog/sec-17a-4-web-archive-monitoring). For long-term preservation beyond a single PDF, full-page captures pair naturally with web archiving. If you have leaned on the Internet Archive for this, our roundup of [Wayback Machine alternatives](/blog/wayback-machine-alternatives-web-archiving) and the broader [guide to website archiving](/blog/website-archiving) explain when you want a capture you control rather than a public archive you do not. ### Who needs automated page-to-PDF capture? The need shows up anywhere a page changes and you must prove what it said before. The common thread is that the live page is not a reliable witness: it updates, it gets edited, it disappears, and a single screenshot is too easy to dismiss. Automated, dated captures turn a moving target into a fixed record. #### Legal and compliance teams Legal teams capture terms of service, privacy policies, marketing claims, and disclosures on a schedule so they can show exactly what a page stated on any given date. When a vendor quietly edits a liability clause or a competitor runs a claim they later retract, the dated capture series is the proof. Daily full-page captures with change alerts mean nothing slips through between manual reviews. #### Competitive and pricing intelligence Tracking a rival's pricing page, promotions, or product claims over time only works if you capture consistently. A folder of screenshots from random days has gaps exactly where the interesting changes happened. A scheduled capture every hour or two builds a complete pricing history you can chart, cite, and act on. #### Brand protection and reputation When you need to document a defamatory post, unauthorized use of your brand, or a misleading third-party claim, the content often gets deleted once you complain. A capture taken automatically while it was live, with a timestamp, preserves it. #### Records and audit trails Government notices, regulatory pages, supplier terms, and contract pages all change without announcement. Teams in regulated industries capture these on a fixed cadence to satisfy retention rules and to reconstruct exactly what a page communicated at a point in time. ### Choosing your PageCrawl plan PageCrawl's **Free plan** lets you monitor **6 pages** with **220 checks per month**, which is enough to start an automated capture archive on your most important pages and see the value before you pay anything. | Plan | Price | Pages | Checks / month | Frequency | |------|-------|-------|----------------|-----------| | Free | $0 | 6 | 220 | every 60 min | | Standard | $8/mo or $80/yr | 100 | 15,000 | every 15 min | | Enterprise | $30/mo or $300/yr | 500 | 100,000 | every 5 min | | Ultimate | $99/mo or $999/yr | 1,000 | 100,000 | every 2 min | Annual billing saves two months across every paid tier. Enterprise and Ultimate scale up to 100x if you need thousands of pages or multi-team access. Standard at $80/year pays for itself the first time an archived capture settles a dispute that a missing screenshot would have lost. 100 pages covers most practical capture programs: a set of competitor pages, your key policy and terms pages, and the compliance or pricing pages relevant to your work. Checking every 15 minutes means your archive catches short-lived changes that a daily capture would sleep through. Enterprise at $300/year adds 500 pages, five-minute checks, and the full API for wiring captures into your own systems. All plans include the **PageCrawl MCP Server**, so you can ask Claude, Cursor, or another MCP-compatible assistant to set up captures and query your history in plain language. ### Getting Started Stop trusting your memory and a folder of loose screenshots. Pick the one page you would most regret not being able to prove, add it to a free PageCrawl account, turn on full-page screenshots, and let the archive build itself from today forward. Set it up once, and every future version of that page captures itself, dated and ready, before you even know you need it. --- Need more? The complete PageCrawl.io help center, with every article, is available as a single document at https://pagecrawl.io/llms-full.txt. Read it for context on anything this page does not cover.