Developer Tools

URL Encoder / Decoder

Encode full URLs, encode query parameters, and decode percent-encoded URL strings locally in your browser.

Runs locally in your browser

URL Encoder / Decoder

Encode full URLs or individual query parameters, decode percent-encoded strings, and copy the result.

Your input stays on this device.

What this tool does

The URL Encoder / Decoder helps you prepare URLs, query strings, and API parameters for safe transport. It supports both full URL encoding and component encoding because those two operations are useful in different situations.

Use Encode URL when you already have a full URL and want to preserve URL separators such as :, /, ?, and &. Use Encode component when you are encoding one parameter value, one path segment, or a piece of text that will be inserted into a URL.

Common use cases

  • Encode a query parameter before adding it to an API request.
  • Decode a callback URL copied from logs.
  • Check whether a redirect URL has been encoded once or twice.
  • Clean up percent-encoded strings before debugging backend routing behavior.

Example

The string hello world becomes hello%20world when encoded as a URL component. A full URL such as https://example.com/search?q=hello world preserves its structure while encoding unsafe spaces.

Privacy note

This tool runs entirely in the browser. Do not paste secrets, tokens, or private customer data into web tools unless you control the environment and understand the risk.

FAQ

URL Encoder / Decoder questions

What is URL encoding?

URL encoding converts characters that are not safe in a URL into percent-encoded sequences, such as turning a space into %20.

When should I use encode component?

Use component encoding for query parameter values, path segments, or small parts of a URL. It encodes more reserved characters than full URL encoding.

Does this tool send URLs to a server?

No. Encoding and decoding run in your browser with built-in JavaScript APIs, so the input is not submitted to this site.

Why does decoding fail for some strings?

Decoding fails when a string contains malformed percent-encoded sequences, such as a percent sign that is not followed by two hexadecimal characters.