WebPDF.pro

PDF pages as HTML elements.

pdf-file loads a PDF. pdf-page shows one of its pages, with text you can select, links that work and forms you can fill. All in the browser: no iframe, no server, no framework.

<script src=//new.webpdf.pro/.js type=module controls></script>
               <pdf-file id=f src=your.pdf></pdf-file>
               <pdf-page of=f></pdf-page>

controlsViewer keys on every page, like video controlsClick or Tab to a page: ← → turn pages, Q E rotate, Ctrl + − zoom, F fullscreen. Put it on the script, a file or a page: the nearest wins, and controls=- turns it off. Click for the docs ↗

Try it live Read the docs Free to evaluate, then from $9.

<pdf-page of=f svg>

One page,
three engines.

Choose how a page is drawn with one attribute. The page here is drawn by all three at once, a third each. Can you spot the seams?

Draw the page with
canvas=.jscanvas=iumsvg

Forms that never leave the device.

Click a field and type: the form is part of the page. Press Ctrl S on it to save the filled PDF, or export only the answers as XFDF. Nothing is uploaded.

<pdf-file id=form src=form.pdf></pdf-file>
               <pdf-page of=form></pdf-page>
<pdf-page of=form>

Signatures, verified on the page.

Add signatures and every signed field shows who signed, when, and whether the file changed since. Certificate chains, RFC 3161 timestamps, OCSP and CRL are checked with Web Crypto.

You choose whom to trust: your own root certificates, or the Adobe , EU , Microsoft and Mozilla trust lists.

aatlAdobe Approved Trust ListThe authorities Acrobat trusts for signed PDFs: about 180 roots, 0.4 MB.

eutlEU Trusted ListsThe qualified trust services of every EU and EEA country (eIDAS): about 880 authorities from 31 national lists, 29 MB.

msMicrosoftThe roots Windows trusts for document signing, from the CCADB: about 80, 0.14 MB.

mozMozillaThe roots Firefox and Thunderbird trust for signed email (S/MIME), from the CCADB: about 90, 0.14 MB.

<pdf-file id=s   src=signed.pdf trust:src=root.pem  signatures></pdf-file>
             <pdf-file id=law src=law.pdf    trust:stores="aatl" signatures></pdf-file>
             <pdf-page of=s  ></pdf-page>
             <pdf-page of=law></pdf-page>✏️ Edit the highlighted attributes
<pdf-page of=s>
<pdf-page of=law>

Built like the rest of the web.

Evaluate on your own site.

Everything works on any domain from the first line. Until a domain is licensed, its pages carry this light watermark with its name; localhost and *.test stay clean, and saved files never carry it.

<pdf-page of=form watermark=your-site.com>✏️ Type your domain

Pricing

Every plan has every feature: three engines, forms, signatures and updates. You pay for the domains that run without a watermark.

  1. Evaluate

    Free

    For trying it out.

    Try it live
  2. 1️⃣ Site

    $9per month$90per year

    For one site or app.

    • 1 domain + subdomains
    • No watermark
    • Email support
    Get a Site license
  3. 🌐 World-wide

    $49per month$490per year

    For agencies and teams.

    • Every domain and app
    • No watermark
    • Priority support
    Get a World-wide license

Free for 👨🏻‍🎓 academic research, 🧑🏻‍🏫 classrooms and 🏔️ open source. Tell us about your project.

Apply for a free license

Questions

Do PDFs leave the browser?

No. Pages are drawn, forms are filled and saved, and signatures are checked right in your visitor's browser. Checking a signature fetches certificate status and trust lists, never the PDF.

Which browsers are supported?

Current Chrome, Edge, Firefox and Safari, on desktop and mobile.

Does it work with my framework?

Yes. pdf-file and pdf-page are standard custom elements, so they work anywhere HTML does.

Where does the watermark show?

Only on screen, on domains without a license; never on localhost or *.test. Saved and exported files are never watermarked.

How is a domain licensed?

Tell us the domain or app and the plan. Once it is licensed, the watermark disappears there, with no change to your code.