About Webkitters

What is Webkitters?

Webkitters is a growing collection of 87+ free online utility tools covering images, PDFs, QR codes, text processing, and developer utilities. Every tool runs entirely inside your web browser using modern JavaScript APIs — no server, no cloud processing, no account required.

Whether you need to resize a photo before uploading it, compress a PDF for email, generate a QR code for your business card, format a JSON response from an API, or create a strong password — Webkitters has a dedicated tool ready in seconds.

We believe the best tools are the ones that just work. No loading screens, no file size limits enforced by a server, no waiting. You open the tool, do the task, download the result, and move on.

Why We Built Webkitters

Most online tools come with frustrating trade-offs: a file size limit here, a mandatory sign-up there, or an upload that makes you wonder where your files are going. Many "free" tools are free only for a limited number of uses, then ask you to subscribe.

We built Webkitters to be the toolkit we always wanted: genuinely free, with no hidden limits, and privacy-respecting by design. Because all processing happens locally in your browser, there is no infrastructure cost for uploads — which means we can offer everything for free, forever.

The site started with a handful of image tools and has grown steadily as we added tools based on what people actually need day-to-day. Every tool added to Webkitters goes through the same design principle: it must work instantly, work offline once loaded, and never touch your files.

What Tools Are Available?

Our Principles

How the Tools Work

When you open a Webkitters tool, the page loads a small, self-contained JavaScript module. When you upload or drag a file, the browser reads it directly into memory — the file never travels over the network.

Image tools use the HTML5 Canvas API to draw, resize, compress, and export images in any supported format. PDF tools use PDF-lib, a pure JavaScript PDF manipulation library. Developer tools process text strings entirely in-memory.

The output — a resized image, a compressed PDF, a generated QR code — is created as a Blob or data URL inside the browser and handed directly to you as a download. At no point does any file touch a server.

What the tools are built on

Some jobs are too big to write from scratch, so the tools lean on established open-source libraries. Every one is served from this domain rather than a CDN, at a pinned version. That is partly speed, but mostly consistency: a tool that fetches its engine from someone else's server can change behaviour without us doing anything, and it tells that server the IP address of everyone who opens the page.

This table is generated from the files actually served, so it cannot drift out of date the way a hand-written one would. Everything else — the image tools, the text and developer tools — uses browser APIs directly and pulls in no library at all.

How to verify the privacy claim

"Your files never leave your browser" is the kind of claim every tool site makes, and you have no reason to take ours on faith. You do not have to — it is checkable in about thirty seconds, with a tool already in your browser.

1. Open any tool here and press F12 to open developer tools.
2. Go to the Network tab and clear it.
3. Drop in a file and run the tool.
4. Watch what gets sent. You will see requests for the page's own scripts, and for analytics and ads — but no request carrying your file, in any direction.

For a harder test, put your browser in offline mode after the page has loaded and run the tool again. Most of them still work, because the processing was never happening anywhere else. Something that uploaded your file could not do that.

Being precise about the boundary: file contents are never transmitted. Page analytics are — this site runs Google Analytics and shows Google AdSense ads, both of which see that you visited, and web fonts are requested from Google Fonts. None of that carries your file, and all of it is set out in the privacy policy. A privacy claim worth anything has to say where it stops.

Browser support, limits, and mistakes

The tools target current versions of Chrome, Edge, Firefox and Safari, on desktop and mobile. Everything is tested in a real browser rather than only in the abstract — file in, result out, output inspected.

Running in the browser has genuine limits, and it is more useful to state them than to pretend otherwise. Very large files are bounded by your device's memory rather than by a server quota, so a 300 MB PDF may struggle on an old phone and be fine on a laptop. WebP output needs a browser that can encode it. Compressing a PDF by rasterising it makes the text unselectable, which is why that tool offers a mode that does not. Lossless formats like PNG cannot be shrunk by a quality setting, so a PNG photo will barely move until it is converted.

If a tool gives you output you believe is wrong, that is worth reporting and we would rather hear it. Tell us which tool, what you put in, what you got, and which browser and version you were using — with those four things a problem is usually reproducible in minutes. The contact page is the fastest route. Since your file never reaches us, we cannot see what happened unless you describe it.