About Shah Khan Tools

Why this site exists

Searching for something as ordinary as “compress an image” or “format JSON” turns up hundreds of results, and most of them work the same way. You land on a page covered in advertising, upload your file to a server owned by someone you have never heard of, wait in a queue, watch a countdown, and eventually get a download — often watermarked, size-limited, or gated behind an account you did not want.

Shah Khan Tools was built because that arrangement is unnecessary. Modern browsers can compress an image, encode Base64, generate a QR code, parse JSON and run every calculation on this site without contacting a server at all. The technology has been capable of it for years. Most tool sites upload anyway, because a file on their server is a business asset and a page view they can monetise. That is a choice, and this site makes the opposite one.

How the tools work

Every tool here is client-side JavaScript. When you drop an image into the compressor, the file is read by your browser's FileReader interface, drawn onto an HTML5 canvas element, re-encoded at the quality you chose and handed straight back to you as a download. At no point does the image data travel across a network. You can verify this yourself: open your browser's developer tools, switch to the network tab, and use any tool on the site. You will see the page load, and then nothing.

This has practical consequences beyond privacy. There is no upload wait, so a 20 MB photo is processed as quickly on hotel Wi-Fi as on fibre. There are no file size caps, because there is no server storage to fill. There are no queues at peak times. And once a tool page has loaded, it keeps working with no internet connection at all — useful on a plane, on a train, or anywhere the signal is unreliable.

What we will never do

• No uploads. Your text, images, code and calculations are processed on your own device and are never transmitted to us.
• No accounts. Nothing here requires an email address, a password or a subscription.
• No watermarks or artificial limits. Output files are clean, full resolution, and there is no daily quota.
• No selling data. We have no user data to sell, because we do not collect it in the first place.
• No dark patterns. No countdown timers, no fake progress bars, no “premium” version of a button that should just work.

How the site is funded

Running a website costs money, and honest tools still have to pay for hosting. Shah Khan Tools is supported by advertising, served through Google AdSense. Ads are placed in fixed positions with space reserved in the layout so they never cause the page to jump around while you are working, and they are never allowed to overlay a tool or interrupt what you are doing.

Advertising has a privacy cost, and it would be dishonest to pretend otherwise. Google and its partners may use cookies to serve ads, and those cookies are described in detail on our privacy policy page along with instructions for opting out of personalised advertising. What advertisers never see is anything you put into a tool — because that information never reaches us either.

Who is behind it

Shah Khan Tools is an independent project, not a venture-funded startup with growth targets. It is built and maintained by a small team who use these tools daily and got tired of the alternatives. Every tool on the site started as something one of us needed and could not find a decent free version of.

That independence is why the tools stay simple. There is no product roadmap pushing towards a paid tier, no investor asking why the sign-up flow is missing, and no reason to add a feature that exists only to collect email addresses. A tool is finished when it does its job well.

How the site is built

The site is static HTML, CSS and JavaScript with no framework and no build-time dependency on a third party. Pages are small, fonts are loaded once and cached, images are lazy-loaded, and layout space is reserved for anything that loads late so the page does not shift under your cursor. The result is a site that loads quickly on a mid-range phone over a mobile connection, which is how most people actually use the web.

What comes next

New tools get added when there is a genuine gap — something people need, that can be done properly in a browser, and that existing free options handle badly. If a tool cannot be built client-side without compromising the no-upload principle, it does not get built. That constraint rules some things out, and we think the trade is worth it.

If a tool here is missing a feature you need, behaving oddly, or if there is something you keep wishing existed, tell us. The contact page reaches us directly, and requests from people who actually use the tools are what shape what gets built next.