JWT Decoder
Inspect any JWT in your browser. Nothing is sent to a server.
Open toolCryptographically secure random identifiers and secrets, generated in your browser.
Runs locally in your browser
Cryptographically secure identifiers and secrets, generated in your browser.
UUID v4
random
UUID v7
time-ordered
Hex 32
16 bytes
Hex 64
32 bytes
Base64 32
24 bytes raw
Kube Secret
base64 of 32 bytes
data: field.All values are generated locally with crypto.getRandomValues. Nothing is sent to a server. If your threat model requires hardware-backed randomness (HSM), don't use a browser tool for that.
UUID v4 is fully random. UUID v7 embeds a millisecond timestamp in the first bytes, so IDs sort by creation time. v7 is the better choice for database primary keys because it avoids the B-tree index fragmentation that v4 causes.
Yes. All values are generated with the browser Web Crypto API (crypto.getRandomValues). You should still not use a browser tool to mint secrets that require hardware-backed randomness (HSM).
Use the "Kube Secret" format. It generates 32 random bytes and base64-encodes them, ready to paste into the data field of a Secret manifest.
Tools are ported from DevOps Daily under the MIT license.View original
Inspect any JWT in your browser. Nothing is sent to a server.
Open toolMD5 / SHA hashes of text or a file, plus a checksum verifier. Browser-only.
Open toolParse CIDR blocks, compute ranges, split into smaller subnets, and check whether an IP lives inside a network.
Open tool