When to encode data and which encoding to use
Encoding is about safe transport, not security. Use Base64 Encode when binary data has to travel through a text-only channel such as a JSON field, a data URI or an email attachment header, and Base64 Decode to read it back. It inflates size by about a third.
For URLs, URL Encode percent-escapes characters that would otherwise break a query string — spaces, ampersands, slashes in parameter values. HTML Encode serves a different purpose entirely, escaping angle brackets and quotes so user content renders as text rather than executing as markup.
How to convert between number bases and data sizes
Base conversion comes up in permissions, colour codes, bitmasks and low-level debugging. The Decimal to Binary Calculator and Binary to Decimal Calculator handle base 2, while Decimal to Hex Calculator and Hex to Decimal Calculator cover base 16, which is compact enough to read a byte at a glance.
Data size units carry a long-standing ambiguity: storage vendors use 1,000 while operating systems often use 1,024, which is why a 1 TB drive shows as roughly 931 GB. The Gigabytes to Megabytes Calculator and bits-to-bytes converter make the convention explicit.
Everyday utilities worth bookmarking
Some tools earn their place by being available in one click. The JSON Formatter pretty-prints and validates a payload, which is the fastest way to find the trailing comma or unquoted key that an API is rejecting. The UUID Generator produces RFC 4122 version 4 identifiers when you need a unique key without a database round trip.
For quick assets and checks, the QR Code Generator turns any URL or text into a scannable code, and the Password Entropy Calculator estimates strength in bits — a far better measure than the colour of a strength meter.
Frequently asked questions
- Is Base64 encryption?
- No — Base64 is an encoding, fully reversible by anyone, with no key involved. It exists to represent binary data in text-safe characters, not to hide anything.
- What is the difference between URL encoding and HTML encoding?
- URL encoding replaces unsafe characters with percent-hex sequences so a string survives being placed in a URL; HTML encoding replaces characters like angle brackets and ampersands with entities so they display as text instead of being parsed as markup. They solve different problems and are not interchangeable.
- Why is my 1 TB drive showing as 931 GB?
- Manufacturers define 1 TB as 1,000,000,000,000 bytes while Windows reports in binary units of 1,024, giving about 931 GiB for the same drive. Nothing is missing — it is a labelling convention difference.
- Are UUIDs guaranteed to be unique?
- Version 4 UUIDs are random 122-bit values, so collisions are theoretically possible but practically negligible — you would need to generate billions per second for decades to have a meaningful chance. They are safe as distributed identifiers.
- What is password entropy and how much is enough?
- Entropy measures unpredictability in bits, where each extra bit doubles the guessing effort required. Roughly 60 bits resists most offline attacks and 80+ is comfortable for high-value accounts.