Encode or decode one exact URL value with explicit RFC 3986 component, full URL, and form-value rules. Inspect UTF-8 bytes, percent escapes, literal plus signs, malformed escapes, and possible double encoding before copying or downloading the result.
Continue with a related workflow or open the next tool that usually follows this task.
Use this repeatable workflow for encoded JSON fields, webhook metadata, headers, cookies, and logs. It validates the alphabet and padding before decoding, preserves binary bytes for download, and keeps Base64 separate from encryption or signature verification.
OpenRelated toolConvert bases, inspect queries, calculate px/rem, transform escapes, and build commit messages in one local workbench.
OpenRelated toolParse bounded HTTP header blocks locally with default secret masking and protocol diagnostics.
OpenRelated toolConvert one IDN between Unicode and Punycode with strict validation and label review.
OpenKeep an untouched copy of the original value, then choose Encode or Decode.
Choose RFC 3986 Component, Full URL, or Form value according to the receiving system.
Enter the exact text without trimming spaces or changing existing percent escapes.
Run one conversion and review UTF-8 byte, %HH escape, and plus-sign counts.
Read warnings for existing escapes, nested URLs, literal plus signs, or another possible encoding layer.
Copy or download the result, then test it in the actual application and compare the received value with the original.
Encode one redirect_uri, next, returnUrl, state, or callback value without turning its internal ampersands into outer parameters.
Prepare a search term, filter, path segment, or API parameter that contains spaces, Unicode, slashes, plus signs, or reserved punctuation.
Encode a readable complete URL while keeping its scheme, host, path separators, query boundaries, fragment, and IPv6 host brackets visible.
Reproduce how HTML form and URLSearchParams-style values distinguish spaces from literal plus signs.
Decode a suspicious value once, inspect remaining %25-derived escapes, and isolate the exact layer that a proxy, SDK, or application encoded twice.
Component mode intentionally encodes slashes, question marks, ampersands, and equals signs. Use it for one value or for a complete URL nested inside another parameter, not for a URL whose structure must stay active.
A literal plus is data in RFC 3986 component mode but represents a space in form encoding. Choose Form value only when the receiving system uses application/x-www-form-urlencoded rules.
Encoding an existing %20 turns its percent sign into %25. Review the existing-escape warning and confirm that a second transport layer is really required.
Decode one identified value once, compare it with the source, and stop unless a remaining %HH layer is proven. Repeatedly decoding a whole URL can turn protected delimiters into active syntax.
Percent encoding changes representation only. Tokens, email addresses, callback state, and passwords remain readable to logs, browsers, and anyone who receives the link.
RFC 3986 Component encodes a complete redirect target when that entire URL must become one outer query value.
https://client.example.com/a b?x=1&y=2https%3A%2F%2Fclient.example.com%2Fa%20b%3Fx%3D1%26y%3D2Form value decoding converts form plus signs to spaces while preserving encoded literal plus signs as plus signs.
C%2B%2B+URL+%EC%84%9C%EC%9A%B8C++ URL 서울RFC 3986 Component leaves only letters, digits, hyphen, period, underscore, and tilde unescaped. Reserved delimiters such as :, /, ?, #, &, =, and + become uppercase %HH sequences based on UTF-8 bytes.
Full URL mode follows whole-URI behavior: it keeps structural delimiters and IPv6 brackets readable while encoding spaces and non-ASCII text. During decoding, escapes that protect reserved delimiters can remain encoded so URL boundaries do not change.
Form value follows application/x-www-form-urlencoded rules. Spaces serialize as +, a literal + serializes as %2B, and decoding reverses those choices. It is a profile for one form value, not a license to replace plus signs globally.
Every percent sign in decode input must have two hexadecimal digits. Valid %HH triplets must also form valid UTF-8; malformed syntax and invalid byte sequences have separate errors and are never repaired silently.
Input is limited to 1,048,576 Unicode characters and 1,048,576 UTF-8 bytes. The transformer preserves surrounding whitespace, performs exactly one requested pass, and reports actual UTF-8 bytes rather than JavaScript UTF-16 length.
Use RFC 3986 Component for one query value, path segment, opaque identifier, or a whole URL transported as one nested value. Use Full URL when scheme, slashes, query separators, and fragment syntax must remain readable and active.
Only Form value mode treats a raw plus as a space. Component and Full URL decoding preserve a literal plus. An encoded %2B becomes a plus in all relevant decode profiles.
A result such as %2F after one decode may indicate another layer, but it may also be intentional data. The tool warns and stops after one pass so you can identify the exact nested value before decoding again.
No. A malformed % sequence and a well-formed sequence whose bytes are invalid UTF-8 are reported separately. The tool does not silently replace, skip, or repair either form.
No. Percent encoding is a transport representation, not encryption, authentication, or access control. Remove secrets from URLs and use HTTPS plus application-level security.
Normal conversion, preview, copy, and text-file download run locally in the browser. Operational analytics may record the selected profile and aggregate byte counts, but the implementation does not include the entered value in those events.
Maintained and tested by SimpleWebUtilsReviewed
Method: This check paired the exact “Encode a nested search URL as one value” input with URL Encoder and Decoder. We followed “Keep the raw source value”, captured the result after “Choose the receiving convention”, and compared it with the example while treating “Including the outer key in the encoded value” and “Treating raw plus as space without checking” as explicit boundary questions.
Expected result: Only the nested search URL was encoded, yielding the documented %3A, %2F, %3F, %20, and %26 sequences while leaving the outer parameter structure available to its receiver.
Sources and standards
Use these focused guides when you need a practical workflow before opening the tool.
Use this repeatable workflow for encoded JSON fields, webhook metadata, headers, cookies, and logs. It validates the alphabet and padding before decoding, preserves binary bytes for download, and keeps Base64 separate from encryption or signature verification.
Workflow guideUse this workflow when a callback, search link, webhook, or API request changes plus signs, repeated keys, JSON string escapes, or a nested return URL after more than one parser touches it.
Workflow guideUse this workflow when a query string is present but the receiving app reads the wrong value, loses a parameter, or treats encoded text as literal data. The goal is to identify the broken layer before rebuilding the link, not to repeatedly encode the entire URL until it appears to work.
Workflow guideUse this workflow when a login, API request, or permission check fails and you need to inspect token claims before changing auth code.
Workflow guideUse this workflow when a website, form, menu, event page, or support link must move from paper, packaging, a PDF, or a presentation into a phone without relying on a tracking or redirect service.
Workflow guideUse this workflow when data inside one query parameter contains spaces, ampersands, equals signs, Unicode, a plus sign, or another complete URL.
Workflow guideUse this workflow when a callback, webhook, proxy, SDK, or copied link contains `%252F`, `%2520`, `%253A`, or another sign that a percent sign was encoded again.
Workflow guideUse this workflow when an OAuth, SSO, webhook, campaign, or application callback looks correct in a browser but the receiving system reads another path or parameter value.
Continue with another maintained workflow
Convert bases, inspect queries, calculate px/rem, transform escapes, and build commit messages in one local workbench.
Parse bounded HTTP header blocks locally with default secret masking and protocol diagnostics.
Convert one IDN between Unicode and Punycode with strict validation and label review.
Encode exact text or a prepared URL, Wi-Fi, email, phone, SMS, or vCard payload as PNG or SVG.
Parse absolute URLs or resolve references with raw, decoded, normalized, and duplicate-query views.