Skip to content

How it works

The short answer: your browser does almost all the work. Here's the long one.

The PDF almost never leaves your device

When you drag a file into one of these tools (all except PDF to Word, explained below), the browser loads it into its own memory, the same way it would a video tab. That file is never sent anywhere: there's no network request uploading it, no server waiting to receive it. The processing — merging, rotating, compressing, whatever it is — happens right there, with the same engine the browser already uses to draw the page.

You can check this yourself: open your browser's developer tools, watch the network tab while using any PDF tool on this site, and you won't see the file go out (except in PDF to Word). That's the difference between "we promise we don't upload it" and "it technically cannot be uploaded".

What WASM actually is

Several of these tools — OCR especially — need to do heavy computation: recognising letters inside an image, for instance. That kind of work was originally written in languages built for speed, not JavaScript. WebAssembly (WASM) is the piece that lets that compiled code run inside the browser, close to the speed of an installed application, without leaving the tab or asking for special permissions.

It isn't magic or a back door: WASM runs inside the same sandbox that already protects any web page, with no free access to your hard drive. It's simply how the browser processes large files without grinding to a halt.

What leaves your device (and what does not)

By default: nothing. Not the file, not its content, not a summary of what it does. All tools but one work entirely locally.

There are two exceptions. The first is PDF to Word: that tool sends the PDF (up to 10 MB) to our server to convert it, says so on its own page, and does not keep the file once the .docx is delivered. The second is the features that use artificial intelligence — summarising a PDF or chatting with its content — which are optional and clearly marked. If you use them, the text extracted from the document does travel to the larebelion AI hub so it can generate a reply. Nothing else on the site depends on that at all, and the privacy page explains it in detail.

Besides that, this site keeps anonymous usage counters (how many times each tool was used, with nobody identified) and, if you fill in the contact form, the message you write there.

The 100 MB limit

Every file you load into a tool has a 100 MB limit (PDF to Word, which converts on the server, accepts up to 10 MB). It isn't an arbitrary business rule: it's what keeps the browser from running out of memory halfway through a heavy PDF, especially in tools that load several pages as high-resolution images at once. Past that size, we'd rather warn you than let the tab freeze.

Which browser you need

Any modern browser: Chrome, Firefox, Edge or Safari on their latest versions, desktop or mobile. All it needs is WebAssembly and Blob API support, both of which have been standard for years. A computer handles large documents more comfortably than a phone, simply because there's more memory available to work with.

Necessary cookies. We use strictly necessary cookies for the quota and sign-in; we do not use analytics cookies. Your PDFs are processed in your browser, except in PDF to Word. Learn more