Data Converters

Format conversion looks trivial until it silently mangles your data. These posts are about the places it does.

What you will find: why Base64 makes a file roughly a third bigger and why we still use it; what UTF-8 actually does to a character above the ASCII range, and why “just encode it” corrupts a name with an accent in it; the difference between encoding a whole URL and encoding one query parameter, and why getting that backwards breaks the link; why a JSON number is not the same thing as a database integer once it passes 2^53.

There is a deeper piece on JSONPath — the query syntax, not the button — because once you understand the grammar you stop guessing at expressions and start writing them.

Aimed at backend developers, data analysts and QA engineers who move payloads between systems all day and would rather find the encoding bug now than in production.

Pair any of these with the JSON Studio — read the theory, then go test the exact case the post describes.