Frequently asked questions
Everything about file handling, privacy, formats, limits and browser support — grouped so you can find the answer without reading all of it.
Getting started
How do I convert a file?
Open the tool that matches your file, drop the file onto the page or browse for it, confirm the output format and start the conversion. When it finishes, the download button appears on the same screen.
Do I need to install anything?
No. The tools run in a modern browser. Nothing is installed, and there is no browser extension to add.
Do I need to create an account?
No. There is no sign-up step, no login and no dashboard. There is nothing to remember.
Privacy and files
Are my files uploaded to your servers?
For supported tools, no. The file is read and processed by your own browser. Tools that cannot run locally are labelled clearly before you select a file.
Do you keep a copy of my files?
There is no upload step for local tools, so there is nothing for us to keep. File data lives in your browser's memory and is released when you reset the tool or close the page.
Is there a file size limit?
The limit is your device's memory rather than a server rule. Image and data tools handle large files comfortably; video and CAD files are the most demanding.
Formats and quality
Will converting reduce quality?
It depends on the formats. Moving to a lossless format such as PNG or FLAC preserves what the source contains. Moving to a lossy format such as JPG or MP3 discards some detail, and the tool lets you control how much.
Can I convert in the opposite direction?
Usually, yes. Each tool links to related conversions, including the reverse direction when it exists.
A format I need is missing. What now?
Request it through the contact page. Formats that browsers can handle locally are the easiest to add, so those requests move fastest.
Troubleshooting
The conversion failed. What should I check?
Confirm the file really is the format its extension claims, that it is not corrupt, and that your device has enough free memory. Reloading the page and trying once more also resolves most transient failures.
The page is slow with a large video file.
Video encoding is CPU heavy by nature. Closing other tabs frees memory and CPU time, and starting from a shorter clip usually finishes faster.
Which browsers are supported?
Current versions of Chrome, Edge, Firefox and Safari. Conversions that rely on WebAssembly need a reasonably recent browser, and the tool page tells you before you start if yours is a limitation.
Still stuck?
Send us the details and we will look into it. Include your browser and the tool you used — never the file itself.