Converter Tools
Browser-based converters for common data formats: JSON to/from CSV with header detection, XML to/from JSON, YAML to/from JSON, Base64 encoding/decoding, URL encoding/decoding, and HTML entity encoding. Paste your data, pick the output format, and copy the result.
Convert between Base64, JSON, CSV, XML, YAML, and other common formats with no uploads required. These utilities are especially useful for developers migrating data between APIs, preparing spreadsheets, or transforming configuration files on the fly. Every conversion runs entirely in your browser — paste your data, pick the target format, and copy the result.
Showing 10 converter tools
Data almost never arrives in the format you need. These converters handle the common migrations — JSON to CSV for spreadsheets, YAML to JSON for configs, XML to JSON for feeds — with the actual parsing happening on your machine.
Try JSON to CSV first
Turn API output into a spreadsheet — the most common conversion request there is.
- 1
Paste your JSON array
Any array of objects works; column headers are extracted automatically from the keys.
- 2
Check the flattened columns
Nested fields become dot-notated columns like address.city — confirm the mapping looks right.
- 3
Download the CSV
Open it in Excel, Google Sheets, or any spreadsheet app for sorting and filtering.
What Each Tool Does
JSON to CSV
Flatten an array of JSON objects into a CSV spreadsheet. Headers are automatically extracted from object keys. Nested objects are flattened with dot notation (e.g., address.city).
CSV to JSON
Parse a CSV file or pasted text into a JSON array. Each row becomes an object with column headers as keys. Handles quoted fields and commas within values.
XML to JSON
Convert XML documents to JSON objects. Preserves element attributes, nested structures, and CDATA sections.
YAML to JSON
Parse YAML configuration files into JSON. Handles multi-line strings, anchors, and aliases. Useful when migrating between tools that expect different config formats.
Base64 Encoder/Decoder
Convert text to Base64 and back. Handles Unicode characters correctly using UTF-8 encoding before Base64 conversion.
URL Encoder/Decoder
Encode special characters in URLs for query parameters, or decode percent-encoded strings back to readable text.
Real Ways People Use These
Importing API Data into Spreadsheets
You fetched a list of users from a REST API as JSON. Convert it to CSV and open it in Excel or Google Sheets for sorting, filtering, and analysis.
Migrating Configuration Files
Your new framework uses YAML config but your old one used JSON. Convert between formats to keep your settings during migration.
Debugging API Requests
An API returns Base64-encoded data. Decode it to see the actual content. Or encode credentials for a Basic Auth header.
Cleaning Up Pasted Data
Someone sent you a CSV with extra whitespace and weird delimiters. Paste it into the CSV-to-JSON converter to normalize the structure, then convert back to clean CSV.
Pick the right tool for the job
Four common scenarios and the tool that handles each one.
| When you need to… | Use | Why |
|---|---|---|
| Analyze API data in a spreadsheet | JSON to CSV | Flattens nested objects into dot-notated columns automatically. |
| Import a spreadsheet into a script | CSV to JSON | Turns rows into objects with headers as keys, handling quoted fields and commas. |
| Migrate config to a new framework | YAML to JSON | Handles anchors, aliases, and multi-line strings during the format switch. |
| Send data through a URL | URL Encoder/Decoder | Percent-encode query parameters without mangling Unicode or special characters. |
Getting the most out of these tools
Keep the nested-column mapping handy
Flattening turns address.city into a column name — for large exports, keep the JSON original around as the source of truth.
CSV headers must be unique
Duplicate headers confuse every parser; rename columns before converting from CSV to JSON.
Prefer JSON for structure, CSV for humans
CSV is for spreadsheets and mail merges; keep the JSON original for anything programmatic.
How it works
Conversions use the browser's built-in JSON.parse(), DOMParser, and TextDecoder APIs. There are no server round-trips, which means your data stays local but you're limited by your browser's available memory.