Who Builds ToolMela
ToolMela is built and run by a small independent team in India. It is not a directory that lists other people's utilities, and it does not wrap third-party widgets and present them as its own: all 367 tools on this site are code we wrote, hosted on this domain, and maintained by us.
This page names no individuals. That is a deliberate choice about our own privacy rather than an oversight, and we would rather say so plainly than fill the space with invented job titles and stock headshots. What we can offer instead is the kind of accountability you can check for yourself: an email address that reaches the people who write the code, a written policy for how pages are researched and corrected, and — on every single tool page — a plain statement of where your file is processed before you upload anything. Those are claims you can test by using the site. A row of faces would not be.
What the team maintains
367 tools, grouped into 21 categories. Most of the work is not adding new ones — it is keeping the existing ones working. Browsers change their handling of canvas and file APIs, the image and PDF libraries underneath get updated, and the size, dimension and format rules that Indian exam boards and government portals ask for change more often than either.
- Image editing and photo sizing
- PDF editing, merging and conversion
- Government and exam document formats
- Bangla and Hindi typing
- Signature cropping and resizing
- QR codes and barcodes
- File format conversion
- Social media image sizes
- Text and writing utilities
- SEO helpers
- Everyday calculators
- Finance and loan maths
- Business documents and invoices
How a tool gets built
- 1
A requirement we can point at
Tools get built for a task someone actually has to complete — a 20 KB passport photo for a form that rejects anything larger, a PDF split before a portal upload, an EMI figure checked against a lender's quote. Not for a keyword.
- 2
The smallest version that works
One screen, no sign-up, no queue. If a tool needs a tutorial before the first click, the tool is wrong rather than the user.
- 3
A decision about where the file goes
The browser is the default. Uploading is chosen only when doing the job properly needs a library that browsers do not have, or produces a visibly better result than canvas code can. Whichever way it goes, the tool page states it.
- 4
Copy written from the code, then checked
The description, steps, limits and FAQ are written after reading the implementation, and two automated checks run before anything ships.
Where your file actually goes
Every tool falls into one of five cases, and a badge near the top of the page tells you which one applies before you choose a file. As the site stands today the split is:
run entirely in your browser
Nothing is transmitted. The work is done by JavaScript and WebAssembly inside the page, so these tools keep working if your connection drops after the page has loaded.
upload the file to our own server
The file goes over HTTPS to a ToolMela API endpoint, is held in memory while an image or document library transforms it, and the result is streamed back. It is not written to disk or kept after the request finishes.
exist only because of a hosted AI model
The text or image you submit is sent to a model provider, because that is the entire feature. These pages say so rather than implying the work happens locally.
are local, with one optional AI button
Every transform runs in the page. One clearly-labelled extra feature calls a hosted model. Ignore that button and nothing leaves your device.
are local by default, with an alternative model on our server
Cropping, resizing and the default background-removal model all run in the tab. Only the alternative model choice sends the photo to us.
That means 252 of the 367 tools transmit nothing at all unless you deliberately press a labelled optional feature. We publish the breakdown instead of a blanket reassurance that your files are safe with us, because a blanket claim would be untrue for the 96 that do upload — and you deserve to know which kind you are using while the file is still on your machine.
How the words on a tool page are kept honest
The description, instructions, limits and questions on a tool page are written after reading that tool's implementation — not after reading its name. If a loan field accepts up to seven years, the page does not say five. If a calculator rounds to the nearest rupee, the page says where that rounding turns up in the total. Figures in a worked example are produced by running the tool's own formula, not estimated to look plausible.
Two automated checks run before anything is published. The first rejects a tool page whose written explanation is too short to be worth reading, or which reuses a sentence that already appears on another tool's page — that second rule is the one that matters most on a site with dozens of near-identical “compress an image to N KB” pages, where the lazy option is to write the copy once and swap the number. The second scans every page for a claim its code does not support.
When a check catches something we cannot fix straight away, the tool is switched off rather than left running with a confident description. Two pages are in that state right now: the Bijoy to Unicode and Unicode to Bijoy converters handed your text back unchanged while labelling it converted, because the character mapping had never been written. The conversion has been removed, each page now explains what is missing and why the mapping is harder than it looks, and both are kept out of search results until it exists. You can open them and check.
What we do not do
No sign-up, no file library
There is no account to create and nothing to log in to. We do not keep a copy of your work to show you later, which also means we cannot recover a file for you after you close the tab.
Calculators do arithmetic, not advice
An EMI, tax or SIP figure here is the output of a formula documented on the page. It is not a recommendation, and it does not replace your lender's sanction letter, a chartered accountant, or a qualified professional.
No government affiliation
ToolMela is not connected to any government department, exam board or official portal. Where a tool targets an official size or dimension limit, that limit came from the portal's own published requirement — confirm it there before your final upload, because those rules change without notice.
No claim we cannot support
We do not describe a tool as AI-powered, lossless or structure-preserving unless the code does that. Where a limit exists, the page names the limit instead of hiding it.
Corrections, bugs and requests
Write to contact.toolmela@gmail.com. It reaches the people who maintain the code, not a ticket queue.
A report is most useful with four things: the page address, what you expected, what actually happened, and the browser and device you were using. File-handling bugs are often specific to one browser, so that last detail saves the most time. If a tool is producing a wrong or corrupted file we would much rather hear about it in two lines than not at all.
A factual error in written content is corrected under our editorial policy. A tool that is genuinely broken either gets fixed or gets switched off with an explanation on the page — and we will tell you which of the two happened.