What private process means here
A colleague sends a .cbz at 11pm. The laptop has a locked-down company image, no comic app, and no permission to install one. You open it in a browser tab instead.
That is the whole idea: the file comes in, the work happens inside the tab, and the result goes back to you. There is nowhere in that loop to send a copy.
Why the other tools need a server
An upload site works the other way round. Your archive leaves the tab, goes to a machine with the software and the memory for the job, and a link comes back. The page in front of you only passes the file along.
A copy sits on hardware someone else controls and stays there until they decide to delete it — often longer, in a cache or a log. Because server capacity costs money, large files usually require an account or a paid tier. And the service still has to exist tomorrow for the tool to work at all. None of that is bad faith; it is what putting a server in the middle produces.
The promises, and what holds them up
You are on hotel Wi-Fi with a work laptop and a strict no-upload policy. The home page makes four promises, and each one rests on something specific.
How the conversion runs, step by step →
| The promise | What holds it up |
|---|---|
| Your file stays on your device | The browser hands the file to the page, and the page has no upload destination to hand it to |
| read | Opened where it already sits, not copied to a service first |
| convert | Decoded and assembled on your machine, not on ours |
| without handing it over | Saved by your browser: no link to collect and no copy for anyone to hold |
The path a file takes
- Unpack
- Decode
- Lay out
- Deliver
A 400 MB archive opens on a phone with no app installed.
Unpack, decode and lay out all happen in the tab, and Deliver has two exits: pixels to the screen, PDF bytes to a download. Neither exit ends at a server.
Where the tab ends (Privacy details)
This site still has a host and a bill, so three minor things happen outside the tab. None of them contains your file.
- Cloudflare (CDN): Sees basic request data like IP address and browser type (but never your files).
- Umami (Analytics): Gets one event per visit or conversion, but no file data.
- Browser Storage: Saves your language choice and reading progress locally. Clearing site data removes both.
Check it in a minute
Pick a real file and watch the browser while it works.
- Open DevTools → Network, filter by this domain, then start the work. The page and its scripts load, one analytics request appears, and nothing carries the archive or the page images.
- On a phone, open this page once while online, turn on airplane mode, reload, then convert a local CBZ. The PDF is still built and saved.
- Search the request list for an endpoint that accepts a file. There is nothing to find.