Frequently asked questions
Short answers to the things people ask most often. If your question is not here, the contact page is one click away.
Are my files and text uploaded to a server?
No. Every tool processes your content inside your own browser using standard web APIs. You can confirm it by opening the network panel in your browser and watching the page make no requests while you work.
Is it really free?
Yes. There is no trial period and no watermark is added to any result.
Which browsers are supported?
Any current version of Chrome, Edge, Firefox, Safari or their mobile equivalents. The tools use standard web APIs, so no polyfills or extra software are needed.
Do the tools work offline?
Mostly, yes. Once a page has loaded, the processing runs locally, so the tools keep working without a connection. Downloaded files and fonts are the only things that need the network.
Is there a limit on how much text or how many images I can use?
There is no artificial limit. The practical ceiling is your device's memory, which matters more for images than for text.
Can I use the results commercially?
Yes. Whatever you produce with these tools is entirely yours, with no attribution required and no watermark added.
Why does the same tool give a different result in another browser?
A handful of tools rely on the browser's own image encoder. Different browsers can pick slightly different compression levels for the same quality setting, so the final file size may vary by a few percent.
How do I report a bug?
Use the contact form and include the tool name, the browser you are on and what you expected to happen. A screenshot makes it much faster to fix.
Can I suggest a tool?
Please do. Tool requests are the main reason the collection keeps growing, and the contact page is the fastest way to send one.
Still stuck? Have a look at the articles and guides — they cover the common workflows in more detail, including how reading time and Base64 actually work.