Skip to content
Lite + Pro Lite limits

Changelog

All notable changes to WPsigner are documented here. Each release lists Edition impact (Lite, Pro, or Both) and Docs links to the guides you should re-read after updating.

LabelMeaning
Edition: BothBehavior exists in Lite and Pro (or shared core)
Edition: ProRequires WPsigner Pro (or a Pro addon / integration)
Edition: LiteAffects the free WordPress.org edition
DocsOfficial guides to open after you update

Compare editions anytime: Lite vs Pro. New to WordPress.org? Start with First Document on Lite.

September 17, 2026 · Edition: Pro

LearnDash settings stay usable when LearnDash is already active. Enable and Save are not locked if detection fails on that admin screen (renamed plugin folder, Multisite, or a tool that unloads LearnDash only on WPsigner pages).

Docs

September 17, 2026 · Edition: Pro

LearnDash can use a different WPsigner template per course. Set a default template, then override it next to each gated course.

Docs

September 16, 2026 · Edition: Pro

The orange signature box on a Formidable E2Pdf feed is saved with the feed. New submissions place “Click to Sign” where you dragged it.

September 16, 2026 · Edition: Pro

Formidable feeds read the signer email from confirmation fields, field keys, and labels such as “correo”. The document is sent and the browser opens the signing page instead of staying in draft.

September 15, 2026 · Edition: Pro

Show WP Menu restores the WordPress admin bar and sidebar immediately. The WPsigner header no longer shifts into an empty 160px gap.

September 15, 2026 · Edition: Pro

Formidable E2Pdf feeds create the document and redirect to signing even when the form On Submit action is “Show message”.

Docs

Formidable + E2Pdf

  • Formidable 6 On Submit actions are rewritten to redirect to /insigner/{token}
  • AJAX submit listens for the signing URL if the success HTML does not run scripts
  • E2Pdf also uses [e2pdf-download] and same-site PDF URLs when [e2pdf-save] does not return a file path

September 15, 2026 · Edition: Pro

Form feeds can map a first name and an optional last name when those are separate fields.

Docs

Signer name mapping

  • First name / full name is required
  • Last name is optional — use it when first and last are independent fields
  • Leave last name empty when one field already has the full name (combined Name fields still join First + Last automatically)

September 15, 2026 · Edition: Pro

Formidable integration feeds keep every field when you save, and Edit shows the current setup.

Docs

Formidable feeds

  • E2Pdf tag on the feed card
  • Edit restores form, E2Pdf template, signers, signature boxes, and After submit
  • After submit sends the signing email or redirects to the signing page from the saved feed

September 15, 2026 · Edition: Pro

E2Pdf Formidable feeds include the visual signature placer again.

Docs

Formidable + E2Pdf

  • Signature placement on the feed: drag or resize the orange box on the E2Pdf page preview
  • Saved X / Y / page / size are the coordinates used on the signing page

September 15, 2026 · Edition: Pro

Formidable Forms feeds can generate the PDF with E2Pdf again, then send it through WPsigner for signing.

Docs

Formidable Forms + E2Pdf

  • If the E2Pdf plugin is active, the Formidable feed shows an E2Pdf template dropdown
  • E2Pdf fills the PDF from the Formidable entry; WPsigner adds a signature box and invites the signer
  • Do not pick a WPsigner PDF template on the same feed. Extra signers and sequential / parallel order still apply
  • Approver role from 3.2.20 is unchanged

September 9, 2026 · Edition: Both

A participant can approve the document before anyone is invited to sign.

Docs

Approver role

  • On Add Signers, set Role to Approver (or Signer)
  • That person receives a Review & Approve email, not Review & Sign
  • The public page shows the PDF with Approve and Reject — no signature pad
  • Signers are emailed only after every approver accepts
  • Reject (optional reason) marks the document declined and notifies the sender
  • The signed PDF no longer draws a blue bar across the top. Each page keeps the same notice at the bottom edge, without a fill: ELECTRONICALLY SIGNED, the date and SHA-256 hash, and the certificate ID.

September 9, 2026 · Edition: Pro

Formidable Forms feeds use a WPsigner PDF template or content signing only.

Docs

Formidable Forms

  • The feed no longer offers a third-party PDF companion. Extra signers and sequential / parallel order stay on the feed
  • Saved feeds that pointed at that companion stop creating documents until you pick a WPsigner template or use content signing

