Toolkit Shelf
Find

URL Encoder / Decoder

Use this URL encoder / decoder to clean campaign links, query values, path segments, QR payloads, redirects, and copied URLs before sharing or debugging.

Live converter

URL encoder / decoder

Output
spring%20launch%20%2F%20QR%20sign%3Fref%3Dmenu%26table%3D12
ModeEncode component

The output is generated in this browser.

Length41 -> 59 characters

Encoding often makes text longer because reserved and non-ASCII characters become percent escapes.

Percent escapes9

Each escape is a percent sign followed by two hexadecimal characters.

Review notes
  • Use component encoding for query values, path segments, fragment values, and other URL parts.
Privacy note

This converter runs in the browser. The text you paste is not uploaded by this tool, but encoded URLs can still reveal whatever values they contain when shared.

Generation method

URL encoding method

Output = input transformed with encodeURIComponent, decodeURIComponent, encodeURI, decodeURI, or form-style plus handling

Use component encoding for individual query values and path segments. Use full URL encoding only when the URL syntax itself should be preserved.

How to use

Steps

  1. Choose whether to encode or decode a URL component, full URL, or form-style query value.
  2. Paste the URL text, query value, path segment, or encoded string into the input box.
  3. Review the output, length change, percent escape count, and warnings.
  4. Copy the output or swap it back into the input to reverse the transformation.

Example

Sample output

Component encodespring launch -> spring%20launch
Reserved charactersa=b&c=d -> a%3Db%26c%3Dd
Form queryhello world -> hello+world

Generator use

Best for

  • Browser-side link, file, format, and web utility tasks that need an output now.
  • Generating reusable artifacts such as QR codes, snippets, exports, or cleaned payloads.

Before relying on it

Check first

  • Use component encoding for individual query values and path segments. Use full URL encoding only when the URL syntax itself should be preserved.
  • Publishing a generated file or code without testing it in the real destination.
  • Encoding private or sensitive data into an output that other people can scan, copy, or inspect.

Details

What to know before using the output

Component modeEncodes reserved separators

Best for individual query values, path segments, and fragments where characters like &, =, ?, and / should not act as URL syntax.

Full URL modePreserves URL syntax

Useful when a mostly complete URL needs non-ASCII or unsafe characters encoded without escaping separators such as ://, ?, and &.

Form query mode+ spaces

Useful for application/x-www-form-urlencoded query-style payloads where spaces are represented as plus signs.

Source notes

References used for this generator

MDN Web DocsDocuments encodeURIComponent and when component encoding is safer than encoding an entire URL.MDN Web DocsDocuments decodeURIComponent behavior and malformed escape handling.MDN Web DocsDocuments URLSearchParams and browser support for query-string work.

Benchmarks

How to read the output

Query value: Component mode.

Use for UTM values, form fields, search terms, and any value that will be placed inside a URL parameter.

Complete link: Full URL mode.

Use when URL separators should remain readable and functional after encoding.

Plus spaces: Form query mode.

Use when working with form-style query payloads that represent spaces as +.

Method and limitations

Methodology and assumptions

Formula, inputs, limitations and review record
Generation method

Output = input transformed with encodeURIComponent, decodeURIComponent, encodeURI, decodeURI, or form-style plus handling

Inputs used

Mode, Input text, URL component, Full URL, Form query value, Encoded text

Limitations

Utility outputs depend on the encoded payload, file format, target app, scanner, printer, browser, and real-world testing before sharing.

Review record

Catalog QA baseline on June 6, 2026. This date marks the catalog-wide automated and editorial QA baseline, not a tool-specific expert review.

Cite this page

Toolkit Shelf. URL Encoder / Decoder. https://toolkitshelf.com/tools/url-encoder-decoder

FAQ

Common questions

Should I encode a full URL or a component?

Use component encoding for a single parameter value, path segment, or fragment. Use full URL encoding only when the URL separators should stay active.

Why did decoding fail?

Decoding can fail when a percent sign is not followed by two hexadecimal characters, or when the text contains malformed encoded Unicode.

Does this upload the URL text?

No. The conversion runs in the browser. Still avoid sharing encoded text that contains secrets because decoding can reveal the original value.