English

URL Encoder & Decoder

Encode text for use in URLs or decode percent-encoded text.

0 characters
0 characters

More tools you might find useful.

Base64 Encoder & Decoder Encode or decode Base64 text locally.
Text to Slug Turn a heading or phrase into a lowercase, hyphen-separated URL slug with sensible Unicode handling.
HTML Entity Encoder & Decoder Encode HTML special characters or decode named and numeric entities into plain text.
JSON ↔ YAML Converter Convert JSON to readable YAML or YAML to formatted JSON locally, with safe parsing and clear errors.
JWT Decoder Decode JWT headers and payloads directly in your browser.
JSON Formatter Format, validate and minify JSON data.
UUID Generator Generate random UUID v4 identifiers instantly.
Unix Timestamp Converter Convert Unix timestamps and readable dates.
CSV ↔ JSON Converter Convert CSV with headers to JSON or flat JSON objects to properly escaped CSV.
Color Converter Convert HEX, RGB and HSL colors with normalized values and a local preview.

Encode and Decode URLs Online

URL encoding, also called percent encoding, converts characters that may have special meaning inside a URL into a safe format.

What does URL encoding do?

Characters such as spaces, ampersands, question marks and Unicode text may need to be encoded when they are used as URL parameters or other URL components.

Example

The text Hello world! becomes Hello%20world! when encoded.

UTF-8 support

Unicode text, including accented characters and emoji, is encoded using the browser's standard UTF-8 URL encoding behavior.

Private browser-based processing

Encoding and decoding happen locally in your browser. Your text does not need to be uploaded to HandyKitz.

Practical example

Encode a parameter value before putting it inside a URL. Encoding a whole address as one component also encodes separators such as slashes and question marks.

The value red & blue becomes red%20%26%20blue. The encoded ampersand stays part of the value instead of separating query parameters.

Frequently asked questions

Should I encode a complete URL as one value?

The tool uses encodeURIComponent, which also encodes URL separators. Encode a parameter value rather than a complete navigable URL unless that URL is itself a parameter.

Why does decoding leave a plus sign unchanged?

decodeURIComponent does not interpret + as a space. In form-encoded input, spaces may use +; handle that convention separately.

Why does %2520 decode to %20 instead of a space?

Decoding performs one pass. The percent sign was encoded twice; decode again only if another encoding layer was intended.