URL Encode / Decode
Adjust the inputs below. Results update as you type.
How it works
URL encoding replaces unsafe characters with %XX (hex code). Space = %20 or +. Reserved characters (; / ? : @ & = + $ ,) have special meaning in URLs and must be encoded in data. encodeURIComponent() encodes everything except unreserved chars (letters, digits, -, _, ., ~). Encode query parameters individually, not the full URL. Non-ASCII characters (e.g., Chinese, emoji) are UTF-8 encoded first, then percent-encoded.
Input guidance
- Confirm date/time/unit settings before comparing outputs.
- If a task has optional fields, run both with and without them to understand impact.
- Save scenario variants when making practical decisions.
The formula
URL (percent) encoding replaces unsafe characters with %HH, where HH is the byte's hex value. Spaces become %20 (or +), and reserved characters are escaped.
Worked example
The query 'a b&c' encodes to 'a%20b%26c', so the space and ampersand do not break the URL.
More examples to test
- Quick-pass example: run default assumptions for a first estimate.
- Refined example: update one assumption at a time to isolate impact.
How to interpret results
Use outputs as operational estimates and pair them with local constraints, business rules, or provider requirements.
When this can be inaccurate
Utilities can miss local policy details, special-case rules, and environment-specific constraints.
Change history
- July 2026: Quality-reviewed for publication with formula checks and explanatory copy updates.
Site-wide corrections also appear on the corrections log.
Find productivity tools for everyday workflows
General recommendation, not professional advice.
Frequently asked questions
Why encode URLs?+
Some characters have special meaning in URLs (?, &, =, spaces). Encoding them as %HH prevents them from breaking the address or query.
What is the difference between encoding a component and a full URL?+
Component encoding escapes more characters (like / and ?) because they would otherwise be interpreted as structure in a full URL.
Is a space %20 or +?+
In paths, spaces become %20. In query strings, + is also accepted for a space; %20 works everywhere and is safest.
Why are outputs slightly different from another tool?+
Different tools can use different rounding rules, default assumptions, and treatment of edge cases.
How can I improve estimate reliability?+
Use verified inputs from real records and re-run calculations after major assumption changes.