URL to PDF: Webpage, Website & HTML to PDF, Bulk avatar

URL to PDF: Webpage, Website & HTML to PDF, Bulk

Pricing

from $1.50 / 1,000 pdfs

Go to Apify Store
URL to PDF: Webpage, Website & HTML to PDF, Bulk

URL to PDF: Webpage, Website & HTML to PDF, Bulk

URL to PDF in bulk: webpage, website and HTML page to PDF with A4, Letter or Legal, margins, page numbers, optional merge. Failed URLs are not charged.

Pricing

from $1.50 / 1,000 pdfs

Rating

0.0

(0)

Developer

Altronite

Altronite

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

19 days ago

Last modified

Features

Limited permissions

Share

URL to PDF in bulk: webpage to PDF, website to PDF and HTML page to PDF from a list of public URLs. Each URL becomes a print-ready PDF: A4, Letter or Legal, portrait or landscape, your margins, optional page numbers, and the site's print or screen styles. Optionally merge everything into one PDF with a bookmark per URL. Common cookie banners are hidden with CSS and robots.txt is respected by default. It prints in a real Chromium browser. A URL that can't be converted becomes an error row with the reason, is never charged, and doesn't stop the run.

Need PNG or JPEG screenshots instead? Use Website Screenshot API.

One link in, one PDF row out

Who it's for

  • Research, legal and compliance: archive public pages, articles and disclosures as dated PDFs.
  • Teams sharing reading packs: merge a list of articles or docs pages into one bookmarked PDF.
  • Reporting: print dashboards or wide tables on landscape Letter with page numbers.
  • AI agents and pipelines: turn URLs into files a document tool can read; every row has a status field to branch on.

Quick start

Copy this into the Input tab (JSON view) and press Start. It converts one public page to an A4 PDF.

{ "urls": ["https://example.com"] }

The row's pdfUrl opens the PDF.

More recipes: convert a webpage to PDF in bulk

Copy one of these into the Input tab (JSON view) and press Start.

