Developer Tools
Small utilities that developers reach for many times a day: looking inside a JSON Web Token while debugging authentication, and generating or inspecting UUIDs for databases, logs and APIs. Tokens and identifiers stay in the browser, which matters when they come from production systems.
JWT Decoder
Inspect JSON Web Token headers and claims, check expiry and verify HMAC signatures.
Full access on every plan
UUID Generator
Generate random UUIDv4 and time-ordered UUIDv7 identifiers, or inspect an existing UUID.
5 → 1,000 UUIDs at once
Which tool to choose
- JWT Decoder
- You need to read or verify a token.
- UUID Generator
- You need new identifiers or want to examine an existing one.
What these tools solve
- Decode JWT headers and claims and see issue, expiry and not-before times in readable form.
- Verify HS256, HS384 and HS512 token signatures with a shared secret.
- Generate random UUIDv4 or time-ordered UUIDv7 values in bulk.
- Inspect a UUID: version, variant and, for UUIDv7, its embedded timestamp.
When they are useful
- An API returns 401 and you need to know whether the token has expired or has the wrong audience.
- Choosing database keys that sort by creation time.
- Generating fixtures and test data.
How it works
JWTs are split and Base64URL-decoded locally; HMAC signatures are recomputed with the Web Crypto API and compared over their full length. UUIDs follow RFC 9562: UUIDv4 uses 122 random bits, UUIDv7 places a 48-bit Unix millisecond timestamp before the random part.
Limits and good practice
- Decoding a JWT does not prove it is authentic. Only a verified signature does.
- Signatures with public-key algorithms (RS256, ES256 and others) are decoded but not verified.
- UUIDs generated at once: 5 without an account, up to 1,000 on Ultra.
Questions about developer
Help centerCan HashlLab verify a JWT signature?
Yes, for HS256, HS384 and HS512, using the shared secret. Tokens signed with public-key algorithms such as RS256 or ES256 are decoded and their claims shown, but the signature is not verified.
Is it safe to paste a production token?
The token is decoded in your browser and not sent anywhere. Still, tokens are credentials: avoid pasting them on shared computers and prefer short-lived tokens when debugging.
Why is a token with alg “none” flagged?
An unsigned token can be forged by anyone. Servers must never accept it, and its presence usually means a misconfiguration or an attack attempt.
Should I use UUIDv4 or UUIDv7?
UUIDv7 starts with a timestamp, so new values sort after older ones — good for database indexes and logs. UUIDv4 is fully random and reveals nothing about when it was created. Both are defined in RFC 9562.
What can I learn by inspecting a UUID?
Its version, its variant and, for UUIDv7, the creation time in milliseconds. The inspector also recognises the special nil and max UUIDs.