DoxDock

Offline-first document & image tools that run 100% in your browser. Nothing you open ever leaves your machine.

DoxDock is a collection of ~20 everyday PDF and image utilities — merge, split, compress, convert, watermark, extract text, and more — built on one hard rule: your files never get uploaded anywhere. Every operation runs client-side, on your device, using your browser's own CPU. No servers, no accounts, no analytics, no network.

It exists for the moment you have a sensitive PDF — a contract, a payslip, a medical scan — and just need to do one thing to it without handing it to a random online converter. Read the ideology letter for the why.

Runs entirely in your browser — no uploads, no network.

• Add DoxDock to Chrome to run every tool from your browser, fully on your device, even offline.
• Open the web app if you would rather not install anything. It works in any modern browser and can be added as a PWA.

Both are the same app, and both keep every file on your machine.

Most "free online PDF tools" upload your file to a server you know nothing about. DoxDock is the opposite, and it's built so you don't have to take our word for it:

1. A strict Content-Security-Policy forbids network access. index.html ships a CSP with connect-src 'self' — the browser will refuse any outbound fetch/XHR/WebSocket to any host but its own origin. If a future change tried to phone home, the browser would block it.
2. Everything is bundled locally. Fonts (system stack), icons (inline SVG), the pdf.js worker, and all WebAssembly are served from the app itself. There are no CDN links, no external fonts, no trackers.
3. It's an installable PWA that works offline. After the first load, a service worker caches everything. Pull your network cable / turn off Wi-Fi — every tool still works.

• Open DevTools → Network tab, then use any tool. You'll see requests only to your own origin (in dev, localhost) — never an external domain.
• Or: load the app once, go fully offline (airplane mode / disconnect), and reload. Everything keeps working.
• Or: read the source. It's MIT-licensed and small. connect-src 'self' is in index.html; the pdf.js worker is bundled in src/lib/pdfjs.js.

We persist only non-sensitive UI state (your theme and last-used tool) in localStorage. File contents are never written to storage and never transmitted.

The quickest way to self-host. DoxDock ships as a static site, so the container just serves the built files with nginx — it makes no outbound calls and can run completely offline / air-gapped.

With Docker:

# build the image (--load puts it in your local image store; needed when the
# active buildx builder uses the docker-container driver)
docker build --load -t doxdock .

# run it (serves on http://localhost:8791)
docker run --rm -p 8791:80 doxdock

With Docker Compose:

docker compose up --build
# then open http://localhost:8791

The image is a multi-stage build (Node builds the site, nginx serves it), so the final image is tiny and contains only static assets — no Node runtime, no source. The app is published on host port 8791 (chosen to avoid clashing with common dev servers); to use a different port, change the left-hand number, e.g. -p 3000:80 (or edit docker-compose.yml).

Self-hosting keeps the "provably local" guarantee intact: the container serves files and nothing else. You can disconnect it from the internet entirely and every tool still works.

# install
npm install

# dev server (http://localhost:5173)
npm run dev

# production build -> dist/
npm run build

# preview the production build
npm run preview

Requirements: Node 18+. No backend, no environment variables, no services to run — it's a static site.

npm run build
npm run preview
# open the URL, then disconnect your network and use the app.
# In DevTools → Network, confirm zero requests leave your origin.

Operations whose client-side result has inherent limits are labelled honestly in the UI and here.

• React + plain JavaScript (JSX) + Vite
• Tailwind CSS (the "Aurora" theme — deep slate with a mint→sky glow, light + dark)
• vite-plugin-pwa for the offline/installable service worker
• Client-side libraries, all bundled locally (no CDN): pdf-lib, pdfjs-dist (worker bundled), jspdf, docx, mammoth, browser-image-compression, fflate (zip). Plus the browser Canvas and Web Crypto APIs.

No dependency makes network calls at runtime. Heavy work (pdf.js rendering, image compression) runs in web workers to keep the UI responsive.

DoxDock uses a plugin/registry architecture. Each operation is a self-contained folder under src/operations/<id>/ with metadata, a component, and pure helpers. A central registry auto-discovers them via import.meta.glob and lists them in a searchable, categorized sidebar with a Cmd/Ctrl+K command palette. Adding a tool = drop in one folder. See CONTRIBUTING.md.

PRs welcome — especially new operations. See CONTRIBUTING.md for a step-by-step guide. The one rule that can never break: no runtime network requests.

Proudly supported by the OSCode Community — an open-source developer community. If DoxDock is useful to you, a ⭐ on the repo helps others find it.

MIT © 2026 Mithun Srinivas