Open a tool — that’s the whole login. Work stays in this tab unless you choose to save it back to your device.
94 tools
30 languages
0 uploads
Both counts are read from this build of Kit — the tool registry and the list of interface languages. The third number is a design decision, not a metric.
| Typical online tool | Kit | |
|---|---|---|
| Your file | Uploaded to their server | Stays in this tab |
| The result you download | Fetched back from their server | Written here, from this tab, onto your disk |
| Account | Email and password | None |
| Tracking | Ads or analytics SDKs | None from Kit |
| Processing | Their computers | Your browser |
| Currency conversion | Often the amount travels, too | Pair codes only, and only when this browser has no fresh cache. Amounts stay here. |
| After you leave | They may keep a copy | Gone with the tab |
1.You open a file
2.The tool runs here
3.You save it back
There is no Kit server in that path. The host may log that you downloaded the page, not the document.
There is no third column. Kit does not have a processing server sitting between this tab and your file.
Keeping files in the browser is not only a privacy stance. It changes what a tool can promise you.
Your files, amounts, and passwords never meet a Kit server, because there is no Kit server to meet.
A large video does not spend minutes uploading before work starts. The tool begins the moment the file is in the tab.
No upload cap, no queue, no premium tier for bigger files. The real ceiling is this device’s memory.
Once a page has loaded, the tool keeps running in airplane mode. Install Kit and the same holds between visits.
Two real examples, traced step by step. Neither touches the network beyond loading Kit itself.
Any of the other 94 tools follows the same shape: input stays here, the engine runs here, the result is written here.
| Job | What runs | Where | Downloads |
|---|---|---|---|
| pdf.js, vendored on this site | This tab | The engine, when you first use a PDF tool | |
| Audio & video | FFmpeg WebAssembly (GPL-2.0-or-later) | This tab | About 10 MB once, then cached |
| Images | Canvas | This tab | Nothing extra — the browser already has it |
| Passwords & hashes | Web Crypto | This tab — Kit does not store the password | Nothing extra — the browser already has it |
| Installed app | Service worker | Caches the app shell, not your files | Nothing extra — it caches, it does not send |
| 30 languages | Interface in this browser | No extra account for a locale | The pages and scripts themselves |
Everything below is measured in this browser, right now — not promised.
Currency rates may query Frankfurter’s public API when this browser has no fresh cache for that pair. Amounts you type are not sent. Everything else that needs a network is fetching Kit’s own static files (pages, scripts, pdf.js, FFmpeg).
Cloudflare Pages (and the GitHub Pages backup) may log standard request data such as IP address when your browser downloads Kit. That is hosting, not file processing.
Lost connection after a page loaded? The tools keep working. Install Kit and the same holds between visits.
Yes. No account, no tiers, no ads. Kit is MIT-licensed open source, and because the tools run in your browser there is no server bill to pass on.
Nowhere. They are read and processed inside this tab and written back to your disk when you save. The network log on this page shows exactly what crossed the wire.
Yes. Once a tool page has loaded — or once Kit is installed — the tools keep working with no connection. The currency converter is the only exception, and only for fresh rates.
Audio and video run on FFmpeg compiled to WebAssembly. That engine downloads once, the service worker caches it, and every file after that reuses it.
Only what you opt into: language, appearance, favorites, presets, and a short history summary — which tool, roughly when, never the file. Clear it any time in Settings.
Clear history in Settings, or delete this site’s data in your browser. After that, this browser holds nothing about your use of Kit.
Yes. Kit is a progressive web app — open it in a mobile browser and install it to your home screen for the same tools on the same terms.
Kit reads this device’s clock and calendar. Nothing about the greeting is sent anywhere. There is no account, so it cannot greet you by name — that is the point.
Pick a file you don’t care about, run it through a tool, and watch the network tab. The strongest claim on this page is the one you can check yourself.
The legal wording lives in the Privacy Policy and Terms. Privacy Policy · Terms of Use
