Phone Number Extractor
Find and normalise every phone number in a text.
Percent-encode text for safe use in a URL.
The URL Encoder percent-encodes text for use in a URL, with two clearly separated modes — one for a single parameter value and one for a complete URL. Confusing those two is the most common URL encoding mistake there is.
A URL can only contain a limited set of characters. Everything else — spaces, ampersands, question marks, accented letters, emoji — has to be percent-encoded, which replaces each byte with a % and two hex digits.
The crucial part is which characters get encoded, and that depends on where the text is going. Encoding a whole URL must leave the slashes, colons and ampersands intact or the URL stops working. Encoding a single query parameter value must encode them, or an ampersand inside the value will split it into two parameters. Getting these the wrong way round is the most common URL encoding mistake, so this tool offers both as separate, clearly labelled modes.
Component mode encodes the structural characters; full-URL mode leaves them intact so the address still works.
%20 for anywhere, or + for a form-style query string — both conventions supported.
é becomes %C3%A9, two bytes and two escapes, which is what the standard requires.
The tool spots existing percent escapes and warns you before turning %20 into %2520.
Which characters were encoded and which were left alone, so the mode choice is verifiable.
A search term, a parameter value or a complete address.
Component mode for a parameter value; full URL mode to keep the structural characters intact.
Encode as %20, or as + for a form-style query string.
Ready to paste into a URL, a link or an API call.
Component mode encodes everything that is not unreserved, including / : ? & and =, which is right for a parameter value. Full URL mode leaves those intact so the URL keeps working. Using component mode on a whole URL breaks it.
In a path, always %20. In a query string, both work but they come from different standards: + is the older form-encoding convention, %20 is the general percent-encoding rule. %20 is safe everywhere, so it is the default here.
They become UTF-8 bytes first, then each byte is percent-encoded. That is why é becomes %C3%A9 — two bytes, two escapes — rather than a single code.
Because the % of an existing escape is itself encoded, turning %20 into %2520. Double encoding is a common bug, so the tool warns you when the input already contains percent escapes.
What people who use the URL Encoder think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the URL Encoder. It takes half a minute and no account.
Write the first reviewFind and normalise every phone number in a text.
Pull every web address out of a block of text.
Remove repeated lines from a list without losing the order.
Turn plain typing into proper typography — curly quotes, real dashes.
Pull the terms a document is actually about out of it.
Spell out text using Alfa, Bravo, Charlie and the rest.
Convert text into decimal character codes.
Strip letters out and keep the numbers, symbols and structure.