One query value
Ada & Co in URL component mode
Produces Ada%20%26%20Co, so the ampersand cannot start a second query parameter.
🔗URL Encoder/DecoderReady
Choose the URL context before transforming text
A complete URL, one query value, and a form body use different escaping rules. This workbench runs entirely in this browser and never opens or sends the text you paste.
URL component: Escapes &, =, ?, / and other delimiters so one value cannot change a surrounding URL.
0 / 250,000 characters
URL inspector
Break down an absolute URL or an explicit relative reference. Nothing is opened or fetched.
Capability checkedVerified September 9, 2026
What works
- Use browser-standard encodeURIComponent/decodeURIComponent semantics for one URL component
- Use encodeURI/decodeURI semantics for a complete URI while preserving structural delimiters
- Use application/x-www-form-urlencoded behavior where spaces become + on encode and + becomes a space on decode
Important limits
- URI component, whole-URI, and form/query modes are intentionally different; choosing the wrong context can change a URL's meaning
- The normalized inspector display removes URL credentials, but the original pasted text remains in the browser input until you clear it
What the URL Encoder/Decoder does—and does not do
Exact supported inputs, outputs, limits, and primary sources for the current implementation.
Accepted input
- Up to 250,000 characters of pasted Unicode text for local encoding or decoding
- A whole URI, one URI component, or an application/x-www-form-urlencoded value selected explicitly
- An absolute URL with a scheme or an explicit relative reference beginning with /, ?, #, ./, or ../ for inspection
- Up to 50 exact custom query or fragment parameter names to mask in a share-safe copy
Produced output
- A copyable percent-encoded or decoded value using the selected context
- Actionable errors for malformed percent escapes, invalid UTF-8 decoding, unpaired UTF-16 surrogates, or size limits
- A credential-redacted URL breakdown with normalized URL, protocol, origin, host, path, raw query, fragment, and decoded query parameters
- A deliberately altered share-safe copy that removes URL credentials and masks common OAuth, API, session, and signing parameter values
Operational limits
- Encoding, decoding, and inspection are limited to 250,000 characters per input
- The inspector does not fetch a URL, test whether it exists, resolve DNS, follow redirects, or assess its safety
- Relative references are parsed against a fixed non-routable placeholder only to reveal their components; no application base URL is inferred
- The share-safe output is not a request-ready URL and cannot guarantee detection of every protocol-specific secret
Known limitations
- URI component, whole-URI, and form/query modes are intentionally different; choosing the wrong context can change a URL's meaning
- The normalized inspector display removes URL credentials, but the original pasted text remains in the browser input until you clear it
- A share-safe copy uses parameter names rather than guessing from values; add protocol-specific names and rotate any secret that was already exposed
- URL parsing is not URL validation for security policy; callers must still allow-list schemes, hosts, paths, and redirects for their own application
Standards and primary sources
Capability claims last reviewed September 9, 2026. Review dates describe the implementation audit, not content freshness by itself.
Use the URL Encoder/Decoder with the right expectations
Percent encoding is context-sensitive. This workbench separates one URL component, a complete URI, and application/x-www-form-urlencoded data so delimiters and spaces behave predictably. Its local inspector reveals raw and decoded query details without opening the URL, and can make a deliberately altered copy that removes credentials and masks common OAuth, API, session, and signing parameter values before a link is discussed.
When it is the right tool
- Encoding one query parameter without letting & or = change its meaning
- Decoding a pasted URL while preserving whole-URI delimiters
- Checking whether a query uses + as a form-encoded space
- Making a discussion-safe copy of a link with visible credentials or token-shaped parameter names
- Inspecting a URL's normalized host, path, raw query, and fragment without a network request
A deliberate choice
Tooleras keeps this page specific to the job above instead of claiming support for adjacent formats, platforms, or edge cases it cannot verify. Open the capability guide for the exact inputs, outputs, limits, and sources.
Checked examples
Form/query value
Ada Lovelace + Co in Form / query mode
Produces Ada+Lovelace+%2B+Co: spaces use + while the literal plus is preserved as %2B.
Need a different tool?
Browse the full catalogue — all free, with data handling documented per tool.