Handy tools — URL encode, JSON, timestamps & more
When you are wiring a page, checking an API, or reading a log, you often need small jobs done fast: percent-encode a query value, pretty-print a one-line JSON blob, turn an epoch into a readable time, hash a string, mint test UUIDs, peek at JWT claims, or check whether text color passes contrast. Each tool is its own page with examples and plain-language help.
Who these tools are for
- Frontend or backend folks checking query strings, JSON payloads, or token fields.
- Students verifying encodings, bases, or timestamps for homework.
- Designers checking hex colors and contrast without opening a full suite.
- Testers who need a handful of random UUIDs or text checksums.
- Works alongside on-site Base64 and color converters.
All handy tools
FAQ
- Does the JWT tool verify signatures?
- No. It only expands header and payload. Do not paste irreplaceable production secrets into public pages.
- Is MD5 OK for passwords?
- No. MD5 is fine for “are these two strings the same?” Prefer SHA-256 for stronger checksums. Passwords need a proper password hash with salt.
- URL encode vs Base64?
- URL encoding makes text safe inside a URL with %XX. Base64 is another text encoding, often for embedding or transport. Different jobs, different pages.
- Timestamp off by eight hours?
- Usually local time vs UTC. The timestamp page shows both — compare the two fields.
- What standard is the contrast checker?
- It compares your ratio to WCAG AA/AAA thresholds for normal and large text so you can fix copy or background colors.