Struggling to tell your APIs from your CDNs? Read our comprehensive cloud computing glossary covering the most common terms.
< Back to glossary
Base64 is an encoding scheme that converts binary data into a text format using 64 ASCII characters (A-Z, a-z, 0-9, +, /). It is commonly used to encode data for safe transmission over text-based protocols like email or HTTP, ensuring that binary information remains intact during transport.
Binary-to-Text Conversion: Each group is mapped to one of the 64 characters in the Base64 index table.
Padding: If the binary data length isn’t divisible by 3 bytes (24 bits), padding characters (=) are added at the end of the encoded string to maintain proper alignment.
Decoding Process: The encoded string is converted back into its original binary form by reversing the mapping process.
Data Transmission in Web Applications: Embeds images or files directly into HTML or CSS using data: URIs.
Email Attachments (MIME): Encodes attachments so they can be safely transmitted via email protocols that only support text.
Authentication Tokens (Basic Auth): Encodes username-password pairs in HTTP Basic Authentication headers.
Compatibility Across Systems: Ensures binary data remains intact when transmitted over text-based systems like email or JSON APIs.
Simple encoding and decoding processes make it widely adopted across programming languages.
Increased Data Size: Encoded data is larger than the original binary data due to padding and conversion overhead.
Not Secure by Itself: Base64 is not encryption; it only encodes data without providing security or confidentiality.
Processing Overhead: Encoding and decoding require additional computational resources compared to raw binary transmission.
A web developer embeds a small image directly into an HTML file using Base64 encoding instead of linking an external file. This reduces HTTP requests but slightly increases the file size due to encoding overhead.