Developer tools that run in your browser

Sixteen named, client-side utilities for JSON, encodings, IDs, time, and strings. This page is an index — open a tool to run it. Nothing is uploaded.

Docify’s developer tools run in the browser with the API named on each page: JSON.parse / JSON.stringify, Papa Parse, js-yaml CORE_SCHEMA, btoa/atob, encodeURI / encodeURIComponent, crypto.randomUUID, crypto.subtle.digest, ECMAScript RegExp, and Horner on BigInt. JWT signatures are never verified. MD5 is a checksum only. Cron is Vixie crontab(5) five-field syntax, not Quartz.

What this hub is

An internal-linking map of the developer-classified tools already on the homepage. Each card names the algorithm and a hard limit so you can pick the right page. It is not a search box, an API, or a server-side sandbox.

Data formats

Encode and decode

Identifiers and checksums

Time and schedules

Strings and values

Guides

Short comparisons that point back to the live tools. They are not thin clones of the pages above.

FAQ

Do these developer tools upload my data?
No. Each page runs in your browser (JSON.parse, crypto.subtle.digest, Papa Parse, js-yaml, and the other named APIs on that page). Files, tokens, and hashes stay on the device.
Which tools belong on this hub?
The 16 encoding, data, ID, time, and string utilities listed below — the same set marked DeveloperApplication on the homepage. Word counting, case conversion, Markdown, and text diff are indexed on /text-tools/. Images-to-PDF and the PDF stamp are indexed on /pdf-tools/.
Does the JWT decoder prove a token is valid?
No. /jwt-decoder/ only splits a compact JWS into three base64url segments and pretty-prints the header and payload as JSON. The signature bytes are shown. There is no HMAC, RSA, or JWKS check, and JWE (five segments) is rejected.
Is the hash tool a password hasher?
No. SHA-256 and SHA-1 are unkeyed hex digests from crypto.subtle.digest. MD5 is an RFC 1321 checksum in JavaScript, not SubtleCrypto. None of them are HMAC, bcrypt, Argon2, or a KDF.

Related