JSON Interop: YAML, CSV, XML, JWT, Schema

JSON rarely lives alone. Convert between JSON and YAML/CSV/XML, decode JWTs, generate types, and validate against JSON Schema — every step staying in the browser.

When you land here

You have JSON on one side and YAML, CSV, XML, JWT, or JSON Schema on the other, and you need to convert or validate across that boundary. Each tool in this section handles one boundary cleanly, in your browser, without uploading the payload.

YAML to JSON / format YAMLJSON ↔ CSV converterJSON ↔ XML converterDecode a JWT (header + claims)Base64 encode/decode (often inside JWTs)URL decode (often around JSON query parameters)Generate TypeScript interfaces from JSON

Conversion guides

Conversions are mostly lossless but have edge cases. Each guide covers the exact rules: how nested objects become CSV cells, how XML attributes survive a round-trip, how YAML anchors don't cleanly map.

Convert YAML to JSON (and avoid indentation errors)Convert JSON to CSVConvert JSON to XMLDecode Base64 strings and JWT payloadsURL-encode and decode query parametersValidate JSON before API requests

The relevant blog walkthroughs

Format-by-format walkthroughs for the most common interop tasks, plus a comparison of JSON Patch vs JSON Merge Patch for partial updates.

JSON vs YAML — when to use whichYAML formatter walkthroughHow to convert JSON to CSVConvert CSV and XML to JSONJSON to XMLXML to JSONHow to decode a JWTWhat is JSON Schema?JSON Patch vs JSON Merge Patch (RFC 6902 vs 7396)

The standards behind each boundary

Each interop boundary is defined by an RFC or working group spec. The list below is the one-line summary plus the source.

YAML 1.2 — JSON compatibilityYAML 1.2.2 publishedYAML spec on GitHub (active)RFC 7519 — JSON Web Token (JWT)RFC 7515 / 7516 — JWS and JWERFC 6901 / 6902 — JSON Pointer and JSON PatchRFC 7396 — JSON Merge PatchJSON Schema 2020-12IETF JSON Schema Draft 2026RFC 8785 — JSON canonicalizationRFC 4648 — Base64 standard

Recommended path

YAML config to JSON for an API client, end to end.

  • 1. Tool: /yaml — paste the YAML, click To JSON.
  • 2. Guide: /guides/convert-yaml-to-json — the rules for the conversion.
  • 3. Blog: /blog/json-vs-yaml — when to keep YAML and when to switch.
  • 4. Reference: /news/yaml-1-2-json-compatibility — why the conversion is possible.
Open JSON FixCompare JSON changes

JSON repair guides

Topic hubs

  1. JSON Parse Errors: Read the Message, Jump to the Fix
  2. Fix Invalid JSON: From 'What's Wrong' to a Clean File
  3. JSON Formatter, Validator, Viewer: Pick the Right Tool
  4. Repair LLM JSON Output: Handling Almost-JSON from AI
  5. Privacy: JSON Tools That Don't Leave Your Browser

Specific guides

  1. How to Decode Base64 Strings (and JWT Payloads)
  2. URL Encoding: Percent-Encode Query Parameters and Paths
  3. Convert YAML to JSON (and Avoid Indentation Errors)
  4. Convert JSON to CSV: Flatten an Array of Objects
  5. Convert JSON to XML: Root Elements, Attributes, and Arrays
  6. Escape JSON as a String Literal (and Decode Double-Encoded JSON)
  7. Fix Trailing Comma in JSON
  8. Fix Single Quotes in JSON
  9. Fix Unquoted Keys in JSON
  10. Repair LLM JSON Output
  11. Fix JSON Parse Error: Expected Property Name
  12. JSON vs JS Object Literal: The Key Differences
  13. Validate JSON Before API Requests
  14. JSON Formatter vs JSON Repair
  15. Fix JSON Unexpected Token Errors
  16. JSON to JavaScript Object Converter