About CloudlessConvert
A small, focused tool built to solve one specific annoyance: converting a photo shouldn't require handing it to a stranger's server.
Why this exists
Every "free online converter" works the same way: you upload your file to someone else's computer, they convert it, and you download the result. For a document that might be fine. For a personal photo — a photo of your kids, your home, your ID card, your medical scan — it means a copy of that photo now sits on a server you know nothing about, run by a company whose privacy policy you didn't read, for however long they decide to keep it.
That trade-off is unnecessary. Every browser built since roughly 2020 can decode and re-encode images entirely on its own — the same code that lets a browser display a JPEG can also produce one. CloudlessConvert exists to use that capability directly, instead of routing your photo through a server that doesn't need to see it.
How it actually works
When you drop a file onto this site, nothing is uploaded. The browser decodes the image using its own built-in decoder, draws it onto an in-memory canvas, and asks the browser to re-encode that canvas in the format you chose. Every step happens using standard Web APIs (createImageBitmap, OffscreenCanvas, a Web Worker so the page doesn't freeze) running on your device. There is no upload endpoint in the code, because there is no server component to upload to — the deployed site is a folder of static files.
You can verify this yourself in about a minute: open your browser's developer tools, switch to the Network tab, and convert a photo. Watch what actually gets sent, and confirm none of it contains your selected image — no upload, and nothing carrying the file's bytes, its filename, or its metadata. After a conversion finishes, you will see one small first-party request, to /conversion-count — it records only which format you converted from and to (for example, heic to jpeg), for anonymous aggregate statistics, and nothing else about the file. You will also see Google Analytics requests, which record page views and the same format pair, never the file itself; the Privacy Policy lists exactly what they contain.
If your browser can't decode HEIC natively (most non-Apple browsers), or the first time you use "Download All," CloudlessConvert loads a small decoder or zip-building library once, from this same domain. That's code coming to your browser, not your photo going anywhere — and once it's loaded, converting doesn't depend on talking to a server at all, including if you go offline. Try it: load the page, use each feature once so those pieces load, then disconnect and convert again.
The full technical writeup, including exactly how metadata preservation and colour handling work, is on the homepage.
What makes it different
Being client-side isn't unique anymore — several other converters now make the same claim, and we're glad more of the field is moving this direction. Where we've put the actual engineering effort is metadata: most converters, including client-side ones, quietly strip the capture date, camera model and GPS location out of your photos during conversion, because the standard canvas-based approach discards all of that by construction. CloudlessConvert reads that data out of the original file and writes it back into the converted one — verified by hand against real HEIC files, not just assumed to work.
Who built it
CloudlessConvert is a MatrixInn Solutions project — a small software house. It was built because we wanted a tool like this to exist and couldn't find one that handled photo metadata honestly, not because it was commissioned by anyone.
Questions, bug reports or feedback: see the contact page.