Tool chooser

Which data export path should I use?

Data export works best when validation comes before conversion. Clean the shape, check headers and delimiters, then export to the format the recipient or system expects.

Developer And Data Tools

Decision map

Start with the closest job

Catch row and delimiter issues before creating a spreadsheet or import file.

Validate CSV before export

Use when: Use this path when CSV will be uploaded, emailed, imported, merged, or converted to XLSX.
Avoid when: Do not use validation to infer business correctness. It checks structure, not whether values are true.

CSV Delimiter Detector Browser-local CSV Encoding BOM Inspector Browser-local CSV Validator Browser-local CSV Missing Value Report Browser-local CSV Column Profiler Browser-local

Clean CSV data and export XLSX Convert JSON to CSV for spreadsheets

Normalize column names and remove structural clutter before handoff.

Clean headers and columns

Use when: Use this path when column headers are inconsistent, empty, duplicated, or not accepted by the destination system.
Avoid when: Do not change headers without checking downstream templates, formulas, imports, or documentation that expects specific names.

CSV Header Normalizer Browser-local CSV Column Cleaner Browser-local CSV Dedupe Browser-local CSV Sort Browser-local CSV Validator Browser-local

Clean CSV data and export XLSX Convert JSON to CSV for spreadsheets

Flatten nested objects before CSV or XLSX output.

Export JSON to a table

Use when: Use this path for API responses, webhook payloads, exported records, and nested JSON that needs a spreadsheet review.
Avoid when: Do not flatten complex nested arrays blindly. Review key paths and row shape before treating the workbook as final.

JSON Validator Browser-local JSON Key Path Extractor Browser-local JSON Flattener Browser-local JSON to CSV Browser-local JSON to XLSX Browser-local

Convert JSON to CSV for spreadsheets Clean CSV data and export XLSX

Turn clean CSV or JSON into a downloadable workbook.

Create XLSX for a recipient

Use when: Use this path when a client, teammate, school, portal, or business system expects an Excel-compatible file.
Avoid when: Do not export to XLSX before validating the source table. Spreadsheet output can hide structural problems until import time.

CSV to XLSX Browser-local JSON to XLSX Browser-local XLSX to CSV Browser-local CSV Validator Browser-local JSON Validator Browser-local

Clean CSV data and export XLSX Convert JSON to CSV for spreadsheets

Review product CSV fields, image references, prices, statuses, and variants before import.

Prepare ecommerce feed data

Use when: Use this path when a store, marketplace, feed, or teammate expects product rows with handles, SKUs, prices, image fields, and variant grouping.
Avoid when: Do not treat generic feed prep as Shopify, Google, Amazon, or marketplace acceptance. Destination rules still need review.

Product CSV Validator Browser-local CSV Header Normalizer Browser-local CSV Column Profiler Browser-local Marketplace Image Compliance Preflight Browser-local CSV to XLSX Browser-local

Clean CSV data and export XLSX Prepare files for upload portals

Use schema tools after sample data parses cleanly.

Draft or check a schema

Use when: Use this path when handoff requires expected columns, JSON types, required fields, or a reviewable data contract.
Avoid when: Do not treat inferred schema as final. It is based on observed sample data and needs human review.

CSV Schema Inferencer Browser-local JSON Schema Inferencer Browser-local JSON Schema Validator Browser-local JSON Validator Browser-local CSV Column Profiler Browser-local

Convert JSON to CSV for spreadsheets Clean CSV data and export XLSX

Keep browsing by workflow

Guides Open all workflow guides Use step-by-step paths that combine tools for PDF, document, image, and data tasks. Tools Search every live tool Use the tool finder when you already know the exact conversion, inspection, or cleanup action you need.