The ink is trimmed and embedded into the PDF as part of the page, a signature library in your browser remembers it for next time, and none of it leaves the Mac — the signature exists only in your browser and in the file you download. It is a visual signature, the way most everyday paperwork is signed, not a cryptographic one; Certify adds a real digital signature with a non-extractable key generated in the browser or your own imported .p12/.pfx certificate, and Request signatures collects signatures from other people without the contract sitting on a server in the clear.
How it works
- Open Bindery in Safari or Chrome and drop the PDF into Sign
- Draw with the trackpad or type your signature, then click where it belongs
- Download the signed PDF
Questions people ask
How is this different from signing in Preview?
Preview stores your signature in macOS and stamps it as an annotation. Bindery keeps the signature in your browser, draws it into the page itself, and sits beside Fill forms, Flatten, Certify and Request signatures so the whole document workflow stays in one place without an upload.
Is a drawn signature enough for a contract?
For most everyday agreements, a visible signature on the document is what the parties expect. Where the other side needs proof the file has not changed since signing, use Certify: a PAdES-style signature verifiable in Acrobat, with the key kept on your Mac. Regulated workflows may require a qualified provider.
Can I use my own certificate?
Yes, in Certify: import a .p12 or .pfx file and it is decrypted in the browser and stored non-extractable, so the private key is never sent anywhere — including to Bindery. RSA and ECDSA keys are supported, and an RFC 3161 trusted timestamp can be added.