50+ free tools where your files never leave the browser
ToolKiya replaces the folder of bookmarks to single-purpose utility sites: image conversion, PDF merging, GST and EMI calculators, and text utilities behind one interface. No signup, no upload limit, no ad wall, and for image and PDF work nothing is uploaded at all.
The problem
Indian users keep a browser full of bookmarks to single-purpose utility sites: a tab each for image compression, PDF merging, GST calculation, password generation and a dozen other small daily jobs. We wanted one clean interface to replace that set, without the four things that usually sit between a person and a small task: a signup, an upload limit, an ad wall, and a paywall or trial timer.
Underneath the product problem sat a distribution problem. A general-purpose tool suite has to be found before it can be used, and ToolKiya competes for terms like free image compressor, PDF merger online and GST calculator against very large incumbents.
We run ToolKiya ourselves, so every one of those decisions is ours to live with, including the ones that cost us a lead capture we could easily have taken.
What we built
Image tools for PNG, JPG and WebP conversion plus resize, compress, crop and optimise. PDF tools for merge, split, compress, password-protect and extract. Text and SEO utilities, developer utilities, and a calculator set, all in one place rather than one site each.
For image and PDF work there is no upload step at all. Processing runs in the visitor's own browser through WebAssembly, so those files never leave the device. That was a privacy decision first, and the speed follows from it: nothing is queued, sent or waited on.
Every tool is free with no trial timer, no upload cap and nothing blocking the screen. No email and no login before you can convert an image or merge a PDF. We were explicit with ourselves about this, because the obvious move for an agency is to gate it and collect the address.
The calculator card leads with GST and EMI, then percentage, age, BMI and currency. That ordering is deliberate: GST calculation is one of the tasks in the bookmark folder this product exists to replace, and it is what an Indian small business actually opens a calculator for.
ToolKiya is also a demonstration of how fast a Next.js site can be when Core Web Vitals and SEO are taken seriously from the start. Sub-second LCP on mobile is the bar it was built to, because a slow tool loses to the search results the visitor just came from.
ToolKiya tracks whether a visitor finished the job they arrived to do rather than whether a page loaded. That same instrumentation now goes into client sites, where the question is form submissions and WhatsApp taps rather than sessions.
How the architecture fits together
The front end is Next.js with TypeScript and Tailwind, and for image and PDF work the heavy lifting sits in WebAssembly inside the visitor's browser. That single choice removes most of the system a tool site would normally need: with no upload path there is no queue, no file storage, and no deletion policy to get wrong.
What is left to get right is the front end itself, which is why the performance work here is not decoration. The tool has to paint and become usable in under a second on a mobile connection or the visitor returns to the search results.
Distribution is treated as engineering too. Schema, content structure and internal linking were built in deliberately rather than bolted on afterwards, because a free tool nobody finds is not a product.
Where it stands
- 50+ tools are live and free on toolkiya.com, with no signup, no trial timer, no upload limit and no ads in the way.
- For image and PDF work, files never leave the visitor's device, because the processing runs in the browser rather than on a server.
- The performance bar ToolKiya was built to now sets the standard on client projects, where Lighthouse 90+ on mobile is the target rather than the aspiration.
- Completion instrumentation, rather than pageview counting, carried across into how we measure client sites.
- It is one of three products we build and run ourselves, alongside PlugEV and CloudNX, which is what keeps the advice we give clients tied to things we have had to live with.
Questions we get about this build
Do my files get uploaded to a server?
For the image and PDF tools, no. Processing runs inside your own browser using WebAssembly, so the file never leaves your device and there is nothing on our side to store or delete. That was the first decision made about the product rather than a feature added later.
Is ToolKiya really free, and do I need an account?
Free, and no account. There is no trial timer, no paywall, no upload limit and no ad wall. Open the site, pick a tool, use it. The obvious commercial move would be to gate it behind an email, and we decided against that deliberately.
Why would an agency build a free tool suite instead of a lead magnet?
Because a lead magnet gets used once and resented. A tool people return to does more for us than a captured address, and building it in public forced us to hold our own site to the performance and SEO standard we sell. It is easier to argue for Core Web Vitals work when you can point at something you run.
What does ToolKiya prove about how you would build our project?
That the speed and structure we recommend are things we do rather than things we quote. The same Next.js discipline, browser-side processing where it removes a whole backend, and completion-based measurement instead of pageviews, all show up in client work. You can open toolkiya.com on a phone and judge the result yourself.
How many people use ToolKiya?
We do not publish a usage figure, and we would rather say so than quote one we have not measured and stood behind. What is verifiable is the product itself: 50+ tools, live, free, no account, and the processing happening in your browser where you can watch the network tab stay quiet.
Can you build a product like this for us?
Yes, and the useful conversation starts with what has to stay on the client and what genuinely needs a server. A lot of what looks like it needs a backend does not, and taking the upload path out removes storage, queues, retention policy and a class of privacy problem at the same time.
Want something like this built?
We run this in production ourselves, so the estimate you get is based on having done it rather than having read about it.