We Built 120 Local-First Browser Tools — and a Playwright Harness That Proves Nothing Gets Uploaded
Every developer and knowledge worker has had the same awkward moment: you need to rotate a confidential PDF, convert a HEIC screenshot, decode a JWT, or validate a JSON schema—you search for an online tool, land on a pag
Every developer and knowledge worker has had the same awkward moment: you need to rotate a confidential PDF, convert a HEIC screenshot, decode a JWT, or validate a JSON schema—you search for an online tool, land on a page covered in ads, and hesitate right before clicking Upload.
Almost every online tool site puts "100% private — your files are processed locally" somewhere on its landing page.
The problem? Users have no easy way to verify that claim, and even well-intentioned apps can accidentally regress when a dependency, CDN fallback, or third-party script starts sending data off-device.
When we built Toolars — a free platform of 120 browser-based tools across 7 categories (Developer, Image Studio, Design & CSS, PDF, Writing, Social Mockups, and File Utilities) with no sign-up required — we decided privacy shouldn't be a marketing tagline. It should be continuously testable against production.
Here is how we architected it and built an open-source Playwright harness that anyone can run against our live site.
1. What Runs Locally (120 Tools, 7 Categories)
Toolars is built with Next.js 16 (App Router) + React 19 + strict TypeScript and runs tool processing client-side in the browser (using dedicated Web Workers and lazy-loaded WASM/browser engines where needed):
- Developer (38 tools): JSON Explorer, JSON Schema Validator, JWT Decoder, Base64, Hash, URL Workbench, Robots Lab, HTML Publishing, and more.
-
Image Studio (19 tools): Format conversion (including HEIC → JPEG via a lazy-loaded ~3.3 MB
libheifdecoder), resizing, cropping, compression, and client-side OCR. - Design (17 tools): CSS and color generators with live preview and copy-ready output.
- PDF Tools (15 tools): Edit, sign, fill forms, whiteout, rotate, merge, split, and compress PDFs entirely on-device.
- Files & Utilities (12 tools): QR codes, password generation, list utilities, CSV/XLSX workflows.
- Social Mockups (11 tools) & Writing (8 tools): Preview generators, formatters, and text analysis tools.
Heavy runtimes (like libheif for HEIC decoding or OCR language packs) are served strictly from our own origin and loaded lazily on first use—never from random third-party CDNs.
2. The Hard Part: Proving "No Uploads" Against Production
Open-sourcing a website's frontend code still doesn't prove what is actually deployed on https://toolars.com today.
Instead of asking people to trust our source repo or a footer badge, we published a standalone, MIT-licensed Evidence Harness (aixtral/toolars-open/evidence-harness) that tests the live deployed website like a skeptical user would.
How the Canary Verification Works
Each run launches fresh headless Chromium contexts via Playwright (with service workers blocked so nothing can hide behind a background cache or intercept) and drives 6 end-to-end scenarios:
-
image-tool-convert— Converts PNG → JPEG and downloads the result twice: a warm-up pass, then a measured pass using a file whose bytes contain a random canary string. -
image-tool-heic-convert— Converts HEIC → JPEG twice: first pass loads the lazy ~3.3 MBlibheifdecoder (asserted same-origin only); the measured pass must issue zero requests. -
ocr-language-pack— Runs English and Simplified Chinese OCR; language packs must arrive only fromtoolars.com, and recognized text is asserted. -
pdf-tool-rotate— Loads a sample PDF, rotates it, and downloads the output. -
csv-excel-relay— Cleans a synthetic CSV with an embedded marker, hands it off in-tab, and exports XLSX. -
custom-text-chain— Runs a two-step local text workflow chain with an embedded marker and verifies the output.
During every measured window, the harness records all network requests—including dedicated Web Worker fetches—and enforces four hard invariants:
1. uploadRequests === 0 // No request body; no non-GET/HEAD/OPTIONS method
2. canaryLeaks === 0 // Random canary string never appears in any URL or body
3. unexpectedCrossOriginRequests === 0 // Nothing leaves toolars.com except disclosed analytics proxy
4. Same-origin decoder/OCR assets & verified local output
The canary check is the strongest guarantee: the input file's raw bytes literally contain a random string. If those bytes ever crossed the network—regardless of host, header, or encoding trick—canaryLeaks trips immediately and fails the run.
Honest Bookkeeping: verified vs violation vs inconclusive
One design detail we cared a lot about: never conflate a flaky network with a privacy violation, and never hide an analytics host.
- The live site loads a cookieless page-view script from
track.toolars.com(our first-party analytics proxy, explicitly disclosed on our Trust Center). Any request to it is still counted and logged in the receipt (disclosedShellRequests), while any upload body or canary leak fails regardless of host. - Runs produce one of four explicit outcomes:
verified,violation,inconclusive(e.g., transient timeout—never silently treated as passing or mislabeled as a leak), orviolation+inconclusive. - Receipts only store request metadata (method, host, path, resource type, whether a body existed)—never file contents.
- A follow-up check (
verify-live-privacy-proof.mjs) binds the captured receipt to the release currently served in production so a green historical badge can never mask a newer deployment.
A GitHub Action runs this entire verification every day at 03:17 UTC against https://toolars.com.
Run It Yourself in 30 Seconds
You don't need our private website repo to audit the live site:
git clone https://github.com/aixtral/toolars-open.git
cd toolars-open/evidence-harness
npm install
npx playwright install chromium
npm run verify
It writes privacy-proof-receipt.json locally and exits 0 only if every single scenario passes.
3. Beyond the Browser: Chrome Extension & Local MCP Server
Because developers don't only work inside web tabs, we also shipped two lightweight companions:
- Chrome Extension (Toolars Developer Toolkit): Local side-panel access plus right-click context actions for JSON, JWT, timestamps, and images.
-
MIT-licensed CLI & MCP Server (
@toolars/cli): Zero-telemetry local stdio utilities (hash,base64,JWT decode,UUID/ULID,timestamp,cron,URL codec) you can wire straight into Claude / Cursor / Antigravity / any MCP client:
npx -y -p @toolars/cli toolars-mcp
Try It & Break It
- Web App (120 free tools, 13 languages, no sign-up): toolars.com
- Trust Center & Live Receipts: toolars.com/trust-center
- Open-Source Privacy Harness & MCP CLI: github.com/aixtral/toolars-open
If you run npm run verify and spot an undisclosed host or edge case we missed, please open an issue on GitHub. And if there's an everyday browser tool you're tired of uploading sensitive files to, drop it in the comments—we're actively expanding the catalog!
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.