Spread the word about this tool
Ultimate one-off tool to encode Base64. Prepare assets for web easily!
Base64 Encoding is a family of encodings, supposed to safely transmit binary data across machines. Base64 turns any binary stream (bytes from
0xFF) into ASCII stream (characters from
/). Base64 encoded data can be read through any text terminal, by people or machines, transmitted over HTTP etc.
Base64 divides data into 6 bits and converts it into alphanumeric characters (A-Z, a-z, 0-9) and symbols (+, /). Converts every 4 characters, and if the last character is less than 4 characters, fill it with an equal sign (=).
Our Base64 encoder is an ultimate tool for encoding binary data, files and image assets to base64 encoding.
Base64 Encode Use cases
Part of the web development workflow
One of the most popular use-cases for Base64 encoding is an embedding (“inlining”) of JPG/PNG/SVG images into HTML or CSS files. The goal is to make images appear on the webpage without additional HTTP requests to server. Such method is used to deliver logos, icons or small images to browser client and to make loading and the first rendering faster.
Another examples of Base64 encoding and decoding that most of time works behind the scenes:
- E-mail messages sent as a MIME encoded strings.
- SSL certificates for webservers are PEM base64 encoded stream of DER encoded structured binary data.
- The Bitcoin address is a Base52 encoded binary stream of the public key and the checksum.
Base64 is around you. Everywhere when you need to transmit binary data over ASCII (“text”) channels, base* family encodings come to help.
Base64 Encoding: Problem and solution
As shown above, the Base16/32/64 and other base-family encodings is a great good. But using Base64 is not so easy.
Every time you need to convert asset to Base64, you have only few options:
- Call CLI tool manually every time. 😭
- Make Base64 converting a build step in your Webpack / another bundling system. 🦸♂️
- 💁♀️ Use another (free) GUI tools.
Using CLI becomes annoying quickly, because command-line interface is error-prone, requires advanced knowledge and typing commands on the keyboard. Lots of developers prefer powerful GUI tools over CLI tools for almost every development task: code editing, debugging and profiling; building and publishing software or libraries; working with versioning systems, etc.
Making Base64 encoding/decoding automatic in the build process is rarely used, but possible.
In most cases automating of the encoding and decoding is not required or leads to significant overhead during the development.
Existing online tools those easily searched in Google are lacking of modern user experience and, basically, they’re lacking of awesomeness!
The solution is straightforward: the MiroTools Base64 Encoder, suitable for big files, all-way encoding with simple yet powerful GUI, that doesn’t transmit anything over network for much better performance. This is how the website was born.