September 9, 2026 · Edition: Pro

Page count and size for generated PDFs are read with FPDI so multi-page files are counted correctly.

Docs

PDF page metrics

  • Page count comes from the generated PDF (FPDI), not a /Count regex that often returned 1
  • Page 0 stays “last page of the signed file”
  • Placement is stored in PDF.js viewport points and scaled if the preview page and the generated page differ in size

September 9, 2026 · Edition: Pro

Signed PDF download no longer fails with “File not found” when PHP GD is missing.

Docs

Signed PDF

  • Stamping a drawn signature without GD no longer aborts the whole completed PDF
  • If flattening still fails, WPsigner serves a copy of the source file so the download works
  • Ask the host for php-gd so the signature image appears on the page

September 9, 2026 · Edition: Pro

Signature boxes on a Formidable feed can be resized by dragging a corner or edge.

Docs

Formidable feed editor

  • Drag a corner or edge of a signature box to resize it. Width and height update as you drag; you can still type the numbers.

September 9, 2026 · Edition: Pro

Reopening a Formidable feed keeps name, email, extra signers, and signature boxes.

Docs

Formidable feed editor

  • Reopening a feed restores name, email, extra signers, and signature boxes (a slow getFeed no longer saves empty defaults)
  • Add signature box — the same signer can have several boxes (initials, page 2, etc.)

September 8, 2026 · Edition: Pro

A Formidable feed can take two (or more) signers without a PHP snippet.

Docs

Formidable extra signers

  • Additional Signers on the Formidable feed (name + email field per person)
  • Sequential signing emails signer 2 after signer 1 finishes; the document is completed only when everyone has signed
  • Parallel invites everyone at once (extra signers still get email if the form opens the signing page)

September 7, 2026 · Edition: Pro

The signing PDF loads on phones again.

Docs

Mobile signing

  • The zoom wrapper keeps full width on small screens, so pages are no longer sized to 0 px
  • Pinch zoom freezes the page layout and only uses transform: scale, so signature fields stay on their boxes
  • The PDF URL carries a short-lived session, not only a cookie, so Safari, in-app browsers, and the app WebView can fetch the file
  • PDF.js loads the file on the main thread; if the worker is blocked it retries without it

September 6, 2026 · Edition: Pro

Formidable Forms at parity with Fluent Forms. Follow-up fixes keep the signing pad as a pad, skip spam false positives on the signature image, show a signed-PDF download after content signing, and keep WooCommerce HPOS declared during recovery mode.

Docs

Formidable Forms

  • Content signing — Name + email + WPsigner Signing (Lite and Pro) or the native Pro Signature field. Feed optional (CC / document title only)
  • OTP — Email, SMS, both, or WhatsApp on the Signing field, same as Fluent Forms
  • PDF template feeds — Field mapping dropdowns, open-for-signing redirect or email request, CC field + extra addresses
  • Signed PDF download — After content signing, Formidable’s success message shows Download Signed PDF. Tags still work in emails: [wps_signed_pdf_url], {inSigner:signed_pdf_url}, {inSigner:download_button}
  • Pad on Formidable 6 — The field registers as its own type so Formidable does not turn it into a text input
  • Spam — Formidable denylist and WordPress disallowed-comment keys skip the PNG data URI so a real signature is not “blocked spam”

Signing zoom

  • Desktop: Ctrl or Cmd + mouse wheel (trackpad pinch counts). Mobile: two fingers. No + / − bar and no zoom label

WooCommerce

  • HPOS (custom_order_tables) and Cart/Checkout Blocks are declared on before_woocommerce_init before recovery mode can exit. Plugins → “Incompatible with WooCommerce features” should not list WPsigner after a recovered fatal

September 3, 2026 · Edition: Pro

