Guide

How a file is processed without uploading it

Damaged files are often private ones. Here the program comes to the file, so the file never travels.

A laptop on a desk with its network cable unplugged
Generated illustration

How it works

The engine is compiled to WebAssembly, which browsers run directly. The page downloads it as it opens, and the work then happens on your processor, in background workers so the page keeps responding.

How to check it

Open the browser's developer tools on the Network tab, then process a file. Requests fetch the program's own files, and the damaged file is not among them. You can also disconnect a few seconds after the page loads, once the engine has downloaded, and process a file.

The trade-off

Everything is held in the browser's memory: the file and the result at once. On a phone, or with very large files, that memory can run out. The page says so when it happens.

Why this matters for recovery

A file you cannot replace is often one you would not hand to a stranger. Recovering it here involves no server, no account and no copy of it anywhere else.

If the file is too large for the device

Close other tabs and try again, or move to a computer with more memory. A desktop browser usually has more room than a phone. The damaged file stays where it was, so a failed attempt costs only time.

What the page still needs

An internet connection is needed to load the page and its engine. After that the rebuild runs on your processor, so its speed depends on your device and the size of the file, and closing the tab stops the work.

Common questions

Does the engine run on every core?

Where the browser allows it, yes. The page reports how many cores are in use.

Is anything stored in my browser?

The result is held in memory until you save it or close the page.

Does it work offline?

Yes, once the page and its engine have loaded, a few seconds after it opens. Reloading the page or stopping a run downloads the engine again.

Sources

Documents consulted for this guide.

  1. WebAssembly
  2. MDN: SharedArrayBuffer