Wall of Tools

Encoding Toolkit: Base64, URL Encode, UUID Generator and Hash

Encode and decode Base64 and URLs, generate UUIDs and make MD5 or SHA-256 hashes, all in your browser, so keys and tokens you paste are never sent anywhere.

  • Runs in your browser, nothing is uploaded
  • Free, no sign-up
  • 117 automated checks

Four small developer jobs on one page

Some tasks come up again and again when you work with web services, data and code: turning text into Base64 and back, making text safe to put in a web address, creating unique IDs, and calculating a hash to compare or sign something. Each one takes seconds when the right tool is to hand. This page puts all four side by side, on tabs, and they all run in your browser, so keys, tokens and customer data you paste in are never sent anywhere.

Which tab do I need?

  • Base64 encodes text or files as plain characters, and decodes Base64 back to text or a file. Use it for data URLs, email attachments, configuration values and the parts of a JWT.
  • URL encode turns spaces and symbols into percent codes (%20, %26) and back, and takes any link apart into its site, path and parameters. Use it for search terms and values in links, and for reading long tracking or redirect links.
  • UUID makes random (version 4) or time-ordered (version 7) unique IDs, one or ten thousand at a time, and reads any UUID you paste. Use it for database keys, test data and file names.
  • Hash calculates MD5, SHA-1, SHA-256, SHA-384 and SHA-512 of text, with HMAC and a compare box. Use it to check a value, sign a webhook test or compare with a hash you were given.

Encoding, hashing and encryption are different things

  • Encoding (Base64, URL encoding) changes how data is written so it can travel safely. Anyone can reverse it. It hides nothing.
  • Hashing makes a fixed-length fingerprint that cannot be turned back into the original. It proves that data has not changed.
  • Encryption locks data so that only someone with the key can read it. For that, use Encrypt Text and Files.

Typical jobs

  • Reading a token or a config value: decode the Base64 to see what is inside.
  • Building a link with a search term that contains spaces or an ampersand: URL-encode the value first.
  • Seeding a test database: generate a list of UUIDs and paste them into a column.
  • Testing a webhook signature: calculate the HMAC-SHA256 of the message with the shared secret and compare it with the header you received.
  • Checking a download: compare the published SHA-256 with the hash of the text or, for a file, with File Checksum.

Good to know

  • UTF-8 everywhere: all four tabs treat text as UTF-8, the standard of the web, so accented letters, other alphabets and emoji give the same results as servers and programming languages.
  • Each tab has its own address, so you can bookmark the one you use most.
  • Files: Base64 can encode and decode whole files. For the hash of a file, use File Checksum, which reads the exact bytes of large files quickly.

How this tool was tested

Before publishing, I ran 117 automated checks on the finished page in Microsoft Edge, which is built on Chromium like Chrome. Last full run: 21 November 2026.

  • Base64 tab
    • Standard examples: the test vectors published in RFC 4648 ("f", "fo", "foo" and so on) encode and decode exactly.
    • Text: accents and emoji as UTF-8, URL-safe Base64, missing padding, spaces and line breaks in the input, lines of 76 characters for email, and 300 random texts with accents, Chinese and emoji that survived a round trip in all three styles.
    • Binary data: 5,000 random bytes gave exactly the same Base64 as the browser's own encoder, and decoded back byte for byte. Invalid characters and impossible lengths are refused.
    • Using the tool: encoding and decoding as you type, Base64 that holds a picture recognised and saved as a PNG byte for byte, a data URL keeping its file type, encoding a file as a data URL, and Swap.
  • URL encode tab
    • Encoding: every special character when encoding part of a link, a whole link keeping its structure, + for spaces in form data, accents and emoji as UTF-8 codes, and the unreserved characters of RFC 3986 left as they are.
    • Round trips: 400 random texts with accents, Chinese and emoji came back exactly in both styles. A lone % and codes that are not valid UTF-8 are refused, with the position given, and double encoding is noticed.
    • Taking links apart: site, port, decoded path, every parameter in order (including empty and repeated ones), the part after #, a link without https:// and text that is not a link.
    • Using the tool: encoding and decoding as you type, switching mode, the warnings and errors, and the link table showing values as text rather than HTML.
  • UUID tab
    • Version 4: 20,000 UUIDs all had the right form, version and variant, with no duplicates; their random digits passed a chi-square test for an even spread, and they come from the secure random generator.
    • Version 7: 5,000 UUIDs had the right form and sorted in the order they were made, even within the same millisecond; the time inside matched the time they were made, and a fixed time gave the right first 48 bits.
    • Reading UUIDs: any format (capitals, braces, no hyphens, urn:uuid:), and the example version 1 and version 7 UUIDs from RFC 9562 read back with the right date and time. Nil and max UUIDs are named; wrong values are refused.
    • Using the tool: a UUID ready on opening, a list of 250 capital v7 UUIDs, quotes and commas for code, the 10,000 limit, the download and the checker.
  • Hash tab
    • MD5 was checked against the seven examples in RFC 1321, lengths around the 64-byte block edge where padding needs an extra block, and UTF-8 text.
    • SHA-1, SHA-256 and SHA-512 against the published values for "abc" and for empty text.
    • HMAC against RFC 4231 (HMAC-SHA256) and RFC 2202 (HMAC-MD5 and HMAC-SHA1), including a key longer than a block; an empty key works too.
    • Using the tool: five hashes as you type, capitals, Base64, the compare box lighting up the matching line, a line break at the end and the option to ignore it, and HMAC with a key.

What the tests did not cover: Files over 50 MB were not tested. Safari and Firefox were not tested. Something not working? Tell me on the contact page.

FAQ

Is it safe to paste API keys and tokens?

Yes. Everything is worked out in your browser; nothing is sent to a server or saved.

Does it work offline?

Once the page has loaded, yes.

Why are MD5 and SHA-1 still here if they are broken?

Many older systems and downloads still use them, so you need them to compare. Use SHA-256 for anything new.

Published 21 November 2026