About LuraPDF

Our Mission

LuraPDF exists to give everyone access to professional-grade PDF tools without cost, registration, or privacy trade-offs. Every major task — merging, splitting, compressing, converting, signing, and editing PDFs — should be instant and free.

We built LuraPDF on a single constraint: your files never leave your device. There is no upload server, no cloud processing, and no file storage. When you close the tab, your data is gone.

Why We Built LuraPDF

The team at Metal Devs needed a way to redact sensitive documents before sharing them. Every major online PDF tool either required an account, charged a fee, or — most troublingly — uploaded the file to a remote server before processing it. The solution was to build a tool that processed everything locally, in the browser.

LuraPDF started as a single-tool project and grew into a full suite. The founding principle has not changed: your files stay on your machine, always.

Built by Metal Devs

LuraPDF is designed, built, and maintained by Metal Devs — a software studio focused on privacy-first web tools. We build things that work without asking for your data.

How It Works

LuraPDF runs PDF processing directly in your browser using WebAssembly and modern JavaScript APIs. When you load a PDF, it is read into memory locally. Operations like compression, merging, and OCR execute on your CPU — not on any server. This architecture means there is no latency from uploads, no file size limits imposed by bandwidth, and no risk of your documents being stored or accessed by a third party.

Open-Source Technology

LuraPDF is built on the shoulders of excellent open-source libraries:

• pdf-lib — PDF creation, modification, and merging
• PDF.js (Mozilla) — PDF rendering and text extraction
• Tesseract.js — OCR engine via WebAssembly, with optional language packs covering 100+ languages
• Fabric.js — Canvas-based PDF annotation and editing

Privacy by Architecture

Most online PDF tools upload your documents to a remote server for processing. LuraPDF does not. The browser receives the tool code, and your CPU does the work. No file ever touches our infrastructure.

We use Google Analytics to understand aggregate usage patterns (pages visited, tool usage counts) and Google AdSense to serve ads that fund free access. Neither service receives your PDF files or their contents.

Contact

Questions, bug reports, or feedback? Reach us at [email protected].