Decode Y29sbGlzaW9ucw== from Base64

Decoded result: collisions

Word Visualization: collisions

Base64 text to decode from

For encoded binaries (like images, documents, etc.) use the file upload form below.

Select output encoding

Process each line as a separate Base64 string

Do not store in history

Live mode

Decode base64 strings in real-time as you type or paste.

Base64 Decoded Result

Add file to Decode

Charset:

Click to upload or drag and drop

Decoding Process: Y29sbGlzaW9ucw== to collisions

About the '=' Padding

The '=' at the end of "Y29sbGlzaW9ucw==" is padding. Base64 encoding requires the input length to be divisible by 4. When it's not, '=' characters are added as padding. These padding characters are represented as '000000' in binary but are not used in the final decoded output.

Step 1: Map Base64 Characters to Binary

Base64 Character	Binary Value	Decimal Value
Y	011000	24
2	110110	54
9	111101	61
s	101100	44
b	011011	27
G	000110	6
l	100101	37
z	110011	51
a	011010	26
W	010110	22
9	111101	61
u	101110	46
c	011100	28
w	110000	48
=	padding (000000)	-
=	padding (000000)	-

Step 2: Group Bits into Bytes

The binary string is grouped into 8-bit chunks (1 byte each):

01100011 01101111 01101100 01101100 01101001 01110011 01101001 01101111 01101110 01110011 0000

Step 3: Convert Binary to ASCII

Binary Value	ASCII Character
01100011	c
01101111	o
01101100	l
01101100	l
01101001	i
01110011	s
01101001	i
01101111	o
01101110	n
01110011	s
0000

When combined, these characters form the decoded string: "collisions"

Word Statistics: collisions

General Statistics

Length: 10 characters
Vowels: 4
Consonants: 6

Letter Frequency

Letter	Frequency
c	1
o	2
l	2
i	2
s	2
n	1

Encode collisions

Related Conversion Tools

Base64 Encode