Collection13 tools
On-device AI tools
Whisper, translation, OCR, segmentation and neural speech, executed on your own CPU or GPU — with the download sizes stated up front.
A few years ago the idea that you could run a speech recognition model in a browser tab was faintly ridiculous. Two things changed. Models got dramatically smaller for a given level of quality, through distillation and quantisation. And browsers grew the runtimes to execute them — WebAssembly with SIMD for CPU inference, and WebGPU for the GPU that has been sitting in your laptop the whole time.
The result is a real category, and it works differently from everything else on this site. Every other tool loads in a second and runs immediately. These download a model first — tens to hundreds of megabytes, once, cached by your browser afterwards — and then run inference locally. The first use is slow. Subsequent uses are not.
What you get in exchange is worth being explicit about, because it is not just privacy. There is no API key, so there is no signup and no billing. There is no rate limit, because there is no service to rate-limit you. There is no per-request cost, so transcribing a hundred files costs the same as transcribing one: your electricity. And the data never leaves, which for medical audio, legal recordings, customer transcripts, HR documents and internal screenshots is not a nice-to-have but the deciding factor.
How the models get here and where they run
Most of these tools use Transformers.js, the JavaScript port of the Hugging Face pipeline API, with ONNX Runtime underneath. On first use the model weights are fetched from the Hugging Face CDN and stored in your browser's cache. From then on the tool works from that cache — the model is on your machine, and re-running it is a local operation.
Execution goes to WebGPU where it is available and the model is suited to it, and falls back to WebAssembly on the CPU otherwise. The difference is large: WebGPU can be several times faster on the image models in particular. Some of the text models here are pinned to WebAssembly deliberately, because they are small enough that the GPU setup cost is not worth paying and because CPU execution is the more predictable path across browsers.
Two tools sit slightly outside that pattern. Image to Text is OCR via Tesseract compiled to WebAssembly, with the worker and core WASM served from this site directly; only the language data file is fetched from the Tesseract project's CDN on first use. Text to Speech uses Piper/VITS voice models — a real neural vocoder producing a downloadable WAV file, not the robotic built-in speech synthesiser — with each voice weighing roughly 20 to 60MB.
One consequence of quantisation deserves a mention because it is visible in the tools. The Translator runs a multilingual model of a few hundred million parameters at 8-bit quantisation, and it is quantised specifically because the full-precision version exhausts browser memory. Quantisation is what makes browser inference possible at all; it also costs a little quality. That trade is present, to different degrees, in every model here.
Speech, text and language
Audio/Video Transcriber runs Whisper locally. You give it an audio or video file, it decodes the audio in the browser, chunks it with overlapping strides so words are not lost at boundaries, and produces a transcript with timestamps — exportable as plain text, SRT or WebVTT. This is the tool on the site that most clearly justifies the whole category: recorded interviews, therapy sessions, legal depositions and internal meetings are exactly the material people are most reluctant to upload to a transcription service, and it is a base-sized Whisper model, not a toy.
Translator does multilingual translation across sixteen languages with no round trip to a translation API. Text Summarizer runs a distilled summarisation model with short, medium and long presets. Sentiment Analyzer gives a positive or negative classification with a confidence score. Zero-Shot Text Classifier is the more interesting one: you supply your own category labels at runtime, with no training and no fine-tuning, and it scores the text against them — which makes it genuinely useful for triaging a pile of feedback into buckets you invented five seconds ago.
PII Detector & Redactor pairs a named-entity model with pattern matching for emails, card numbers, IP addresses and phone numbers. It is the natural bridge to the AI developer tools: running it locally over text before that text goes to a hosted API is a sensible habit.
One clarification, since it is in the same part of the site: Text Similarity is not a model at all. It is TF-IDF and cosine similarity implemented in plain TypeScript. It is fast, it needs no download, and it is honest about being classical information retrieval rather than an embedding model.
Vision
Background Removal is the most immediately useful of the image models — a segmentation model that separates subject from background and exports a transparent PNG, in batches, with the model and its runtime fetched from a version-pinned CDN on first use. Object Cutout is the interactive counterpart, based on a compact Segment Anything variant: click a point on the thing you want, click again to add or exclude regions, and get a cut-out with a transparent background. Click-to-select is a much better interface than a lasso tool for anything with a complicated edge.
Image Upscaler runs a super-resolution transformer at a fixed 2x. It is real reconstruction rather than interpolation — it does better than bicubic on text and edges — and it is not the marketing version of upscaling: there is no invention of detail that was not implied by the input, and the input is capped in size because the memory cost scales with it.
Image Captioner produces a one-line description of a photograph, which is useful for draft alt text over a batch of images, with the emphasis on draft. Depth Map Generator estimates per-pixel depth from a single photo and renders it as a greyscale or false-colour image — input to compositing, parallax effects, or 3D work, from a plain photograph and no depth sensor.
When to use this and when not to
Use on-device inference when the data is sensitive, when you have volume and no budget, when you need it to work without an account, or when the task is genuinely small — a sentiment classification does not need a frontier model.
Use a hosted API when you need the best available quality, when the input is long and the latency matters, when you are running this in production for other people, or when the task requires reasoning that a 100-million-parameter model simply cannot do. The AI developer tools collection is the set of utilities for that path.
The two are complementary more often than people assume. Redact locally, then send. Transcribe locally, then summarise with a hosted model. Classify locally to route, then escalate the hard cases.
Thirteen models, thirteen tools
Each downloads its model on first use and caches it afterwards. Speech and text first, then vision.
- Audio/Video TranscriberAI ToolsTranscribe an interview, meeting or lecture with timestamps and SRT/VTT export, without uploading the recording.Open tool
- Image to Text (OCR)Text & Language ToolsOCR a scan, a photo of a page, or a PDF, in five languages including Arabic. Tesseract in WebAssembly.Open tool
- TranslatorAI ToolsTranslate across sixteen languages with no translation API involved.Open tool
- Text SummarizerAI ToolsCondense a long piece of text at short, medium or long settings.Open tool
- Sentiment AnalyzerAI ToolsClassify text as positive or negative with a confidence score.Open tool
- Zero-Shot Text ClassifierAI ToolsSort text into categories you define at runtime — no training data, no fine-tuning.Open tool
- PII Detector & RedactorAI ToolsFind and mask names, organisations, emails, card numbers, IPs and phone numbers before sharing text.Open tool
- Text to SpeechText & Language ToolsGenerate speech with a neural voice and download it as a WAV file. Ten voices across five languages.Open tool
- Image CaptionerImage ToolsGet a one-line description of a photo — a starting point for alt text at volume.Open tool
- Background RemovalImage ToolsCut the background out of photos in a batch and export transparent PNGs.Open tool
- Object CutoutImage ToolsClick on the object you want and get it isolated with a transparent background.Open tool
- Image UpscalerImage ToolsDouble an image's resolution with a super-resolution model rather than interpolation.Open tool
- Depth Map GeneratorImage ToolsEstimate depth from a single photograph and export it as a greyscale or false-colour map.Open tool
The honest trade-offs
These models are smaller and slower than what an API gives you. That is the deal, and it is not a small deal. A data-centre GPU running a large model will beat a browser running a distilled, quantised one on almost every quality metric, and it will do it faster. Transcribing an hour of audio in a tab takes real time — minutes, not seconds — and on a machine without WebGPU it takes considerably longer. If you need the best possible transcript of a difficult recording, a hosted service will produce it.
The first run downloads a model. Depending on the tool that is tens of megabytes to a few hundred. On a metered or slow connection that is a genuine cost, and it happens before you see any output. The browser caches it afterwards, but clearing site data means downloading again.
Quantisation costs accuracy. Several of these models are quantised to fit in browser memory — that is why they can run at all. Expect a small quality gap against the same architecture at full precision.
Browser and hardware variance is real. WebGPU availability differs by browser, operating system and GPU; without it, everything falls back to CPU and gets slower. Memory limits are per tab, which is why several tools cap their input size rather than letting you crash the page. Long documents and long recordings hit those ceilings first.
And an important scope note: this collection is on-device *models*. Live Dictation is not in it, despite being a speech tool, because it uses the browser's built-in Web Speech API — which in several major browsers performs recognition on the vendor's servers. If you need speech recognition that is genuinely local, the tool for that is Audio/Video Transcriber.
Related collections
- AI and LLM developer toolsToken budgets, prompt shaping, and the config files you end up writing when you build on top of a language model.
- Privacy-first toolsMetadata, credentials, redaction and signatures — handled in the tab instead of on someone else's server.
- Image toolsEighteen canvas utilities for the four things people actually do to images: make them smaller, change the format, change the shape, make them presentable.