Convert between JSON, CSV, XML, YAML, TSV, SQL, and Excel — flatten, normalise, and prepare data for any system.
Byte array to string converter for decimal UTF-8 bytes. Paste comma-separated or whitespace-separated values and review the decoded text.
CSV to JSON converter for files and pasted data. Choose the delimiter, set header handling and type parsing, then copy or download the JSON.
JSON to CSV converter for spreadsheet exports. Convert an array of objects into rows and columns, then review and save the CSV output.
CSV to XML converter for spreadsheet data. Use column headers as element names, review the record structure, and copy or download the XML.
Convert XML into JSON, then review how elements, attributes, and text are represented.
Inspect hexadecimal values for ASCII text and copy the output.
Inspect text represented by hexadecimal values and copy the result.
Convert JSON into XML and review the element names and structure.
JSON formatter and validator for readable output and syntax checks. Choose indentation, format or minify the input, and review any parser error.
YAML to JSON converter for configuration files and examples. Paste YAML or select a file, review the formatted JSON, and copy or download the output.
Turn tab-separated rows into JSON and check the resulting keys and values.
JSON to YAML converter for configuration, API samples, and test data. Paste JSON or select a file, review the YAML, and copy or download the result.
Convert a JSON array of objects into tab-separated rows.
JSON to SQL converter for generating INSERT statements from an array of objects. Set the table name, review the SQL, and copy or download it.
Convert XML to YAML, then check the structure and value types.
Convert XML records to CSV and review the columns before importing.
Convert YAML to XML and check the document against your destination format.
Data lives in many formats — JSON for APIs, CSV for spreadsheets, XML for legacy systems, YAML for config files, SQL for databases, Excel for business reports. Tooloogle's data converters move structured data between these formats losslessly so you don't waste hours writing one-off scripts to bridge two systems.
Flatten nested JSON into CSV columns using dot-notation paths (user.address.city → user.address.city). Re-inflate CSV back to nested JSON for API consumption. Handles arrays via index notation or comma-separated cell values. Configurable delimiter (comma, tab, pipe, semicolon), quoting, and header row.
Convert JSON documents to well-formed XML and back, with options for attribute vs element representation, namespace handling, and root element naming. Useful for integrating with SOAP services, RSS feeds, and legacy enterprise systems.
Switch between JSON and YAML for configuration files, CI/CD pipelines, and Kubernetes manifests. Preserves data types correctly (numbers, booleans, nulls) and handles multi-line strings via YAML literal/folded scalars.
Convert CSV files to Excel workbooks with proper data typing (numbers stay numbers, dates parse as dates, leading zeros preserve where intended). Convert Excel back to CSV for tools that don't read XLSX.
Generate ready-to-run SQL INSERT statements from a CSV file, with configurable target table name, column types, and dialect (MySQL, PostgreSQL, SQLite, SQL Server). Reverse: parse INSERT statements back to CSV for data migration.
Switch between any delimiter style. Useful when target systems insist on tabs (Google Sheets imports), pipes (legacy mainframe exports), or custom characters.
Convert JSON to TOML and back for use in Cargo, Hugo, and other modern config-file consumers.
Split a JSON array into newline-delimited JSON for streaming processing, log ingestion, and big-data pipelines. Combine NDJSON files back into a single array for easier client-side handling.
Split a multi-sheet workbook into separate single-sheet files. Merge multiple workbooks into a single file with one sheet per source. Reorder, rename, and remove sheets without opening Excel.
Writing a custom script for every conversion is wasteful. Excel can convert simple cases but chokes on nested JSON. Online converters fill the gap: they handle the long tail of edge cases (escaped quotes inside CSV cells, mixed-type arrays in JSON, character encoding mismatches) so you don't have to debug them yourself.
Where mathematically possible, our converters preserve every byte: types, ordering, comments (in formats that allow them), and whitespace conventions. We document where lossy conversion is unavoidable (e.g., XML attributes vs elements, YAML's optional quoting) and let you pick the trade-off.
All conversions run in your browser. Your data — which is often production records, customer details, or internal exports — never leaves your machine. This is essential when handling regulated data (PII, PHI, financial records) where uploading to a third-party service would be a compliance breach.
Most converters stream large files in chunks so you can handle hundreds of megabytes without crashing the tab. For multi-gigabyte conversions, we recommend a local CLI, but for most everyday tasks the browser is more than enough.
Backend developers integrating with new APIs. Data analysts preparing CSVs for BI tools. DevOps engineers translating between Docker Compose YAML and Kubernetes manifests. Database administrators migrating between systems. Business analysts cleaning and reformatting Excel reports. QA engineers building test fixtures. Anyone working with data export/import workflows.
Always validate the output against your target system before relying on a converted file. Use a small sample first (5-10 rows) to verify the schema mapping is correct. For production migrations, version-control both source and converted files so you can re-run conversions if requirements change. Document your conversion settings (delimiter, quoting, encoding) alongside the data so future engineers can reproduce the conversion. Watch out for character encoding: assume UTF-8 unless proven otherwise, and BOM-handle Excel-friendly CSVs explicitly.
Excel auto-corrupts CSVs with leading zeros (postcodes, phone numbers) and dates (DD/MM vs MM/DD). Use the converters' "preserve text" mode for sensitive columns. JSON booleans (true/false) are not the same as YAML booleans (true, yes, on, y); be explicit. SQL INSERTs need proper escaping for quotes within string values; let the converter handle this rather than concatenating strings yourself. Date formats vary by locale; always specify ISO 8601 (YYYY-MM-DD) for cross-system portability.