Local by default
Small conversion jobs do not need a source-file upload. Browser processing creates a clear privacy boundary and keeps the tool useful without accounts or cloud drafts.
Why DataFormatKit exists
Data conversion should show its work
Most small format jobs are treated as plumbing: upload a file, click convert, trust the download. DataFormatKit is built around a different premise—structure and risk should be visible before export.
Narrow tools, specific decisions
Delimited text needs row-shape checks. JSON needs number and nested-array handling. XML needs record-node and entity boundaries. Separate tools can be honest about those differences.
Evidence over a green checkmark
A parse-success message says too little. A preview, categorized issues, and a transformation report give someone enough context to review the result.
First-release scope
Useful boundaries are part of the product
DataFormatKit currently focuses on five browser-local workflows: text to CSV, CSV to Excel, JSON to Excel, JSON to CSV, and XML to CSV. It is not a database migration service, spreadsheet editor, schema registry, or cloud document platform.
The current 10 MB and 50,000-row limits favor inspectable jobs that browsers can handle predictably. Unsupported ambiguity is surfaced or blocked instead of being hidden behind a best-effort output.
Use the product principles