Encoding Tools
URL, Base64, timestamp and UUID helpers, all computed locally
Enter a timestamp and click Convert to get the local time, ISO string and seconds/milliseconds values.
Uses crypto.randomUUID when available and falls back to a random string.
Encoding and decoding utilities explained
The utilities page bundles URL encoding and decoding, Base64 encoding and decoding, timestamp conversion and UUID generation. Each action runs independently and computes locally, which suits request parameters, log fields and temporary identifiers.
URL encoding follows UTF-8 percent escaping and helps build query parameters. Base64 handles Chinese text and emoji, while the timestamp tool switches between seconds and milliseconds and shows both local time and ISO 8601 for cross-timezone checks.
UUID generation prefers the browser crypto random interface and falls back to a random string, and the result can be copied directly. Every action reports success or failure so a result is never assumed to be copied.
Frequently asked questions
- Should a timestamp use seconds or milliseconds?
- A ten-digit value is usually seconds and a thirteen-digit value is usually milliseconds. The wrong unit produces a time that differs by a factor of one thousand, so confirm the source first.
- Can Base64 output be placed in a URL directly?
- Standard Base64 contains plus, slash and equals characters, so it needs another URL encoding pass. Use a URL-safe variant for links when possible.
- Can generated UUIDs collide?
- With the crypto random source the probability is extremely low and acceptable for ordinary identifiers. For strict uniqueness, validate on the server as well.