ENCODING ERROR PLAYGROUND #506

Encoding Error & Mojibake Playground

Explore how decoders handle invalid sequences, byte-level truncation, Base64 padding corruption, and Mojibake character set mismatches.

20 chars | 0 errors detected

Byte-by-Byte Timeline Inspector

[0]S0x53
[1]G0x47
[2]V0x56
[3]s0x73
[4]b0x62
[5]G0x47
[6]80x38
[7]s0x73
[8]I0x49
[9]F0x46
[10]d0x64
[11]v0x76
[12]c0x63
[13]m0x6D
[14]x0x78
[15]k0x6B
[16]I0x49
[17]Q0x51
[18]=0x3D
[19]=0x3D

Valid Encoded Sequence (0 Errors)

The provided string strictly complies with the specification for Base64. No decoding exceptions or illegal character offset violations detected.

Common Encoding Pitfalls & Explanations

Key concepts in string encoding, byte offsets, and decoding errors.

Base64 Padding

Padding '=' Symbol Failures

Base64 processes data in 3-byte (24-bit) blocks. When input length is not a multiple of 3 bytes, trailing '=' characters pad the remaining 6-bit units. Omission or misplaced '=' causes decoder exceptions.

UTF-8 Truncation

Replacement Character ()

UTF-8 uses variable-length encoding (1 to 4 bytes per codepoint). If a multi-byte sequence is truncated mid-stream, standard decoders emit the Unicode replacement character `` (U+FFFD).

Mojibake

Character Set Misinterpretation

Mojibake occurs when text written in one encoding (e.g. UTF-8) is decoded using a different character set (e.g. ISO-8859-1), displaying garbled symbols such as "é" instead of "é".