About
Every tool. One place.
OmniKitly is a universal utility workspace: documents, images, media, developer utilities and everyday digital tasks, built to grow to hundreds of tools without becoming a mess.
Why another utility site
Most online tool sites are either one good tool wrapped in ads, or a hundred mediocre ones behind a sign-up wall. We want the opposite: a toolbox that is fast to open, private by architecture, honest about what runs where, and organised so that the two-hundredth tool is as easy to find as the first.
Principles
- Local first. If a task can run in your browser, it does.
- Server when necessary. Some jobs need real hardware. The badge tells you before you start.
- Account only when necessary. Bulk, history and API — not for merging two PDFs, and not for workflows, which live in your browser.
- No fake claims. Not about privacy, not about compliance, and not about which features exist yet.
What works today, and what does not
No claim on this site outruns what is built. Here is exactly where the line is.
Working today
- 230 tools that run entirely in your browser — the file never leaves your device
- 49 server tools: real conversion, compression, OCR and encryption
- Uploads validated by magic bytes, not by file extension
- Signed, expiring download links; results deleted on expiry
- Global search with aliases and keyboard navigation
- Favourites, recent tools and theme (stored in this browser only)
- Accounts, sessions and API keys
- Bulk processing: many files through one tool, each tracked and retried on its own
- Workflows: chain tools, set each step, save the recipe in this browser
- Fair-use limits and a self-hosted challenge — no third-party CAPTCHA
- A written page for every tool, checked against the code behind it
Not built yet
- 1 tool is listed but withdrawn: Webpage to PDF needs a headless browser this server does not run
- Signature requests — sending a document to someone else to sign, with an audit trail
- PDF/A conversion — needs a colour-profile engine this server does not run
- Teams and integrations
What was built, in order
- The client processing engine for local tools (PDF.js, pdf-lib, Canvas, Web Workers).
- The jobs API, queue and isolated workers for server tools.
- Accounts, the bulk dashboard and workflow execution on the shared engine.
- A page for every tool, each checked against the code that implements it.
Still to come
- Signature requests — sending a document to someone else to sign, with an audit trail.
- Teams and integrations.
The architecture, including the security requirements every server tool meets, is documented in README-ARCHITECTURE.md alongside this build.