Utility Tools
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
spring%20launch%20%2F%20QR%20sign%3Fref%3Dmenu%26table%3D12
The output is generated in this browser.
Encoding often makes text longer because reserved and non-ASCII characters become percent escapes.
Each escape is a percent sign followed by two hexadecimal characters.
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.
Quick answer
URL Encoder / Decoder generates encoded or decoded URL text from mode, input text, URL component, full URL, form query value and encoded text. The visible generation method is Output = input transformed with encodeURIComponent, decodeURIComponent, encodeURI, decodeURI, or form-style plus handling.
Generation method
Output = input transformed with encodeURIComponent, decodeURIComponent, encodeURI, decodeURI, or form-style plus handlingUse 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
Example
Generator use
Before relying on it
Details
These notes make the assumptions explicit, especially where the same search query can mean slightly different things.
Best for individual query values, path segments, and fragments where characters like &, =, ?, and / should not act as URL syntax.
Useful when a mostly complete URL needs non-ASCII or unsafe characters encoded without escaping separators such as ://, ?, and &.
Useful for application/x-www-form-urlencoded query-style payloads where spaces are represented as plus signs.
Source notes
Benchmarks
This generator is a drafting aid, not a fixed rule. Use the output to compare options and document your assumptions. Benchmark ranges are broad planning heuristics unless this page names a specific source for the range.
Use for UTM values, form fields, search terms, and any value that will be placed inside a URL parameter.
Use when URL separators should remain readable and functional after encoding.
Use when working with form-style query payloads that represent spaces as +.
Method and limitations
The generation method, inputs, example, and limitations are shown so the draft output is checkable, not treated as final copy.
Output = input transformed with encodeURIComponent, decodeURIComponent, encodeURI, decodeURI, or form-style plus handling
Mode, Input text, URL component, Full URL, Form query value, Encoded text
Utility outputs depend on the encoded payload, file format, target app, scanner, printer, browser, and real-world testing before sharing.
June 6, 2026
Toolkit Shelf. URL Encoder / Decoder. Last reviewed June 6, 2026. https://toolkitshelf.com/tools/url-encoder-decoder
FAQ
Use component encoding for a single parameter value, path segment, or fragment. Use full URL encoding only when the URL separators should stay active.
Decoding can fail when a percent sign is not followed by two hexadecimal characters, or when the text contains malformed encoded Unicode.
No. The conversion runs in the browser. Still avoid sharing encoded text that contains secrets because decoding can reveal the original value.
Use the page notes for each tool. Browser-side utilities can generate outputs locally, but the final file or code may still reveal whatever you encode or share.
Scanners, printers, file viewers, apps, and platform previews can behave differently, so test the exact downloaded output before using it publicly.
Different tools may use different rounding, assumptions, default rates, methods, formulas, or input timing. Compare the visible method and inputs before relying on the output.