Codxing

Dev Hub

Format, encode, hash, decode and compare — the everyday developer bits.

JSON FormatterPrettify, minify and validate, with the exact parse error.Diff CheckerLine-by-line comparison of two blocks of text.Base64Encode and decode, with a URL-safe variant.URL EncoderPercent-encoding both ways, plus a breakdown of the URL parts.Hash GeneratorSHA-1, SHA-256, SHA-384 and SHA-512 as you type.UUID GeneratorUUID v4, Nano IDs and short IDs in bulk.JWT DecoderRead the header and payload, and check the expiry.Regex TesterLive matches, highlighting and capture groups.Timestamp ConverterUnix time to readable dates and back, with a live clock.

About the Dev Hub

The Dev Hub is the set of small utilities you reach for several times a week: pretty-printing a JSON blob, decoding a JWT to see why auth is failing, testing a regex against real input, hashing a string, converting a Unix timestamp to something readable. The reason these run locally matters more here than elsewhere — pasting a production token or a customer record into a random online formatter sends it to someone else’s server. Nothing here leaves the tab.

Questions

Is it safe to paste a real JWT or API key here?

Safer than any hosted tool, because there is no server to receive it and no analytics script to leak it. The decoding happens in your browser. That said, treat any token you paste anywhere as worth rotating.

Why is there no MD5 hash option?

The browser’s Web Crypto API does not implement MD5, and it has been cryptographically broken for two decades. SHA-256 is offered instead.

Does the JWT decoder verify signatures?

No. It reads the header and payload and checks the expiry. Verifying a signature requires the secret or public key and must happen on your server — anyone can craft a token with any payload they like.