Text tools
Encode text for safe use in URLs. Spaces become %20, special characters are percent-encoded.
URL-encoded output
Hello%2C%20World!%20%F0%9F%8C%8D
URL encoding converts special characters and spaces into percent-encoded format (e.g., space becomes %20). This is essential when embedding text in URLs.
URL encoding (also called percent encoding) is a standardized method for representing characters in URLs by converting unsafe symbols into %HH sequences, where HH is the hexadecimal code of the character. This ensures text can be transmitted safely through web browsers and APIs without breaking links or causing parsing errors.
The tool reads your input text and converts each special character—spaces, ampersands, hyphens, Unicode characters—into its UTF-8 byte representation, then expresses each byte as %HH in hexadecimal. Alphanumeric characters (A-Z, a-z, 0-9) and safe symbols (hyphen, underscore, tilde, period) pass through unchanged. The encoded output is copy-ready for query strings, form submissions, and API calls.
Percent encoding: CHAR → %HH (where HH = hex code of UTF-8 byte)Each unsafe character is converted to its UTF-8 byte value and represented in hexadecimal with a % prefix. For example, space (ASCII 32) becomes %20, and & becomes %26.
| Input | Result | Notes |
|---|---|---|
| hello world | hello%20world | Space becomes %20, the most common encoded character in URLs |
| user@example.com | user%40example.com | @ symbol becomes %40, essential for email parameters in query strings |
| price=$99 & tax=10% | price%3D%2499%20%26%20tax%3D10%25 | Multiple special chars: = becomes %3D, & becomes %26, % becomes %25 |
You likely encoded the entire URL including the protocol and domain. Encode only the parameter values and path segments, not https:// or the domain name.
URL encoding escapes characters for safe use in URLs (spaces → %20), while HTML encoding escapes for safe display in HTML (< → <). They serve different purposes.
No. URL encoding is purely a format conversion for safe transmission—it's easily reversed. Use HTTPS to encrypt sensitive data in URLs.
Spaces, special symbols (&, #, %, @, =, +, ?, :, /), and non-ASCII characters must be encoded. Safe characters (A-Z, 0-9, -, _, ., ~) do not require encoding.
Yes. Unicode characters are converted to UTF-8 bytes, then each byte is percent-encoded. For example, é becomes %C3%A9.
URLs have a practical limit of 2,000–8,000 characters depending on the browser and server. Encoding increases length (each special char becomes 3+ characters), so very long text may exceed limits.