toolsconvertor

About toolsconvertor

Powerful tools. Simple experiences. Accessible to everyone — including people on a cheap phone, a slow connection, or a budget of nothing.

The problem we are solving

Splitting a PDF is not a hard technical problem. Neither is resizing a photo, or converting a spreadsheet. These are five-second jobs. Yet doing them usually means one of three bad options: buy software you will use twice a year, install something you do not trust, or upload a private document to a website plastered with adverts and hope for the best.

The gap is worst for the people with the fewest options. A student on a shared laptop, a small business owner on a phone, a teacher in a school with no software budget, a non-technical person who just needs the thing to work. They end up on the sites with the most aggressive advertising and the least clarity about what happens to their files.

What we decided to do differently

Run the work on your device

82 tools here never send your file anywhere. Browsers have become genuinely capable — WebAssembly, canvas, Web Crypto — so a PDF merge or an image resize can happen on your own machine as fast as on a server. We took that seriously as an architecture rather than a footnote.

This has three consequences, and only two of them are good for us:

  • Your privacy stops depending on our promises. We cannot misuse a file we never receive.
  • It is fast, because there is no upload and no queue.
  • We cannot see what people do, which means we know far less about how tools are used than a competitor does. We accepted that trade.

Refuse to fake it

It is trivially easy to publish two hundred tool pages with confident buttons and let people find out one broken attempt at a time which ones are real. Plenty of sites do exactly that, and it works commercially, because a visitor who bounces has still been counted.

Every tool here declares in code whether it has a working engine behind it, and an automated test fails the build if a tool claims to be live without one. When a card says Live, that is a machine-checked fact, not a marketing decision. When a tool is not available, its page says what it is waiting on and points you at the working tools that come closest.

Say the unhelpful thing

Compress a scanned PDF here and it may tell you it could not make the file smaller, and that your original is the better file. A site optimised for conversion would show a success tick and a download button regardless. We would rather be useful than look successful.

Tools we will not build

Two categories of frequently requested tool are deliberately absent, and will stay absent.

Watermark removal. A watermark exists because someone marked their work. Removing it is almost always about using that work without permission. We build watermark addition instead, so you can mark your own.

Downloaders for third-party platforms. These breach the terms of the services they target and mostly exist to take creators' work. If you want to process media, upload your own.

Both of these get real search traffic. Declining them costs us visitors. That is the point of having a line.

Responsible AI

Where AI genuinely improves an outcome, we use it. Where it is decoration, we do not.

  • An AI tool names the provider that will receive your text before you enter anything.
  • Nothing you submit is used to train a model, and prompts are not stored after the response.
  • We say plainly that model output can be confidently wrong, especially on the tools where that would matter.
  • We do not let a tool imply a person reviewed its output when none did.
  • We do not add an AI feature to a tool that works better without one. Resizing an image needs arithmetic, not a model.

How this gets paid for

Worth stating plainly, because "free" usually has a catch and you are right to look for it.

Running tools on your device costs us almost nothing — no processing servers, no storage, no bandwidth for file uploads. That is what makes a genuinely free tier sustainable rather than a loss leader waiting to be withdrawn.

The intended model is paid tiers for the expensive things: AI usage, which costs real money per request, and server-side processing of large media files. The free tools stay free and stay complete. We will not degrade a working free tool to make a paid one look better, and we will not introduce a daily cap on something that costs us nothing to run.

There is no advertising, and there will not be. Advertising on a tools site means tracking, and tracking contradicts everything above.

Accessibility

The platform targets WCAG 2.2 AA. Every control is a real form element, focus is always visible, contrast is checked in both light and dark themes, pinch-zoom is never blocked, and the reduced-motion setting is respected. Accessibility is built into the design system, so a new tool inherits it rather than needing it retrofitted.

We have not had an external accessibility audit, so we say "targets" rather than "complies". If you hit a barrier, tell us at naseershafqat@gmail.com and it goes to the front of the queue.

Built for everywhere

The architecture assumes it will be used in many languages, including right-to-left ones, and on devices far weaker than a developer's laptop. Dates, numbers and currencies are formatted by locale rather than hardcoded to one convention. Pages are static HTML served from a CDN, so they load on a slow connection. The tools that matter most work offline once the page has loaded.

Where the platform actually stands

82 tools work today with no configuration. 45 are built and waiting on an API key. 24 need a processing engine that is not bundled. 16 are specified and not yet built. The numbers on this page come straight from the registry, so they cannot drift out of date.