A WordPress form signature field does one thing, and does it well: the person draws their name with a finger or a mouse, and the drawing is saved as an image with the rest of the form entry. For a sign-up sheet or an acknowledgement nobody will ever argue about, that is often all you need. What it does not produce on its own is the record that e-signature law describes and a dispute goes looking for: which text was on the screen, a separate agreement to sign electronically, a fingerprint tying the signature to that exact text, and a copy the signer keeps.
That is not a criticism of the field. It is a difference between two jobs.
What the form plugins offer
Of the four form plugins this article is about, three offer a signature field as an add-on and one leaves it to other people's plugins. From each vendor's own documentation:
Gravity Forms. The Gravity Forms signature field comes from its Signature Add-On, which Gravity Forms makes available with its Elite and Nonprofit licences. The person signs with a touchscreen, a mouse or a touchpad, and the signature is saved as a PNG image with the entry.
WPForms. The WPForms signature addon is included from the Pro licence up. It adds a Signature field to the form builder, and the signature is saved as a PNG with the entry, where it can also appear in notification emails.
Fluent Forms. The Fluent Forms signature field is a separate Signature Add-On, which Fluent Forms' own guide installs alongside Fluent Forms Pro. The drawing is converted to an image and stored on your server with the rest of the submission.
Contact Form 7. There is no signature field among the form-tags Contact Form 7 ships with. Several third-party plugins in the WordPress directory add one, and that is where a Contact Form 7 e-signature usually comes from.
Each of these does what it says. A person draws, and the drawing is kept with what they typed. The question is what that amounts to a year later.
What an image in an entry shows
What a WordPress form signature field leaves you is an entry showing that somebody drew something in a box on your form and submitted it with the other fields. That is real evidence, and it is worth something.
What it cannot show by itself is the rest. The terms were a paragraph on the page, or a link to another page, and either can be edited next week without the entry knowing. The drawing is a picture in one place and the text it was meant to accept is in another, and the only thing joining them is the entry's say-so. The person who signed went away with a confirmation message, which is not a copy of what they agreed to. Some of that can be closed with more add-ons — a PDF of the entry emailed to the person, for instance — and whether that is enough depends on what the form is for.
What e-signature law asks a record to show
ESIGN and UETA define an electronic signature broadly: an electronic sound, symbol or process, attached to or logically associated with a record, and executed or adopted by a person with the intent to sign it. A drawing saved with a form entry can fit that description. The definition is rarely where the difficulty is.
The difficulty is in what the rest of the record can show, and that follows the four things set out in what the ESIGN Act and UETA actually require.
Intent. The person meant to sign: a distinct act, understood as signing, with the document in front of them.
Consent to sign electronically. UETA applies only between parties who have agreed to deal electronically, and ESIGN adds its own consent steps for consumers in some cases. A signature box on a form is one act. Consent recorded separately, before the signature, is two.
Association with the record. The signature is attached to, or logically associated with, the exact document. A fingerprint of the text, taken at the moment of signing and kept with the signature, is how a record shows which document that was.
Retention. Both laws speak of a record that accurately reflects what was agreed and stays accessible for later reference, and where a law requires something to be given to a person in writing, UETA accepts an electronic record only if the recipient can keep it. In practice: the signer gets a copy, and what you hold later is what they saw.
Put those against a form entry and the questions get concrete:
- Which text was on the screen when they signed?
- Is a fingerprint of that text kept with the signature?
- Would a later edit to the entry, or to the page, show?
- Was agreeing to sign electronically a step of its own?
- What did the signer take away?
When a WordPress form signature field is plenty, and when it is not
Plenty, when the stakes are low and everybody knows it. A volunteer confirming a rota. Members acknowledging a club's code of conduct. "I have read the studio rules" on a class booking. An internal form a member of staff fills in at the end of a shift. If one of these were ever disputed the dispute would be small, and a separate signing step would cost more in friction than it saves in evidence.
Not enough, when the document gives something up or takes something on. A waiver of claims. A rental agreement with damage terms in it. A guardian's consent for a child. A repair authorisation with a price. These are the documents that get read closely later, by somebody who was not there, and every question in the list above gets asked of them.
The line is about stakes, not about technology. On the right form, a WordPress form signature field is the proportionate answer.
Connecting a WordPress form to a signing page
The SignSealer plugin for WordPress keeps the form you already have and moves the signing to a page that records the rest. Under SignSealer → Forms you choose, for a Gravity Forms, WPForms, Fluent Forms or Contact Form 7 form, which SignSealer form it starts, which field holds the email address and which the name, and which blanks in the document fill from other fields. After they submit, the person goes straight to the signing page, or the form's own confirmation gains a link to it. The WordPress plugin page covers the rest, and there are step-by-step guides for Gravity Forms, WPForms and Contact Form 7, among others.
What the plugin will not do matters as much. It never draws a signature pad in WordPress: signing happens on SignSealer's own page, where the agreement to sign electronically is recorded as its own event before the signature is accepted, the document's exact text is fingerprinted into every entry on the trail, and the signer is emailed the signed copy with a code anybody can check it by. It never stores the evidence: the form entry keeps the document's id, title and status, with a note when that changes, and WPForms Lite and Contact Form 7, which keep no entries, leave you to see who signed in SignSealer. And it connects over OAuth 2.0 with PKCE, scoped to one business, rather than holding a master key. What is recorded at each step is on our page about evidence and the audit trail.
SignSealer is not a law firm and this is not legal advice. What the statutes say is described here in general terms; whether a particular signature does what you need, for a particular document where you operate, is a question for a lawyer.
