How to Convert My Website to PDF Online

For one webpage, open it in Chrome, press Ctrl+P (Cmd+P on macOS), choose “Save to PDF,” adjust the page settings, and save. This is the fastest free way to convert a website page to PDF online. For a selected section, use Acrobat’s browser extension. For multiple pages or an entire site, Acrobat desktop can crawl a URL. For a repeatable application workflow, use an HTML-to-PDF API or ScreenshotNeo.

1. Convert one webpage to PDF with your browser

Open the exact webpage you want to save.
Wait for the page to finish loading. Scroll through it once if images or other content load lazily.
Open the print dialog with Ctrl+P on Windows/Linux or Cmd+P on macOS.
Choose Save to PDF (or the PDF destination offered by your browser).
Set the page range, orientation, paper size, margins, scale, background graphics, and headers or footers as needed.
Choose Save, name the file, and select a folder.

Print-to-PDF is best for a single page or an occasional archive. It uses the page as rendered in your browser, so the output can differ when the site has responsive layouts, sticky navigation, animations, cookie dialogs, or content that appears only after interaction.

Settings that affect the result

Setting	When to change it
Orientation	Use landscape for wide tables, dashboards, or two-column layouts.
Margins	Reduce margins when content is being clipped; increase them when text is too close to the edge.
Scale	Lower the scale when columns run off the page; increase it when the text is unnecessarily small.
Background graphics	Enable this when colors, shaded sections, or background images carry meaning.
Page range	Print only the pages you need instead of the entire long document.
Headers and footers	Turn them off for a clean copy; turn them on when the URL, title, or date is useful context.

2. Save a page or selection with Acrobat’s browser extension

If the Acrobat browser extension is installed, choose Convert to PDF from its toolbar. Acrobat can convert an HTML file, an entire page, or a selected part of a page. Name the document and save it.

This route is useful when you need to capture a specific region rather than the browser’s complete print view. Check the result afterward: selection boundaries, fixed-position elements, and scrollable panels can produce unexpected page breaks.

3. Convert multiple pages or an entire website with Acrobat desktop

A browser print dialog normally handles one rendered page. Acrobat desktop is better suited to a crawl across several pages.

Open Acrobat and choose Create > Web page.
Enter the starting URL.
Choose the number of crawl levels, or select Get entire site.
Optionally restrict the crawl to the same path or the same server.
Create the PDF and inspect the page count, links, images, and navigation.

Whole-site conversion needs boundaries. A site can contain thousands of URLs, external links, login-only pages, search results, or endlessly generated calendar pages. A crawl level limit and same-path or same-server restriction help keep the output focused.

Acrobat controls worth checking

For more controlled documents, Acrobat provides settings for bookmarks, PDF tags, headers and footers, encoding, colors, multimedia, images, links, scrollable blocks, page size, orientation, margins, and scaling. These controls matter when the PDF is intended for distribution, accessibility review, or long-term archiving rather than a quick reference.

4. Fix layout problems before you save

A PDF is a fixed page layout, while a website is usually responsive and interactive. Inspect the saved file instead of assuming the preview is correct.

Clipped columns: switch to landscape, reduce scale, or widen the paper size.
Missing images: wait for lazy-loaded content, scroll through the page, and print again.
Cookie banners or chat widgets: dismiss them before printing. If they cannot be dismissed, use a capture workflow that can remove them before rendering.
Scrollable boxes: expand the box or use a tool with scrollable-block handling; otherwise only the visible portion may appear.
Broken page breaks: try different margins, scale, and orientation. A table or card grid may need a wider page.
Blank or incomplete pages: check that the page finished loading and that the content is not behind a login, bot check, or script error.
Interactive content: videos, forms, menus, and hover states may become static or may not appear at all. Save the source URL alongside the PDF when interaction is important.

5. Automate website-to-PDF conversion

For scheduled reports, document archives, or many URLs, a browser dialog is difficult to operate consistently. An automated system should load the page, wait for the content that matters, apply a viewport and print configuration, then store the resulting PDF and record whether the capture succeeded.

What an automated workflow should control

URL validation and redirect handling.
Viewport size, device emulation, orientation, paper size, margins, and scale.
Waiting for a selector, a fixed delay, or network idle.
Lazy-loaded images and content revealed after scrolling.
Cookie banners, newsletter popups, chat widgets, ads, and trackers.
Authentication through headers, cookies, or an authorization token.
Timeouts, retries, rate limits, and an audit record for each URL.

A self-hosted browser can provide this control, but it also means maintaining browser binaries, fonts, sandbox permissions, proxy settings, concurrency limits, and failure handling.

