PAdES: Signature Levels, Formats and LTV Explained
András Somkuti, CEO & Founder · Updated 18 November 2026
PAdES (PDF Advanced Electronic Signatures) is the European standard format for electronic signatures in PDF files, published by ETSI as EN 319 142-1. The signature is embedded in the PDF, so one file carries the document and its signature. Four baseline levels, B-B, B-T, B-LT and B-LTA, add trusted time and validation data step by step.
What Is a PAdES Signature?
A PAdES signature is an electronic signature stored inside a PDF in the format that ETSI EN 319 142-1 specifies. It can carry any eIDAS signature level, up to a qualified electronic signature, and it is the format this guide’s levels, tables and checks refer to. You can sign a PDF with a qualified signature in the Netlock app.
The standard builds on the signature mechanism that the PDF standard itself defines: ISO 32000-1 for PDF 1.7 and ISO 32000-2 for PDF 2.0. Inside the PDF’s signature dictionary sits a CMS signature, and that CMS object forms a CAdES signature as defined in ETSI EN 319 122-1 (EN 319 142-1, clause 6.3, requirement h). That is why ETSI says PAdES supports signature formats equivalent to CAdES (clause 1).
Three details explain how a PAdES signature behaves in practice:
- It covers the whole document. The signed byte range has to comprise exactly the entire PDF revision being signed, except the space reserved for the signature value, with no unsigned gaps (clause 4.1). If anyone changes a signed byte, validation shows it.
- It grows by incremental updates. A second signature, validation data or a timestamp is appended to the file as a new revision, without touching the bytes the first signature covers. That is how one PDF carries several signatures and how a signature moves up from one level to the next (clause 6.1, note 5).
- It has a format marker. A PAdES baseline signature carries the value ETSI.CAdES.detached as its SubFilter (clause 6.3, requirement l). The older value adbe.pkcs7.detached may still be supported to verify existing PDF 1.7 signatures, but the standard prefers ETSI.CAdES.detached for new signatures and requires it for PDF 2.0 (clause 5.3).
Is a PAdES Signature Legally Binding?
The format doesn’t decide that; the signature level does. ETSI states that PAdES signatures aim to support simple, advanced and qualified electronic signatures and electronic seals under eIDAS (EN 319 142-1, clause 1, note). The legal effect comes from the eIDAS Regulation (EUR-Lex): an electronic signature “shall not be denied legal effect and admissibility as evidence in legal proceedings solely on the grounds that it is in an electronic form” (Article 25(1)), and “a qualified electronic signature shall have the equivalent legal effect of a handwritten signature” (Article 25(2)). Our article on SES, AES and QES explains the three levels.
The Four PAdES Levels: B-B, B-T, B-LT and B-LTA
EN 319 142-1 defines four PAdES signature levels, and each level meets every requirement of the levels below it (clause 1). The table sums up what each one adds (clause 6.1 and Table 1 in clause 6.3):
| Level | What it adds | What it proves or keeps |
|---|---|---|
| PAdES B-B (basic) | The signature, the signing certificate and the claimed signing time | Who signed and that the document hasn’t changed. The time comes from the signer’s own device, so it is a claim, not proof. |
| PAdES B-T (time) | A trusted token proving that the signature existed at a given date and time: a signature timestamp or a document timestamp (requirement n) | When the signature existed, so it can be shown that it was made while the certificate was valid |
| PAdES B-LT (long-term) | All the material needed to validate the signature, stored in the PDF’s Document Security Store (DSS): the certificates and the revocation data (CRLs or OCSP responses) for the signer and for the timestamp authority (requirements r–t) | Validation no longer depends on the certificate authority’s online services still answering years later |
| PAdES B-LTA (long-term with archive timestamps) | At least one document timestamp over the whole document, applied after the validation data was added (requirements w–y) | The availability and integrity of the validation data over the long term; it can help validate the signature after algorithms weaken or the validation data expires (clause 6.1, note 3) |
B-LT and B-LTA are the levels for signatures that have to stay checkable after certificates expire or are revoked, or after algorithms become obsolete (clause 6.1, note 2). For B-LTA, ETSI notes that it “is considered an appropriate preservation and transmission technique for signed data” (note 3). It isn’t a one-off, though: the protection can be extended beyond the life of the last document timestamp by adding the data needed to validate that timestamp and then a new document timestamp (clause 5.4.1). Our guide to electronic archiving covers retention periods and long-term signature validity. The glossary entry on PAdES Baseline LTA gives the short version, and our article on whether your electronic signature will still be valid in ten years explains why the archive question belongs at the start.
These two extensions, the DSS and the document timestamp, are what EN 319 142-1 calls support for Long Term Validation (LTV) of PDF signatures (clause 5.4.1). You may still meet older names: signatures made to the earlier PAdES Baseline Profile, ETSI TS 103 172, are now called legacy PAdES baseline signatures (clause 3.1), and Adobe’s documentation describes its LTV data with reference to Part 4 of the older ETSI TS 102 778 series.
PAdES vs CAdES vs XAdES: Which Format When?
The ETSI signature formats share the same four-level model, from B-B to B-LTA, but each one signs a different kind of data. Choose the format by what you sign and by who has to open it:
| Format | Standard | Built on | Where the signature sits | Use it for |
|---|---|---|---|---|
| PAdES | ETSI EN 319 142-1 | PDF signatures (ISO 32000) with a CAdES signature inside | Inside the PDF | Documents people open and read: contracts, letters, certificates, reports |
| CAdES | ETSI EN 319 122-1 | CMS signatures (IETF RFC 5652) | Around the data or in a separate file, for example a .p7s file | Any file type, including binary files, when the signature can travel next to the file |
| XAdES | ETSI EN 319 132-1 | XML digital signatures | In the XML document or alongside the signed data | XML data that software reads and processes |
| JAdES | ETSI TS 119 182-1 | JSON Web Signatures (IETF RFC 7515) | In or alongside the JSON data | JSON data and web APIs |
| ASiC | ETSI EN 319 162-1 | A ZIP container | In the container, next to the files: CAdES or XAdES signatures, or timestamps | Several files signed together, or a non-PDF file and its signature delivered as one package |
ASiC comes in two types (EN 319 162-1, clauses 4.3 and 4.4). ASiC-S (extension .asics, or .scs) links one data file with its signatures or a timestamp. ASiC-E (.asice, or .sce) can hold several signature and timestamp files, each applying to its own set of files. ASiC also defines four baseline levels, built on the CAdES or XAdES levels of the signatures inside (clause 5.1).
In practice, the choice is usually short. If the result is a document a person will read, use PAdES: the recipient gets one PDF that opens like any other, and a reader that validates signatures shows the signature details. If systems exchange XML, use XAdES; for JSON, JAdES. For any other file, or when the signature has to stay separate from the data, use CAdES, and use ASiC when several files belong together.
Which Signature Formats Must EU Public Bodies Accept?
If a member state requires an advanced electronic signature for an online public service, it must recognise advanced and qualified electronic signatures “in at least the formats or using methods defined in the implementing acts” of eIDAS Article 27(5) (Article 27(1)–(2)). The same rule applies to electronic seals (Article 37). And for cross-border use, member states “shall not request … an electronic signature at a higher security level than the qualified electronic signature” (Article 27(3)).
The implementing act changed in 2026:
- Commission Implementing Decision (EU) 2015/1506 (EUR-Lex) required member states to recognise XML, CMS or PDF advanced electronic signatures “at conformance level B, T or LT”, or an associated signature container, made to the ETSI baseline profiles TS 103 171, 103 172, 103 173 and 103 174 (Article 1 and Annex). Its recital 5 explains that the long-term archiving forms were left out because the standards for them were being revised. EUR-Lex gives 22 February 2026 as the end of its validity.
- Commission Implementing Regulation (EU) 2026/248 (EUR-Lex) repealed it (Article 5). Its Annex I lists the current baseline standards: XAdES EN 319 132-1 V1.3.1, CAdES EN 319 122-1 V1.3.1, PAdES EN 319 142-1 V1.2.1, JAdES TS 119 182-1 V1.2.1 (with one adaptation) and the ASiC containers of EN 319 162-1 and -2 V1.1.1. Annex II keeps the old TS profiles, still limited to the B, T and LT levels; Annex I lists the EN standards without that limit.
| Date | What applies under Regulation (EU) 2026/248 |
|---|---|
| 23 February 2026 | The Regulation enters into force, and Decision (EU) 2015/1506 is repealed. References to the Decision now count as references to the Regulation (Article 5). |
| 23 February 2027 | Member states must recognise the Annex I formats, the current EN baseline standards PAdES included (Articles 1(1), 3(1) and 6). |
| 23 February 2028 | Signatures and seals in the old Annex II profiles are recognised only if they were created before this date (Articles 1(2) and 3(2)). |
Formats that aren’t on either list can still be accepted: a member state must recognise them if the member state where the signer’s trust service provider is established offers a validation method for them that works online, free of charge and with clear instructions, and that confirms the points Article 2(2) lists. Recital 8 adds that the obligation to recognise a signature lasts as long as EU or national law requires it to be validated.
ETSI published PAdES V1.3.1 in November 2026; the Regulation names V1.2.1 (2024-01). The four levels are defined in the same words in both versions (clause 6.1).
LTV in Adobe Acrobat: What “Signature Is Not LTV Enabled” Means
In Acrobat’s terms, an LTV-enabled signature is one whose PDF carries the data needed to validate it later, and Acrobat shows for each signature whether it is LTV enabled. Adobe’s Digital Signature Guide explains why: without that data in the PDF, a signature can be validated only for a limited time, because the certificates behind it expire or are revoked, and once a certificate has expired, its issuer is no longer responsible for providing its revocation status. Long-term validation means embedding the signing certificate chain, the certificate revocation status and, where used, a timestamp in the PDF, either when signing or afterwards.
So “Signature is not LTV enabled”, often followed by “and will expire after” and a date, means that the PDF doesn’t contain that validation data. It doesn’t say on its own that the signature is invalid today; it says that the file lacks what a validator will need once the certificates’ status can no longer be fetched online.
Keep in mind that Acrobat’s LTV label and the PAdES levels are two different scales. Adobe’s preference reference gives adbe.pkcs7.detached (PKCS#7) as Acrobat’s default signing format and documents an option to include the revocation status in signatures, while a PAdES baseline signature must use ETSI.CAdES.detached (EN 319 142-1, clause 6.3). A signature Acrobat calls LTV enabled is not necessarily PAdES B-LT, and Acrobat doesn’t name PAdES levels.
How to Fix “Signature Is Not LTV Enabled” in Acrobat
- Add the verification information. Open the PDF in Acrobat, right-click the signature and choose Add Verification Information, then save the file (Adobe help). Acrobat has to be online to fetch the revocation data, and it has to trust the signer’s certificate chain. For EU qualified certificates, Adobe documents that Acrobat can download the European Union Trust List (EUTL) and then trusts signatures that chain to its certificates.
- Let Acrobat add it automatically. Adobe’s preference reference places the setting “Automatically add verification information when saving signed PDF” under Preferences > Signatures > Verification > More > Verification Information.
- When you sign in Acrobat yourself, turn on the signing preference that includes the signature’s revocation status, configure a timestamp server (Adobe notes that Acrobat doesn’t set a default one when several are listed), and choose ETSI.CAdES.detached as the default signing format, which a PAdES baseline signature requires.
- Do it early. Once a certificate in the chain has expired, its issuer no longer has to provide its revocation status, so the data may no longer be available to add.
Embedding the validation data in the PDF is what the B-LT level requires of a PAdES signature. For B-LTA, a document timestamp has to be added after the validation data (EN 319 142-1, requirement x); Adobe’s preference reference describes the ETSI.CAdES.detached format as part of the feature that adds an invisible timestamp signature to a document. A PDF signed with Netlock already contains both, since it is created at B-LTA. Whether Acrobat shows it as trusted still depends on Acrobat’s trust settings.
How to Check a PDF’s PAdES Level
Look for the elements each level requires. EN 319 142-1 doesn’t write the level into the file as a label, so a validator works it out from what the PDF contains (clause 6.3, Table 1):
| You find in the PDF | The signature reaches at least |
|---|---|
| A signature with SubFilter ETSI.CAdES.detached and the signing certificate | B-B |
| A signature timestamp, or a document timestamp (SubFilter ETSI.RFC3161) | B-T |
| A Document Security Store with the certificates and the revocation data (CRLs or OCSP responses) | B-LT |
| A document timestamp added after the Document Security Store | B-LTA |
Three ways to check:
- In Adobe Acrobat, open the signature’s properties. Adobe documents that a signing time taken from the signer’s computer is labelled as local time in the Date/Time and Summary tabs of the Signature Properties dialog, so you can tell a claimed time from a timestamp. Acrobat also tells you whether the signature is LTV enabled, but, as above, it doesn’t name the PAdES level.
- With a validator that reports the ETSI level. The European Commission’s DSS demonstration web app reports signature formats such as PAdES-BASELINE-LTA. The Commission says the demo is for testing only, and files you upload are sent to its infrastructure, so use a copy without sensitive content.
- With a PDF inspection tool, look up the values in the table: the SubFilter of each signature, a DSS entry in the document catalog, and a DocTimeStamp signature after it.
If the result is adbe.pkcs7.detached instead of ETSI.CAdES.detached, the PDF holds a basic PDF signature rather than a PAdES baseline signature. That still says nothing about its legal level; it only tells you which format the signing software used. To check whether the signature itself is valid, not only its format, see how to validate an electronic signature.
How Netlock Signs: PAdES B-LTA With a Qualified Timestamp
Every signature you make in Netlock is created as PAdES B-LTA and carries a qualified timestamp from Netlock’s own qualified timestamping service. You don’t have to choose a level or arrange timestamps yourself: the validation data and the timestamps are in the signed PDF from the start.
The timestamp matters legally as well as technically. Under eIDAS, “a qualified electronic time stamp shall enjoy the presumption of the accuracy of the date and the time it indicates and the integrity of the data to which the date and time are bound” (Article 41(2)).
Netlock is a qualified trust service provider on the EU Trusted List and in the register of the Hungarian supervisory authority, the NMHH. How it works:
- Register and get identified. The qualified certificate is free, and from registration to a working qualified electronic signature takes 1 minute. Identification is automatic and works with any device that has a camera, using an EU identity card or passport (in the US, a passport or driver’s licence).
- Upload a PDF and sign. You confirm the signature with two-step verification, and you can sign several documents at once with bulk signing.
- Everyone gets the signed PDF. Every signer receives the signed copy by email, and it can also be downloaded in the app.
Because the signature is inside the PDF, the recipient gets one file that opens in any PDF reader. Companies can also seal documents with an electronic seal in the app; our article on the electronic signature or seal explains when a company needs which. If you sign PDFs in Acrobat with your own certificate, you can buy Netlock’s qualified timestamps in the app: after paying, you get your own timestamp URL to set in Acrobat, and the log-on fields stay empty.
FAQ
B-LT stores in the PDF all the certificates and revocation data needed to validate the signature. B-LTA adds at least one document timestamp over the document after that data, which protects the validation data itself and can help validate the signature after algorithms weaken or the validation data expires (ETSI EN 319 142-1, clause 6.1).
Not necessarily. PAdES is a file format that can carry a simple, advanced or qualified electronic signature, or an electronic seal (EN 319 142-1, clause 1). A signature is qualified when it is an advanced electronic signature created by a qualified signature creation device and based on a qualified certificate, and then it has the equivalent legal effect of a handwritten signature (eIDAS Articles 3(12) and 25(2)).
It means the signed PDF doesn’t contain the data needed to validate the signature without going online: the certificate chain, the revocation status and, where used, a timestamp. Adobe explains that without that data, a signature can be validated only for a limited time. You can usually fix it by right-clicking the signature, choosing Add Verification Information and saving the PDF, as long as the revocation data can still be fetched.
No. A signature covers the exact data that was signed, and under eIDAS an advanced electronic signature is “linked to the data signed therewith in such a way that any subsequent change in the data is detectable” (Article 26(d)). Converting an XML file or a .p7s package into a PDF creates new data, which the original signature doesn’t cover. To get a PAdES signature, the PDF has to be signed again.
Under Implementing Regulation (EU) 2026/248, a member state that requires an advanced electronic signature for an online public service must recognise signatures made to PAdES EN 319 142-1 from 23 February 2027, and Annex I sets no level limit. Signatures made to the older PAdES profile, ETSI TS 103 172, are recognised at the B, T and LT levels if they were created before 23 February 2028 (Annex II).
Not without care. Its protection lasts as long as the last document timestamp can be trusted. ETSI describes how to extend it: add the data needed to validate the last timestamp, then add a new document timestamp (EN 319 142-1, clause 5.4.1). How long you have to keep a signed document is a separate question, set by the law that applies to it.
Yes. EN 319 142-1 covers electronic seals, advanced electronic seals and qualified electronic seals as well as signatures (clause 1), and Regulation (EU) 2026/248 applies the same format list to advanced electronic seals (Article 3).
Register with Netlock: the qualified certificate is free and you get 15 free signatures, each created as PAdES B-LTA with a qualified timestamp. After that, one signature costs 1 credit (see pricing).
Sign your PDFs in PAdES B-LTA with a qualified timestamp, without configuring anything. Netlock is a qualified trust service provider: sign up for free, get 15 free signatures and a qualified certificate in 1 minute; after that, each signature costs 1 credit (see pricing).
PAdES B-LTA and a qualified timestamp on every signature, 15 free signatures
Related Articles
Sources
- ETSI EN 319 142-1 V1.3.1 (2026-11), PAdES digital signatures, Part 1: Building blocks and PAdES baseline signatures: clauses 1 (scope and note), 3.1 (legacy PAdES baseline signature), 4.1, 5.3 (SubFilter), 5.4.1 (DSS, Document Time-stamp, LTV, extending protection), 5.4.3, 6.1 (levels and notes 1–5), 6.3 (Table 1, requirements h, l, n, r–t, w–y): https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.03.01_60/en_31914201v010301p.pdf · V1.2.1 (2024-01), the version Regulation (EU) 2026/248 names, same clause 6.1 wording: https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf
- ETSI EN 319 122-1 V1.3.1 (2023-06), CAdES digital signatures, Part 1: clause 1 (scope, four levels, note on eIDAS): https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf
- ETSI EN 319 132-1 V1.3.1 (2024-07), XAdES digital signatures, Part 1: clause 1 (scope, built on XML digital signatures, four levels): https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.03.01_60/en_31913201v010301p.pdf
- ETSI EN 319 162-1 V1.1.1 (2016-04), Associated Signature Containers (ASiC), Part 1: clauses 1, 4.3 (ASiC-S, .asics/.scs), 4.4 (ASiC-E, .asice/.sce), 5.1 (baseline levels): https://www.etsi.org/deliver/etsi_en/319100_319199/31916201/01.01.01_60/en_31916201v010101p.pdf
- ETSI TS 119 182-1 V1.2.1, JAdES digital signatures, Part 1: clause 1 (JSON, built on JWS, IETF RFC 7515): https://www.etsi.org/deliver/etsi_ts/119100_119199/11918201/01.02.01_60/ts_11918201v010201p.pdf
- eIDAS Regulation (EU) No 910/2014, consolidated text of 18 October 2024, Articles 3(12), 25(1)–(2), 26(d), 27(1)–(3), (5), 37, 41(2): https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02014R0910-20241018
- Commission Implementing Decision (EU) 2015/1506 of 8 September 2015, recital 5, Article 1 and Annex; EUR-Lex status “No longer in force, Date of end of validity: 22/02/2026; Repealed by 32026R0248”: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32015D1506
- Commission Implementing Regulation (EU) 2026/248 of 2 February 2026 (OJ L, 3.2.2026), recital 8, Articles 1–6, Annexes I and II: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32026R0248
- Adobe, Acrobat Desktop Digital Signature Guide, Pre-deployment Configuration, “Long term validation” and “Timestamp servers” (LTV purpose, required elements, embedding at or after signing, ETSI TS 102 778 Part 4, no default time-stamp server, local time labelled in Signature Properties), and the EUTL section: https://www.adobe.com/devnet-docs/acrobatetk/tools/DigSigDC/planning.html
- Adobe, Acrobat Preference Reference (Windows), Security: “Signing: Long Term Validation” (bIsEnabled, GUI “Include signatures revocation status when signing”; iAutoAddLTV, GUI “Preferences > Signatures > Verification panel (More) > Verification Information > Automatically add verification information when saving signed PDF”), “Signing: Format” (aSignFormat default adbe.pkcs7.detached; ETSI.CAdES.detached and the invisible timestamp signature), “European Union Trust List”: https://www.adobe.com/devnet-docs/acrobatetk/tools/PrefRef/Windows/Security.html
- Adobe Help, “Add verification information to digital signatures” (command name): https://helpx.adobe.com/acrobat/desktop/e-sign-documents/fill-sign-documents/add-verification.html
- European Commission, DSS Demonstration WebApp, validation page (privacy notice: files are transmitted to the Commission’s infrastructure) and DSS documentation, section 1.4 (demonstrations for testing purposes only) and Table 4 (PAdES-BASELINE level names): https://ec.europa.eu/digital-building-blocks/DSS/webapp-demo/validation · https://ec.europa.eu/digital-building-blocks/DSS/webapp-demo/doc/dss-documentation.html
- EU Trusted List, Netlock: https://eidas.ec.europa.eu/efda/trust-services/browse/eidas/tls/tl/HU/tsp/6 · NMHH register: https://esign.nmhh.hu/bszny/
- Netlock glossary, “PAdES Baseline LTA”: https://netlock.com/company/glossary#term-pades-baseline-lta