Free tools for formatting, validating, diffing, and converting structured data formats - JSON, XML, YAML, TOML, HTML, and Markdown. The JSON Formatter prettifies minified JSON, validates syntax, and highlights errors with line numbers. JSON Tree renders any JSON as an interactive collapsible tree. JSON to TypeScript generates type definitions from a JSON sample. JSON Diff compares two JSON objects and highlights structural differences. XML Formatter and YAML Converter handle the configuration and data exchange formats used by SOAP APIs, Kubernetes manifests, GitHub Actions, Docker Compose, and Hugo. The Markdown Editor provides a live preview with GitHub Flavored Markdown support.

When to use Text & Data

1Debugging API responses: paste the JSON response from any API into the JSON Formatter to identify syntax errors and inspect the data structure clearly.
2Writing TypeScript: paste a JSON API response into JSON to TypeScript to automatically generate interface and type definitions - eliminating manual type writing.
3DevOps and infrastructure: use the YAML Converter to switch between YAML and JSON for Kubernetes manifests, GitHub Actions workflows, and Docker Compose files.
4Content creation: write blog posts or documentation in the Markdown Editor with real-time preview, then export as HTML, PDF, or DOCX.
5Code review: use JSON Diff or Text Diff to compare configuration files before and after changes - clearly showing what was added, removed, or modified.

Frequently Asked Questions

Why does JSON require double quotes for keys?+

JSON (JavaScript Object Notation) is a strict subset of JavaScript object notation. The JSON spec mandates double-quoted strings for both keys and values - single quotes are not valid JSON. The JSON Formatter validates this and highlights any key that uses single quotes or is unquoted.

What is the difference between YAML and JSON?+

YAML is a superset of JSON - all valid JSON is valid YAML. YAML allows comments (# comment), uses indentation for hierarchy instead of braces, and supports multi-line strings more naturally. JSON is more universally supported for API data exchange. YAML is preferred for human-edited configuration files.

How do I generate TypeScript types from a JSON API response?+

Copy the JSON response body from your browser DevTools or API client, paste it into the JSON to TypeScript tool, and click Generate. The tool analyses the value types (string, number, boolean, array, nested object) and outputs a set of TypeScript interfaces ready to use in your project.

What is GitHub Flavored Markdown (GFM)?+

GFM extends standard Markdown with tables (| col | col |), task lists (- [ ] item), fenced code blocks with syntax highlighting (triple backtick with language name), strikethrough (~~text~~), and autolinked URLs. The Markdown Editor in this category supports full GFM, matching how GitHub renders README files.

About Text & Data

When to use Text & Data

1Debugging API responses: paste the JSON response from any API into the JSON Formatter to identify syntax errors and inspect the data structure clearly.

2Writing TypeScript: paste a JSON API response into JSON to TypeScript to automatically generate interface and type definitions - eliminating manual type writing.

3DevOps and infrastructure: use the YAML Converter to switch between YAML and JSON for Kubernetes manifests, GitHub Actions workflows, and Docker Compose files.

4Content creation: write blog posts or documentation in the Markdown Editor with real-time preview, then export as HTML, PDF, or DOCX.

5Code review: use JSON Diff or Text Diff to compare configuration files before and after changes - clearly showing what was added, removed, or modified.

Frequently Asked Questions

Why does JSON require double quotes for keys?+

What is the difference between YAML and JSON?+

How do I generate TypeScript types from a JSON API response?+

What is GitHub Flavored Markdown (GFM)?+