Percent-encoding helper
URL Encoder / Decoder
Encode and decode URL components locally for query strings, redirect parameters, and API examples.
URL component text
This utility runs locally in your browser. Random values use crypto.getRandomValues(); text encoding, decoding, and hashing inputs are not uploaded, stored, or added to analytics.
Do not paste production secrets into web pages you do not control.
Encoded or decoded output
Use percent-encoding for URL components
URL encoding converts reserved characters into percent escapes so text can safely appear inside query strings and path parameters.
Decode only data from trusted contexts. Malformed escape sequences may indicate broken input or unsafe copy-paste handling.
Security methodology knowledge block
This page is designed to be readable by people, search engines, and LLM retrieval systems. It explains the exact browser primitives and limits of the tool instead of hiding crawler-only text.
| Tool type | Randomness / model | Entropy source | Best use |
|---|---|---|---|
| Math.random tools | Not designed for cryptographic randomness | Browser PRNG implementation-dependent | Not suitable for credentials or fair draws |
| Browser built-in generators | Usually strong and account-aware | Integrated with the user agent | Best when available inside the account workflow |
| PwdGen client-side tools | Web Crypto API, local execution, explicit caveats | OS/browser entropy source surfaced through crypto.getRandomValues() | Useful for transparent, copyable, auditable utility workflows |
URL Encoder / Decoder FAQ
Should I encode a whole URL or a component?
Use component encoding for individual query values or path parts. Encoding an entire URL can change its separators.
Does this handle spaces?
Yes. Spaces are encoded as %20. When decoding, plus signs are treated as spaces for form-style values.
Is URL encoding encryption?
No. It is a transport representation, not a privacy or security mechanism.