Under the hood

A private process, not a service

Everything below happens inside this tab — there is no server side to send anything to.

  • No upload
  • No account
  • Right-to-left ready
  • Remembers your page

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 promiseWhat holds it up
Your file stays on your deviceThe browser hands the file to the page, and the page has no upload destination to hand it to
readOpened where it already sits, not copied to a service first
convertDecoded and assembled on your machine, not on ours
without handing it overSaved by your browser: no link to collect and no copy for anyone to hold

The path a file takes

  1. Unpack
  2. Decode
  3. Lay out
  4. 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.

Questions

How does local processing actually work?

The browser reads the ZIP central directory in the tab, pulls one page at a time, and pdf-lib writes the PDF bytes locally. The finished file is handed to you as a Blob download made in the tab, so no request carries the archive and there is no copy on a server to expire or to delete.

Is this the same as the privacy page?

The privacy page lists what is collected and why. This page covers what the code does with the file.

What is sitting in my browser storage?

A language preference and reading progress, plus the service worker copy of this page. Clearing site data removes all of it.

Why did a conversion finish on a plane?

A service worker kept the page and its scripts after the first visit. The archive was already on your disk.

What happens if I switch browsers?

Nothing carries over. Reading progress stays in the browser that wrote it.

Read a CBZ right now

Drop a file into the reader. It stays on your device.

Open the CBZ reader