Encode URL components without confusing + and %20.
Choose whether you are encoding a URL component or a form value; their space rules differ.
URL value
URL encoding output
textMode: URL componentUTF-8 bytes: 32Encoded valuesummer%20air%20conditioning%20%2B%20tariff
Processed locally — inputs and results stay in this browser tab. Copy and download actions run only when you choose them.
More Signalbench tools
Small tools for stubborn bugs.
Format JSON, inspect JWT claims, explain cron expressions, and compare text locally in your browser.
Format and validate JSON without leaving your browser.
Format, indent, and validate JSON locally in your browser, with a clear error message when the syntax is invalid.
Decode a JWT and read its claims.
Decode a JSON Web Token locally to read its header and payload claims — decoding a JWT is not the same as verifying it.
Understand any cron expression at a glance.
Parse a five-field cron expression and see the minute, hour, day, month, and weekday fields explained in plain language.
Component versus form encoding
URL components use percent escapes. HTML form values traditionally represent spaces with plus signs, so a literal plus must be escaped.
- Decode only the component, not an entire URL.
- Malformed percent escapes are rejected.
- Generated results include a canonical encoding.
Signalbench
Inspect, transform, and debug data without sending it away.