A standard Digital Signature on a PDF can expire or become invalid within one to three years. A Long-Term Validation (LTV) signature embeds all the cryptographic evidence needed to verify the signature decades after it was applied. According to the European Telecommunications Standards Institute, LTV signatures are now required for documents that must remain legally verifiable for 10 years or longer under regulations like eIDAS in Europe and the ESIGN Act in the United States (ETSI, "Technical Specification for Long-Term Digital Signatures", 2024). For contracts, property deeds, regulatory filings, and intellectual property records, adding LTV protection turns a temporary signature into a permanent one.
Key Takeaways
A Long-Term Validation signature embeds timestamp tokens, certificate revocation status, and the full certificate chain directly into the PDF, so the signature can be verified even after the signing certificate expires. Standard digital signatures lack this embedded evidence and become unverifiable once the certificate authority's online validation services are no longer available. Adding LTV to an already-signed PDF is possible through most PDF tools as long as the original signing certificate has not yet expired.
How a Standard Digital Signature Works and Why It Expires
A standard digital signature places a cryptographic hash of the document content into the PDF along with the signer's certificate. When someone later opens the document, the PDF reader checks the certificate against the issuing Certificate Authority to confirm it has not been revoked and is still within its validity period. Most signing certificates issued by public CAs are valid for one to three years. Once the certificate expires, the signature status changes to unverified or invalid even though the document content has not changed and the signature was legitimate when applied.
The problem is that standard signatures depend on live online services. The reader must contact the CA's OCSP responder or download a Certificate Revocation List to confirm the certificate status at the time of verification. When the CA stops operating those services, which can happen years or decades after the certificate was issued, the signature becomes permanently unverifiable. For legal and PDF Archive archival documents, this creates a serious problem: a signed contract from 2025 might appear invalid when presented as evidence in 2040.
What a Long-Term Validation Signature Adds to the PDF
An LTV signature solves the expiration problem by embedding all the verification evidence directly into the PDF at the time of signing, or shortly afterward. This evidence includes a trusted timestamp token that proves the exact time the signature was applied, the certificate revocation status showing the certificate was valid at that time, and the full certificate chain from the signer's certificate up to the root CA. With all of this evidence stored inside the PDF itself, no external services are needed for verification. A PDF reader can confirm the signature was valid at the time it was applied even if the signing certificate, the CA, and even the timestamp authority have all ceased to exist.
The timestamp token is the critical component. It is issued by a trusted Timestamp Authority (TSA) and cryptographically binds the document hash to a specific date and time. Even if the TSA's own certificate eventually expires, the timestamp proves that the signature existed before the signer's certificate expired, which is the essential fact that a verifier needs to confirm. PDF tools that support LTV signatures, including WukongPDF's signing feature, automatically request and embed the necessary timestamp and revocation data as part of the signing process.
Adding LTV to an Existing Signature
If you already have a signed PDF and the signing certificate has not yet expired, you can add LTV information to the existing signature without re-signing the document. Most PDF desktop applications include an Add Verification Information or Enable LTV option in their signature panel. The tool contacts the CA's OCSP server, retrieves the current revocation status, embeds the certificate chain, and adds a timestamp. This process should be done while the signing certificate is still valid because the OCSP response confirming the certificate was not revoked at that moment is the key piece of evidence that future verifiers will rely on.
For documents that were signed years ago with expired certificates, LTV cannot be added retroactively because the window for obtaining a favorable OCSP response has closed. This is why organizations that handle legal, financial, or regulatory documents should add LTV at the time of signing or shortly afterward as a standard practice, rather than treating it as an optional extra step. A small investment of time at signing prevents a much larger problem years later when the document's legal validity is called into question.
Choosing a Timestamp Authority for Long-Term Validation
Some PDF signing tools allow you to configure a default TSA URL so that every signature automatically includes a timestamp without requiring you to select the authority each time. This is worth setting up if you sign documents regularly. The TSA URL for most commercial providers is publicly documented. For example, DigiCert's public timestamp server is accessible at timestamp.digicert.com. Using a well-known commercial TSA is almost always preferable to leaving the timestamp field blank, which is what happens by default when no TSA is configured.
The Timestamp Authority you select directly affects the long-term trustworthiness of your signatures. Government-operated TSAs, such as those run by EU member states under eIDAS, carry the strongest legal presumption of validity. Commercial TSAs operated by established certificate authorities like DigiCert, GlobalSign, or Sectigo are also widely accepted in both European and North American jurisdictions. Free TSAs exist but should be approached with caution for anything beyond personal use because their long-term operational stability is less certain.
When evaluating a TSA, check whether their timestamp certificates are themselves issued with sufficient validity periods and whether they have published a practice statement that commits to long-term record keeping. A TSA that goes out of business does not invalidate timestamps it already issued, but it does raise questions during legal proceedings that could have been avoided by choosing a more established provider. For documents that must remain verifiable for decades, consider obtaining timestamps from two independent TSAs to provide redundancy.
For documents subject to specific regulatory requirements, check whether the regulation mandates a particular type of TSA. eIDAS in the European Union distinguishes between qualified and non-qualified timestamp services, with qualified timestamps carrying a legal presumption of accuracy. The US ESIGN Act does not make this distinction but courts have historically given more weight to timestamps from established commercial or government TSAs. Matching your TSA choice to the document's regulatory context is a small step that can make a significant difference if the signature is ever challenged.
Verifying an LTV Signature Years Later
Opening an LTV-signed PDF in a modern PDF reader shows the signature status in a blue ribbon or information bar. If the signature was valid when applied and the LTV evidence is intact, the reader displays Signature is LTV enabled or Signature Valid regardless of the certificate's current expiry status. This is the key visual confirmation that the LTV information is doing its job. The document can be opened on a computer that has never connected to the internet, and the signature will still verify because all the necessary evidence is inside the file.
If verification fails on an LTV-signed document, the most common cause is that the trusted root certificate is no longer in the reader's trust store. Operating systems and PDF readers periodically update their list of trusted root certificates, and very old root CAs are sometimes removed. Adding the root certificate back to the trust store, if it can be obtained from a reliable source, restores full verification. This is good practice when working with documents that use a
Frequently Asked Questions
Is LTV the same as a Qualified Electronic Signature (QES)?
No, they address different aspects of signatures. A QES is a legal classification under eIDAS that requires identity verification of the signer and use of a qualified signature creation device. LTV is a technical mechanism for extending the verifiability of any digital signature over time. A signature can be both QES and LTV-enabled, which is the recommended combination for documents that need the highest legal standing across EU jurisdictions and must remain verifiable for many years.
Does adding LTV increase the PDF file size?
Yes, typically by 20 to 50 KB per signature. The additional data includes the OCSP response, the full certificate chain, and the timestamp token. For a document with a single signature, the increase is negligible. For documents that require dozens or hundreds of signatures, the cumulative size increase can become meaningful, but it is still small relative to the size of a typical multi-page PDF.
Can I add LTV to a PDF that was signed with a self-signed certificate?
Technically yes, but the practical value is limited. LTV embeds revocation status from a CA, but a self-signed certificate does not have a CA that can issue OCSP responses. The timestamp can still prove when the signature was applied, but the identity of the signer remains unverified. For documents that may face legal scrutiny, use a certificate from a recognized CA rather than a self-signed one.