Skip to content
nah

How it works

Most tools run on your device. A few need a hosted service. Here is what that means in practice.

Local file processing

PDF editing, image conversion, background removal, media processing and transcription run in your browser using JavaScript, WebAssembly and, where supported, WebGPU. Resume and invoice generation also happen locally. These browser tools do not upload your source files for processing. Drafts and progress may be stored in this browser, so export a backup before clearing site data.

Your device supplies the memory and processing power. Large files, long recordings and bigger AI models can be slow or exceed available memory, especially on a phone. Lossy conversion and compression can reduce quality; inspect the output and keep the original.

Downloads and connections

Local processing still needs software. FFmpeg downloads from unpkg, transcription models from Hugging Face and background-removal models from a Cloudflare R2 host. The site also loads Google Fonts. Downloads contact those providers without turning file processing into a server upload.

A tool may keep working offline after its code and resources have loaded, but this depends on browser caching and the tool. First use and missing resources need a connection. Offline use is not guaranteed across reloads or after clearing browser data.

Hosted features

Short links and dynamic QR codes store redirect destinations and settings on Cloudflare D1 with KV caching. Link-in-bio pages store and publish the profile and links you provide. These features depend on the hosted service; a static QR code instead contains its data directly. Management uses passphrases stored as bcrypt hashes, without an account signup.

Protected redirects record click details including location fields, device category, referrer and a shortened user-agent string. Bio pages count views and record link-click details. Rate limiting and optional Turnstile verification also use request information. Deactivation disables a hosted record rather than deleting it. Read the privacy policy for the stored fields and the limits of what is known about infrastructure logging and retention.

Cost and availability

Running computation in your browser reduces server processing work, but hosting, bandwidth, model delivery and databases still have costs. The source code does not verify a current monthly bill or guarantee future capacity, pricing or availability. Hosted APIs also apply rate limits.

The MIT-licensed source is available to inspect and self-host. Self-hosting hosted features requires configuring their infrastructure and dependencies. You can also use your browser’s network tools to inspect the requests made by the feature you are using; source code alone cannot reveal every live hosting setting.