Skip to main content
FileForge

URL Encoder / Decoder

Percent-encode text for URLs, or decode %20-style strings back into readable text. Choose component encoding (strict) or full-URL encoding.

Runs in your browser — files never leave your device

Free · No sign-upOutputs Plain text, URL
Loading tool…

How to use URL Encode/Decode

  1. Paste the text or URL.

  2. Pick Encode component, Encode full URL, or Decode.

  3. Click Convert.

  4. Copy the result.

About this tool

URLs only allow a limited character set; everything else must be percent-encoded. The important distinction this tool makes explicit: component encoding (encodeURIComponent) escapes characters like /, ? and & — correct for a single query-string value — while full-URL encoding (encodeURI) leaves URL structure intact — correct when encoding a complete address. Using the wrong one is the classic cause of broken links and double-encoded %2520 artifacts. Decoding reverses either form.

This distinction trips up even experienced developers — encoding a whole URL with component-encoding mangles the `://` and `?` that make it a working link, while encoding a query parameter with full-URL encoding fails to escape characters like `&` that would otherwise break the parameter boundary.

Common ways people use this

  • Encoding a search term or query parameter safely before appending it to a URL
  • Decoding a %20-style URL to read what it actually contains
  • Diagnosing a broken link caused by double-encoding or the wrong encoding mode

Tips for better results

  • If you're encoding just one value that will be placed into a query string (like a search term), use component encoding — it's the right choice in the vast majority of cases.
  • If a decoded URL still shows % symbols, it's likely been encoded twice — try decoding it a second time.

Frequently asked questions

Component encoding vs full-URL encoding — which do I need?
Encoding a value that goes inside a query string (like a search term): component. Encoding a complete URL while keeping :// and ? working: full URL. When in doubt for a single parameter value, use component.
Why does my decoded text show %2520?
That's double encoding — a %20 was encoded again, turning % into %25. Decode twice to recover the original, and fix the pipeline that encodes twice.
Are + signs spaces?
Only in the historical form-encoding of query strings. Standard percent-encoding uses %20 for a space; this tool follows the standard and also decodes + as a space in decode mode when it appears in query-style input.
Will encoding change letters and numbers?
No. Letters, digits and a small set of safe characters (like - _ . ~) are left unchanged; only characters with special meaning in URLs are percent-encoded.
Can I decode a URL that contains both encoded and plain characters?
Yes, decoding only affects percent-encoded sequences and leaves already-plain characters untouched.

Related tools

Other tools people commonly use alongside this one.

Base64 Text

Convert text to Base64 and back. Unlike naive implementations, this handles UTF-8 correctly, so emoji and non-Latin text round-trip safely.

Developer

JSON Formatter

Paste minified or messy JSON and get a cleanly indented, readable version. Invalid JSON produces an error with the line and position of the problem.

Developer

QR Code Generator

Create a QR code from any text or URL and download it as PNG or scalable SVG. No watermark, no expiry — the code is generated in your browser.

Developer