zeal.tools
Free tools, made with zeal.
No sign-ups, no watermarks, no nonsense — and your files never leave your device.
Open the tools → · Blog · API · Request a tool
The web is full of bad utility tools: QR generators stuffed with ads, outputs with watermarks, sign-up walls in
front of a ten-second job. zeal.tools is the alternative — fast, clean, open-source tools that do the job and get
out of the way. Almost all of them run entirely in your browser, including the AI ones.
The tools
| Tool | What it does | API · MCP |
|---|
| ▦ | QR Code Generator | Static QR codes for links, WiFi, vCards, email, phone and SMS — no expiry, PNG or SVG | ✓ |
| 🪄 | Background Remover | Cut the subject out of a photo with an AI model that runs on your machine | |
| 🎚️ | Stem Splitter | Split a song into vocals, drums, bass and the rest — or six stems — in the browser | |
| 🗜️ | Image Compressor | Compress, resize and convert images in a batch, without uploading them | |
| ⇄ | Send to Device | Phone to laptop and back, directly over your network — no cable, no cloud | |
| 🧾 | Invoice Maker | Write an invoice, save it as a PDF, keep your details for next time | |
| 🔑 | Password Generator | Strong passwords from your OS's cryptographic randomness, never sent anywhere | ✓ |
| 🙈 | Image Redactor | Brush over faces, plates or text to blur, pixelate or black them out | |
| 🔍 | EXIF Viewer | See what a photo reveals — location included — and strip it losslessly |
The Zeal Promise
On every tool, non-negotiable:
- No sign-up, ever. There is no account system to sign up for.
- No watermarks on anything you download.
- No ads near the download. That area is never blocked or crowded.
- Privacy-first. Processing happens in your browser wherever it possibly can — even the background remover and
stem splitter run their AI models on your own machine. The one tool that must touch a server, the meta tag checker,
says so on the page.
- Open source, MIT. Audit it, contribute, or self-host it.
Use it from code, too
The tools whose logic is a pure function — QR codes, passwords, chord charts, name picking and meta tags — are also
callable over REST and MCP, from the same implementation the UI uses.
REST — no key, no sign-up, 120 requests a minute:
curl -X POST https://zeal.tools/api/v1/qr \
-H 'content-type: application/json' \
-d '{"data": "https://zeal.tools"}' # → SVG
curl 'https://zeal.tools/api/v1/qr?data=hello&format=png' -o qr.png
The full list lives at /api/v1 and in the
RFC 9727 catalog.
MCP — add it to Claude, your IDE or any MCP client:
{ "mcpServers": { "zeal-tools": { "url": "https://zeal.tools/mcp" } } }
Agents can start from llms.txt.
Built to be auditable
Tool logic ships with zero runtime npm dependencies. The app shell is Nuxt and Tailwind; everything a tool
actually computes is ours. The QR encoder is a from-scratch ISO/IEC 18004 implementation — segment encoding,
Reed–Solomon over GF(256), all eight masks with penalty scoring — and it is verified by round-tripping payloads
through an independent decoder held as a devDependency, across every version, error-correction level and mask.
There is exactly one exception, and it is documented:
onnxruntime-web, because executing a neural network is a whole ML runtime rather than a format we could own. It
loads lazily, only on the tools that need it, and the model weights stream from Hugging Face — nothing large ships in
a deploy.
Why bother?
- Readable in an afternoon. A tool site handles WiFi passwords, contact details and photos. You should be able
to read every line that touches them.
- Isomorphic by construction. Pure functions run identically in your browser, in Cloudflare Workers and behind
the MCP endpoint — one implementation, three surfaces.
- Proof, not vibes. Self-written cores are tested against independent implementations and the spec, not just
against themselves.
Accessibility and performance
WCAG 2.2 AA in both themes: keyboard-complete, visible focus, 44px targets, live announcements and reduced motion.
The homepage and tool pages score 100 on Lighthouse accessibility, best practices and SEO. Every page is
prerendered and served from Cloudflare Workers, and each tool's code loads only on its own page.
Architecture
One Nuxt 4 app, composed from domain slices as Nuxt layers. Everything that belongs to a tool lives in one
folder:
tools/qr-code-generator/
├── meta.ts # registry entry: name, keywords, variants, api/mcp flags
├── core/ # ★ pure, isomorphic, zero-dependency logic + unit tests
├── app/ # pages, components, composables — this slice only
└── server/ # REST endpoint, importing the SAME core/
Adding a tool means adding a folder and one line in shared/registry; the homepage, search, sitemap, API index and
MCP tool list all follow from it. Slices never import from each other — shared code graduates to shared/. See
CONTRIBUTING.md for the slice template and the per-tool checklist.
Development
pnpm install # also runs nuxt prepare
pnpm dev # dev server on :3000
pnpm test # unit tests, including the encoder round-trips
pnpm lint # eslint
pnpm build # build for Cloudflare Workers
pnpm preview # run the build in the real Workers runtime
Pushes to main deploy through Cloudflare Workers Builds; there are no credentials to set up.
Contributing
Ideas and bug reports are welcome — every tool page has a Report an issue button that fills in which page you
were on. To suggest something new, request a tool.
Pull requests should follow CONTRIBUTING.md.
License
MIT — built with zeal by zernonia.
