Decode aHVydGluZw== from Base64

Decoded result: hurting

Word Visualization: hurting

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: aHVydGluZw== to hurting

About the '=' Padding

The '=' at the end of "aHVydGluZw==" 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
a	011010	26
H	000111	7
V	010101	21
y	110010	50
d	011101	29
G	000110	6
l	100101	37
u	101110	46
Z	011001	25
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):

01101000 01110101 01110010 01110100 01101001 01101110 01100111 0000

Step 3: Convert Binary to ASCII

Binary Value	ASCII Character
01101000	h
01110101	u
01110010	r
01110100	t
01101001	i
01101110	n
01100111	g
0000

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

Word Statistics: hurting

General Statistics

Length: 7 characters
Vowels: 2
Consonants: 5

Letter Frequency

Letter	Frequency
h	1
u	1
r	1
t	1
i	1
n	1
g	1

Encode hurting

Related Conversion Tools

Base64 Encode