16 tools
Formatters and converters that never see your data
Format, validate and convert the data formats you work in daily. Everything runs in your browser, so an API response full of customer records is safe to paste here.
16
Tools in this category, all free
0 bytes
Uploaded — there is no server to send to
No
Account, watermark or daily limit
- JSON FormatterBeautify, minify and inspect JSON with clear syntax errors.
- JSON ValidatorCheck JSON for syntax errors and see exactly where they are.
- JSON to CSVFlatten a JSON array of objects into CSV rows.
- JSON to XMLConvert JSON structures into equivalent XML markup.
- XML BeautifierFormat, minify and check XML without mangling CDATA or attributes.
- XML to JSONConvert XML documents into readable JSON.
- Regex TesterTest regular expressions live with match highlighting and groups.
- SQL FormatterIndent and align SQL queries across every major dialect.
- YAML ValidatorValidate YAML syntax and preview the parsed result as JSON.
- HTML BeautifierRe-indent minified or messy HTML into readable markup.
- CSS MinifierStrip comments and whitespace to shrink a stylesheet.
- JavaScript FormatterFormat JavaScript and TypeScript with Prettier in your browser.
- URL ParserBreak a URL into its protocol, host, path and query parameters.
- Cron Expression GeneratorBuild and read cron schedules without memorising the syntax.
- Unix Timestamp ConverterConvert between Unix epoch timestamps and human-readable dates.
- HTTP Header ParserParse raw HTTP headers into a readable, annotated table.
About these tools
This is the category where sending data to a server is least defensible and most common. The payload a developer wants to pretty-print is very often a real API response, a production log line, a database dump or a token — the exact things that should not be pasted into a stranger’s web form. Every formatter and converter here parses and re-prints in the page.
The tools parse rather than pattern-match, which is a duller claim than it sounds and matters in practice. A minifier that treats a stylesheet as text will happily corrupt a string containing braces, a `calc()` expression or an at-rule prelude. An XML formatter that treats angle brackets as structural will mangle CDATA and anything inside `xml:space="preserve"`. Converting between formats has real limits too: XML attributes, namespaces, comments and mixed content have no direct JSON equivalent, so a round trip through JSON and back is not guaranteed to return what you started with.
When something will not parse, the tools give you the line and column the parser gave up on rather than a red box saying the input was invalid — which is usually the only part of the answer you actually needed.
Frequently asked questions
Yes, in the specific sense that matters: nothing you paste leaves your browser. The page is served as static files, it has no backend, and its security policy forbids it from connecting to any host. Analytics records that a tool was run, never what was put into it.
Not necessarily. XML can express things JSON cannot — attributes, namespaces, comments, ordering and mixed content — so a conversion in that direction has to make choices, and reversing it will not always reproduce the source exactly. Convert when you need the data in another shape, not as a storage round trip.
Two spaces is the most common convention and what most linters expect; four is easier to read on deeply nested documents. Minifying is for transmission, not for storage you will read later. Key order is preserved either way, because reordering keys would change a document that some consumers treat as ordered.
The rest of the toolbox
Every category works the same way — the file or the text stays on your device.