Create PAdES B-B signatures with an X.509 cert (.p12/.pfx) or Autofirma. Validation depends on certificate validity and verifier trust settings; software cert material is handled locally.
Digital signatures cryptographically bind certificate material to a document through a CMS/PKCS#7 envelope. OpenPDF creates PAdES B-B signatures using a software X.509 certificate (.p12 / .pfx) or Autofirma for a smartcard, DNIe or installed certificate. Acceptance depends on certificate validity and the verifier's trust settings; chain retrieval or optional timestamping can require the network.
Software X.509 certificates in PKCS#12 format (.p12 / .pfx) — accepted from FNMT, idCAT, ACCV, Camerfirma and any eIDAS-compliant issuer. Smartcards, DNIe and OS-installed certificates are supported through Autofirma.
OpenPDF produces PAdES B-B signatures (ETSI EN 319 142). Whether a verifier accepts the result depends on the certificate, its validity and the verifier's trust settings; a qualified signature also requires the appropriate qualified certificate and device.
For software certificates, the password unwraps the certificate locally in the browser and the private key is not uploaded. Autofirma uses a local desktop bridge; certificate-chain retrieval or timestamping can still require the network.
You can sign several PDFs while the certificate remains unlocked in that browser session. To stop using it, return to the signing-method selector and follow the tool's controls; persistent browser state is managed separately.
OpenPDF is an independent project where PDF document processing runs in the browser using WebAssembly and modern JavaScript APIs. The toolkit includes merge, split, sign, organize, annotate, compress, watermark, page numbers, add image and fill forms. Practical limits depend on the operation, document and device. The page source and privacy policy describe consent controls, analytics, advertising and optional services before you use the tool with sensitive documents.
By Marco B. · Last updated: