About Kaazo Tools
Kaazo Tools exists for the small jobs that somehow turn into twenty-minute detours: two PDF pages need removing, a photo is too large for a form, a CSV needs cleaning, or a scanned page needs searchable text.
We keep those jobs separate. One tool, one clear task. That makes the interface easier to understand—and makes failures easier to spot.
What we build for
The collection covers PDF organisation and editing, image conversion and metadata, Office and data conversion, OCR, text cleanup, developer utilities, QR codes, SEO helpers, local-business workflows, security-related utilities and everyday calculators.
A rule shapes the product: the tool should make its boundary clear. A crop is not a redaction. A decoded JWT is not a verified JWT. A generated sitemap does not guarantee indexing. Those distinctions belong in the product, not buried in fine print.
Why so many focused tools?
A giant “do anything” screen sounds convenient until every job has twenty irrelevant controls. Kaazo splits common actions into focused pages so someone trying to rotate a PDF does not need to understand OCR settings, and someone checking JSON does not need a file editor.
The collection currently contains 175 tools across 12 categories. We would rather keep a narrow tool honest than stretch its description to cover jobs it does not actually perform.
Browser-side processing, where it makes sense
Many supported file operations run in the browser after the page has loaded. That reduces unnecessary file transfers for those workflows and makes quick jobs feel immediate. It also shifts some work to your device, so very large PDFs, high-resolution images and long videos can run into memory or browser limits.
We do not claim that every possible task on the site is “private because it is local” without qualification. Analytics and advertising scripts are separate parts of the website, and each tool's processing behaviour should be described accurately.
Conversion has limits. We say so.
Word, PDF and Excel use different layout models. OCR can misread a name. Image re-encoding can strip metadata. Browser video APIs do not offer the same export options as a desktop editing suite.
Important output deserves a check. Keep the source. Open the download. Search a searchable PDF. Inspect a CSV row with an embedded comma. Those tiny checks prevent a surprising number of bad hand-offs.
How releases are checked
Known failures become regression cases. Release checks look for missing assets, malformed pages, JavaScript parse errors, broken internal links, redirect chains, sitemap mistakes and content/schema mismatches. File-processing tools also receive targeted sample-based checks where we can reproduce an output risk.
During recent QA, that process caught issues such as mixed-size PDF pages being stretched during PowerPoint conversion, duplicate CSV headers losing data, invalid colour values being accepted and editor timing states becoming inconsistent. Fixing a bug is good. Keeping a regression test for it is better.
Read How We Test for the fuller release process, or check the changelog to see what has changed.
Advertising and the product
Kaazo uses advertising to support a free tool collection. Ads do not change a tool's calculation or file-processing logic. We keep the tool action and result separate from advertising placements so the workflow remains understandable.
Found something wrong? The feedback page explains what details help us reproduce it quickly.