Developer Format Converters

One hub for the data-format conversions devs bounce between a dozen ad-heavy sites to get. Everything runs in your browser — paste-safe for secrets, configs, and anything you wouldn't upload.

All developer converters

Base64 Decoder Base64 Encoder CSV to JSON Converter JSON to CSV Converter JSON to TOML Converter JSON to XML Converter JSON to YAML Converter JWT Decoder Regex Tester TOML to JSON Converter URL Decoder URL Encoder XML to JSON Converter YAML to JSON Converter

Which format should I use?

JSON is the web's lingua franca — almost every API speaks it, every language parses it natively. YAML is JSON's more readable sibling: whitespace-indented, comment-supporting, the default for Kubernetes, GitHub Actions, Ansible, and most CI/CD configs. TOML is the modern config format the Rust and Python tooling ecosystems picked — Cargo, pyproject, and most CLI dotfiles. CSV is the flat-data interchange format every spreadsheet and BI tool accepts. XML predates JSON but still rules Java/.NET configuration, Android manifests, RSS feeds, and SVG. Beyond converters, this hub also includes the encode/decode utilities every dev hits weekly — base64, URL escapes, JWT inspection, and a regex tester.

Format Best for Comments Types
JSON APIs, data interchange, logs No Strings, numbers, booleans, arrays, objects, null
YAML CI/CD, configs, Kubernetes, Ansible Yes All JSON types + dates, anchors, references
TOML Cargo, pyproject, Hugo, modern CLI dotfiles Yes All JSON types + first-class dates/times
CSV Spreadsheets, BI imports, tabular data No Strings only (typed on export)
XML Legacy configs, RSS, SVG, SOAP Yes Elements, attributes, CDATA, namespaces

Frequently asked questions

Are my files uploaded?

No. Every conversion here runs entirely in your browser — your JSON, YAML, or CSV never leaves your device. That matters for configs containing secrets, API keys, internal schemas, or customer data.

Which library powers each conversion?

JSON↔YAML uses js-yaml (the reference implementation for Node + browser). CSV↔JSON uses PapaParse, the de-facto browser CSV library. XML↔JSON uses fast-xml-parser. All three are battle-tested and maintained.

Does YAML → JSON preserve comments?

No — JSON doesn't support comments. If you need YAML comments preserved, keep the YAML as your source of truth. The JSON output is for programmatic consumption.

What does CSV → JSON do with the header row?

The first row becomes the object keys. Every subsequent row becomes an object in the output array. Numbers and booleans are auto-detected — `"42"` becomes `42`, `"true"` becomes `true`.

Can I convert nested JSON to CSV?

CSV is flat by definition — it can't represent nested objects or arrays of objects directly. For nested JSON, consider using a jq flatten step first, or keep the data as JSON. The converter will refuse non-array JSON and surface a clear error.

Does XML → JSON handle attributes?

Yes. XML attributes are prefixed with `@_` in the JSON output (e.g. `<user id="42">` becomes `{"@_id": 42}`), so you don't lose information when round-tripping.