ChatGPT / Custom GPT engine over insigner/v1/ai/*. Sending requires the user to confirm.

Docs

ChatGPT

  • Integrations → ChatGPT — Site URL, AI API base, API key link, OpenAPI download, and Custom GPT instructions
  • RESTGET /ai/templates, GET /ai/templates/{pdf|builder}/{id}, POST /ai/preview, POST /ai/send, POST /ai/from-content, GET /ai/openapi
  • Human confirmationsend=true is refused unless confirm=true. Preview fields with the user first
  • Merge tokens((name)), ((country)), ((date:start_date)), ((signature:1)) in Document Builder text become fields. {{name}} also works. Signature and initials stay empty for the signer
  • from-content — Requires the Document Builder addon

September 1, 2026 · Edition: Both

Silent zoom on the signing page: Ctrl/Cmd + wheel on desktop, pinch on mobile. No zoom buttons. Fields stay aligned with the PDF.

Docs

August 31, 2026 · Edition: Pro (app / REST)

App endpoints match WordPress audit and send gates.

Docs

  • Documents API

  • Security & Compliance

  • Fields from the appPOST /documents/{id}/fields keeps field keys and resolves conditional logic after save

  • Review securityGET /signing-gates and send accept OTP, KYC, and access code with the same Always / Per document / Off rules

  • In-person access code — Host signing from a draft runs the same send gates

  • Signed PDF downloadGET /documents/{id}/file no longer decrypts the completed PDF incorrectly. Add ?variant=certificate for the Certificate of Completion. PATCH cannot set status to sent

  • Mobile auditGET /documents/{id}/audit returns the same header, signers, KYC, hashes, timestamps, cloud backups, and timeline as wp-admin

  • Didit reportGET /documents/{id}/kyc-report?signer_id= downloads the same compliance PDF

  • Faster mobile listGET /documents skips per-row disk checks. Detail omits fields unless include_fields=1

August 31, 2026 · Edition: Pro (app / REST)

Docs

  • Documents API

  • Statistics API

  • Void from the appPOST /documents/{id}/void cancels a draft, sent, or viewed document and writes document_voided. Signing links stop

  • Upload and send — If a document has no fields when it is sent (or opened in person), WPsigner places one signature box per signer

  • StatsGET /stats includes cancelled

August 29, 2026 · Edition: Both (sender-chosen access codes) · Edition: Pro (Fluent Forms CC field)

Sender-chosen access codes with an optional prompt, safer delivery of known secrets, and Fluent Forms CC from a form field.

Docs

Access codes

  • I’ll set the access code — 4–8 digits you choose (last 4 of SSN, date of birth MMDDYYYY, and similar), plus an optional Signer prompt on the signing page
  • Generate a random 6-digit code — same as before; after send you can still copy the PIN
  • Include access code in signing email — off by default when you set your own code, so the invite can be the link only
  • Request access code — only for random codes, and only to the signer’s email or the phone already on file. Known secrets cannot be resent from the signing page
  • Existing documents keep their hashed PIN. You do not need to resend pending envelopes

Fluent Forms (Pro)

  • CC email field on the feed — map a Fluent Forms Email field (typed or filled from the URL) onto the signed-PDF / completion CC
  • Additional CC emails — optional fixed addresses, combined with the mapped field
  • Works for content-signing feeds and PDF-template feeds

August 22, 2026 · Edition: Pro

Unicode signed PDFs, WordPress user picker on Add Signers, and an optional per-signer WordPress login gate. This is the release that includes the work built on top of 3.1.3 (Appearance and Bulk Send stay in that version).

Docs

Signed PDF fonts

  • Languages → Signed PDF fonts — Optional Noto packs so flattened signed PDFs keep accents and non-Latin scripts. Does not translate the WPsigner screens
  • Packs — Accented Latin (Vietnamese, Turkish, Polish, and other Latin languages with accents), Japanese, Chinese Simplified, Chinese Traditional, Korean, Arabic, Hebrew, Thai
  • One active pack — Install only what you need. Use for signed PDFs sets the active pack. Files download to uploads/wps-pdf-fonts/ after install and are not inside the plugin ZIP

WordPress signers

  • User search — Type at least two characters in a signer name or email to pick an existing WordPress user
  • Add me as signer #1 — Fills the first row with the current account. Does not turn on the login gate by itself
  • Signer order — The first person you add is Signer #1 (their signature fields). Drag rows to change the order
  • Use Template — Same search and checkbox per slot (for example signer #1 must log in, signer #2 can be a guest)

WordPress login for a signer

  • Per signer, off by default — Check Require WordPress login with this email. The email must already belong to a WordPress user (the checkbox is turned off if it does not). The signing token is not enough; the WordPress account email must match that signer
  • Same message on the signing page — Log in (or log out and switch accounts) and return to the document
  • Does not replace OTP, KYC, or access codes
  • No campaign hybrid — An active public campaign cannot share a document with a gated signer, and you cannot turn the checkbox on while a campaign is active. Individual links for those signers are not redirected to the campaign URL. Public reuse of that email still requires the matching WordPress login
  • Bulk Send and public guests — CSV rows and new public-campaign signers do not get this gate

Download from your Account Portal.

August 20, 2026 · Edition: Both (Pro 3.1.3, Lite 1.0.2)

Official compatibility with WordPress 7.1 and WooCommerce 11.0.1. WPsigner’s document editor and signing pages are not Gutenberg blocks, so the always-iframed post editor in 7.1 does not affect sending or signing. The WooCommerce integration uses the order API (HPOS) and does not customize the checkout form.

Pro also adds Appearance (brand, signing-page buttons, and client portal on one page) and Bulk Send (CSV invitations from a template, with a tag you name for each send).

Docs

Signing page buttons (Pro)

  • Signing Page tab — Under More → Appearance. Pixel controls for font, padding, corner radius, and border width, plus color, hover, style (solid / outline / soft), weight, and width. S / M / L remain as shortcuts that fill the pixel fields
  • Live preview — Sidebar mockup updates as you edit, with a light/dark toggle and a contrast warning when text is hard to read
  • Applied everywhere signers tap a primary action — Finish, Apply, OTP, KYC, the public “start signing” button, and campaign embeds. Decline stays red
  • Brand color finally reaches the signing page — A custom Primary Color from Appearance → Brand now styles signing buttons. Stock plugin blue/indigo is unchanged until you save a custom button color
  • Button labels stay in Custom Texts — Finish, Complete, and Decline copy is still edited there
  • No flash of default styles — Brand colors, theme, and fonts apply on the first paint so signers do not see a generic look first
  • Appearance hub — Brand, Signing Page, and Client Portal are tabs on one Appearance page. Previous Signing Appearance and Client Personalization URLs redirect there

Bulk Send (Pro)

  • Documents menu — New Bulk Send item next to Documents, plus a button on the Documents list
  • CSV — Download a sample file (name, email, optional title). Up to 200 rows
  • Batch name = tag — You name the send; every document in that send gets that tag so you can filter the batch in Documents
  • Emails in batches — Default 4 per step (1–20). Pause, cancel, or leave the page; leftover batches continue via cron

Download from your Account Portal. Lite updates via WordPress.org.

August 20, 2026 · Edition: Pro (official addon)

Native Uncanny Automator integration: field tokens and prefill, cloud/payment/delete triggers, messaging actions, signer loops, and a settings page for signing-URL privacy.

Docs

1.2.0

  • Dynamic template signer-slot hint (AJAX) and up to five signers on create
  • Template FIELD_* tokens and variable prefill (key=value or JSON)
  • Triggers for cloud backups, document update/trash/delete, Stripe fail/refund
  • Channel reminders (WhatsApp, SMS, Slack, Telegram, Teams) and Slack custom message
  • Automator Pro condition “signer is a WordPress user” and loopable signer tokens
  • Settings to hide signing URLs and field values; hourly create cap

Previously 1.1.0 added certificate/owner/tag tokens, PDF and Stripe succeeded triggers, tag/signer/expiration actions, and the “document has tag” condition. 1.0.0 was the initial integration.

August 3, 2026 · Edition: Pro (forms integrations)

Fluent Forms and WPForms reliability for larger forms with inline signing and OTP, safer signer name detection, and a clearer PDF field editor (name / mapping popup and delete control).

Docs

Forms & OTP

  • Fluent Forms OTP submit — Large forms with signature + OTP no longer fail with “Please verify your identity…” after a successful verification. The token is kept through Fluent Forms’ AJAX submit (with a browser-session fallback)
  • Fluent Forms email field — OTP uses the feed’s mapped signer email instead of guessing the wrong field on complex forms
  • WPForms OTP + feeds — Same reliability: session OTP fallback, smarter name/email detection (avoids “Username”), OTP only when a signature is present, and content-signing feeds save without forcing a template
  • Signer name field — Name detection no longer mistakes “Username” for the person name; Fluent Forms names (first/last) is preferred
  • Content-signing feed save — Saving a feed for inline signing no longer asks for a template when Feed Name and Form are already set

PDF field editor

  • Field Properties (double-click) — Set Field name, optional Mapping name (Zapier / forms / API), and Placeholder. Empty mapping uses the field name (slugified). Docs: Form fields
  • Floating popup — The editor opens outside the field box (not clipped inside it)
  • Delete (X) — The remove control sits outside the field corner again

Content signing

  • Multiple signatures (Fluent Forms / WPForms) — Forms with several WPsigner Signing fields include every filled signature on the generated PDF, each with its field label
  • Form tags in Documents — Documents created from form integrations get a tag like “Form: [form name]” (same idea as Campaign tags)
  • Certificate of Completion (forms) — Signature thumbnails load correctly for content-signing documents; multiple Signing fields appear as separate cards labeled with the form field name (e.g. Client / Witness)

Download from your Account Portal.

August 1, 2026 · Edition: Pro (portals, campaigns, team roles) · shared admin/diagnostics for Pro installs

A clearer admin experience, better portals, smarter team access, more reliable campaigns, and safer storage tools. Your existing documents and signer data are kept when you update.

Docs

Easier admin screens

  • System Status is a practical diagnostics hub (compatibility, storage, cron repair, and cleanup tools when you need them)
  • Storage & Retention uses the same clear layout as the rest of WPsigner
  • License page matches the standard WPsigner admin design (activate, verify, renew, and remove license with less confusion)
  • Signer Protection cards (OTP, KYC, Access Code) line up evenly on Security & Compliance
  • Security settings save button stays aligned correctly

Client Portal and Admin Portal

  • Cleaner Client Portal login and document list (items that need attention appear first)
  • Option to hide your theme header and/or footer on portal pages
  • “Enable Client Portal” now saves correctly
  • Front-end Admin Portal: clearer stats, activity, and “needs attention” view

Team access that matches each role

  • Dashboard shows all documents for Managers, Viewers, and Admins; Senders still see only their own
  • Viewers no longer see a New Document button they cannot use
  • Users page works for inSigner Admins (not only WordPress Administrators)
  • Clearer “No Access” option when assigning roles

Campaigns — one completed document per signature

  • Each campaign signature is saved as its own completed document in Documents, with the campaign tag
  • Audit trail opened from a submission focuses on that independent signed document (not the shared template)
  • Campaign signed PDFs and certificates no longer show the internal “Campaign template” as a signer
  • Empty “Pending” boxes from that template no longer appear on campaign PDFs
  • Campaign links stay open for many people to sign; the shared template is not closed after the first submission
  • Legacy shared-template submissions are promoted to independent documents when you open Submissions, Audit, or Download

Fields and languages

  • New VAT field type available in the PDF editor, campaigns, Document Builder, and the signing page
  • Language pack updates correctly overwrite short-locale .mo copies and refresh WordPress translation file cache
  • Locale fallback prefers regional packs (for example es_ES) over stale short codes (es)

Storage — Delete Everything

  • Storage → Delete Everything permanently removes all documents and PDFs (including signed), plus templates, campaigns, submissions, tags, payments, and audit logs
  • Runs in safe batches so large libraries do not time out the server; keep the page open until it finishes
  • Plugin settings and license are kept

Signing experience and small fixes

  • Legal Notice from settings is included on the certificate page of the signed PDF
  • Telegram Chat ID in the document wizard only appears when Telegram is connected
  • Signing page “Page X of N” controls stay readable with common themes (including Astra and WooCommerce)
  • Creating and sending signature requests is done in WordPress admin under New Document; the front-end Admin Portal is for reviewing status
  • Production ZIPs are Linux/WordPress-compatible (forward-slash paths) with UTF-8 encoding verification before packaging

Download from your Account Portal.

July 2026 (maintenance builds after 3.0.0) · Edition: Pro

Incremental fixes and integration improvements shipped between 3.0.0 and 3.1.0, including Fluent Forms feed UI and OTP, Contact Form 7 parity, WhatsApp Complete Setup, language packs foundation, Storage & Retention tools, and related hardening. These builds are superseded by 3.1.0.

Docs

July 2026 · Edition: Pro

Major release with official addons, Fluent Forms content signing, and Stripe improvements.

Docs

  • Addons Overview

  • Account Portal

  • Smart Signing Forms

  • Fluent Forms

  • Stripe

  • Addons marketplaceWPsigner → Addons to install and activate official extensions

  • Account Portal integration — Download addons from app.wpsigner.com

  • Smart Signing Forms (addon v1.6.0) — Drag-and-drop signing forms with design presets, OTP, Stripe payments, and signed PDF output

  • Fluent Forms content signing — Sign inline with the WPsigner Signing field; PDF generated from form content without a template feed

  • Fluent Forms OTP — Email, SMS, and WhatsApp verification on the Signing field before submit

  • Fluent Forms merge tags{inSigner:signed_pdf_url} and {inSigner:download_button} in notification emails

  • Stripe — Server-side PaymentIntent verification, webhook hardening, restricted API keys (rk_*) recommended

  • Submission blocked when content-signing PDF generation fails (no orphaned Fluent Forms entries)

  • Security and compatibility improvements across signing and integrations

Download from your Account Portal.

Edition: Pro · Docs: Smart Signing Forms

  • 4-step wizard: configuration, form builder, design presets with live preview, compliance
  • Field types: signature, payment (Stripe), OTP, columns, conditionals, file upload, and more
  • Stripe Payment Element flow with server-side payment verification before PDF generation
  • Entry management with signed PDF download and audit trail links

June 10, 2026 · Edition: Both (field editor / signing UX) · Pro addons page

A major update to the field editor and the signing experience.

Docs

  • Form Fields

  • Creating Documents

  • First Document on Lite

  • Quick Start

  • Addons Overview

  • Checkbox groups — place checkboxes anywhere on the PDF and set optional, “pick at least one”, or “pick exactly one” rules.

  • Conditional fields — show, hide, or require fields based on what the signer answers.

  • Right-click menu on fields to clone, delete, or change checkbox options.

  • Checkbox stamp mode — drop one checkbox, then click to add more. Press Escape when you’re done.

  • Custom labels and placeholders — double-click any field to edit.

  • Addons page — Smart Signing Forms available; Flow Builder coming soon.

  • Better signing page on mobile, especially for long PDFs.

  • Fields stay in place when you zoom in the editor.

  • Dates and times now match your WordPress site timezone everywhere.

  • Saves no longer lose fields on multi-page documents.

  • Public document verification page works reliably.

  • Signing links and PDF viewing work better with caching and security plugins.

Download from your license portal.

April–May 2026 · Edition: Pro

Interim release with webhook reliability, admin tooling, and integration prep ahead of the 2.5.0 field-editor work.

Docs: Webhooks · REST API

March 4, 2026 · Edition: Pro (API / webhooks) · shared signing hardening

Security and reliability improvements:

Docs: REST API · Webhooks · Security & Compliance

  • Stronger protection for API access and signing order.
  • Webhooks fire correctly again when documents are signed or completed.
  • Better IP detection when your site uses Cloudflare or a CDN.
  • Safer storage for certificates and integration credentials.
  • General hardening across the signing page and admin.

February 24, 2026 · Edition: Pro

Docs: Didit · Twilio · Security & Compliance

  • Identity verification with Didit.me. Signers can now verify their identity with a government ID, selfie, and liveness check before signing. You set it up once and get real-time status updates.
  • SMS verification via Twilio. Signers can verify by text message, email, or both.
  • New option in settings to choose how verification codes are delivered.
  • The signing page now adapts based on the verification method you’ve picked.

February 12, 2026

  • Encryption is now set up automatically when you install the plugin. One less thing to configure.
  • Fixed Google Drive disconnecting when the token expired. Reconnection is handled automatically now.
  • Admin notices now link directly to the relevant setup guide instead of a generic settings page.

January 30, 2026

  • Redesigned the timestamp verification email. Much clearer now.
  • Blockchain verification links open a clean branded page instead of a raw URL.
  • Fixed an edge case where some timestamp providers were incorrectly filtered out.

January 20, 2026

  • IP detection now works correctly when your site is behind Cloudflare, load balancers, or reverse proxies.
  • All parts of the plugin now use the same IP source, so rate limiting and audit logs stay consistent.
  • Added support for custom proxy headers if your hosting setup needs it.

January 8, 2026

Big encryption upgrade. Your stored credentials are now much more secure.

  • Encryption keys come from your site’s unique WordPress configuration instead of the database.
  • Certificate passwords use stronger encryption with unique keys for each operation.
  • Tighter file validation across uploads, downloads, and templates.
  • Location lookups are encrypted in transit.
  • You’ll see a warning if encryption keys change after a site migration.

December 18, 2025

  • Fixed a crash on mobile with large PDFs (100+ pages).
  • Pages now load as you scroll, so your device doesn’t run out of memory.
  • Automatic cleanup for pages you’ve scrolled past.
  • Better performance on lower-end phones and tablets.

December 2, 2025

  • Rate limiting on all API and integration endpoints.
  • Security review of every admin form and input field.
  • Third-party credentials (API keys, tokens) are now stored encrypted.
  • Plugin uses ~12% less memory.

November 15, 2025

  • Reorganized the integrations page by category: Forms, Messaging, Automation, CRM, Cloud Storage.
  • Added “coming soon” labels for Make, n8n, Telegram, Gravity Forms, Dropbox, and Teams.
  • New card designs with official brand icons for each integration.

October 28, 2025

  • Fixed PDF viewer not loading on some shared hosting setups.
  • Fixed WhatsApp templates breaking when document titles have special characters.
  • Better loading indicators for documents over 20 pages.

October 6, 2025

Biggest release since launch.

  • WhatsApp Business. Send signing requests, reminders, and completion notifications via WhatsApp.
  • Integrations Hub. New admin page showing all integrations and their connection status.
  • Google Drive. One-click setup. Signed PDFs are saved to your Drive automatically.
  • License System. Manage plugin licenses through WooCommerce.
  • Smoother mobile signing with larger buttons and better scrolling.

September 8, 2025

  • Signers now see the full document first instead of being auto-scrolled to the first field.
  • Better keyboard navigation and accessibility across the signing page.
  • Fixed a validation issue with the consent checkbox on Safari and iOS.

August 11, 2025

  • OTP Verification. Signers confirm their identity via email before signing.
  • Location capture. Optionally log where signers are located for richer audit trails.
  • Browser, platform, and timezone are now included in the audit trail.
  • Consent checkbox gets its own timestamp for compliance records.

June 23, 2025

  • REST API. Full API with key management, permissions, and rate limits.
  • Zapier integration. Connect WPsigner to 6,000+ apps with real-time triggers and actions.
  • API documentation with examples in PHP, JavaScript, Python, and cURL.
  • Cleaner email templates.

May 5, 2025

  • Roles. 4 roles: Sender, Viewer, Manager, Admin. Each with specific permissions.
  • Download links for signed documents now expire after 48 hours.
  • You can add custom messages to signing request emails.
  • More reliable auto-reminders, even on sites with inconsistent WordPress cron.

March 17, 2025

  • Translations. English, Spanish, Italian, French, German, and Portuguese (Brazil).
  • All fonts and scripts are self-hosted. No external requests, fully GDPR compliant.
  • Pages load ~300ms faster.

February 3, 2025

  • Digital ID. Generate a self-signed certificate directly from the settings page.
  • Elementor Forms and Fluent Forms integrations. Turn form submissions into signing documents.
  • New system status page with a health score, auto-fix tools, and debug export.
  • Dashboard widget showing health score and pending reminders.

December 16, 2024

  • Security Center. New settings page with a real-time compliance score.
  • Upload your own certificates for Adobe-verified digital signatures.
  • Timestamp Authority integration for legally provable signing times.
  • 6-digit access codes for sensitive documents.
  • Compliance badges for ESIGN Act, eIDAS, and UETA.

October 28, 2024

  • Webhooks. Get real-time notifications when documents are signed, viewed, or completed.
  • Compatibility fixes for WP Rocket, LiteSpeed Cache, and Autoptimize.
  • Added Portuguese (Brazil), French, and German translations.

September 2, 2024

  • Document Wizard. 4-step guided flow: Upload, Signers, Fields, Review.
  • Sequential signing: set a strict order or let everyone sign at the same time.
  • One-click copy for signing links after sending a document.
  • White-label: use your own logo, colors, and footer text.

August 4, 2024

  • Multi-signer support. Up to 6 signers per document.
  • Color-coded fields so each signer’s fields are easy to identify.
  • Quick-share modal for signing links.

July 15, 2024

Initial release.

  • PDF upload with drag-and-drop.
  • Electronic signatures: draw, type, or upload an image.
  • Form fields: signature, initials, date, text, checkbox.
  • Automatic email notifications for signing requests and completions.
  • Audit trail with timestamps, IP addresses, and action logging.
  • PDF certificate of completion with QR code verification.
  • Works on desktop, tablet, and mobile.