Your files never leave your device
Every one of Morphixel's 48 tools runs inside your browser. There is no upload step, no server doing the work, and no copy of your file anywhere but your own machine. Here is exactly how that works — and how to check it for yourself.
Verify it yourself in ten seconds
You should not have to take this on trust. Unlike a privacy policy, this claim is falsifiable in your own browser, right now:
- Open your browser's developer tools (F12, or ⌘⌥I on a Mac) and select the Network tab.
- Go to any tool — HEIC to JPG, say — and convert a file.
- Watch the requests. The first conversion downloads the engine from morphixel.com. After that, nothing. No request carries your file anywhere.
There is a stronger version of this test. Load the page, then turn off your Wi-Fi completely, then convert a file. It still works, because there was never anything on the other end of a connection to begin with.
To be precise about what you will see: the engine binaries do download, from our own domain, the first time you use a tool. They are cached afterwards. Those are programs arriving at your browser — not your file leaving it.
What actually runs where
A conventional online converter is a thin front end over a server. You upload, a machine somewhere does the work, and you download the result. That machine has your file, and what happens to it afterwards is a matter of policy rather than architecture.
Morphixel inverts that. The conversion engines are compiled to WebAssembly and shipped to your browser as static files, the same way an image or a stylesheet is. Your file is read from disk into memory by your own browser, processed there, and written back out as a download. At no point does it become an HTTP request body.
The practical consequence is that there is no server-side privacy policy to trust, because there is no server-side anything. We could not look at your files if we wanted to — they never arrive.
The engines
These are real, mature, open-source libraries — the same code that runs in desktop software and on servers, compiled to WebAssembly so it can run in a browser tab instead.
| Library | Version | What it does |
|---|---|---|
wasm-vips | 0.0.18 (libvips 8.18.3) | Image decoding, conversion, resizing, cropping, rotation and metadata stripping. |
heic-to | 1.5.2 (libheif 1.23) | Decodes HEIC photos from iPhones. wasm-vips ships no HEVC decoder, so this fills the gap. |
pdf-lib | 1.17 | PDF structure: merging, splitting, rotating, page numbers, watermarks and reordering. |
pdfjs-dist | 6.1 | Renders PDF pages to images and extracts their text layer. |
tesseract.js | 7.0 | Optical character recognition for scanned documents. |
docx | 9.7 | Writes the Word documents produced by the PDF to Word tool. |
fflate | 0.8 | Packs multiple results into a ZIP for download-all. |
All of it is served from our own domain rather than a CDN. That is deliberate: a third-party CDN request would reveal which tool you are using and when, even though the file itself stays put.
Why this needs cross-origin isolation
The image engine uses multiple threads, which in WebAssembly means shared memory — specifically SharedArrayBuffer. Browsers disabled that API for everyone after Spectre, and only restore it for pages that prove they are properly sandboxed.
Earning it back means serving every page with two headers, Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp, which together cut the page off from most cross-origin resources. It is a real constraint: no third-party embeds, no CDN scripts, nothing loaded from anywhere else without explicit permission.
That constraint happens to point the same direction as the privacy goal. A page locked down tightly enough to run a threaded image codec is also a page that cannot quietly phone home.
Why the page never freezes
Converting a large photo is genuinely heavy computation. Run it on the main thread and the tab locks up — no scrolling, no clicking, the spinner itself stops animating.
So none of it runs there. Every conversion happens in a Web Worker, a separate thread with its own memory. The interface stays responsive while the work proceeds, and progress is reported back as it goes. On a big batch you can keep using the page.
It works with no internet at all
Morphixel is a progressive web app. A service worker caches the interface and the engines after your first visit, so you can install it from your browser's menu and launch it like any other application.
Once installed it works in airplane mode. That is not a party trick — it is the clearest possible demonstration of the architecture. Software that needs a server cannot run without one.
What we collect
Nothing. There is no analytics script on this site, no cookies, no accounts, no tracking pixels and no third-party embeds — the isolation headers above would block most of them anyway.
We do not know what you converted, how many files you processed, or that you were here at all beyond what any web server records when it sends you a page.
The honest limits
Running everything locally has a real cost, and it would be dishonest to pretend otherwise.
Your browser caps how much memory one tab may use.A very large PDF or a 48-megapixel RAW file can exhaust it. We warn you when a file looks large enough to be a problem, but the ceiling is the browser's, not ours, and we cannot lift it from inside the tab.
The first run of a tool is slower. The engine has to download — around 11 MB for images, roughly 30 MB for OCR including its English language data. It is cached afterwards, so this is a one-time cost, but it is a real one.
Some things genuinely need a server. Faithful PDF to Word conversion of complex layouts needs a full office engine; our version reconstructs text and structure well but simplifies multi-column layouts, tables and positioned images. OCR currently recognises English only.
Try it
All 48 tools are free, have no signup, add no watermark, and impose no file limits beyond what your browser can hold. Start with the image tools or the PDF tools — or go straight to OCR, which is the one most people are surprised can work this way.