Skip to main content

URL Encode / Decode

Percent-encode URLs for safe use in query strings, or decode encoded URLs back to plain text.

Input
0 chars | 0 bytes
Encode
Output
0 chars | 0 bytes

Every character that carries special meaning in a URL β€” spaces, ampersands, equals signs, hash marks β€” must be percent-encoded before it can safely travel as part of a query string or path segment. Skip this step and browsers, servers, or intermediary proxies will misparse your URL, silently dropping parameters or returning 400 errors that are frustratingly hard to trace.

This tool is essential when building redirect links, constructing API query strings by hand, debugging OAuth callback URLs, or inspecting encoded parameters pasted from server logs. Paste a raw string to encode it for safe embedding, or paste a mangled URL from a log file and decode it back to readable form in one click.

How to URL Encode and Decode Online

  1. 1

    Paste Your URL or String

    Paste a plain URL or a percent-encoded string into the input panel.

  2. 2

    Choose Encode or Decode

    Toggle between encode and decode. Encoding converts unsafe characters to %XX sequences. Decoding reverses the process.

  3. 3

    Copy the Result

    Copy the encoded or decoded output. All processing runs in the browser β€” no server requests.

How Percent-Encoding Works

RFC 3986 defines which characters are 'unreserved' in a URI β€” letters, digits, hyphens, underscores, tildes, and dots β€” and requires everything else to be encoded as a percent sign followed by two uppercase hex digits representing the byte value. A space becomes `%20`, an ampersand becomes `%26`, and a non-ASCII character like `Γ©` is first UTF-8 encoded to two bytes (`0xC3 0xA9`) and then encoded as `%C3%A9`.

The older `application/x-www-form-urlencoded` scheme (used in HTML form posts) encodes spaces as `+` instead of `%20`, which is why decoding a `+` character requires context β€” in a query string value it is a space, but in a path segment it is a literal plus sign. This tool handles both conventions correctly.

Why Use FileCrank URL Encoder / Decoder?

  • βœ“ Supports RFC 3986 standard encoding and form encoding (+) convention.
  • βœ“ Full URL mode preserves scheme and slashes; component mode encodes everything.
  • βœ“ Handles non-ASCII characters including Unicode and emoji.
  • βœ“ Runs entirely in your browser β€” no data sent to any server.

Features & Specs

Max File Size
Up to 100 MB
Privacy
Files deleted after about an hour
Price
Free, no signup
Processing
100% client-side
Standard
RFC 3986 URL encoding
Your data never leaves your browser β€” all processing is local.No account or signup required.Free with no usage limits.

Frequently Asked Questions

What is the difference between URL encoding and percent encoding?

They are the same thing. 'Percent encoding' is the formal name from RFC 3986. 'URL encoding' is the informal name developers use. Both describe replacing unsafe characters with % followed by two hex digits.

When should I use %20 versus + for spaces?

Use %20 when encoding a URL path segment or query value following RFC 3986. Use + only in application/x-www-form-urlencoded form data. Most APIs expect %20.

Does this tool encode the entire URL or just a component?

By default the tool encodes each character that is unsafe in a URL component. If you paste a full URL with a scheme (https://), the colon and slashes are preserved. Use component mode to encode every reserved character.

Why does my encoded URL contain %2F instead of a slash?

You are encoding a full path segment. Slashes inside a value must be encoded as %2F. If you want slashes preserved, use the standard URL mode rather than the component mode.

URL Encoding vs. HTML Entity Encoding

URL encoding and HTML entity encoding solve different problems. Percent-encoding makes data safe for URI syntax, while HTML entities make characters safe for HTML markup. An ampersand in a URL query string needs `%26`; inside an HTML attribute it needs `&`. Using the wrong encoding in the wrong context is a common source of XSS vulnerabilities and broken links, so choosing the right tool for the right layer matters.

FileCrank URL Encode / Decode converts between plain text and percent-encoded URL strings following RFC 3986, running entirely in your browser.

Advertisement

Ad