Privacy

Privacy First

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.

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 tools

Private

Your files never leave your device for the current browser-side tools.

Secure

Local browser processing avoids sending documents to a conversion server.

Fast

Processing starts on your device without waiting for upload queues.

Free

No registration is required to use the available LiftPDF tools.

No 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.

Why local processing is safer

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.

  • No document upload is required for the current tools.
  • Files are not stored on LiftPDF servers by the available tools.
  • Sensitive PDFs, scans, IDs and work files remain on your device.

Technologies used

LiftPDF uses browser-compatible libraries that run on the user's device. The exact library depends on the tool.

  • PDF.js renders and reads PDF pages for previews and text extraction.
  • pdf-lib creates, copies, rotates and edits PDF pages in the browser.
  • QPDF WASM handles real password protection and unlocking locally.
  • Browser APIs handle files, canvas rendering, Blob downloads and object URLs.

Tools that currently work in the browser

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.

  • Images to PDF, JPG to PDF and PNG to PDF
  • Merge, Split, Delete, Extract and Reorder Pages
  • PDF to JPG, PDF to PNG and PDF to Text
  • Protect PDF and Unlock PDF with QPDF WASM

Browser compatibility

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.

Optional analytics

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 Policy

Frequently Asked Questions

Are my PDF files uploaded to LiftPDF?

The 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.

Does LiftPDF store my documents?

No. The current tools do not store your documents on LiftPDF servers. Output files are generated in your browser for you to download.

Can a future tool require a server?

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.

What happens to passwords?

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.

Related trust pages