QPDF WASM
Protect PDF and Unlock PDF use QPDF compiled to WebAssembly, so encryption and decryption can run locally in modern browsers.
Security
Security Overview
LiftPDF protects files by reducing unnecessary movement. The safest upload is the one your browser does not need to make.
Browser ProcessingNo UploadPrivacy FirstLocal ConversionFast
LiftPDF promise
The current LiftPDF tools are built around browser-side processing. Files are selected, processed and exported locally on your device.
Browse toolsNo server upload
How browser processing works
Your device
You choose files in your browser.
Local processing
PDF.js, pdf-lib or QPDF WASM runs the task locally.
Download
The result is created for you to save.
LiftPDF tools are designed so the selected files are read by the browser and processed on your device. The current tools do not require a document upload API.
PDF.js
PDF.js renders previews and extracts readable PDF content in the browser without needing a document upload endpoint.
COOP and COEP
LiftPDF serves Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy headers to support isolated browser execution for advanced workflows.
crossOriginIsolated
When supported by the browser and headers, this creates a stronger execution environment for WebAssembly and related browser features.
What LiftPDF does not claim
LiftPDF does not claim ISO 27001, SOC2, external audit status or any other certification that has not been earned. The security promise is intentionally narrower: the current tools are designed to process files locally in the browser whenever possible.
Security FAQ
Do passwords leave my browser?
Protect PDF and Unlock PDF use the password locally in the browser through QPDF WASM. LiftPDF does not need to send the password to a backend API for these tools.
Why does LiftPDF use COOP and COEP headers?
These headers help enable a safer isolated browser context for advanced WebAssembly workflows. They are part of the production configuration.
Does LiftPDF claim a security certification?
No. LiftPDF does not claim ISO, SOC2 or external audit certification. The trust model is based on transparent browser-side processing.
Are encrypted PDFs really encrypted?
Protect PDF uses QPDF compiled to WebAssembly to create password-protected PDF files. The exported file requires the password in PDF viewers.