About
A toolkit, not a platform.
MakeMyToolkit is the front door to a family of 12 small, single-purpose web apps. Each sister site handles one category — PDFs, images, audio, text, colors, passwords — and tries to stay out of your way while you finish the job you came to do.
The itch behind it
Every online utility eventually turns into a platform. A tool that used to compress a PDF now asks for your email, dims the download button until you sign in, and queues your file behind a watermark you have to pay to remove. The work gets harder over time instead of easier.
The MakeMy family is the reaction. Twelve separate sites, each one narrow on purpose, each one free forever, each one allergic to upsells and onboarding flows. When a tool outgrows its category we spin off a new sibling instead of piling features onto the old one.
What this hub is for
This site — makemytoolkit.com — doesn't process files. It exists to introduce the family, help you find the right sister site for your task, and serve as the one canonical directory of everything we've built. The toolkit grid on the landing page is the map.
How the tools work
Most sister sites do their processing in the browser. Your file loads into a tab, the work happens on your own CPU, and the result comes back without ever being sent to a server. When a task genuinely requires server-side computation we say so on the page, and we delete what we received as soon as the job is done.
There are no accounts. There is no sync, no history, no saved workspace. Close the tab and the tool forgets you were there — which is the point.
How it stays free
Running 12 sites costs money, so the tools carry ads. The deal is straightforward: the ads pay for the hosting, and in exchange we never paywall features, never ask for an email, never hold your output hostage behind a "pro" plan. If an ad ever feels out of place — autoplay video, dodgy redirect, obscuring the tool — that's a bug and we want to know.
Who built it
The family is built and maintained by a small independent team that got tired of the state of online tools and decided to make the ones we wanted to use ourselves. We ship when a tool is ready, not on a release calendar, and we'd rather add a new sister site than cram another feature into an existing one.
A word on AI
We use AI where it helps — writing boilerplate, reviewing pull requests, generating test cases. We don't use it to write the copy on the tool pages or to pad the site with generated content. If a page reads like it was written by a person, that's because it was.