DocuSeal
Open-source document signing and fillable PDF forms, self-hosted or cloud.
Opens the vendor's own site.
Jobs covered
Open a task to see exactly what the vendor documentation supports.
Sign
Browse all sign toolsrunning a document signing workflow in DocuSeal by uploading a document or starting from a template and placing fields with the PDF form builder, adding multiple submitters who are invited by automated email to review, fill and sign, with signatures drawn or typed in the signing tool or applied as a signature image, after which each submitter receives a copy of the filled and signed files and the completed PDF is automatically signed with a platform PDF eSignature that can be verified through the platform for authenticity, with an audit log available alongside the completed document
Edit
Browse all edit toolsbuilding fillable PDF form templates and placing fields through the WYSIWYG field builder, embedded text field tags or the HTML API; not general PDF content editing
Where your files are processed
Reported to upload your files
The vendor states that files are uploaded to their servers. We have not independently tested this. That is a property of the library itself: what an application built with it does with your file depends on that application, not on this.
Cloud service: uploaded documents and user data are stored on DocuSeal’s cloud, primarily AWS US-Northern Virginia, with a separate EU cloud. The on-premises edition runs on servers you control, and self-hosting is a deployment choice rather than a guarantee about every communication: the project documents local disk or AWS, Google and Azure storage, and SMTP for delivery, so what leaves the organisation depends on how it is configured.
Recipient delivery, SMS verification and webhooks are further configured paths, so hosting and recipient access are separate facts.
What it does
An open-source platform for building fillable PDF forms and collecting signatures. A visual builder places signature, date, file, checkbox and other field types; documents go out by email, shared link or an embedded signing form, with audit logs and optional SMS identity verification.
It runs as a self-hosted Docker deployment or on the vendor's US or EU cloud, with a free tier and a paid Pro plan that unlocks email volume and integrations. Self-hosting is a deployment choice rather than a guarantee about every communication: the project documents local disk or AWS, Google and Azure storage, and SMTP delivery, so what leaves the organisation depends on configuration.
Best for
Developers and small businesses that want an embeddable, self-hostable signing and form-filling engine they can white-label.
Worth knowing
The free cloud tier allows only ten signature request emails a month, and bulk send, SSO, automated reminders and white-labelling need Pro. The licence is AGPL-3.0, and the Section 7(b) additional terms require that interactive interfaces retain the original attribution.
That is an attribution condition rather than a ban on commercial or competing use, so the two should not be run together; Pro features carry their own separate licence. Read the exact version’s licences before building on it, and take your own advice on what the AGPL obliges you to do.
Self-hosting decides where the documents live, not what every configured path transmits: storage backend, SMTP delivery, recipient access, SMS verification and webhooks are separate facts, and each follows from the configuration rather than from the licence.
Details, and where each comes from
Vendor statements, our own reading of their pages, and the things nobody has established yet, each answered separately. Where we have not confirmed something it says so rather than guessing, and a row nobody has established is greyed out.
- Versions covered
- Web · API · Self-hosted
- Website
- docuseal.com
- Requires an account
- Not applicable
- Watermark on the free tier
- Not verified
- Maximum file size
- 100 MB
- Batch processing
- Yes
- Data residency
- Multiple regions
- Open source
- Yes
- Self-hostable
- Yes
- Licence
- AGPL-3.0 with Section 7(b) additional terms
- Redaction
- No redaction feature
- Programmatic access
- HTTP API · Embeddable library
- Last availability check
- Responded in 61 ms 21 October 2026
Checked automatically by our own runner, not reported by the vendor. 100% of our last 30 checks got a response.
What the redaction verdict rests on
From the vendor's own documentation, read 22 September 2026. Not tested by us.
What that does not establish
The vendor’s own site was read on 22 September 2026 and contains no mention of redaction, sanitisation, blackout or whiteout. Absence from a vendor’s own material is not proof that a feature does not exist - it may be undocumented, or on a page the reading did not reach - but for a NEGATIVE claim it is the strongest evidence available, and it is weaker than a positive quote.
Recorded as such rather than presented as certainty.
What the vendor says
Claims are labelled rather than repeated as fact. Where we have checked something ourselves, it says so and shows when. Checked means we read the vendor's own page and it says what we recorded - not that we tested the behaviour, unless the note says we did.
-
“Free forever for individuals, extensible for businesses and developers.”
Checked by us - the source says this Read 22 September 2026
Confirmed verbatim: the sentence appears unaltered on the homepage. The scope is doing the work - "free forever for individuals" - and the same sentence offers the paid dimension for businesses and developers, where "extensible" is a licensing word rather than a price one.
So the claim is honest and narrower than "free forever" would read alone, which is the opposite of the usual direction of drift in this tier. DocuSeal is open source, so the individual tier is not a promotional concession.
Recorded as the vendor's description; no account was created.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 45fc7dddd3896718926f12ae310bc789302072e2a9b1ae141f986896905a0688
How we checked
Re-verified verbatim on 2026-09-22: https://www.docuseal.com/ re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-www-docuseal-com-eebe3bea.txt.
-
“DocuSeal is an open source platform that provides secure and efficient digital document signing and processing.”
Checked by us - the source says this Read 22 September 2026
Confirmed verbatim: the README opens with the sentence exactly, and it continues into a description of PDF forms filled and signed online on any device. The word doing the work is "open source", which the repository supports by existing in public; whether the licence permits a given commercial use is a separate question this page does not answer, and no licence file was read for this entry.
Recorded as the project's description; no control was run.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- a7cff554844e9f7c2cc1dfff08486d205135d892d8fdd71f555dca161711629e
How we checked
Re-verified verbatim on 2026-09-22: https://github.com/docusealco/docuseal re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-github-com-docusealco-docuseal-cca5da9a.txt.
Each claim is quoted from the vendor's own pages. This section describes what we have and have not checked - it is not a judgement about anyone.
Sponsorship is distribution, not an endorsement or a promise of search rankings, AI citations, traffic, or sales. This listing is a free entry, compiled from published sources.
Related reading
- Open source PDF tools, and what their licences require - what open source does and does not tell you.