Weave Code
Filament Signature Pad Laravel Package
savannabits/filament-signature-pad
Filament Signature Pad adds a canvas-based signature field to Filament forms, letting users draw with mouse or touch and save signatures as images. Easy to install and configure, it fits smoothly into admin panels for approvals, contracts, and sign-off workflows.
Signature Pad for FilamentPHP
Frequently asked questions about Filament Signature Pad
- How do I install and use filament-signature-pad in a Laravel app?
- Install it with Composer using composer require savannabits/filament-signature-pad, then add the signature pad field to a Filament form schema and add a column on the model to hold the output. The package is a single form field that wraps a canvas-based JavaScript library, so integration is mostly one field call plus persistence. Expect a short spike rather than a large project, with the storage decision being the main design work.
- Which Filament versions does savannabits/filament-signature-pad support?
- Because this is a third-party Filament form field, check the composer.json constraint of the exact version you install, since Filament major upgrades such as v3 to v4 are hard breaks for field plugins. The evaluation notes a last release in October 2024, no confirmed Filament v4 branch, and zero dependents. The code surface is small and MIT licensed, so forking to support a newer Filament version is measured in hours rather than weeks.
- Does filament-signature-pad save signatures as base64 or as files?
- The field hands back a base64-encoded image data URL on the form state, and that is the only output described. It does not include a built-in disk persistence hook comparable to a file upload field, so storing base64 in a text column is the path of least resistance. The package makes no storage decision for you.
- How should I store signature images in the database?
- Base64 inflates payloads roughly 33 percent over raw bytes, and signatures typically land at 10 to 50 KB each, which bloats rows, backups, replication and naive CSV or JSON exports. Prefer writing the decoded image to disk or object storage and keeping a path or hash on the model instead. Treat the package purely as a UI component and own the storage layer yourself.
- Is a signature pad image a legally valid e-signature?
- No. A signature pad image is a bitmap that looks like a wet-ink artifact; it is not an e-signature and carries no legal or audit weight on its own. If a workflow has legal, clinical or financial significance you must supply signer identity, timestamp, IP and user agent, document hash, the version of terms signed, plus retention and immutability controls yourself. The package addresses none of that, and it is the largest hidden cost in adopting it.
- Can the signature field be validated as required or non-blank?
- Validation support is limited and should be confirmed in the source before relying on it; typically you can mark the field required, but distinguishing drew nothing from cleared is not guaranteed. If exact non-blank enforcement matters, add your own validation rule or a stroke-count check. Test the behavior rather than assuming it.
- Does the signature pad work inside Filament Repeaters, Wizards and modals?
- This is untested territory for a low-adoption plugin. Canvas capture inside nested Livewire components such as Repeaters, Wizards and modal actions can hit touch-scroll versus draw conflicts and state dehydration quirks. Spike those specific cases explicitly if your form uses them.
- Is filament-signature-pad accessible for keyboard and screen reader users?
- The field is canvas based and mouse or touch driven, so keyboard and screen reader users have no equivalent path to sign. If you ship it you inherit a WCAG exposure and should provide an alternative signing mechanism. Confirm whether any accessibility options exist in the specific version you install.
- Is filament-signature-pad actively maintained, and what are the alternatives?
- It is MIT licensed with roughly 77 stars, zero dependents and a single small-agency maintainer, with the last release in October 2024. That is low community validation and little pressure on the maintainer to track Filament's release cadence, so plan for the possibility of a fork. Alternatives include building your own Filament field around the signature_pad JavaScript library, or using a full e-signature provider when legal evidence is required.
- Is filament-signature-pad safe to use in production?
- It is reasonable as a presentation-layer UI component with near-zero architectural coupling, provided you own persistence and the surrounding evidence layer. Treat it as an optional capability rather than compliance infrastructure, and avoid storing base64 blobs in a text column at scale. Verify Filament version compatibility, tests and CI coverage before committing, and budget for a fork at the next Filament major release.
Weaver
How can I help you explore Laravel packages today?