URL Encoder & Decoder

Input

0 characters

Output

Auto-updates as you type 0 characters

▸ Query String Parser

💡 What does this do?

Parse a URL's query parameters (the part after ?) into an editable table. Perfect for:

🔍 Analyzing API URLs: See all parameters clearly
✏️ Editing parameters: Change values without manual encoding
🔗 Building URLs: Add/remove parameters visually
🐛 Debugging: See what data you're sending to APIs

Example: Paste an API URL like https://api.example.com/search?q=test&page=2&limit=10 and edit the parameters in the table below!

▸ Query Parameters

Key	Value (Decoded)	Actions

Rebuilt URL

▸ Enter Full URL

▸ Batch Processing

Input (one URL per line)

Output

🔗 What is URL Encoding?

URL Encoding (also known as percent-encoding) is a mechanism for encoding information in a Uniform Resource Identifier (URI). It converts characters that aren't allowed in URLs into a format that can be safely transmitted over the Internet.

The web uses the ASCII character set. Any character that isn't an unreserved ASCII character (A-Z, a-z, 0-9, and - _ . ~) must be encoded. This is done by replacing the character with a % followed by its two-digit hexadecimal value.

Why is it necessary?

Ambiguity: Characters like &, =, and ? have special meaning in URLs. If you want to use them literally (e.g., in a password), they must be encoded.
Safety: Spaces and unsafe ASCII characters (like <, >, ") can break URLs or confuse servers.
Data Integrity: Ensures that the data you send matches exactly what the server receives, regardless of browser or network interpretations.

🛠️ How to Use This Tool

Modes

This tool is split into four specialized modes:

Encode/Decode: The standard tool. Type text on one side, see the result on the other. Use "Auto-detect" to smart-switch based on input.
Query Parser: Paste a full URL to see a table of all query parameters. Edit values individually without worrying about encoding syntax.
URL Breakdown: Dissects a URL into its components: Protocol, Host, Port, Path, Query, and Hash. Perfect for debugging complex routing issues.
Batch Mode: Process lists of URLs (one per line). Great for cleaning up log files or preparing bulk redirect lists.

Tips for Power Users

Swap Button (⇄): Quickly toggle between encoding and decoding. Useful when you accidentally paste into the wrong box.

Smart Paste: In Query Parser mode, pasting a URL automatically triggers the parser. No need to click "Parse".

💡 Common Use Cases

1. API Parameters

When sending data to REST APIs via query parameters, everything must be encoded. If you search for "C++ & Java", sending it as ?q=C++ & Java will break because & starts a new parameter. Encoded, it becomes ?q=C%2B%2B%20%26%20Java.

2. Redirect Return URLs

Authentication flows (OAuth) often need a return_url parameter. Since this is a URL inside a URL, the inner URL must be fully encoded to prevent the browser from misinterpreting where the first URL ends.

3. UTM Tags for Marketing

Marketers use UTM parameters to track clicks. If a campaign name contains spaces or emojis (e.g., "Summer Sale ☀️"), it must be encoded to ensure analytics tools capture it correctly.

4. Form Data

When browsers submit HTML forms using application/x-www-form-urlencoded, they automatically apply this encoding. This tool helps you debug raw form data or simulate form submissions.

⚡ Tips & Tricks

Space Encoding: + vs %20

Spaces can be encoded as %20 (standard) or + (legacy, used in query strings). This tool defaults to %20 for maximum compatibility, but handles decoding both correctly.

encodeURI vs encodeURIComponent

In JavaScript development:

Use encodeURI() for full URLs. It preserves protocol/host separators like : and /.
Use encodeURIComponent() for values within a URL (like query parameters). It encodes everything including / and :.

Avoid Double Encoding

A common bug is encoding text that is already encoded, resulting in %2520 (encoded %) instead of %20. Use the "Decode" mode first if you're unsure.

❓ Frequently Asked Questions

Does this tool handle Emoji?

Yes. Emojis and unicode characters are first converted to UTF-8 bytes and then percent-encoded. For example, 😊 becomes %F0%9F%98%8A.

Is my data private?

100% Client-Side. No data is sent to any server. All processing happens in your browser's memory, making it safe for internal URLs, tokens, or sensitive query strings.

Why does my decoded URL look wrong?

You might need to decode multiple times. Some systems apply encoding layers (e.g., a URL inside a JSON object inside a URL). Click "Decode" repeatedly until it looks readable.

Can I encode large blocks of text?

Yes, but keep in mind that URLs generally have a max length limit (often 2048 characters) in many browsers and servers. For larger data, consider using Base64 or POST requests instead.

Input

Output

▸ Query String Parser

💡 What does this do?

▸ Query Parameters

▸ Enter Full URL

▸ URL Components

▸ Batch Processing

🔗 What is URL Encoding?

🛠️ How to Use This Tool

Modes

Tips for Power Users

💡 Common Use Cases

1. API Parameters

2. Redirect Return URLs

3. UTM Tags for Marketing

4. Form Data

⚡ Tips & Tricks

Space Encoding: + vs %20

encodeURI vs encodeURIComponent

Avoid Double Encoding

❓ Frequently Asked Questions

Does this tool handle Emoji?

Is my data private?

Why does my decoded URL look wrong?

Can I encode large blocks of text?