1. What the catalog contains
The catalog contains 500 distinct tool routes across data, APIs, text, security, networks, documents, media, mathematics, design, and business calculations. Some routes share a workspace component or parser. The count describes public task pages; it does not mean that every format, codec, algorithm, or branch of an external specification is implemented.
Each page identifies its task, presents the available controls, shows the output produced by that workspace, and documents practical limits. The controls on the page define the supported scope.
2. Browser processing boundary
Tool inputs are designed to be processed in the current browser tab. Text and numerical tools use JavaScript and browser APIs. File tools use browser decoders or bundled parsers after the user selects a local file. Tool code does not intentionally send entered payloads to a CZOA processing API.
The website still loads HTML, scripts, fonts, and other assets. Analytics and advertising can make separate requests when enabled, as described in the Privacy Policy. Browser extensions, managed-device software, and browser behavior are outside the project's control. Users should not treat a normal web page as an isolated or air-gapped security environment.
3. Implementation and limits
- Calculations: displayed precision, units, assumptions, and rounding rules determine how a result should be interpreted. JavaScript floating-point limits apply unless a tool explicitly uses BigInt or decimal-safe handling.
- Text and structured data: supported syntax is limited to the parser and controls shown. Large or malformed input can fail, and a lightweight helper may implement only a documented subset of a larger language.
- Documents and media: codecs, file size, memory, and browser support vary by device. Keep the original file and inspect any exported artifact before relying on it.
- Security tools: encoders, inspectors, hashes, and cryptographic helpers do not replace an audited security product, professional review, or independent verification.
4. How releases are checked
Release checks cover TypeScript compilation, static generation, route and metadata audits, internal links, browser rendering, representative input/output vectors, localized page output, and selected real file artifacts. The current suite also opens every English tool route in a browser and attempts a workspace run where a safe sample is available.
No finite test suite proves every result for every possible input. A page loading successfully proves neither every algorithm branch nor every file produced by that page. For money, safety, security, compliance, or irreversible file changes, verify important results with an independent source and retain the original input.
5. Editorial principles
Descriptions should reflect the current implementation. Standards are cited only when they directly govern the relevant format, protocol, or formula; a citation is not certification or a claim of complete conformance. When a defect is reproduced, the implementation, explanation, and regression test should be corrected together.
Advertising, when enabled, is visually labelled and kept away from tool action and download controls. Commercial relationships do not determine tool output. Affiliate links, if present, are disclosed on the Affiliate Disclosure page.
6. Accessibility and feedback
The interface aims to provide labelled controls, keyboard access, visible focus, responsive layouts, and readable contrast. Compatibility can differ across browsers and assistive technologies. Report an incorrect result, misleading description, translation problem, or accessibility defect through the Contact page with a sanitized reproducible example.