PDFFileElement: signatures property

Works in all major browsers

Since July 2026

WebPDF works in Chrome and Edge 125, Firefox 153 and Safari 18, on desktop and mobile, and in every later version: the oldest versions its PDF.js build supports, which already have every platform feature WebPDF needs. Since July 2026, that is every major browser.

The signatures property of the PDFFileElement interface sets or returns whether the pages of a <pdf-file> show the cards of its digital signatures. It reflects the signatures HTML attribute.

Value

A boolean value: the effective one, also when the file inherits it.

The attribute is multi-homed: when the file has none, it follows the WebPDF <script>; its pages can set their own.

A page's own signatures wins. Hotspots over signature fields are always there. Setting false writes signatures=-; null removes it. With controls, Alt Shift S toggles it, and every page follows.

Examples

Signature cards on every page

HTML

html

<pdf-file id=s src=//new.webpdf.pro/signed.pdf trust:src=//new.webpdf.pro/demo-root.pem signatures></pdf-file>
<pdf-page of=s scale=0.6></pdf-page>

Result

Specifications

Not part of any specification. <pdf-file> and <pdf-page> are autonomous custom elements defined by WebPDF.pro. It implements:

Specification
ISO 32000-2:2020 (PDF 2.0) # 12.8 Digital signatures

Browser compatibility

	desktop					mobile
	Chrome	Edge	Firefox	Opera	Safari	Chrome Android	Firefox for Android	Opera Android	Safari on iOS	Samsung Internet	WebView Android	WebView on iOS
`signatures`	125	125	153	111	18	125	153	83	18	27	125	18

signatures · Chrome, Edge, Firefox, Opera, Safari, Chrome Android, Firefox for Android, Opera Android, Safari on iOS, Samsung Internet, WebView Android, WebView on iOS: Secure contexts (HTTPS) only; elsewhere every signature verifies as unknown.

: Full support
: See implementation notes.