Developer Tools
Format, encode, decode and hash data on your device.
Ready to use
- JSON FormatterFormat, check and make JSON smaller.
- Base64 Encoder & DecoderChange text to Base64 and back again.
- Hash GeneratorMake SHA-256, SHA-384 and SHA-512 hashes from text or a file.
- URL Encoder & DecoderEncode or decode text for safe use inside a URL.
- UUID GeneratorGenerate random, unique UUID v4 identifiers.
- Unix Timestamp ConverterConvert between Unix timestamps and readable dates.
Formatting, encoding, hashing and IDs
These six tools cover different everyday jobs:
- Messy or minified JSON? Use JSON Formatter to pretty-print it, minify it, or check it's valid.
- Need text as Base64, or to decode some? Use Base64 Encoder & Decoder.
- Need text safe to put inside a URL? Use URL Encoder & Decoder.
- Need a checksum or fingerprint of some text or a file? Use Hash Generator for SHA-256, SHA-384 or SHA-512.
- Need a random unique identifier? Use UUID Generator for a UUID v4.
- Working with Unix time? Use Unix Timestamp Converter to convert a timestamp to a readable date, or the other way around.
Encoding, hashing and URL-safety are not the same thing
It's easy to mix these up. Base64 is an encoding, not encryption or compression — it just represents the same bytes using a different, text-safe alphabet, and anyone can decode it straight back with no key involved. URL encoding (percent-encoding) solves a narrower problem: making specific characters safe to place inside a URL, such as turning a space into %20. A hash is different again — SHA-256/384/512 are one-way in normal use: the same input always produces the same fixed-length output, but there is no way to run it backward to recover the original text, which is why hashes are used to verify data rather than to hide it reversibly.