Measured Base64 overhead at 10,000 bytes
The committed run produced 13,336 Base64 characters from 10,000 deterministic input bytes. The Lab also shows why 1- and 2-byte inputs have much larger padding overhead.
See all Base64 casesFocused utilities for inspecting, converting, generating, and preparing digital data. Most tools process input locally in your browser, and the claims behind them are tied to published first-party test results.
The committed run produced 13,336 Base64 characters from 10,000 deterministic input bytes. The Lab also shows why 1- and 2-byte inputs have much larger padding overhead.
See all Base64 casesThe suite records actual behavior for Unicode, trailing commas, BOM input, invalid escapes, a large integer, and 100-level nesting rather than claiming generic “validation.”
See the JSON matrixBlack on white is one of five committed reference pairs used to check the same relative-luminance math exposed by the Color & Contrast tool.
See contrast resultsThe image suite records baseline bytes, output bytes, codec availability, and savings for JPEG, PNG, and WebP settings on a deterministic fixture—with explicit limits on what those numbers prove.
See image resultsThe Lab renders result files committed with the source. It does not expose a public “run benchmark” endpoint, and timing measurements are labeled with their exact runtime instead of being presented as universal browser performance.
Every tool keeps a stable URL. Processing labels distinguish browser-local workflows from the Image Compressor's temporary server workflow.
Format, minify, sort keys, validate syntax, and open local JSON files with byte/type summaries.
Local processingInspect header and payload, translate time claims, and flag algorithm/security context without claiming signature verification.
Local processingEncode/decode UTF-8 text, local files, and Data URLs with download reconstruction and byte-overhead feedback.
Local processingHash text or local files with MD5 and SHA-family algorithms; legacy algorithms are clearly labeled.
Local processingCompare component vs full-URI percent encoding with character/byte counts and malformed-input diagnostics.
Local processingLive GFM preview, sanitized HTML, and PDF/PNG/Word export from local browser content.
Local processingCreate URL/text/Wi-Fi/email/phone/SMS payloads with correction levels, or scan a local image.
Local processingConvert HEX/RGB/HSL/HSV/CMYK and check arbitrary foreground/background WCAG ratios.
Local processingServer-side PHP GD compression with bounded uploads, protected downloads, and short-lived temporary files.
Temporary server processingJSON, JWT, Base64, Hash, URL, Markdown, QR, Password, Case, and Color perform their primary transformations client-side. Their tool algorithms do not POST the working input to a processing API.
Images are processed by PHP GD. Uploads use randomized session-bound names; downloads are token-protected and temporary image files are cleaned within 5 minutes.
The current review build uses the AdSense account meta tag plus ads.txt for publisher association. Visible ad slots and the Google advertising script are not enabled.
Exact length formula, padding behavior, UTF-8 bytes, and the same measured cases published in the Lab.
Seven deterministic parser cases plus the distinction between syntax validity and application-schema validity.
Codec settings, temporary-file controls, shared-hosting limits, fixture results, and the boundaries of those measurements.
Z Tools is independently built and maintained. Public changes are recorded in the changelog, benchmark environments are published in the Lab, and weak or overlapping guides are kept out of the public index until they add distinct value.