Frequently asked questions

Yes. Published file tools do their work inside your browser, so the file you choose is read by the page you already have open rather than sent anywhere. You do not have to take that on trust: open your browser developer tools, watch the network panel while a tool runs, and you will see that the file bytes never appear in a request.

• Security
• Privacy policy

No. There is no upload step for the published file tools, which is why there is no progress bar waiting on a server and why they keep working on a slow connection once the page has loaded.

There is nothing to delete. A file that was never sent to us cannot be stored by us, so no retention window applies and no cleanup job runs. When you close the tab, the copy your browser was working on goes with it.

No. We never receive file contents, file names, extracted text, or generated output. If you allow optional analytics, measurement records which tool ran and whether it succeeded, with sizes bucketed into ranges such as 1-5 MB rather than exact numbers.

No. We do not receive your files, so there is nothing of yours to train on, and no ToolsVerse tool sends your content to an external AI service.

Yes, and it is worth being clear about it. Processing locally moves the boundary to your own machine: a compromised browser extension or an infected device can read what you open here exactly as it can on any other site. Local processing removes us from the equation, not everyone.

• Security

Only what the site needs until you decide otherwise. Your theme choice and your consent decision are stored in your browser; analytics cookies are set only after you choose Allow analytics, and Cookie settings in the footer reverses that at any time. The cookie policy names every cookie and stored value, with what each is for and how long it lasts.

• Cookie policy
• Privacy policy

No. Every published tool runs without signing up, signing in, or giving us an email address. There is no account to create and therefore no profile to delete later.

Yes. The published tools are free to use, with no trial period, no export fee and no watermark held back for a paid tier. You may use the results in commercial work.

There are 124 published tools across 10 categories, and the catalogue grows as engines are reviewed and released. Anything listed on the site is a tool you can actually open.

• All tools
• Calculators
• Developer tools
• File tools
• Video tools

Current versions of the major standards-based browsers. Chromium browsers such as Chrome and Edge, and Firefox, are the ones we test each release against; other modern browsers generally work, and a tool that needs a capability your browser lacks says so before you start rather than failing halfway.

• Check your browser

Yes. The site is built mobile-first because most people arrive on a phone. The practical limit is memory rather than screen size: a very large file may succeed on a laptop and run out of room on a phone.

It varies by tool, and each tool states its accepted formats and limits before you choose a file rather than after. Because the work happens on your device, the ceiling on size is your device memory, not a server quota.

Almost always memory. A browser tab has a bounded amount of it, and a large image, PDF or video can exceed that during processing. Closing other tabs, using a desktop browser, or splitting the work into smaller pieces usually gets it through.

• Compress PDF
• Split PDF
• Compress an image

Never. Your file comes out carrying exactly what you put in. The only tool that adds a watermark is the one whose entire job is to add a watermark, and only where you place it.

• Add a watermark

No. There is no extension, no desktop application and no sign-up. The tool is the web page, and some tools fetch their processing engine the first time you use them, which is why the first run of one can take a moment longer than the second.

Largely by what people ask for. Requests are reviewed, published to the community board, and the ones that collect the most votes are the ones built first. A well-described request carries more weight than a one-word one, because it tells us what the tool actually has to do.

Use the request page. Describe the result you need and the kind of file you would start from — that is the difference between a request we can build and one we have to guess at. Requests are usually reviewed within 24 hours.

• Request a tool

A person reads it. If it is something we can build in the browser and it is not already covered, it is published on the community board for others to vote on; if it is not, you get an answer explaining why rather than silence.

No. Voting asks for your email address once, purely so one person cannot vote fifty times, and remembers it afterwards so every later vote is a single click. It is not added to a mailing list.

• Community request board

Because it is not finished. A tool appears on the site when its browser engine has been reviewed and it genuinely works; until then it stays unlisted rather than appearing as a page that cannot do the job. Requesting it is the fastest way to move it up the queue.

No advertising or tag-manager script is loaded at the moment. If that changes we will name the provider, update the privacy and cookie policies, and ask for any consent required before a single ad script loads.

• Privacy policy
• Cookie policy

Yes. There is no separate licence for business use and no restriction on the results. You keep every right you already had in the files you process.

• Terms & Conditions

Through the contact page, which reaches the people who build the tools rather than a ticket queue. For a suspected security issue, say so in the subject and we will treat it as the priority it is.

• Contact us
• Security

The same contact page. Privacy requests — access, correction, deletion, objection — are answered within the period the applicable law requires, and the privacy policy sets out which rights apply.

• Contact us
• Privacy policy