Everyday Developer Utilities Explained: Encoding, Number Bases, and Timestamps

A handful of small utilities show up in nearly every developer's toolbox, precisely because computers and humans don't naturally speak the same "language" for numbers, text, or time.

Base64: encoding, not encryption

Base64 converts arbitrary binary data into a text-safe format using only 64 printable characters (A-Z, a-z, 0-9, +, /). It's used to safely embed binary data (like images) inside text formats (like JSON or email), not to hide information — Base64 is trivially reversible by anyone, with no key required. "Hello, world!" encodes to "SGVsbG8sIHdvcmxkIQ==", and decoding it takes exactly the same amount of effort as encoding it, which is the opposite of what encryption is supposed to do.

Number bases: same value, different representation

The number 255 in decimal (base 10) is FF in hexadecimal (base 16) and 11111111 in binary (base 2) — all three represent the exact same quantity, just grouped differently. Hexadecimal is popular in programming because each hex digit maps cleanly to exactly 4 binary bits, making it a compact way to write out binary values (a full byte, 8 bits, is always exactly 2 hex digits). This is why you'll see colors written as hex codes like #FF0000 — three bytes (red, green, blue), each represented in exactly 2 hex characters.

Unix timestamps: counting seconds since a fixed moment

A Unix timestamp is simply the number of seconds elapsed since midnight UTC on January 1, 1970 — an arbitrary but universally agreed "epoch." The timestamp 1735689600 corresponds to January 1, 2026 UTC. Storing dates as a single incrementing number (rather than a formatted string) makes date arithmetic, sorting, and comparison trivially fast for computers, at the cost of not being human-readable without a conversion step.

URL encoding: making text safe for a URL

URLs can't contain literal spaces or certain punctuation, so those characters get percent-encoded — a space becomes %20, an ampersand becomes %26, and so on. "hello world & more" becomes "hello%20world%20%26%20more" when encoded, ensuring the string survives being embedded in a URL without being misinterpreted as a separator between parameters.

Aspect ratios and CSS units

Outside of encoding, developers constantly convert between pixel-based CSS units (px) and relative units (rem, em) for responsive design, and calculate proportional image dimensions to avoid distortion when resizing — both are simple ratio calculations once you know the reference value (root font size, or original image dimensions).

• The Base64 encoder/decoder and URL encoder/decoder handle the two encoding schemes above
• The number base converter converts between binary, octal, decimal, and hex instantly
• The Unix timestamp converter, CSS unit converter, and aspect ratio calculator round out the everyday developer utility set