Kit-Bin VS ShellNewHandler

Kit-Bin's answer

Kit-Bin's tools run entirely client-side, in the browser, using JavaScript/WASM — no file is ever transmitted to a server. That's a stronger claim than most "privacy-friendly" converters make, since it's an architectural fact you can verify yourself (open devtools, watch the Network tab while using any tool) rather than a retention policy you have to trust. It's also open source, no accounts, no signup, and no feature paywall — the entire 60+ tool suite (PDF, image, audio, video, data, and developer utilities) is free and usable immediately.

Kit-Bin's answer

Most free converter sites — even ones that market themselves as privacy-conscious — still upload your file to a server to process it and rely on a policy promise ("we delete it after 24 hours") rather than a technical guarantee. Kit-Bin never uploads anything in the first place, so there's nothing to trust and nothing that can leak in a breach, because the file never leaves your device. For anyone converting or editing something sensitive — a scanned ID, a document with personal data, a photo with embedded location metadata — that's a meaningful difference, not a marketing detail. It's also genuinely free with no account wall, and open source, so the claim is checkable rather than taken on faith.

Kit-Bin's answer

Two overlapping groups: privacy-conscious individuals who specifically don't want to upload personal files to a third-party server (students, professionals handling sensitive documents, anyone converting photos or scans with personal data attached), and developers/technical users drawn to the developer-tool utilities (SHA-256, Base64, UUID generation, JSON schema validation, QR codes) who value the same no-upload guarantee for things like credentials, config files, or internal data.

Kit-Bin's answer

It started from a personal frustration: needing to convert, merge, or clean a file — sometimes something sensitive, like a scanned document or a photo that still had GPS metadata embedded in it — and finding that every "free" tool available wanted it uploaded to a server first. Rather than trust a privacy policy, the goal became building tools that were private by construction instead of by promise. Once a couple of tools worked that way, the same principle applied naturally to every other file type people deal with regularly, which is how one converter grew into a full suite across PDF, image, audio, video, data, and developer tooling.

Kit-Bin's answer

Client-side JavaScript/WebAssembly for the actual file processing (so tools run entirely in the browser), with Astro powering the site itself. Double-check this against your actual current stack before submitting — I'm working from what's visible in the codebase/site structure, not a confirmed tech-stack list, and don't want to state something that's since changed.