Analytics cookies start only if you accept. Rejecting keeps tools available. Consent Mode may send cookieless signals. File contents, typed text, email and payment details are not sent to GA4.
Add CSV, TSV or JSON files and choose an output format.
Files processed on this deviceOriginal files kept intactReview results before download
Processed on this device · No work-file upload · Details
Core processing stays in this browser; signed-in features store service metadata such as account, quota and jobs, not copies of your work files. Handling details
Loading tool workspace…
How to use, plans and common questions
STEP 01Add files
Add CSV, TSV or JSON data files.
STEP 02Choose settings
Choose an output format and confirm the credit cost before running.
STEP 03Review & download
Preview parsed output, then download one file or a ZIP.
FREE + PROStart free and upgrade when the workload grows.Free: 5 conversions per rolling 24 hours, 25 MB/file and 3/batch. Pro: 300 per 30 days, 50 MB/file and currently 20/batch, plus advanced naming, templates and priority processing.
Processed in this browserCore file processing runs on this device; the work files do not need to be uploaded to FileNest first.
File contents are not uploadedWork files stay on this device for this tool; outputs are generated or downloaded within the browser workflow.
Service metadata ≠ file copiesSigned-in features may store account, quota, job, download or saved-rule records; those records do not contain copies of your work files.
Practical use cases
Less mechanical sorting, more focus
System imports
Turn several CSV files into JSON object arrays for internal tools.
Cross-system exchange
Switch between CSV and TSV to resolve delimiter compatibility.
Data checks
Preview parsed output before download to catch syntax problems early.
FAQ
Questions before you begin
Are commas inside CSV fields supported?
Yes. Common double-quoted fields, escaped quotes and line breaks are parsed.
Can JSON have any shape?
For reliable tabular conversion, input must be an object or object array; nested values are serialized as JSON text.
Is the data retained?
No. Parsing and download happen in the current browser.
Convert a spreadsheet export to JSON for an API or script, or turn JSON objects back into CSV or TSV for a colleague. Preview field counts, quoted commas and IDs such as 00127 before delivery. Processing stays in your browser; the converter cannot reconstruct source values that were already lost.
CSV → JSON
Use the CSV header as field names and convert data rows into a JSON object array for APIs, scripts or internal tools.
JSON → CSV / TSV
Convert an object or object array back to tabular data. Nested values follow the current tool rule and are serialized as JSON text.
Quoted fields and local preview
Common double-quoted fields, escaped quotes and line breaks are parsed, and you can inspect the result before download while data stays in the browser.
Vendor handoff: keep 00127 and a comma-containing name intact
If a SKU is 00127 and the contact is Shah, Mira, inspect the source CSV as text: spreadsheet software may already have changed the ID to 127, while the name needs CSV double quotes. Check the parsed column count and resulting JSON field values before delivery; lost leading zeros cannot be guessed back. On JSON-to-CSV/TSV exports, also review spreadsheet-formula risk warnings and the receiver’s required fields.
Task examples, guides and AI assistance
Practical guide
Understand the workflow before processing the file