I Built Free PDF Tools That Run 100% in the Browser — No Server, No Uploads

Description and use

A fully client‑side PDF toolset was built to let users merge PDFs, convert images to PDFs, and extract images from PDFs without uploading files, ensuring privacy and zero hosting costs.

Problem

Pakistan's news readers needed simple, trustworthy utilities—merge a PDF, turn photos into a PDF, pull images out of a PDF—without uploading personal documents to a random server.

Outcome

The client‑side PDF toolset operates without a server, keeps user data private, runs on mobile and desktop browsers, and incurs negligible hosting costs.

Workflow

• 1. User selects files via drag‑and‑drop or file picker.
• 2. pdf-lib merges PDFs or assembles JPGs into a PDF.
• 3. pdf.js rasterizes PDF pages to JPGs for export.
• 4. Operations run in chunked async steps to keep the UI responsive.
• 5. Result is downloaded locally; no upload endpoint is used.

Evidence

Pakistan's news readers needed simple, trustworthy utilities — merge a PDF, turn photos into a PDF, pull images out of a PDF — without uploading personal documents to a random server.

Source

The stack is deliberately boring: two CDN libraries, zero backend.

Source

pdf-lib handles merge and JPG-to-PDF assembly.

Source

pdf.js (Mozilla's renderer) handles PDF-to-JPG page rasterization. Every operation runs in the browser with chunked async steps, so the UI never freezes on a 50-page document. The key privacy property: files never leave the device.

Source

No-backend means no bills. Hosting is a static page. The tools cost essentially nothing to run at scale — a meaningful property when your audience is price-sensitive students and job applicants.

Source