No file upload — what it means (and what it doesn’t)

Many file tools say “no upload” or “local processing”. That’s a strong privacy promise — but it helps to know exactly what it covers.

What “no file upload” usually means

• Your file stays on your device. The browser reads it via the File API; nothing is sent to a server.
• No account, no storage. There’s nowhere for us to keep your file, because we never receive it.
• Works offline (once loaded). For purely client-side tools, the page logic runs in the browser; no round-trip needed.

What it doesn’t mean

• Some tasks (e.g. heavy compression, OCR, PDF→Word) may use a Pro or server-backed option. In that case, the file is uploaded for processing — and you should see a clear notice before you start.
• “No upload” applies to the tool you’re using. If you switch to a cloud-backed feature, the rules change; we say so.

Bottom line: if a page says “no upload” and “processed locally”, that’s the default. If a feature uses the cloud, we say it — and explain retention and deletion. No surprises.