JWT ToolsJSON ToolsCryptographic Key GeneratorsEncryption & Security ToolsPassword & Identity ToolsData Encoding & FormattingWeb Resources & Content Tools
DevKitData Encoding & FormattingURL Encoder/Decoder

URL Encoder / Decoder

Safely percent-encode text to drop into URLs, or decode URL parameters back into readable text.

Input
Output

URL (Percent) Encoder & Decoder Online

URLs can only be sent over the Internet using the ASCII character-set. Our free online URL Encoder & Decoder tool instantly converts unsafe ASCII and non-ASCII characters into their valid, percent-encoded representation (e.g., converting a space into %20).

Local Processing: Utilizing your browser's native JavaScript APIs (encodeURIComponent and decodeURIComponent), your data is translated instantly without ever making a network request.

Core Features

  • Instant TranslationPaste your complex, parameter-heavy URL or string of text, and see it percent-encoded or decoded in real-time as you type.
  • Handles Special CharactersSafely process emojis, foreign language characters, and reserved URL characters (like &, =, ?) so they don't break your web server's routing or query parsing.
  • Strict Standard ComplianceConforms strictly to RFC 3986. The tool ensures that the resulting string is fully safe to use as a query parameter value or URL path segment in any modern web application.

URL Encoding Example

Unsafe Text (Input)
https://example.com/search?q=coffee & tea ☕
Percent-Encoded (Output)
https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dcoffee%20%26%20tea%20%E2%98%95
Notice how the ampersand (&) becomes %26. If we hadn't encoded it, the web server would have mistakenly thought " tea ☕" was a brand new query parameter!

Related Tools

Base64 Encoder / DecoderEncode binary data or long strings into a 64-character alphabet.URL ParserBreak down a URL into its protocol, host, path, and extract its decoded query parameters into a table.HTML EntitiesEncode characters for safe display within HTML documents (e.g., converting < to &lt;).

Categories

EncodingDevelopment

Frequently Asked Questions

Why do spaces sometimes become "%20" and sometimes "+"?
It depends on where the space is located in the request. According to standard percent-encoding (RFC 3986), a space is encoded as %20. However, historically, when HTML forms are submitted via application/x-www-form-urlencoded, spaces in the form data are encoded as +. Our tool strictly follows RFC 3986, consistently encoding spaces as %20 for maximum compatibility across modern APIs.
What characters are "safe" (unreserved) in a URL?
According to the specification, "unreserved" characters that do not need to be percent-encoded include uppercase and lowercase letters (A-Z, a-z), digits (0-9), and four specific symbols: hyphen (-), period (.), underscore (_), and tilde (~). Every other character should be encoded.