Developer tools that run in your browser

Twenty-nine 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 entirely in your browser using standard JavaScript APIs: JSON.parse/stringify, Papa Parse for CSV, js-yaml for YAML, btoa/atob for Base64, encodeURIComponent for URL encoding, crypto.randomUUID for UUIDs, crypto.subtle.digest for hashes, and more. Each tool page names the specific API it uses. All data stays on your device — nothing is uploaded to a server.

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

Base64

Encode and decode Base64 text and files in your browser with btoa and atob (RFC 4648). UTF-8, + / = alphabet. Nothing uploaded.

Open

Base64url

Encode and decode Base64url in your browser with RFC 4648 §5 (- and _, no padding). UTF-8 via btoa/atob. Nothing uploaded.

Open

Base32

Encode and decode Base32 in your browser with RFC 4648 §6 (A–Z 2–7, = padding). UTF-8 via encodeURIComponent. Nothing uploaded.

Open

Base32hex

Encode and decode Base32hex in your browser with RFC 4648 §7 (0–9 A–V, = padding). UTF-8 via encodeURIComponent. Nothing uploaded.

Open

Base16

Encode and decode Base16 (hex) in your browser with RFC 4648 §8 (0–9 A–F, no padding). UTF-8 via encodeURIComponent. Nothing uploaded.

Open

URL Encoder

Encode and decode URLs with percent-encoding (encodeURI and encodeURIComponent). Spaces become %20, not +. Nothing uploaded.

Open

URLSearchParams

Encode and decode form-urlencoded query strings in your browser with WHATWG URLSearchParams. Spaces become +, not %20. Nothing uploaded.

Open

URL Parser

Parse URLs in your browser with WHATWG new URL(). Split host, path, query, and hash locally. Nothing uploaded.

Open

Punycode

Encode and decode Punycode in your browser with RFC 3492. Raw Punycode, no xn-- prefix. Nothing uploaded.

Open

IDNA

Encode and decode IDNA in your browser with UTS #46 ToASCII and ToUnicode. Convert Unicode domains to ACE labels locally. Nothing uploaded.

Open

Unicode Normalize

Normalize Unicode text in your browser with UAX #15 NFC, NFD, NFKC, and NFKD. Compose or decompose characters locally. Nothing uploaded.

Open

HTML Encoder

Encode and decode HTML entities in your browser. Escapes ampersand, angle brackets, and quotes as named or numeric references locally. Nothing uploaded.

Open

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 entirely in your browser using JavaScript APIs like JSON.parse, crypto.subtle.digest, Papa Parse, and js-yaml. Your files, tokens, and hashes never leave your device.
Which tools belong on this hub?
The 29 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. The JWT decoder only splits a compact JWS into its three base64url segments and pretty-prints the header and payload as JSON. The signature is displayed but never verified. There is no HMAC, RSA, or JWKS check, and JWE tokens (which have five segments) are rejected.
Is the hash tool a password hasher?
No. SHA-256, SHA-1, and MD5 are unkeyed message digests — they produce a fixed-size hash from any input. They are suitable for checksums and data integrity, but not for password storage. Use bcrypt, Argon2, or scrypt for passwords.

Related