Tools

One tool, one job

Most file tasks are small. Turn this into that, make this smaller, pull these together. They do not need a dashboard, a project, an account or a subscription, and they certainly do not need you to hand a private file to a server before you can get on with your day. Every tool in this library is built for exactly one of those small jobs and nothing else. Open it, do the thing, close the tab. There is no second screen trying to sell you the rest of a suite.

The list above grows as tools are added. Rather than sort them into folders you have to guess your way through, everything sits on one page: filter by category, or type the job you have — a format, an action, a file type — and the list narrows as you go. Pressing the search shortcut opens the same thing from anywhere on the site.

Everything runs in your browser

This is the one promise the whole library is built on, so it is worth being precise about it. The code that does the work arrives with the page and runs on your own device, using your own processor and memory. Your file is opened by the tab in front of you and is never sent anywhere. There is no upload, which means there is no copy of your file sitting on a disk you cannot see, no retention window anyone has to promise to honour, and no breach that could one day expose a folder of your documents. It also means the tools are as fast as your machine, not as fast as a shared server on a busy afternoon.

You do not have to believe any of that, which is the point of doing it this way. Open a tool, wait for it to finish loading, then switch on airplane mode or pull your network cable. Do the job anyway. It still works, because nothing was ever going to be sent. That check takes about ten seconds and it is the only guarantee on this site you can verify with your own eyes rather than take on trust.

A small number of jobs genuinely cannot run on your device, and where that is ever the case the tool says so plainly, above the controls, before you start — never buried in a policy. If a tool does not carry that warning, it ran locally and your file stayed with you.

No account, no watermark, no catch

Nothing here asks you to sign up. There is no free tier that quietly stops working at the third file, no watermark stamped across the result, no size cap that exists only so a paid plan can lift it. Because the work happens on your device, there is no server cost to recover and therefore nothing to gate. You can use any tool as many times as you like, on as many files as your device can hold in memory at once.

That last part is the only real limit worth knowing. The ceiling is your hardware, not a rule imposed here: a phone will handle a modest batch comfortably, a laptop will work through a large one without complaint. If something very large stalls or the tab reloads itself, split the batch in half and run it twice.

Built to be readable, not clever

Every tool aims to do the obvious thing by default and explain the few choices it offers in plain language. Where a setting changes the result — a quality level, a page size, an output format — it is shown up front with a sensible default already chosen, so the tool is useful the moment it loads and adjustable only if you want to adjust it. Nothing important is hidden behind a menu, and nothing asks you to read documentation before you can convert a single file.

The library keeps growing

New tools are added over time, grouped into broad categories so the page stays navigable as the list gets longer. If the tool you need is not here yet, there is a request form at the bottom of this page. Say what you are starting with, what you need to end up with, and what usually goes wrong when you try it elsewhere. Requests are read every week, and the job that gets asked for most is the one that gets built next. A good description of a real problem is worth more than a vote — it is often the thing that shows exactly what the tool has to handle.