About PayloadTools

PayloadTools started from a familiar annoyance: needing to format an API response, diff two config files, or decode a JWT, and having to search for whatever "online json formatter" ranked first that week. Most of those sites work, but they come with ad networks fighting for space around the editor, signup walls in front of basic features, and no clear answer to the one question that actually matters when you're pasting in a real payload — where does this data go?

That last question is the one that mattered most. JSON payloads, XML configs, and JWTs are rarely just sample data — they're often API responses with real customer records, tokens, or internal config, copied out of a terminal or log for a five-second check. Pasting that into a site with no stated data policy, just to see it formatted, is a bad trade most developers make anyway, because the alternative — opening a full IDE or writing a throwaway script — is slower.

So PayloadTools was built as one place instead of six: the same interface, the same Monaco editor that powers VS Code, and the same rule for every tool — nothing you paste ever leaves your browser. It stayed a static, focused toolkit rather than growing into a platform, because the tools developers reach for most often — format, validate, compare, convert — don't need to be anything more than that.