URL encoder and decoder

Component and full-URL modes differ

Component mode uses JavaScript encodeURIComponent and decodeURIComponent. It escapes delimiters such as & and / when encoding one value. Full-URL mode uses encodeURI and decodeURI so structural delimiters remain intact; decodeURI also leaves encoded reserved delimiters in encoded form.

For example, component-encoding “fox & owl” produces “fox%20%26%20owl”. Choose full-URL mode for a complete address rather than concatenating separately encoded addresses. Neither mode checks whether the resulting address is valid, reachable or safe to visit.

Decoding is explicit

An optional component-decoding setting interprets + as a space, useful for form-style query values. It is disabled in encoding and full-URL modes. By default, a plus sign stays a plus sign.

Incomplete percent escapes, invalid UTF-8 sequences and malformed Unicode produce an error instead of a partial result. The tool does not open or fetch any address, and encoding is not encryption or HTML sanitization.

Local text processing

The input is processed in this browser and is not sent to our servers or included in tool-use analytics. Use up to 20,000 UTF-16 input units at a time. Copy output keeps your original input intact; if clipboard access is blocked, the output is selected for manual copying.

Questions

• Why is %2F still encoded in full-URL decoding? decodeURI preserves encoded reserved delimiters so decoding does not silently change the URL structure. Use component decoding when you mean to decode a single value fully.
• Does this send a request to the URL? No. It transforms text locally and does not open, fetch or check the address.