A file converter that tells you the truth

What “beta” means here

FileTools360 is in public beta. That label is about the site, not the converters: every one of the 521 listed here works and is covered by an automated suite that runs real conversions and checks the bytes that come out, rather than only checking that nothing threw an error.

What beta does mean is that the site is young. The interface will change, some pages are still thin, and if you find a conversion that behaves oddly it is worth reporting rather than assuming it is meant to be that way. Nothing here expires, costs money, or requires an account while it is in beta — and none of that is planned to change for the converters that are already free.

What it is

521 working converters and tools across 11 categories: images, video, audio, PDFs, documents, spreadsheets, presentations, data formats, archives, fonts and e-books. Every one of them runs inside your browser. None of them upload your file.

The principle behind it

Online converters have a credibility problem. They advertise conversions that quietly produce garbage, upload files to servers with vague retention policies, and stamp watermarks on the output unless you pay. The interesting question was whether you could build one that does none of that.

Three rules came out of it, and they shaped everything else:

• Never claim a conversion that does not work. 20 conversions in the directory are listed as unsupported, each with the specific technical reason and a suggested alternative. Legacy .doc needs LibreOffice on a server. DRM-protected e-books cannot be converted at all. Saying so is more useful than a spinner that ends in an error.
• Describe what a conversion actually does. JPG to SVG does not vectorise your photograph — it wraps it in an SVG, and the page says exactly that. MP3 to FLAC gives you a bigger file, not better sound, and the page says that too.
• Do not make privacy a promise when it can be a property. Running conversions locally means there is no upload to trust us about. You can verify it by disconnecting from the internet mid-conversion.

How it is built

Next.js and TypeScript on the front, with a conversion registry at the centre. Every converter, page, sitemap entry, structured-data block and internal link is generated from that registry, so adding a conversion is a data change rather than a new page.

The engines are real: FFmpeg compiled to WebAssembly for media, pdf.js and pdf-lib for PDFs, SheetJS for workbooks, Tesseract for OCR, libheif and libavif for modern image formats. Documents flow through a shared intermediate model, which is how eight readers and seven writers become fifty-plus conversions without a bespoke code path for each.

There is a fuller technical account here.

What it is not

FileTools360 is a working tool, but it is not a company. There is no legal entity, no uptime commitment and no paid plan you can buy — the pricing page says so plainly rather than showing a checkout that goes nowhere.