Frequently asked questions

No. Every converter on this site runs entirely in your browser using WebAssembly and standard browser APIs. Once the page has loaded you can disconnect from the internet and conversions still work — which is the simplest proof that nothing is being sent anywhere.

No. Every converter and tool works without signing in, with no watermark and no artificial limits on the output. An account does one thing: it keeps your starred tools with you across devices, and it holds a per-tool count for seven days so your own recent list is useful. Nothing is gated behind it, and nothing about the files you convert is stored in it.

Limits are set per conversion — 120 MB for images, 512 MB for video, 200 MB for PDFs. Because the work happens on your own device, the real limit is your available memory: a laptop handles far more than a phone. FileTools360 tells you before it starts rather than failing halfway through.

It depends on the formats. Converting to a lossless format like PNG or FLAC preserves everything that is there. Converting to a lossy format like JPG or MP3 discards some data — the quality slider controls how much. Each converter states plainly which case it is, and warns you when a conversion cannot improve quality, such as MP3 to FLAC.

Yes. Add as many as you like and press Convert All. Each file is handled independently, so a corrupted file fails on its own and you can retry it without redoing the batch. When you are done, everything downloads together as a ZIP.

Yes. The interface is built mobile-first, with a bottom-sheet format picker, large touch targets and a sticky convert button. You can pick files straight from your camera roll. Very large video conversions may exhaust a phone's memory — FileTools360 will say so rather than silently failing.

Because pretending would be worse. Legacy binary formats like .doc and .ppt need a server-side LibreOffice worker, which FileTools360 does not run, and DRM-protected e-books cannot be converted at all. Those conversions are listed with the specific reason and a suggested alternative rather than being quietly hidden or, worse, failing after you upload.

Because PNG is lossless and JPG is not. PNG stores every pixel exactly, which usually takes more space than JPG's compressed approximation. Converting to PNG cannot recover detail the JPG already discarded — it only stops any further loss. If your goal is a smaller file, WebP or AVIF is the better target.

Yes, with OCR PDF. A scanned page is an image with no text layer, so ordinary text extraction returns nothing — FileTools360 detects this and tells you rather than handing back an empty file. OCR PDF runs character recognition on the page images, entirely on your device. Accuracy depends on the scan: clean, straight, high-contrast pages at 300 DPI work well.

Only that file fails. The rest of the queue carries on, the failed file shows what went wrong and what to try, and a Retry button re-runs just that one. You never have to restart a batch because of a single bad file.

No. There is no watermark, no metadata tag advertising FileTools360 in your images, and no trailing page in your PDFs. PDFs do record FileTools360 as the producing application, which is a standard field in the format — the Remove PDF Metadata tool clears it if you would rather it were not there.

Once a converter page has loaded, yes — for most conversions. The engine is already in your browser at that point. Two exceptions need a network request the first time you use them: OCR downloads its language model, and PDF export of non-Latin text downloads a Unicode font. Both are cached afterwards.

Current Chrome, Edge, Firefox and Safari. FileTools360 needs WebAssembly and modern canvas APIs, which rules out Internet Explorer and very old mobile browsers. If something is unavailable in your browser, the converter says so instead of failing partway through.