UUID Studio

UUID Studio

URL Encoder & Decoder

Percent-encode or decode URL components client-side.

  • đź”’ No data stored or uploaded
  • ⚡ 100% client-side
  • 🆓 Free, no account
Click Convert when ready

Override only when Auto cannot parse your paste. Changing this loads a matching sample into Input — click Convert to run. Use Load sample to cycle every format example.

All conversions

Read-only representations of the same 16 bytes. Every textual form is listed here, not in “Prefer format”.

Paste two values: if both sides are valid JSON, a structural diff appears; otherwise UUID / bytes are compared when both decode to the same format.

A
B

Create or edit JSON here (syntax colors), then format, validate, or convert - same as MongoDB $binary UUID blobs on the Convert tab once detected.

New document

Hash, HMAC, AES-GCM/CBC + RSA-OAEP, codecs, JWT decoding, UUID v4, and secure random - all client-side. JWTs use Base64URL (three segments), not a single MIME Base64 block - use Decode JWT below, not raw Base64 decode.

Examples

  • Text to encode 
    https://uuidstudio.com/search?q=hello world&tag=dev
  • Percent-encoded to decode 
    hello%20world%2Fapi%3Fid%3D1%262

About URL Encoder & Decoder

Spaces, ampersands, slashes, and non-ASCII characters all break a URL if they're pasted in raw - a query string with an unencoded space or `&` silently truncates or misparses on the receiving end.

Percent-encode text to make it safe inside a URL (query parameter, path segment, redirect URI), or decode a percent-encoded string back to readable text. Uses the same encodeURIComponent/decodeURIComponent behavior your JavaScript runtime already has, so results match what your code will actually produce.

FAQ

Does this encode the whole URL or just a component?
It encodes/decodes a single component (like a query value), matching encodeURIComponent - characters such as :/?# that are meaningful in a full URL are also escaped, so don't run a complete URL through it expecting the scheme and slashes to survive.
Is this the same as Base64?
No. Base64 re-encodes bytes into a fixed alphabet; URL/percent-encoding only escapes characters that aren't safe inside a URL, leaving the rest of the text readable.