A4 PDFs in bulk (one PDF per URL, the site's print styles, 10 mm margins):

{ "urls": ["https://example.com", "https://example.org", "https://example.net"] }

US Letter, landscape, with page numbers (wide pages, "1 / 12" footer):

{ "urls": ["https://en.wikipedia.org/wiki/PDF"], "paperFormat": "Letter", "landscape": true, "pageNumbers": true }

Merged into one PDF (in input order, one bookmark per URL; the single PDFs are kept too):

{ "urls": ["https://example.com", "https://en.wikipedia.org/wiki/PDF", "https://apify.com"], "mergeIntoOne": true }

Archive articles as PDFs, waiting for dynamic content (wait for the network to go quiet, then print):

{ "urls": ["https://example.com/article-1", "https://example.com/article-2"], "waitUntil": "networkidle", "delayMs": 1000, "pageNumbers": true }

Legal-size pages with wider margins (for forms and documents):

{ "urls": ["https://example.com/form"], "paperFormat": "Legal", "margin": 20 }

Looks like the browser (screen styles instead of the print stylesheet, no margins):

{ "urls": ["https://example.com"], "mediaType": "screen", "margin": 0 }

Output

One dataset row per non-blank URL when the input contains at least one valid URL, plus one extra row for the merged file when mergeIntoOne produced one. PDFs are saved in the run's key-value store and pdfUrl links to each. The Output tab links to the dataset and the stored files.

{
"status": "ok",
"url": "https://en.wikipedia.org/wiki/Portable_Document_Format",
"finalUrl": "https://en.wikipedia.org/wiki/PDF",
"httpStatus": 200,
"title": "PDF - Wikipedia",
"pdfUrl": "https://api.apify.com/v2/key-value-stores/<store-id>/records/pdf-0001-63672d491ca0.pdf?signature=...",
"storageKey": "pdf-0001-63672d491ca0.pdf",
"pages": 24,
"bytes": 474730,
"paperFormat": "A4",
"takenAt": "2026-10-07T20:20:14+00:00"
}

finalUrl is the address after redirects; title is cut at 300 characters; pages is the page count of the PDF; bytes is the file size; takenAt is the UTC row creation time.

The merged file has its own row, with type: "merged" and no url:

{ "status": "ok", "type": "merged", "pdfUrl": "https://api.apify.com/v2/key-value-stores/<store-id>/records/merged.pdf?signature=...", "storageKey": "merged.pdf", "pages": 39, "bytes": 4844835, "sourceCount": 3, "takenAt": "2026-10-07T20:24:17+00:00" }

Uncharged error rows have status, url, error (at most 500 characters), input, takenAt and scrapedAt (same time as takenAt). Rejected HTTP pages and bot checks also have httpStatus.

{ "status": "error", "url": "https://en.wikipedia.org/wiki/ThisPageDoesNotExist", "httpStatus": 404, "error": "The page answered 404", "input": "https://en.wikipedia.org/wiki/ThisPageDoesNotExist", "takenAt": "2026-10-07T20:21:01+00:00", "scrapedAt": "2026-10-07T20:21:01+00:00" }

Use it from code or an AI agent

Run this actor with the Apify API, the Apify Python or JavaScript clients, or as a tool through the Apify MCP server. Pass the same input JSON through any of these. Check status on each row, then fetch pdfUrl for ok rows; error rows explain what failed.

Minimal input:

{ "urls": ["https://example.com"] }

Integrations

Connect it to Make, Zapier, n8n or your own webhook through Apify integrations, or run it on a timer with Apify Schedules. Rows come out as a dataset (JSON, CSV or Excel), and the PDFs sit in the run's key-value store behind each pdfUrl.

Input

Fill in the fields below, or paste JSON into the Input tab. Only urls is required.

FieldDefaultWhat it does
urls["https://apify.com"]Public pages, one PDF each, up to 500. A missing scheme becomes https://.
paperFormatA4A4, Letter or Legal.
landscapefalsePrint pages sideways.
printBackgroundtrueKeep background colours and images.
mediaTypeprintprint uses the site's print stylesheet; screen looks like the browser.
margin10Margin in mm on all four sides, 0 to 50. At least 12 mm at the bottom when pageNumbers is on.
pageNumbersfalseCentred "page / total" footer.
waitUntilloadload, domcontentloaded or networkidle.
delayMs0Extra wait before printing, up to 30,000 ms.
hideCookieBannerstrueHide common consent pop-ups with CSS.
respectRobotsTxttrueSkip URLs robots.txt disallows (uncharged error row).
timeoutSecs45Per step (load, then print): 5 to 180.
maxConcurrency2Pages at once, 1 to 7; each parallel page needs memory. Memory defaults to 1 GB and goes up to 4,096 MB; the run log ends with a "Peak memory" line to help you size it.
mergeIntoOnefalseAlso join delivered PDFs in input order into merged.pdf, one bookmark per URL (named after the page title, or the URL). Needs 2 or more delivered PDFs totalling at most 10% of the run's memory (about 102 MB at 1 GB).

Pricing

Pay per event. You pay for up to three things:

EventPriceWhen
pdf$0.0015 per PDFeach ok URL row
merge$0.002 per merged fileonce, only with mergeIntoOne and only when merged.pdf is stored (2 or more delivered PDFs, within the memory limit)
apify-actor-start$0.002 per runonce per run, one event per GB of memory with a 1 GB minimum

Examples:

  • 100 URLs, all converted: 100 x $0.0015 + $0.002 = $0.152.
  • Same 100 URLs merged into one file: $0.152 + $0.002 = $0.154.
  • 100 URLs where 10 fail: 90 x $0.0015 + $0.002 = $0.137. Failed URLs are never charged.

Not charged: HTTP 4xx/5xx pages, detected bot checks, robots.txt skips, invalid URLs, pages that failed after the retry, prints that ran past the timeout, a failed merge, and a merge skipped over the memory limit. Successful-status login or paywall pages can still be printed and charged; there is no general login-wall detector. A URL listed twice is converted and charged twice. Prices were read from the Store on 21 Oct 2026; the Pricing tab is the source of truth.

Reliability

  • One bad URL never fails the run. Any failure becomes an error row with the reason.
  • Navigation errors and timeouts, and browser errors while printing, are retried once, after a short random pause, in a fresh browser context. HTTP rejections, bot checks and robots skips are not retried.
  • Timeouts apply per step. timeoutSecs limits page loading, then PDF printing, separately. A print that runs past the limit is reported, not retried: raise timeoutSecs for very long pages.
  • Lazy images: before printing, native lazy images are switched to load immediately, the page is scrolled at most 20 steps / about 5 s and back to the top, then it waits up to 3 s for images still loading. Images that load later may be missing.
  • Chinese, Japanese, Korean and emoji fonts are installed, so text doesn't print as empty boxes.
  • Invalid input (for example, no valid URL at all, or a paper size that isn't offered) stops the run at the start with a message saying what to fix. Nothing is charged.

FAQ

How do I convert a webpage to PDF? Put the page address in urls and run the actor. You get a PDF in the run's key-value store and a pdfUrl link in the dataset row. Paste many URLs to convert them all in one run.

Can I combine several web pages into one PDF? Yes. Set mergeIntoOne to true and the delivered PDFs are joined in input order into merged.pdf, with one bookmark per URL. The single PDFs are kept too.

Can I convert a whole website to PDF? It converts the URLs you list; it does not crawl links. Pass the pages you want, up to 500 per run. Cookie banners are hidden with CSS only (nothing is clicked), so custom pop-ups may still print.

Why does my PDF look different from the website? By default it uses the site's print styles, which many sites write to hide menus and ads. Set mediaType to screen to keep the on-screen look. Pages are laid out at paper width, so wide layouts may reflow; try landscape.

Does it respect robots.txt? Yes, by default. Before converting a URL, it reads that site's robots.txt (cached per origin) and skips URLs disallowed for all user agents (User-agent: *). A robots.txt that returns any 4xx status or can't be reached counts as "allowed"; one that returns a server error (5xx) counts as "disallow everything". Rules use longest-match precedence, * wildcards and $ end anchors; Allow wins ties. The final redirect target is checked before printing if its host differs (after the redirected request has happened). Turn respectRobotsTxt off only for pages you have the right to capture.

Does it get past logins, paywalls or bot protection? No. It never logs in, uses no proxy and doesn't evade bot protection. Recognized Cloudflare bot checks become uncharged errors. Other protections may not be recognized.

Why was my merge skipped? The merged file is built in memory, which takes about 5 times the size of the PDFs being joined. To keep the run from running out of memory, merging stops at PDFs totalling 10% of the run's memory (about 102 MB at the default 1 GB). The error row gives the size and the limit. Raise the run's memory (up to 4 GB) or merge fewer URLs per run. The single PDFs are delivered either way.

Can I convert raw HTML to PDF? Not as pasted text. It converts HTML pages from a URL, so put the HTML somewhere reachable (a static host or a public storage link) and pass that URL. It renders in a real Chromium browser, so CSS, web fonts and images print as they do on the page.

Troubleshooting

You see in errorCauseFix
"The page answered 404" (or another 4xx/5xx)The site returned an error statusFix the link. Error pages are never printed or charged.
"The site showed a bot check (Cloudflare) instead of the page"Bot-protection page detectedNot bypassed; never charged. Try again later.
"page did not finish loading within 45s" or "navigation failed: ..."Slow or unreachable page; retried onceRaise timeoutSecs or use waitUntil: domcontentloaded.
"PDF printing did not finish within 45s (very long page? raise timeoutSecs)"A very long page took too long to printRaise timeoutSecs (up to 180). Not retried.
"PDF printing failed: ..."Browser error while printing; retried onceRun again; if it repeats, open an issue with the URL.
"skipped: robots.txt disallows this URL ..."Site robots.txt blocks the URLSet respectRobotsTxt to false only for pages you have the right to print.
"not a web URL (expected http:// or https:// and a host name)"Entry is not a web linkFix the entry.
"merge skipped: X MB of PDFs exceeds the Y MB limit at Z MB memory ..."Merge limit is 10% of run memoryRaise memory (up to 4,096 MB) or merge fewer URLs. The single PDFs are still delivered; no merge charge.
"merge failed: ..."A stored PDF could not be read back or joinedRun again; single PDFs are unaffected and not charged twice.
Status message "no merged file: fewer than 2 PDFs were delivered"mergeIntoOne needs 2 or more delivered PDFsAdd URLs; no merge charge.
Out of memory with many parallel pagesEach parallel page needs memoryLower maxConcurrency or raise memory.

Limits

  • Up to 500 URLs per run, http and https only.
  • Paper sizes: A4, Letter and Legal. No custom sizes, page ranges, custom header or footer text, watermarks, encryption or password protection.
  • Very long pages make large PDFs and can take longer than the default 45 s timeout.
  • The default maxConcurrency is 2 at the default 1 GB memory; image-heavy pages use the most memory. Raise memory for heavy sites or higher concurrency, and check the "Peak memory" line at the end of the run log.
  • Merging is limited to PDFs totalling 10% of the run's memory: about 102 MB at 1 GB, 409 MB at 4 GB. Over the limit, no merged file is made and merge isn't charged; you get an error row saying so, and every single PDF is still delivered.
  • No raw-HTML input, custom cookies or headers, proxies or geo-targeting.
  • For PNG or JPEG images of pages, use Website Screenshot API.

Support

Is a page not converting correctly? Open an issue on the Issues tab with the URL and your input.