URL Encoder Decoder

How Does ETTVI’s URL Encoder Decoder Works?

Encode URLs in Bulk

STEP 1: Enter URL(s)

Enter single or multiple URLs in the text box for ASCII encoding 

STEP 2: Run the Tool 

Click on “Encode”

STEP 3: Check Encoded URLs 

ETTVI’s URL Encoder will convert the non-conforming characters into their ASCII codes in each URL and then display the encoded URLs in separate rows.

Decode URLs in Bulk 

STEP 1: Enter URL(s)

Enter single or multiple URLs in the text box for decoding ASCII codes 

STEP 2: Run the Tool 

Click on “Decode”

STEP 3: Check Decoded URLs 

ETTVI’s URL Decoder will convert the ASCII codes in each URL and then display the decoded URLs in separate rows. 

Beginner's Guide to URL Encoding Decoding

URL Encoding, also known as Percent Encoding, is a technique utilized to encode URLs with special characters. In your URL, there may not be allowed characters that need to be replaced with special characters, such as spaces needing to be replaced by%20. For example, if you have the text hello world and want to encode it, spaces need to be replaced by + or %20. As a result, hello world will become hello%20world or hello+world after encoding. You can use ETTVI's URL Encoder Decoder tool to decode an encoded URL that you copied from your web browser's address bar to comprehend the URL better. This is known as URL Decoding or Percent Decoding.

What is the Purpose of URL Decoding?

URL encoding is followed by URL decoding, which is the exact opposite operation. Useful for analysing URL query strings or path parameters.

Using the US-ASCII character set, URLs can only include a restricted number of characters. URL encoding or Percent encoding is used to encode characters that fall outside of this allowed set. You'll find these characters in the below table with the alphabet, digits (0 to 9), punctuation marks, and punctuation symbols (.).

To access the actual numbers, it is necessary to decode URL query strings or path parameters.

What's the Deal with URL Decoding?

The following rules apply when query strings, path parameters, or HTML form parameters are decoded:

• A-Z, a-z and 0 - 9 are all retained in their current form.
• As far as characters like -, _, and ~ are safe characters, they remain unchanged.

This means that any sequence of the type "% xy," where xy is the two-digit hexadecimal equivalent of 8 bits, is considered as one byte. This is followed by the replacement of all substrings that contain more than one of these byte sequences in a sequential manner with the character(s) whose encoding would produce those consecutive bytes.

What is Percent Encoding (URL Encoding)?

URL Encoding is the process of converting URLs that contain reserved, unsafe, or non-ASCII characters into a format that can be read by any web browser or server. The character is initially converted to a byte. Next, two hexadecimal digits preceded by a percent sign (%) are used to represent each byte. This character, the % sign, serves as an "escape”.

Using characters from the US-ASCII character set, URLs are constructed. There are numerals (0-9), letters (A to Z), and some special characters (“-“, ".", "_", and "~") in this set of characters.

URLs cannot contain ASCII control characters (for example, vertical tab, backspace, horizontal tab, line feed), unsafe characters (e.g. space), or characters outside the ASCII charset.

As a last note, URLs contain a number of characters that have unique value. This type of character is referred to as "reserved." There are a number of characters that are considered to be "reserved," including “?, / and #”. These characters must not be included in any URL data, whether in the query string or the path segment.

Why do you Need to Encode your URLs?

You need Url encoding to send data that would be difficult or impossible to send over the Internet.

AJAX or POST requests could require you to encode your URLs, thus you'll need to use Url encoding to do so. Often the URL of these requests is encoded so that someone who doesn't have necessary permissions on your website can't readily change it - this way they'll just see nonsense!

There are several websites out there that can assist you in deciphering URLs, however keep in mind that 'easy' often comes at a price! Double-check what's flowing into and out of those utilities, as well as their source, if you decide to take this path.

What are the most Typical Applications of URL Encoding?

In the end, encoding works even if you don't know why, because as we've seen % u2013 having nonsense in URLs may secure us from malicious people who try to exploit these flaws.

URL encoding examples for use in an online context (examples website, email, and Facebook)

