WEB & DEVELOPER
URL Encoder & Decoder
Encode or decode a query value, path component, complete URL or form value. Choose the semantics explicitly, inspect the result and keep the whole job in your browser.
URL ENCODING
Encode, decode and inspect URLs
Use component, full-URL or form-value semantics deliberately. Everything runs in this browser.
Ready. Component mode is safest for one query or path value.
Choose the right encoding semantics
Component mode is for one path or query value and escapes separators that would otherwise change URL structure. Full URL mode preserves structural characters such as slashes, colons, question marks and ampersands. Form value mode follows application/x-www-form-urlencoded value semantics, including plus signs for spaces.
Use strict RFC 3986 when an integration requires it
Standard component mode follows the browser’s encodeURIComponent behaviour. Strict mode additionally percent-escapes the small set of printable characters that encodeURIComponent leaves literal but stricter RFC 3986 consumers may expect encoded.
Check query parameters after the change
In full-URL mode, PBT shows decoded query parameters as separate pairs. This makes accidental separators, repeated keys and double encoding easier to spot.
Malformed input fails closed
Invalid or incomplete percent sequences are rejected rather than guessed. PBT does not silently repair a value that could change meaning.
Frequently asked questions
What is the difference between %20 and + for a space?
URI component encoding uses %20. HTML form-value encoding commonly uses + for a space, so PBT exposes it as a separate mode instead of conflating the two.
Can this repair a malformed percent sequence?
No. If a percent sequence is incomplete or invalid, PBT reports the problem instead of inventing a replacement.
Is the value sent to PBT?
No. Encoding, decoding and query inspection happen in your browser.