Blog

Three major changes shipped in June 2026: share URLs rolled out to every tool, every tool gained a long-form article, and this blog launched. Here's the context and intent behind each.

Salary figures, freelance gross income, household composition, property valuations, estate estimates — the inputs to Japanese tax and social-insurance calculators rank among the most sensitive numbers in a person's life. Here is why the gap between "free online tax calculator" and "browser-only calculator" is especially meaningful for this category of tools.

The Japanese tools on NoSend Tools — kanji-to-hiragana, kanji-to-romaji, wakati-tokenize, furigana-html, japanese-counter-word and more — all run morphological analysis in the browser using kuromoji.js. Here is what the 12 MB IPADIC dictionary contains, how Viterbi tokenisation works, and what it means to run Japanese NLP without sending text to a cloud API.

HuggingFace's transformers.js uses ONNX Runtime Web to run models like Whisper and RMBG-1.4 entirely in the browser. Model weights are downloaded and cached locally; your audio and images never leave your machine.

GPS leaks from EXIF metadata, sensitive face data and unreleased designs passing through servers, and the amplification of privacy exposure when multiple photos are combined — image tools carry distinct risk layers. Here is how NoSend Tools handles each class without sending data outside your browser.

NoSend Tools' PDF suite is built on two libraries with very different jobs: pdf-lib for creation and editing, PDF.js for rendering and parsing. Here is why the split exists, what each library handles, why PDF structure makes this harder than it looks, and why keeping the whole pipeline inside the browser matters for documents that frequently contain personal or legal data.

ffmpeg.wasm compiles the C ffmpeg project into a WebAssembly module that runs entirely inside a browser. This post explains what is actually downloaded (~30 MB), how SharedArrayBuffer and cross-origin isolation enable multi-threaded encoding, and why the WASM sandbox itself enforces the "media never leaves your device" guarantee.

A privacy claim in a footer is just trust. NoSend Tools is built so the claim is verifiable in two ways: open DevTools and see no requests, or read the source on GitHub. Here is how to do each.

NoSend Tools launched in May 2026. Following the actual commit log, here's what got built in the first three weeks and how the architectural choices played out.

A decade ago, video conversion and PDF editing on the web defaulted to server-side processing because nothing else worked at acceptable speed. WebAssembly broke that assumption. Here's the technical stack NoSend Tools relies on, and why it matters.

"Files are deleted right after processing" is a promise users cannot verify after the fact. Once data leaves your machine over the network, it has already passed through caches, logs, and infrastructure outside your control. Here's why NoSend Tools doesn't transmit user input at all.