Why are spaces encoded as %20?

Spaces are not valid raw URL characters. Some form encoders use +, but percent encoding uses %20.

Can this decode Unicode?

Yes. Browser URL APIs decode UTF-8 percent sequences back into Unicode text.

URL

URL Encoder / Decoder

Encode and decode URL components

Developer ToolsRuns in browserNo signup

InputOutputread only

About URL Encoder / Decoder

URLs have reserved characters with special meanings, such as question marks, ampersands, slashes, hashes, and spaces. Percent encoding converts unsafe characters into byte sequences like %20, allowing text to travel inside links, query parameters, redirects, callbacks, and API requests without being misread by browsers or servers.

This tool supports two common modes. Component mode uses encodeURIComponent, which is best for query parameter values, path segments, and individual pieces of a URL. Full URL mode uses encodeURI, which preserves characters that already structure a complete URL, such as :, /, and ?.

Decoding is equally useful when debugging OAuth redirects, analytics links, webhook payloads, signed URLs, and form submissions. Everything runs locally in your browser, so private tokens or callback URLs never leave your device. Invalid escape sequences are caught and reported clearly instead of breaking the page.

URL Encoder / Decoder Knowledge Base

What It Is Used For

Encode and decode URL components. People usually use this tool when they need fast, repeatable output without opening a heavy desktop app or sharing private data with a third-party service.

How To Use It

Paste your input, adjust the visible options, run the action, then copy or download the result. For keyboard-heavy workflows, supported tools also respond to Ctrl+Enter or Cmd+Enter.

Search Topics Covered

url encode online, url decoder, percent encoding. This page is written to answer those common search intents with practical browser-based examples and privacy-first processing.