About ClientKit
Learn why ClientKit exists, how local processing works, and how its tools and documentation are maintained.
A workspace for everyday conversions and checks
ClientKit brings together text comparisons, JSON and SQL formatting, image and PDF processing, and other everyday checks in a browser workspace. Its purpose is to reduce the setup needed for a small task while preparing code, documents, or visual assets. Browse the categories to find a tool for your data.
Local processing and network requests
Tool inputs are transformed or analyzed on your device. Network requests are still needed to load pages and assets such as OCR language data, a background removal model, and PDF fonts. Local processing means your input is not uploaded to a processing server; it does not mean the entire site makes no network requests. See the Privacy Policy for external services, including advertising.
Documentation and checking results
Each tool page explains its workflow, gives an input and output example, and describes limitations and common questions. Documentation should follow the implemented behavior rather than promise unsupported features. Before using output in a system or document, try a small sample and compare it against the original. Report discrepancies with reproduction steps through the Contact page.