daytics™
daytics is free. Help keep it that way.
Built by one person. No ads, no paywalls. If it saved you time, a coffee goes a long way.
How to Use This Tool
Percent-encoding (also called URL encoding) replaces characters that have a special meaning in URLs — spaces, &, ?, #, / in certain positions — with their hexadecimal byte representation preceded by a percent sign. A space becomes %20 and an ampersand becomes %26. This tool offers two encoding modes: "Component" encodes aggressively (safe for ?query=value parameters), and "Full URL" preserves the URL structure (slashes, scheme, colons).
How to Use
- Pick Encode or Decode at the top.
- If encoding, choose Component for query-string values, or Full URL for whole URLs.
- Paste or type your input and click Convert.
- Click Copy to use the result elsewhere.
Frequently Asked Questions
What is percent-encoding?
A way to represent characters in a URL that otherwise have a special meaning, or aren't safe in a URL at all. Each unsafe byte is written as a "%" followed by its two hex digits.
When should I use encodeURI vs encodeURIComponent?
Use encodeURI when you have a full URL and want to keep delimiters like "/" and "?" intact. Use encodeURIComponent for a single value — e.g. a query-string parameter — where every special character should be escaped.
Does URL encoding encrypt the URL?
No. It is a transformation, not encryption. Anyone can decode an encoded URL by reversing the percent-encoding.
Why do spaces sometimes become %20 and sometimes +?
%20 is the correct percent-encoding for a space in URL paths. The "+" is a legacy substitution used specifically in application/x-www-form-urlencoded form submissions — it only applies to query strings in form data, not to the rest of the URL.