Text or URL Input

          

Encoding Tools / URL Encoding

URL Encoder Decoder for practical developer workflows

Use this URL Encoder Decoder when text, query values, route segments, callback URLs or copied percent-escaped strings need a quick two-way check. Encode mode uses URI component escaping, so spaces, Unicode text and reserved characters become URL-safe percent sequences. Decode mode reverses percent-encoded input and treats plus signs as spaces for common form-style query strings. The page is useful for API debugging, redirect URLs, UTM parameters, OAuth-style examples and broken-link troubleshooting, with line-numbered panes, byte counts, paste, swap and copy actions in the browser.

link

Encode URI components

Convert query values, path segments and copied text with encodeURIComponent so unsafe characters become percent-encoded.

rule_settings

Decode escaped URLs

Read percent-encoded text with decodeURIComponent and convert plus signs to spaces for form-style query values.

content_copy

Inspect and copy output

Use line-numbered input/output panes, byte counts, paste, clear, swap and copy while debugging URL payloads.

How URL percent encoding works

URLs use characters such as ?, &, =, / and # as structure. Percent encoding rewrites characters that should be treated as data, such as spaces, punctuation or Unicode text, into byte-based escape sequences like %20.

This page encodes with encodeURIComponent, which is best for query parameter values, path segments and text that will be inserted into a larger URL. Decode mode uses decodeURIComponent and first converts + to spaces, which helps with common form-encoded query strings.

URL encoding is not encryption. It makes characters safe for URL transport, but anyone can decode the text, and private links or tokens remain exposed if you paste or share them.

Common URL encoder decoder use cases

API debugging: Encode query parameter values before testing a request in a browser, client or script.

Redirect URLs: Encode a nested callback URL before placing it inside another URL's query string.

UTM parameters: Decode copied campaign links to inspect spaces, symbols and Unicode text in parameter values.

OAuth-style examples: Prepare safe sample callback values without using real secrets or production tokens.

Broken-link checks: Decode confusing percent sequences to see what a copied link is trying to contain.

Route segments: Encode names, slugs or labels before inserting them into URL path or hash values.

URL encoding examples

These examples show component-style encoding. Do not use real tokens, customer links or private callback URLs in examples you plan to share.

Query value input:
devbruh tools & docs

Encoded output:
devbruh%20tools%20%26%20docs

Encoded input:
redirect%3D%2Ftools%2Fencoding%2F%3Ftab%3Durl+tools

Decoded output:
redirect=/tools/encoding/?tab=url tools

Syntax, privacy and scope notes

Component-focused encoding: Encoding a full URL will also escape structural characters like :, /, ? and &. That is correct for nesting a URL as data, but not always for preserving a clickable URL.

Malformed escapes can fail: Decode mode expects valid percent sequences. A broken sequence such as %ZZ can produce an error instead of readable output.

Local processing: Encoding, decoding, line numbers, byte counts, swapping and copy actions run in browser JavaScript. Avoid pasting private URLs, tokens or session-bearing links into any web page unless you trust the device and browser session.

Related URL and encoding tools

Encoding Tools - use the hub when you need URL, HTML, JSON string, UTF-8, Base64 and byte encoders.

HTML Encoder Decoder - escape text for HTML display when markup characters are the problem.

JSON String Encoder Decoder - escape quotes, slashes and control characters for JSON string literals.

URL Parser - split a full URL into protocol, host, path, query and hash parts before editing it.

JSON to URL Converter - turn JSON values into URL-style query parameters when data starts as JSON.

YAML to URL Converter - convert YAML data into URL-friendly parameter output for handoff checks.

URL Encoder Decoder FAQ

What does this URL encoder decoder do?

This URL encoder decoder converts text, query values and URI components into percent-encoded output with encodeURIComponent, then decodes percent-encoded text with decodeURIComponent. It includes encode and decode modes, line-numbered editors, paste, clear, swap, byte counts and copy output.

When should I encode a full URL versus a URI component?

Use component encoding for query parameter values, path segments and text that will be inserted into a URL. A full URL has structural characters such as colon, slash, question mark, ampersand, equals sign and hash that may need to stay readable, so parse or handle full URLs carefully before encoding every character.

Why do spaces become %20 or plus signs?

Percent encoding represents a space as %20. Some form-style query strings use plus signs for spaces, so decode mode converts plus signs to spaces before percent-decoding. A literal plus sign should be encoded as %2B when it must remain a plus.

Can it decode query strings?

Yes for percent-encoded query strings and query values. Paste the full string or a single parameter value into decode mode to read escaped characters. For structured URL parts such as protocol, host, path, query and hash, use the URL Parser.

Is URL encoding the same as encryption?

No. URL encoding is reversible escaping for characters that need to travel safely inside URLs. It does not hide, encrypt, sign or protect tokens, private URLs, passwords or customer data.

Is URL encoding processed locally?

Yes. Encoding, decoding, line numbers, byte counts, swapping and copy actions run in browser JavaScript on this static page. Avoid pasting secrets into any web page unless you trust the device and browser session.