Skip to main content
The Signature block gives respondents an interactive canvas (mouse, trackpad, or touch). The stroke is smoothed and stored as a compact SVG string in the submission payload — not as a separate upload file. Optional download (SVG / WebP) is for the respondent’s browser only; it does not write to your media disk.

Business Use Cases

Contract Agreements

Collect an embedded signature on NDAs, service agreements, or B2B contracts.

Delivery Confirmations

Allow customers to sign a tablet upon receiving a high-value shipment.

Waivers & Liability

Require an electronic signature before participation.

Configuration & Usage

1

Deploy to Canvas

Drag the Signature block from the Component Catalog onto the Canvas.
2

Style the Canvas

Adjust pen color, width, and optional guidelines to match your brand.
3

Enforce Validity

Raise Min Strokes so a single accidental tap cannot pass validation.

Technical Configuration Schemas

string
HEX ink color (e.g. #000000).
float
Stroke thickness.
string
Canvas background. Leave empty for transparent SVG.
boolean
default:"false"
Full-screen signing mode on small screens.
boolean
default:"false"
Smooth stroke paths for a more natural look.

Data Payload Architecture

Unlike File Upload / Voice Note, signatures are not staged to disk. The answer is the SVG markup string inside the submission payload (same on webhooks and in the database).

Best Practices & FAQs

Set Min Strokes to at least 2 so a single tap cannot pass as a signature.
Transparent SVG (empty background) overlays cleanly onto contract lines in generated PDFs. A solid background color makes overlays harder.
Last modified on September 7, 2026