Converters & Encoders
Convert and encode between formats and units.
About Converters & Encoders
Converting between formats is the plumbing of most technical work, and it goes wrong in quiet ways — a Base64 string that loses non-English characters, a CSV whose quoted commas split into extra columns, a timestamp read in the wrong time zone. These converters handle the awkward cases rather than the demo case: full Unicode, custom delimiters, non-linear conversions like temperature. Paste in one side and the other updates as you type, both directions. Your input stays in the browser, so pasting a config file or an API response into one of these does not put it on someone else's server.
Time is where most conversion bugs actually live. A Unix timestamp is a count of seconds with no time zone attached, so the same number is a different wall-clock reading in every city — which is why the timestamp and time zone converters are separate tools that answer different questions. If you are debugging a log, start with the timestamp converter; if you are scheduling something across offices, start with the time zone one, because it accounts for daylight saving having already moved on one side and not the other.
The encoders each have a job they are not for. Base64 makes binary safe to paste into text — it is not encryption and anyone can reverse it. Hashing runs one way and cannot be undone, which is what makes it useful for checking that a file arrived intact. URL encoding exists so that characters with a meaning in a web address survive being part of one. Reaching for the wrong one of those three is the single most common mistake in this category, and the fix is to ask whether you need it read back, checked, or transported.