Encoding schemes and when each fits
API debugging often stalls on mismatched encoding: a token pasted from a log may be Base64 while your client expects percent-encoded query values. This page lets you flip directions on the same snippet so you can confirm what a gateway or SDK actually produced.
Base64 round-trips
Base64 expands data by roughly one-third and is not encryption. Use it to inspect JWT middle segments, embed small blobs in JSON, or verify that a decoded string matches the original UTF-8 text. Invalid padding or non-alphabet characters surface as decode errors rather than silent corruption.
URL and hex transforms
URL encoding replaces spaces and reserved symbols with %XX sequences—essential before dropping arbitrary strings into GET parameters. Hex mode is useful when comparing binary fingerprints, color values, or firmware dumps where a human-readable alphabet is not the goal.