URL Encoder / Decoder

Encode and decode URLs with percent encoding. Perfect for web developers and API testing.

0 characters

0 characters

How to Use the URL Encoder/Decoder

Single Mode

  1. Select your operation: Encode URL or Decode URL
  2. Enter or paste your text or URL in the input area
  3. The conversion happens automatically in real-time
  4. View encoding details to see which characters were encoded
  5. Click the "Copy" button to copy the result to your clipboard

Batch Mode (New!)

  1. Switch to "Batch" mode using the mode toggle
  2. Upload a TXT or CSV file, or enter multiple URLs (one per line)
  3. Click "Process Batch" to encode/decode all items at once
  4. View results in a detailed table with success/error indicators
  5. Download results as TXT (plain output) or CSV (with input/output columns)

Batch mode is perfect for processing large lists of URLs, log files, or API parameters. Process hundreds of URLs in seconds with individual error handling.

Common Use Cases

  • Encoding URL parameters for API requests
  • Decoding URLs from server logs and analytics
  • Preparing search queries for web requests
  • Debugging web application URL handling
  • Creating shareable links with encoded parameters
  • Testing URL parsing and encoding in applications

Understanding URL Encoding

URL encoding (also called percent encoding) converts special characters in URLs to a format that can be safely transmitted over the internet. Special characters are replaced with a percent sign (%) followed by two hexadecimal digits representing the character's ASCII code. For example, a space becomes %20, and an ampersand (&) becomes %26.

Which Characters Are Encoded?

URL encoding is required for characters that have special meaning in URLs or are not safe for transmission:

  • Reserved characters: : / ? # [ ] @ ! $ & ' ( ) * + , ; =
  • Unsafe characters: Space, ", <, >, {, }, |, \, ^, `, and non-ASCII characters
  • Safe characters (not encoded): A-Z, a-z, 0-9, -, _, ., ~

Common Encoding Examples

  • Space: " " → %20 or +
  • Ampersand: & → %26
  • Question mark: ? → %3F
  • Equals: = → %3D
  • At sign: @ → %40
  • Forward slash: / → %2F

Frequently Asked Questions

What's the difference between %20 and + for spaces?

Both represent spaces in URLs, but %20 is the standard percent encoding while + is a special encoding used in query strings (application/x-www-form-urlencoded). This tool uses %20 for consistency.

Should I encode the entire URL?

No, only encode the parameter values and query strings. Don't encode the protocol (https://), domain, or structural characters like :, /, and ? that define the URL structure.

Does this support UTF-8 characters?

Yes, the encoder properly handles international characters and emojis using UTF-8 encoding, which may result in multiple percent-encoded sequences per character.

What if decoding fails?

If the input contains invalid percent encoding (like %ZZ or incomplete sequences), you'll see an error message. Make sure the encoded URL is properly formatted.