Skip to content

URL Encoder and Decoder

Encode text so it's safe to put in a web address, or decode a messy link back into readable text. It all runs in your browser.

What are you encoding?

0 characters · 0 lines
0 characters · 0 lines

How to encode or decode a URL

  1. Choose Encode or Decode.
  2. Paste your text or link into the left box, or press Try an example.
  3. Set the options. When encoding, pick Encode everything for a single query value or Keep URL structure for a whole link, and decide whether spaces should become +. When decoding, switch on Treat + as a space for form-style links.
  4. Copy or download the result. If you decoded a full URL, check the Query parameters table below the boxes.

Features

  • Two encoding modes based on the browser's standard encodeURIComponent and encodeURI functions.
  • Spaces as + option for HTML form and query-string style encoding, and the matching Treat + as a space option for decoding.
  • Full UTF-8 support for any language and emoji.
  • Query parameter table that lists every parameter of a pasted URL with its decoded value.
  • Clear error when a link has a broken or incomplete % sequence.
  • Use result as input to reverse the direction in one tap.
  • Live results with character and line counts, copy and download.

Why use Fileora's URL encoder

Links frequently carry more than they appear to: session IDs, one-time login tokens, email addresses, internal redirect paths. Pasting them into an encoder that runs on someone else's server hands all of that over. Fileora encodes and decodes with the functions built into your browser, so the text never leaves your device and nothing is recorded.

It's free, requires no sign-up, and works as well on a phone as on a desktop, which is handy when you need to read a long link someone sent you in a chat.

Related tools: turn a title into a clean address with the text to slug converter, encode binary data with the Base64 encoder, or tidy a JSON API response with the JSON formatter.

Reserved characters and their encodings

A URL can only contain a limited set of ASCII characters. Some of them have jobs to do, so when they appear inside a value they must be escaped. These are the ones you'll meet most often:

  • Space: not allowed at all, so it becomes %20, or + in form-style query strings.
  • / separates path segments and becomes %2F inside a value.
  • ? starts the query string: %3F.
  • & separates one parameter from the next: %26.
  • = separates a parameter name from its value: %3D.
  • # starts the fragment, the part the browser keeps to itself: %23.
  • % starts every escape, so a literal percent sign is %25.
  • + can mean a space in forms, so a real plus sign is safest as %2B.

If a search term such as "fish & chips" isn't encoded, the & splits it into two parameters and the server only receives "fish ". Encoding the value first avoids that class of bug.

Frequently asked questions

What is the difference between the two encoding modes?

Encode everything uses the browser's encodeURIComponent, which escapes every reserved character including / ? & = and #. Use it for a single value that goes inside a URL, such as a search term. Keep URL structure uses encodeURI, which leaves those characters alone so a complete link still works, and only escapes spaces, non-English letters and other unsafe characters.

Should spaces become %20 or +?

In the path of a URL, a space must be %20. In a query string sent by an HTML form, spaces are traditionally written as +, and many servers expect that. Switch on Spaces as + when you're building form-style query strings; leave it off otherwise. When decoding, turn on Treat + as a space if the link came from a form.

Why do I get an error when decoding?

Every % in encoded text must be followed by two hexadecimal digits, and multi-byte characters need all their bytes. If a link was cut short, for example %E0%A4 instead of the full three-byte sequence, or contains a stray % sign, it can't be decoded, and the tool tells you so rather than showing a half-broken result.

Can it decode Urdu, Hindi or Arabic text in a link?

Yes. Non-English characters are stored in URLs as UTF-8 bytes, each written as %XX. The decoder reassembles those bytes, so a link like ?city=%D9%84%D8%A7%DB%81%D9%88%D8%B1 turns back into readable text. Encoding works the same way in reverse.

How do I see the parameters in a long tracking link?

Choose Decode and paste the whole link, starting with https://. Below the result, the tool lists every query parameter and its decoded value in a table, which makes it easy to spot tracking tags, redirect targets and search terms buried in a long URL.

Is URL encoding a way to hide information?

No. Percent-encoding only makes text safe to transmit in a URL. Anyone can decode it instantly. Don't put passwords or personal data in a link, encoded or not, because URLs are stored in browser history and server logs.

Can't find the tool you need, or something isn't working?

Tell us which tool you'd like next or what went wrong. We read every message, and requests decide what we build next.

Opens your email app. Please don't attach private files.