6. Or skip the browser setup

ScreenshotNeo provides a website capture API and MCP server. Its capture pipeline can accept consent banners before rendering and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Clean shots are the only billable results: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies the result with X-Page-Verdict and X-Billed headers.

The API supports PNG, JPEG, WebP, and PDF output, with options for full-page capture, lazy images, CSS-element capture, dark mode, device presets, custom viewports, retina scale, PDF paper size, margins, landscape mode, and page ranges. You can also set custom CSS or JavaScript, click an element, wait for a selector or network idle, block requests or resource types, provide headers, cookies, user-agent and Authorization values, set timezone or geolocation, resize images, cache with a chosen TTL, create signed links, submit asynchronous jobs with signed webhooks, capture up to 100 URLs per bulk call, and query usage. See the ScreenshotNeo documentation for the current parameter names and PDF request format.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const data = Buffer.from(await res.arrayBuffer());
require('fs').writeFileSync('shot.webp', data);

For AI workflows, ScreenshotNeo also provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. A free account includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.

7. Performance, reliability, and cost considerations

Browser printing

For a single page, browser printing has no conversion-service cost and usually starts immediately. Its reliability depends on the local browser state, loaded fonts, network speed, page scripts, and whether the page requires interaction.

Desktop crawling

Whole-site jobs take longer as crawl depth and URL count increase. Restrict the path or server, exclude areas that do not belong in the document, and review the resulting link set before distributing the PDF.

Automated capture

Use explicit waits instead of an arbitrary long delay when a known selector indicates readiness. Set a bounded timeout, retry transient failures, limit concurrency to protect the target site, and cache unchanged pages where appropriate. Store the URL, capture time, settings, status, and output location so a failed or changed document can be traced.

ScreenshotNeo billing behavior

Only clean shots are billed. Responses expose whether a result was a page verdict and whether it was billed, which lets an integration distinguish a successful document from a bot check, blank page, timeout, failed load, or cache hit.

8. Troubleshooting checklist

Symptom	Likely cause	Fix
Text is tiny	The page is wider than the paper.	Use landscape, a larger paper size, or a higher scale after reducing excess margins.
Right side is missing	A wide layout is being forced onto a narrow page.	Choose landscape and reduce scale.
Images are absent	Images load lazily or were blocked before printing.	Scroll through the page, wait for completion, and retry.
A consent dialog covers content	The banner was still open at capture time.	Accept or dismiss it first, or use a capture service that handles consent elements before rendering.
Only part of a panel appears	The panel has its own scroll container.	Expand it or use scrollable-block handling.
The PDF is blank	The page failed to load, requires authentication, or triggered a bot check.	Open the URL normally, verify access, and inspect capture status or verdict headers.
Some pages are missing from a site crawl	The crawl depth or same-path/server restriction excluded them.	Increase the selected levels or adjust the restriction deliberately.
The API request times out	The page is slow, blocked, or waiting on a resource.	Use a bounded longer timeout, configure a readiness wait, and inspect the page verdict before retrying.
Repeated captures cost more than expected	Caching is disabled or its TTL is too short.	Choose a cache TTL appropriate for how often the page changes.

9. Which method should you use?

Need	Best fit
One page, one time	Browser Print to PDF
A selected page region	Acrobat browser extension
Several linked pages or a whole site	Acrobat desktop with crawl limits
Scheduled or high-volume conversion	An HTML-to-PDF API or ScreenshotNeo automation
Pages with consent banners, popups, or chat widgets	ScreenshotNeo, which removes supported elements before capture
AI-agent screenshot or PDF tasks	ScreenshotNeo MCP tools

FAQ

Can I convert an entire website into one PDF?

Yes. Use Acrobat desktop’s web-page creation workflow, choose a crawl depth or the entire-site option, and restrict the crawl to the same path or server when appropriate. Review the URL scope before sharing the result.

Will a PDF preserve a webpage exactly?

It preserves a rendered snapshot, not the website’s live behavior. Responsive layouts, lazy content, scrollable areas, animations, and interactive controls can change what appears on paper.

Can I save only part of a webpage?

Yes. Acrobat’s browser extension can convert a selected portion. You can also use a capture workflow that targets a CSS selector.

Those elements may have been dismissed, blocked, or removed before rendering. If you need a clean document without them, configure the capture workflow to hide or remove them intentionally.

What is the simplest free method?

Use the browser’s built-in Print dialog, select Save to PDF, adjust orientation and scale, and inspect the saved file.