BlogProduct
WPsigner for WordPress electronic signatures
Electronic signatures should adapt to the business. WPsigner keeps the workflow in WordPress. inSigner keeps it in a managed account.
The choice is where the PDF and the record are kept, and who operates that place.inSigner
Electronic signatures should adapt to the way a business already works. WPsigner is a self-hosted WordPress plugin: the PDF, the signers, and the audit record stay on that WordPress site unless an optional integration sends data elsewhere. inSigner is a managed cloud service for people who want to send a document without running a site. This note follows WPsigner's public introduction and the way inSigner works today. Counsel still decides whether a simple signature fits the document.
01 · What WPsigner is
What WPsigner is
WPsigner runs inside a WordPress installation. From the dashboard you upload a PDF, place fields, invite signers, and keep the signed file with its audit record on that site. The introduction describes two editions. Lite signs PDFs and limits invited signers to two. Pro raises that limit and adds templates, campaigns, and integrations. Hosting, a Pro license, and any third-party service you turn on are separate costs. The plugin does not charge a fee for each envelope.
Signers open a browser link. They do not need a WordPress account. When everyone has signed, the finished PDF can be downloaded with a certificate of completion. That package is the file and the record. It is not, by itself, a ruling on which signature level the document required.
02 · Signing without leaving WordPress
Signing without leaving WordPress
The introduction walks through a short sequence: upload the PDF, add each signer, choose a parallel or sequential order, place signature, date, text, and checkbox fields, then send. You can track the document from the same dashboard. Reminders and an expiration date are part of the workflow the documentation describes.
The same introduction names WooCommerce, Fluent Forms, Formidable Forms, and Elementor. A shop can ask for a signature around checkout. A form entry can start a signing request. That is useful when the customer relationship already lives on the WordPress site, because the agreement does not have to leave the tools the team already uses.
The useful question is where the file lives, and whether this document can use a simple signature.
03 · Why a self-hosted signature matters
Why a self-hosted signature matters
By default, document files and records remain on the WordPress infrastructure you control. Their documentation says data leaves that installation only when you configure an external service, and it gives cloud storage, identity checks, messaging, payments, and automation as examples. You also choose the hosting region, the backup policy, and how long the files stay.
Self-hosting puts server security, WordPress updates, plugin updates, and backups on the site owner. SHA-256, in their documentation, is a hash used to detect a later change in the file. It is an integrity check. It is not encryption, and it does not decide whether the signature is simple, advanced, or qualified. Their introduction treats the usual workflow as oriented to a simple electronic signature, and it says advanced and qualified signatures need further technical and provider conditions.
- ✓Will we operate the server, the updates, and the backups?
- ✓Does an integration we turn on send data outside WordPress?
- ✓Is a simple signature enough for this document?
- ✓Has counsel read the jurisdiction before the first send?
04 · WPsigner and inSigner
WPsigner and inSigner
Both products help a business move an everyday agreement off paper. WPsigner fits a team that already operates WordPress and wants the signing steps in wp-admin, with the file on that server. inSigner fits a person or a company that wants a managed account: upload the PDF, place the fields, send it, and download the completed file with its completion record. WordPress is not required.
The standard signature in inSigner is not a qualified electronic signature. QES for Europe is an Enterprise option, priced separately, and it is not on Essential or Pro. A certificate applied inside the WordPress plugin is a different control. It is not, by itself, a qualified electronic signature under eIDAS. In both products, the document, the jurisdiction, and the level of assurance still decide what is enough.
| Question | WPsigner | inSigner |
|---|---|---|
| Place | WordPress plugin on your site | Managed cloud account |
| WordPress | Required | Not required |
| Files | Your server, unless an integration sends them out | The account you sign in to |
| Record | Audit trail and a SHA-256 hash | Completion record and a SHA-256 hash |
| Level | Simple signature. A certificate is not QES by itself | Standard signature. QES is Enterprise only |
| Upkeep | Your hosting, updates, and backups | The service operates the platform |
05 · Which path fits the business
Which path fits the business
Choose WPsigner when the organization depends on WordPress, the signature should sit next to site activity, and the team will operate the hosting. Choose inSigner when the organization wants a managed place to send, sign, and keep the PDF, without maintaining a server for that workflow.
Country guides on this site name the public rule they discuss. A simple signature still depends on the document. Read the guide that matches the governing law, then ask counsel before the first send. The objective in either product is the same: finish the agreement and keep a record that shows what was signed.
Standard signatureQualified signatureWhere inSigner is legal
Primary sources
WPsignerWPsigner introductionEuropean Union: eIDAS Regulation (EU) No 910/2014






