Developer Tools

Two encodings, two different jobs Both Base64 and URL encoding replace “unsafe” characters with safe ones. That surface similarity is why they get mixed up — and why people sometimes apply both when one would do, or apply the wrong one entirely. The short version: Base64 makes binary data survive a text-only channel. Percent-encoding makes text survive a URL. What each one actually does Base64 rewrites bytes using a 64-character alphabet (A–Z a–z 0–9 + /, plus = padding). Every 3 bytes become 4 characters, so output grows by about 33%. ...

The number that means nothing at a glance 1735689600 is a perfectly valid date. So is 1735689600000. They are a second apart in meaning and a thousand times apart in magnitude, and telling them apart by eye is the first thing that trips people up. Both are Unix timestamps: the count of time since 1970-01-01T00:00:00Z, known as the epoch. Databases store them, APIs return them, logs are full of them — and humans cannot read them. ...

Why unreadable JSON is a daily problem Every API response, config file and log line is JSON. Minified, it is a single wall of characters; pretty-printed, the same data becomes something you can scan in two seconds. The data is identical — only the whitespace differs — which is why “formatting” is one of the most common developer searches on the web. This guide covers what formatting actually does, how validation works, and the handful of errors responsible for almost every “invalid JSON” message you will see. ...

The broken link problem You build a search URL and it works fine in English, then breaks the moment a user types anything interesting: https://example.com/search?q=书签管理 & page=2 The server sees q=书签管理 and a stray parameter called page. The & that was supposed to be part of the query value has been read as a separator. The same thing happens with #, =, ?, + and spaces. The fix is percent-encoding (URL encoding): replace unsafe characters with % followed by two hexadecimal digits representing the UTF-8 byte. ...

The problem Base64 solves Many systems only transport text. Email was designed for 7-bit ASCII, JSON is defined as text, and HTML attributes hold strings. But the things we actually want to move around — images, PDFs, encryption keys, binary protocol buffers — are bytes that can easily include control characters, quotes, or newlines. If you paste raw binary into a text channel, something will eventually eat a byte: a line ending gets rewritten, a quote terminates a string early, a proxy strips a NUL. Base64 gives you a safe envelope by re-encoding those bytes using only 64 characters that every text system agrees on: ...