About

Why this exists

Converting a photo or shrinking a PDF is work a browser has been able to do on its own for years. Almost every site that offers it still uploads your file first, because that is the easier way to build a website and because it lets them put your file behind an account.

That trade never made sense for the documents people actually convert. They are passport scans, signed contracts, medical letters, bank statements and photographs of children. So this does the work where the file already is, and sends nothing anywhere.

Who made it

One person. It is not a company, there is no team, and nothing here is venture funded. That is why there is no sign-up flow and no upsell.

How it is paid for

The tools are free and will stay free. The site will carry advertising to cover the cost of the domain, which is currently the only cost, the hosting is free because there is no server doing any work. Ads sit around the tool, never over it, and they cannot see your files, because your files never leave your device for anyone to see.

Something not working?

If a file will not convert, or a tool you need is missing, say so. Email leniv.tech@gmail.com, which reaches one person. Knowing which file broke is worth more than any feature request, and it is the only way the awkward formats get fixed. Please describe the file rather than attaching it: the whole point of this site is that your files stay on your device, and there is more on that on the contact page.

Why not just upload the file?

Because of what people actually convert. The files that arrive at a converter are rarely holiday photographs. They are passport scans for a visa application, a signed contract that needs to be a PDF, a payslip for a landlord, medical letters, bank statements, a photograph of an ID card. Uploading one means handing a copy to a company you have never heard of, under a retention policy you did not read, on infrastructure you cannot inspect, in a jurisdiction you did not choose. Most of the time nothing bad happens. The point is that you have no way of knowing, and no way of getting it back.

Browsers have been able to do this work locally for years. The decoders are already in every browser because the web is made of images, and the awkward ones, HEIC and AVIF, run as WebAssembly that your device downloads once and then executes itself. Nothing here is technically clever. It is the same work, done in the place where the file already is.

What this cannot do

Being straight about the limits is more useful than a longer feature list:

• No OCR. A photograph of text stays a photograph. Reading the words out of an image needs a trained model, and running one honestly in a browser is a different project. Converting an image to Word puts the picture in a document; it does not type it out.
• PDF to Word recovers text, not design. A PDF records where each glyph sits on a page, not what it means, so columns and tables cannot be reliably rebuilt. Tools that claim otherwise are doing heavy processing on a server, with your document.
• Word to PDF typesets the content, not your exact layout. Reproducing that needs the same fonts and the same layout engine Word used, and neither exists here.
• No animation out. An animated GIF converts to a single still frame, because a browser canvas has no way to write animation back.
• Only .docx. The older .doc is an undocumented binary from before Microsoft published a format.

How to tell if any of this is true

Do not take it on trust, because a promise about privacy is worth exactly as much as the promise of whoever made it. Two checks take under a minute. Open your browser's developer tools, switch to the Network tab, and convert something: there is no upload to see. Then turn your internet connection off entirely, and convert something else. It still works, which would be impossible if a server were doing any part of it.

Every tool, and a page for each individual conversion, is listed on the converter.