Sign a document — or just certify one exactly as it stands — and it's registered with a tamper-evident fingerprint automatically. No paid "Digital ID" add-on, no envelope fees, no account needed to verify it. One browser tab does the editing, the signing, and the proof.
Built for documents where "is this the real one?" actually matters
In plain terms
When a document is signed or certified, we take its exact bytes — every word, every pixel — and turn them into a unique fingerprint (a string of characters called a hash). That fingerprint gets saved. Change even one letter in the document afterward, and the fingerprint no longer matches. Checking a copy just means: does its fingerprint match the one we saved? Yes or no, instantly.
Without this, a signed document is just a PDF — anyone could edit a clause after the fact and there'd be no way to prove which version was real. A tamper-evident seal removes that doubt. A landlord, an insurer, a court, or the other side of a deal can confirm — for free, with no account — that the copy in front of them is exactly what was agreed to, not a quietly modified version.
How it works
Sending, verifying identity, and proving authenticity are usually three separate products. Here they're three steps in the same workflow.
Open or write the document, add each signer's name and email, and drag their signature boxes onto the page. Everyone gets a private link — no account or app on their end.
See Send for Signature →Before a signature counts, a signer can be asked to confirm who they are — email OTP, a passcode, or a government-ID check — so the signature holds up as non-repudiable evidence, not just a typed name.
See Identity Verification →Once completed (or certified on its own, no signing required), the document gets a certificate page and a registered fingerprint. Anyone holding a copy confirms it's genuine at /seal — free, forever.
Try /seal →Not just post-signature
Most "certified signature" tools only seal what they signed themselves. Seal & Certify Document (in the app's Extras menu) registers a tamper-evident fingerprint of any document exactly as it stands right now — a report, an already-signed PDF from somewhere else, a final draft you want to lock in — and hands back a copy carrying its own certificate page.
It isn't a signature and doesn't claim to be one. It's proof that a specific file existed, unaltered, at a specific moment — the same evidentiary building block, without forcing a signing workflow onto documents that don't need one.
Open the editor →
Public & portable verification
A recipient, a lawyer, an insurer or a court doesn't have to trust your word or log into your portal. They upload the file at /seal and get an instant, cryptographic answer: does this match a sealed original on record, who signed it, and when — free, with no login, any time.
That's the opposite of a locked-down enterprise certificate store or a signature that only your own paid portal can confirm.
Try the verification page →
The full evidence trail
Every completed signature request and every certified document carries a Certificate of Signing or Certification: signer names, emails, timestamps, and — for Video Signing Room sessions — device, IP address and a full Audit Report you can export as PDF or CSV.
That's the actual thing a dispute turns on, and it comes bundled in rather than sold as a compliance add-on.
Read how tamper-sealing works →
Why it's different
DocuSign expects a finished document — edit it elsewhere first. Here you edit text, run OCR on a scan, place signature and identity checks, and verify the seal, in the same browser tab, start to finish.
Third parties check a document's authenticity by scanning the seal or visiting /seal directly — no account, no subscription, no dependency on you or your portal staying reachable.
Volume doesn't change your bill. One flat price for unlimited sending, and certification itself has never been a paid add-on here — unlike the "Digital ID" tiers on Acrobat or DocuSign's per-envelope credits.
Compare
The honest version: they have deeper enterprise integrations. We have a public verification hub, a built-in visual seal, and a price that doesn't scale with how many documents you send.
| Feature | EZ PDF Editor | Adobe Acrobat / Adobe Sign | DocuSign |
|---|---|---|---|
| Audit verification | Public 1-click hub (/seal) | Complex certificate stores & enterprise tools | Internal portal lock-in / paywalled logs |
| Visual stamp / seal | Automatic embedded seal & timestamp | Requires paid Digital ID add-ons | Separate paid add-on feature |
| Workflow friction | Edit, sign, verify — one web app | Multiple apps / cloud tools | Signature-only, no full PDF editor |
| Pricing model | Single flat platform price | Per-seat / enterprise tier lockouts | Strict per-envelope transaction limits |
| Identity verification | Native OTP / ID gate, included | High-tier enterprise requirement | Per-recipient ID verification charges |
| Certify without signing | One click, any document | Not offered as a standalone action | Not offered as a standalone action |
| Free tier that verifies for real | Unlimited public verification | Reader-dependent, limited | Trial only, then paid |
Competitor columns describe the common shape of the market as of September 2026 and are generalised on purpose — plans, add-ons and pricing change often, so check each vendor's current terms before deciding. Everything in the EZ PDF Editor column is live today.
Pricing
Editing, certifying and verifying stay free forever — including on the free plan. You only pay when you need to send documents out for signature at volume.
FAQ
It's a cryptographic fingerprint (a SHA-256 hash) of a finished document's exact bytes, registered the moment it's completed or certified. Change a single character afterward and the fingerprint no longer matches — so checking it proves whether a copy is the genuine, unaltered original.
Go to /seal, upload the PDF you want to check, and click Verify File Authenticity. It's free, takes seconds, and needs no account — you'll see whether it matches a sealed original on record, plus who signed it and when.
Yes. EZ PDF Editor edits, fills, signs, seals and publicly verifies documents in one browser tab — no per-envelope fees, no per-seat pricing, and no paid add-on required for a tamper-evident seal or identity verification, both of which sit behind extra-cost tiers on DocuSign and Adobe Sign.
Yes. Seal & Certify Document (in the app's Extras menu) registers a fingerprint of any document exactly as it stands right now and gives you back a copy with a certificate page — no signing or signers required. It's for proving a file hasn't changed, not for collecting a signature.
The record behind a signature: who signed, their email, the timestamp, and — for higher-assurance signings — their IP address, device and identity-check result. Every completed signature request and certified document carries this trail, viewable on the Certificate of Signing page and exportable as an Audit Report.
No. Public verification at /seal is free, unlimited, and needs no account — for anyone, not just EZ PDF Editor users. Certifying or signing a document does require a free account.
Yes. Certifying builds a snapshot of the document and gives you back a separate, certified copy — it doesn’t lock or replace what’s open in your editor. Keep editing freely; if you want a certified copy reflecting your latest changes, just certify again to get a new one. Your earlier certified copy stays valid and verifiable forever.
Electronic signatures are recognized across Canada under PIPEDA and the provincial e-commerce acts. What matters in a dispute is the evidence behind the signature — who signed, when, from where, and whether the document changed afterward. Every signing and certification captures that record and seals the result. This is general information, not legal advice.
Signing collects one or more people's electronic signatures on a document and seals the completed result. Certifying skips the signing step entirely — it registers a tamper-evident fingerprint of a document exactly as it already exists, signed by anyone or by no one, so you can later prove it hasn't changed.