Back to Tools

Convert Website to PDF

Capture a live website and download it as a PDF. The capture runs on our server to avoid cross-site restrictions.

Enter a public URL and we will generate a PDF snapshot for you.

Convert any website to PDF with full-page capture

This tool works by spinning up a headless browser environment, loading the URL you provide, and rendering the page at your chosen viewport dimensions before exporting the result as a PDF document. The rendering happens server-side, so the output reflects what a real browser would display, including layout, images, and typography, rather than a raw extraction of HTML text.

Converting a webpage to PDF is useful whenever you need a portable, printable snapshot of live content: archiving a report, saving a receipt, documenting a design for review, or preserving a page whose content may change. The PDF you receive is a faithful visual record, not a reformatted interpretation.

How the URL to PDF conversion works

When you submit a URL, the tool queues a background job and returns a job ID. A screenshot engine loads the page at the viewport size you configured, captures the rendered output, and converts it to a PDF. You can track progress through the status indicator on the page, which polls the job endpoint until the status changes from "queued" or "processing" to "done." At that point the download becomes available.

Two screenshot engines are used in sequence. The primary engine handles most requests. If it fails, a fallback engine captures a PNG image and converts that to an A4-sized PDF automatically. Either way, you receive a single PDF file.

A few technical boundaries apply:

Viewport settings and full-page capture explained

The viewport is the simulated browser window the rendering engine uses. Width and height both accept values between 320 and 5000 pixels, with defaults of 1280 x 720. A narrow width (for example, 375px) triggers responsive breakpoints, producing a mobile layout in the output. A wide width renders the desktop version. This matters because many sites serve substantially different layouts depending on viewport width.

The "Full Page" toggle tells the renderer to extend the capture to the entire scrollable height of the page rather than stopping at the visible viewport. When this is off, only the above-the-fold content appears in the PDF. When it is on, the renderer scrolls through the full document height before exporting, so long articles, dashboards, and product listings are captured completely.

Choosing the right settings depends on your goal:

Step-by-step: How to turn a webpage into a PDF

  1. Open the Website to PDF tool on PDFDeal.
  2. Paste the full URL of the page you want to capture (include https:// ).
  3. Set the viewport width and height. The defaults (1280 x 720) work for most desktop pages.
  4. Toggle "Full Page" on if you want the entire scrollable content, not just the visible area.
  5. Click the capture button. A job is created and queued immediately.
  6. Watch the progress indicator. Processing typically completes within a few seconds to under a minute depending on page complexity.
  7. Download the PDF when the status shows completion.

Jobs are stored temporarily and removed after one hour, so download your file promptly after the job finishes.

When to use this tool versus related options

This tool renders a live URL by loading it in a headless browser. That is different from converting a local HTML file, which involves uploading markup directly rather than fetching a remote resource. If you have an HTML file on your device rather than a public URL, the HTML to PDF tool handles that workflow instead.

The visual output also differs from text-based conversion approaches. Because rendering happens in a browser engine, CSS, web fonts, JavaScript-rendered content, and background images all appear in the PDF. A plain text or document converter would strip those elements.

Common situations where this tool is the right choice:

If you need to work further with your PDF after capture, such as adding a watermark or combining it with other files, PDFDeal's watermark tool and other PDF utilities are available from the main toolbar. .

Watch How It Works

See the tool in action with this quick tutorial video:

FAQ

The tool loads your URL inside a headless browser engine on the server, renders the page at the viewport dimensions you choose, and captures the visual output. That capture is then packaged as a PDF document. Because a real rendering engine processes the page, CSS layouts, web fonts, and JavaScript-driven content are all reflected in the final file, not stripped out.

With "Full Page" off, the renderer captures only the portion of the page visible within the viewport height you set (default 720px). With it on, the renderer measures the entire scrollable height of the document and expands the capture area accordingly before exporting. This means a long article or product page is captured in its entirety rather than cut off at the fold.

Each conversion job spins up a headless browser session, loads a remote URL, and waits for the page to render fully. This is a resource-intensive operation. The 60-second cooldown between requests per user prevents the server queue from being overwhelmed and ensures consistent processing times for everyone. The timer starts from the moment you submit a job, not from when the download is ready.

The tool uses two engines in a fallback chain. If the primary engine does not return a result, the secondary engine captures the page as a PNG image instead. That PNG is then converted to an A4-format PDF automatically. The output format you receive is the same in both cases: a downloadable PDF file. You do not need to do anything differently to trigger the fallback.

Allowing requests to internal IP ranges (10.x, 172.16.x, 192.168.x, 127.x) or localhost would let the server-side renderer access resources on the internal network that runs the service. This is a class of vulnerability known as server-side request forgery. Blocking these addresses at the URL validation stage prevents that attack vector entirely, regardless of what is running at those addresses.

Jobs and their associated PDF data are held in server memory and automatically pruned after one hour from creation. Once a job is pruned, the download link no longer works. Download your file as soon as the status shows completion. The tool does not persist files to long-term storage, which also means your converted content is not retained after that window closes.

This tool fetches a live URL from the internet and renders it in a headless browser before converting it. The HTML to PDF converter accepts a local HTML file you upload directly, processing the markup you provide without making any outbound network request. Use this tool for public web pages you want to capture as they appear online. Use the HTML converter when you have an HTML file on your device that you want to turn into a PDF.

Because the tool uses a headless browser to render the page, JavaScript executes during the load process. Content that is injected or revealed by JavaScript after the initial HTML is parsed should appear in the output, provided it finishes loading before the renderer takes the screenshot. Pages with very long load times or content behind authenticated paywalls may not render completely.

Yes. Set the viewport width to a narrow value such as 375 or 390 pixels before submitting. Responsive websites use CSS breakpoints that respond to viewport width, so the renderer will trigger the mobile layout at those dimensions. The height setting matters less for mobile captures if you also enable full-page capture, since the entire scrollable content will be included regardless.

No. The renderer loads the URL without any session cookies or authentication credentials from your browser. Pages that redirect to a login screen, display a paywall, or require a session token will render the login or access-denied state rather than the protected content. Only publicly accessible pages can be captured with this tool.

The tool is available to use on PDFDeal without requiring a paid subscription for standard conversions. The 60-second cooldown between requests applies to all users. If you need to process many URLs in sequence or require API access for automated workflows, check the PDFDeal pricing page for plan details that cover higher usage volumes.

The default values of 1280px wide by 720px tall reflect a common desktop browser window size and work well for most standard websites. If the page you are capturing uses a wide-format layout or a large data table, increasing the width (up to 5000px) prevents horizontal content from being clipped. For documentation or archiving purposes, enabling full-page capture alongside the default width is usually sufficient. You can also read about broader PDF conversion considerations in the PDFDeal blog.