Private
Your files never leave your device for the current browser-side tools.
Privacy
LiftPDF is built around a simple idea: when a PDF task can run in your browser, your file should not need to leave your device.
The current LiftPDF tools are built around browser-side processing. Files are selected, processed and exported locally on your device.
Browse toolsYour files never leave your device for the current browser-side tools.
Local browser processing avoids sending documents to a conversion server.
Processing starts on your device without waiting for upload queues.
No registration is required to use the available LiftPDF tools.
No server upload
You choose files in your browser.
PDF.js, pdf-lib or QPDF WASM runs the task locally.
The result is created for you to save.
A typical online converter receives your document, processes it on a remote server and then sends a result back. LiftPDF's current tools avoid that upload step. Your browser reads the file, performs the operation and creates a downloadable result locally.
LiftPDF uses browser-compatible libraries that run on the user's device. The exact library depends on the tool.
The available LiftPDF tools are designed as client-side workflows. This includes image conversion, PDF page organization, PDF to image, page numbers, watermarks, compression, protection, unlocking and text extraction.
LiftPDF is built for modern browsers such as Chrome, Edge, Firefox and Safari. Advanced tools that use WebAssembly, PDF.js or canvas may work best on up-to-date browsers with enough device memory for the file size being processed.
LiftPDF uses Google Analytics only after you accept analytics. Tool events are limited to product usage signals such as tool name, route, output format and coarse file-size buckets. LiftPDF does not intentionally send file names, document contents, extracted text, passwords or local file paths to analytics.
Read the Cookie PolicyThe current LiftPDF tools are designed for browser-side processing, so selected files are processed locally on your device and do not require a document upload API.
No. The current tools do not store your documents on LiftPDF servers. Output files are generated in your browser for you to download.
Some future workflows, such as advanced OCR or Office document conversion, may require server-side processing. If that happens, LiftPDF should label the behavior clearly before files are selected.
Protect PDF and Unlock PDF run with QPDF compiled to WebAssembly in the browser, so passwords are used locally for the encryption or decryption task.