Facebook - You can post a link to your Facebook profile using the format 'facebook.com/username', which will automatically encode the URL for you. This can be done by going to Settings -> Security -> Restrict Access and turning on "Encode URLs from third-party sites."

After that, paste any URLs into the textbox where it asks for Url Encode and then click Update Status or Share Link to save your changes. You can use "percent 25" instead of spaces if you don't want to use them – however, spaces are generally used in URLs!

Email - One of the easiest examples of encoding is email, which is done automatically every time. There's nothing to worry about.

Website - Your website's links should be encoded with Url Encode (). RFC 1738 compliant character codes are used to substitute specified characters or sequences in a given string. Email messages (and other environments) don't guarantee that hyperlinks won't be destroyed by incorrect decoding of text before display, hence URL encoding is required when posting any link in an email message (or other environment). Because of this method, special characters like spaces, ;, =, +, [, ], @, &, *, (, ) will be encoded as HTML entities instead of HTML characters, ensuring that these symbols will appear appropriately when the message is shown.

Encoding Reference for the ASCII Character Set

The following table lists the URL encoded form of each ASCII character.

Decimal	Character	URL Encoding
0	NUL(null character)	%00
1	SOH(start of header)	%01
2	STX(start of text)	%02
3	ETX(end of text)	%03
4	EOT(end of transmission)	%04
5	ENQ(enquiry)	%05
6	ACK(acknowledge)	%06
7	BEL(bell (ring))	%07
8	BS(backspace)	%08
9	HT(horizontal tab)	%09
10	LF(line feed)	%0A
11	VT(vertical tab)	%0B
12	FF(form feed)	%0C
13	CR(carriage return)	%0D
14	SO(shift out)	%0E
15	SI(shift in)	%0F
16	DLE(data link escape)	%10
17	DC1(device control 1)	%11
18	DC2(device control 2)	%12
19	DC3(device control 3)	%13
20	DC4(device control 4)	%14
21	NAK(negative acknowledge)	%15
22	SYN(synchronize)	%16
23	ETB(end transmission block)	%17
24	CAN(cancel)	%18
25	EM(end of medium)	%19
26	SUB(substitute)	%1A
27	ESC(escape)	%1B
28	FS(file separator)	%1C
29	GS(group separator)	%1D
30	RS(record separator)	%1E
31	US(unit separator)	%1F
32	space	%20
33	!	%21
34	"	%22
35	#	%23
36	$	%24
37	%	%25
38	&	%26
39	'	%27
40	(	%28
41	)	%29
42	*	%2A
43	+	%2B
44	,	%2C
45	-	%2D
46	.	%2E
47	/	%2F
48	0	%30
49	1	%31
50	2	%32
51	3	%33
52	4	%34
53	5	%35
54	6	%36
55	7	%37
56	8	%38
57	9	%39
58	:	%3A
59	;	%3B
60	<	%3C
61	=	%3D
62	>	%3E
63	?	%3F
64	@	%40
65	A	%41
66	B	%42
67	C	%43
68	D	%44
69	E	%45
70	F	%46
71	G	%47
72	H	%48
73	I	%49
74	J	%4A
75	K	%4B
76	L	%4C
77	M	%4D
78	N	%4E
79	O	%4F
80	P	%50
81	Q	%51
82	R	%52
83	S	%53
84	T	%54
85	U	%55
86	V	%56
87	W	%57
88	X	%58
89	Y	%59
90	Z	%5A
91	[	%5B
92	\	%5C
93	]	%5D
94	^	%5E
95	_	%5F
96	`	%60
97	a	%61
98	b	%62
99	c	%63
100	d	%64
101	e	%65
102	f	%66
103	g	%67
104	h	%68
105	i	%69
106	j	%6A
107	k	%6B
108	l	%6C
109	m	%6D
110	n	%6E
111	o	%6F
112	p	%70
113	q	%71
114	r	%72
115	s	%73
116	t	%74
117	u	%75
118	v	%76
119	w	%77
120	x	%78
121	y	%79
122	z	%7A
123	{	%7B
124	|	%7C
125	}	%7D
126	~	%7E
127	DEL(delete (rubout))	%7F