If you have ever waited for a progress bar while a “free” site uploaded your tax PDF, wedding photos, or mix stems — then asked you to create an account to download the result — you already know the product model. Your file is the product. The converter is the bait.
Shift is built the other way around. When the browser can do the job, we keep the bytes on your machine. When it cannot, we say so plainly and delete temporary server copies on a schedule.
Modern browsers ship serious capabilities: WebAssembly (FFmpeg builds, image codecs), Web Workers
(so the UI stays responsive), Canvas and OffscreenCanvas, the Web Crypto API, and File System
access patterns that never need a round-trip to a vendor. A client-side tool loads a page, you
pick a file with an <input type="file">, and JavaScript transforms it locally.
The network may download the tool’s code once — but your document does not leave the tab.
That matters for three reasons:
Not every format belongs in a tab. LibreOffice document conversion, OCR that needs large language models or trained tessdata packs, Calibre ebook pipelines, and heavy audio mastering still run better on a machine we control. On Shift, those tools are labeled. Examples:
Using a server tool is a conscious trade: temporary custody of a file in exchange for software that does not fit in a browser bundle. We do not train on those uploads.
We will not hide uploads behind friendly copy. We will not hold your download hostage for an email. We will not pretend a calculator is financial advice. And we will not pretend every utility needs a $12/month plan.
Next: About Shift · Privacy Policy · HEIC without upload