URL Encoder and Decoder

0 chars 0 words 0 lines
πŸ“ Drop file here to convert
0 chars 0 words 0 lines

Key Features

β–Ό
⚑

Instant Conversion

Encode and decode URLs instantly. No waiting, no page reloads.

🌍

UTF-8 Support

Fully supports UTF-8 characters, including emojis and international text.

πŸ”’

Secure & Private

All conversions happen locally in your browser. Your data never leaves your device.

πŸ”—

Full URL Encoding

Properly encodes all special characters including spaces, symbols, and non-ASCII characters.

πŸ“‹

One-Click Copy

Easily copy results to clipboard with a single click for quick use in your projects.

πŸ’Ύ

History Tracking

Automatically saves your recent conversions for quick reference and reuse.

URL Encoding Examples

β–Ό
hello world
hello%20world
user@example.com
user%40example.com
100% Complete
100%25%20Complete
https://site.com/?q=test&lang=en
https%3A%2F%2Fsite.com%2F%3Fq%3Dtest%26lang%3Den
δ½ ε₯½δΈ–η•Œ
%E4%BD%A0%E5%A5%BD%E4%B8%96%E7%95%8C
πŸ”’ Secure
%F0%9F%94%92%20Secure

About URL Encoding

β–Ό

What is URL Encoding?

URL encoding (also known as percent-encoding) is a mechanism for encoding information in a Uniform Resource Identifier (URI) under certain circumstances. It converts unsafe ASCII characters into a format that can be transmitted over the Internet.

Why Use URL Encoding?

URL encoding is commonly used in:

  • Query Parameters: Passing data in URL query strings safely.
  • Form Data: Encoding form submissions for GET requests.
  • API Requests: Transmitting special characters in API endpoints.
  • File Paths: Encoding file names and paths in URLs.

How URL Encoding Works

URL encoding replaces unsafe ASCII characters with a "%" followed by two hexadecimal digits. For example, a space is encoded as "%20", and an "@" symbol becomes "%40". Non-ASCII characters are first converted to UTF-8 bytes, then each byte is percent-encoded.

Common Encoded Characters

URL Encoding Reference Table

CharacterEncodedDescription
space%20Space character
!%21Exclamation mark
@%40At symbol
#%23Hash/Number sign
$%24Dollar sign
%%25Percent sign
&%26Ampersand
/%2FForward slash
=%3DEquals sign
?%3FQuestion mark

How to Use This Tool

  1. To Encode: Type or paste your URL or text into the input box and click "Encode".
  2. To Decode: Paste a URL-encoded string and click "Decode".
  3. Copy Result: Click "Copy Result" to copy the output to your clipboard.

Frequently Asked Questions

β–Ό

What is the difference between encodeURI() and encodeURIComponent()?

+

encodeURI() encodes a complete URI but leaves characters like :/?#=@& intact since they have special meaning in URLs. encodeURIComponent() encodes all special characters including these, making it suitable for encoding individual query parameters or URL components. This tool uses encodeURIComponent() for full encoding capability.

Why are spaces encoded as %20 instead of +?

+

Both %20 and + are used to encode spaces in URLs. %20 is the standard percent-encoding for spaces. The + sign is used in application/x-www-form-urlencoded data (like form submissions). This tool uses %20 which is more universally compatible with modern URL standards.

How are non-ASCII characters encoded?

+

Non-ASCII characters (like emojis or Chinese text) are first converted to UTF-8 byte sequences. Each byte is then percent-encoded. For example, "δ½ ε₯½" becomes "%E4%BD%A0%E5%A5%BD" - each %XX represents one byte of the UTF-8 encoding.

Is URL encoding encryption?

+

No, URL encoding is not encryption. It is simply a way to represent special characters safely in URLs. Anyone can decode a URL-encoded string. It does not provide any security or data protection - it only ensures safe data transmission through URLs.

When should I use URL encoding?

+

Use URL encoding whenever you need to include user input or special characters in a URL. This includes query parameters, form data in GET requests, API endpoints, and any time you're constructing URLs dynamically. Failing to encode properly can result in broken URLs or security vulnerabilities.