Free · No signup required

URL to PDF Converter

Paste a URL, get a PDF. Captures the full rendered page including JavaScript, images, and fonts.

PDF captured successfully

- pages · - · A4

Download PDF

Capture failed

Need this programmatically?

This tool uses the same API you can call from your code. Capture any URL as a PDF at scale — with custom headers, cookies, viewport sizing, and wait strategies.

100 free API credits, no card required
Custom headers + cookies for authenticated pages
JavaScript injection + wait strategies
capture.ts

import PDFBase from 'pdfbase'

const client = new PDFBase()

const pdf = await client.pdfs.create({

url: 'https://example.com/report',

format: 'A4'

})

// pdf.url → signed download URL

// pdf.pages → number of pages

// pdf.bytes → file size in bytes

200 OK 3.2s

What is URL to PDF conversion?

URL to PDF conversion takes a live webpage and captures it as a static PDF document. A headless browser navigates to the URL, loads all resources (HTML, CSS, JavaScript, images, fonts), waits for the page to fully render, and then generates a PDF snapshot of the result. The output is a portable document that preserves the exact visual layout of the original page.

This is different from HTML to PDF in a fundamental way: you don't need the source markup. Point it at any publicly accessible URL and you get the fully rendered page as a PDF — complete with external stylesheets, loaded images, executed JavaScript, and web fonts. Single-page apps built with React, Vue, or Angular render correctly because the conversion uses a real Chromium browser under the hood.

Common use cases include archiving web content for legal or compliance purposes, generating PDF snapshots of dashboards and reports for stakeholders who don't have login access, capturing web receipts and confirmations as permanent records, and converting web-based documentation into offline-readable PDFs. If it renders in Chrome, it can be captured as a PDF.

How this tool works

1

Paste a URL

Enter any publicly accessible URL into the input field above. The tool accepts any valid HTTP or HTTPS URL — webpages, dashboards, documentation sites, web apps, or any content that renders in a browser.

2

Configure page settings

Choose page size (A4, Letter, or Legal) and orientation (portrait or landscape). These map directly to the PDFBase API's format and landscape parameters — the same options you'd pass programmatically.

3

Capture + download

Click "Capture to PDF" (or press Ctrl+Enter / Cmd+Enter). A headless Chromium browser navigates to your URL, waits for the page to fully load and render, then captures it as a PDF. This typically takes 3-8 seconds depending on page complexity.

Why developers use URL to PDF

URL to PDF fills a different niche than HTML to PDF. Instead of generating documents from templates, it captures existing live pages. Here are the primary patterns developers build with this capability:

Automated reporting

Schedule nightly PDF captures of internal dashboards (Grafana, Metabase, Looker, custom analytics) and email them to stakeholders. No one needs dashboard access — they get a pixel-perfect PDF snapshot in their inbox every morning.

Legal archival

Capture timestamped PDF snapshots of web content for compliance, litigation, or regulatory requirements. Terms of service pages, competitor pricing pages, user-generated content — anything that might change or disappear. The PDF serves as a permanent, shareable record.

Dashboard snapshots

Turn live dashboards into sharable reports without rebuilding the UI as a PDF template. Point the API at your dashboard URL (with auth cookies), and the Chromium browser renders charts, tables, and interactive elements exactly as they appear in the browser.

Web scraping to PDF

Capture structured web content as portable documents. Research papers, documentation pages, product listings, news articles — convert any web content into an offline, annotatable PDF without building a scraper or parsing HTML.

Common use cases

URL to PDF is the right tool whenever you need to capture existing web content rather than generate documents from data. Here are the most common patterns:

Scheduled report delivery

Cron job captures your analytics dashboard URL every Monday morning and emails the PDF to your team. Works with Grafana, Metabase, Looker, Retool, or any web-based reporting tool — no custom PDF templates needed.

Compliance snapshots

Capture timestamped snapshots of terms of service, privacy policies, or regulatory pages for your compliance archive. Proves what was published on a specific date. Some teams capture daily for audit trails.

Documentation export

Convert web-hosted documentation into offline PDFs for air-gapped environments, client deliverables, or printable manuals. Capture individual pages or crawl an entire docs site and stitch PDFs together.

Client-facing proposals

Build proposals as web pages (easier to design, easier to update) and capture them as PDFs for client delivery. Update the web version, re-capture, and the PDF always matches the latest content.

Receipt & confirmation archival

Automatically capture order confirmations, payment receipts, or booking confirmations as PDFs. Run the capture as part of your post-checkout flow and attach the PDF to the confirmation email.

Competitive monitoring

Capture competitor pricing pages, feature comparison pages, or landing pages on a schedule. Build a searchable archive of how competitors position and price their products over time.

Tips for better URL to PDF output

01

Wait for dynamic content to load. Many modern pages load content asynchronously. The PDFBase API supports wait strategies — waitForSelector waits for a specific element to appear, and waitForTimeout adds a fixed delay. Use these to ensure charts, lazy-loaded images, and SPA content are fully rendered before capture.

02

Set the viewport width for responsive pages. Pages render at a default viewport width of 1280px. If the site is responsive and you want the desktop layout, this is usually fine. For mobile captures, pass a narrower viewport width via the API. For dashboards with lots of columns, try 1920px.

03

Use cookies for authenticated pages. The free tool captures public URLs only, but the PDFBase API lets you pass cookies and custom headers with your request. Grab your session cookie from DevTools and include it in the API call to capture pages behind login walls.

04

Hide cookie banners and popups. Many sites show GDPR banners or newsletter popups that clutter the PDF. Via the API, use the javascript option to inject a script that hides these elements before capture. A simple document.querySelector('.cookie-banner')?.remove() does the trick.

05

Choose the right format for the content. Use A4 portrait for article-style pages and documentation. Use Letter landscape for dashboards, spreadsheet views, and wide data tables. Legal format works well for legal documents that need extra vertical space per page.

Frequently asked questions

Is this URL to PDF converter free?
Yes, completely free with no signup required. This tool is powered by the PDFBase API and uses a full Chromium rendering engine to capture webpages. There are no conversion limits on the free tool, and your URLs are not logged after conversion.
Does the URL to PDF tool render JavaScript?
Yes. The tool uses a full Chromium browser to load and render the page, including JavaScript execution. Single-page apps built with React, Vue, Angular, and other frameworks render correctly. The browser waits for the page to fully load before capturing the PDF.
Can I capture pages that require authentication?
The free tool captures publicly accessible URLs only. For authenticated pages, the PDFBase API supports passing custom cookies and headers with your request, allowing you to capture pages behind login walls programmatically. Grab your session cookie from Chrome DevTools and include it in the API call.
How long does URL to PDF conversion take?
Typical conversions take 3-8 seconds depending on page complexity. The tool loads the full page in a Chromium browser, waits for all resources (images, fonts, scripts) to load, then renders the PDF. Complex pages with heavy JavaScript or many external resources take longer. Simple static pages can convert in under 3 seconds.
What's the difference between URL to PDF and HTML to PDF?
URL to PDF navigates a real browser to the webpage and captures everything — including external stylesheets, images, fonts, and JavaScript execution. HTML to PDF takes raw HTML markup you provide and renders it. Use URL to PDF when you want to capture an existing webpage; use HTML to PDF when you're generating documents from templates in your code.
Can I use this programmatically via an API?
Yes. This tool uses the same PDFBase API you can call from your code. Send a POST request with a URL and options (page size, orientation, viewport size, wait strategies) and get back a PDF. The API also supports custom headers, cookies, and JavaScript injection for advanced capture scenarios. Get 100 free API credits with no credit card required.