How webcapture is run
webcapture is a URL to PDF API: one REST call renders a public web page as a print-stable PDF, the same call captures full-page PNG, JPEG, and WebP screenshots, and Markdown extraction comes with it. Rendering runs in headless Chromium.
Who runs it
webcapture is built and maintained by one systems engineer in Hong Kong. That fact sits on this page instead of a team photo because it is the honest answer. It also makes accountability direct: the inbox that answers hello@webcapture.io is the inbox that ships the fixes.
How the claims on this site are made
The comparison tables come from the vendors' own documentation. Check dates are printed beside the tables, and webcapture's own gaps are named in the same tables: the capability matrix holds eight vendors on fourteen rows with our missing cells marked. The security page lists compliance gaps, not badges.
What is kept, and for how long
Rendered files are the only copies this service holds, and they auto-delete after 7 to 30 days, depending on plan (tiers.ts). Leaving is easy: billing runs through Stripe and your outputs are plain files.
Method
Checked 2026-10-19 against the running code. Questions: hello@webcapture.io. Corrections and feedback: feedback.webcapture.io.
Render your first page in seconds
Mint a key, POST a URL, and the finished document comes back in the same response; pass ?wait=false for a job ticket with poll and download URLs. The first 50 renders a month are free, and there is no credit card. Not ready for a key? The free URL to PDF tool renders public pages without one.