Per platform
| iPhone and iPad | High fidelity | |
|---|---|---|
| Android | High fidelity |
How it works
- Import the JSON file, or share it with Tramuta.
- Pick CSV among the formats.
- Tap “Convert”, then “Share” or “Save to…”.
A JSON export from an app, an API or a database is hard to read by eye and doesn’t open in a spreadsheet. As CSV it becomes a table anyone can sort and filter. Tramuta does the JSON to CSV conversion on the phone, without sending the data to an outside service.
From JSON to rows and columns
CSV has a single shape, the table, while JSON can nest as deep as it likes. Tramuta follows stated rules. If the root is a list of objects, each object becomes a row. If the root is an object, the first value that is a non-empty list of objects is used. The columns are the union of the keys; numbers and booleans are written as text (4.5, true), and null becomes an empty cell.
Nested values stay whole in their cell, as compact JSON. With two objects, one holding "extra": {"a": 1} and one holding "altro": [1, 2], the CSV comes out like this:
id,extra,altro
1,"{""a"":1}",
2,,"[1,2]"
Quotes are added only where a cell contains the separator, quotes or line breaks, as the CSV format requires. That is why the conversion is “High fidelity”: every value reaches the file, even though nested ones don’t get columns of their own.
JSON to CSV on iPhone, iPad and Android
The same Dart engine does the work on both platforms, so the CSV is byte-for-byte identical. The output is UTF-8 without a BOM, with LF line endings and a final newline; the separator is a comma unless you pick another one in the options.
The options in this direction
The “Options” sheet only shows “Column separator”, which here sets the separator of the CSV you get: “Automatic” and “Comma (,)” write a comma; the alternatives are “Semicolon (;)”, “Tab” and “Pipe (|)”. A semicolon helps when the CSV goes to a program that expects one. The header and number recognition settings are about reading a table and don’t appear here: the row of column names is always written.
How to do it in Tramuta
- Tap “Choose or drop files” and pick the
.jsonfile, or share it to Tramuta from Files, Mail or another app. - Under “Convert to”, pick “CSV”.
- If you need a separator other than a comma, pick it in “Options”.
- Tap “Convert”.
- Open the result in a spreadsheet with “Open in…”, or use “Save to…” or “Share”.
If you need a real spreadsheet, with numbers and a bold header row, continue with CSV to Excel XLSX. The reverse path is CSV to JSON; for a more readable form of the same structure there is JSON to YAML, and from an Excel sheet you get a CSV with Excel XLSX to CSV.
Questions
My JSON keeps the records under a key such as “rows”. Does that work?
Yes. When the root is an object, Tramuta uses the first value that is a non-empty list of objects, in key order, and skips lists of plain values. The other keys at the root don’t go into the CSV.
Are nested objects flattened into separate columns?
No. An object or a list inside a field stays in one cell, written as compact single-line JSON. Nothing is lost, but if you need separate columns you have to split them afterwards in your spreadsheet.
What if the objects don’t all have the same keys?
The columns are the union of all keys, in the order they first appear. Where an object lacks a key, the cell is left empty; null values become empty cells as well.
Why does the conversion stop with an error?
It happens when the JSON holds no table: a single value, a list of numbers, or an object without any list of objects. CSV needs rows and columns, so Tramuta doesn’t make up a structure.
Free on iPhone, iPad and Android
No ads, no in-app purchases, no account.
-
App Store
iPhone and iPad, iOS 15.0 or later.
Coming to the App Store -
Google Play
Android 7.0 or later.
Coming to Google Play -
APK for Android
Android 7.0 or later, without Google Play.
The APK is not available yet.