Convert PLIST to JSONL
Turn PLIST files into JSONL. Each entry of a top-level list becomes one line of compact JSON, and any other value becomes a single line, with values and key order kept.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop PLIST files on the dialor turn it to pick what to do
Property lists as JSON Lines.One line of compact JSON per list entry, with values and key order kept.
What you get
One JSONL file. If the top level of the PLIST is a list, each entry becomes one line of compact JSON. Any other top-level value becomes a single line.
Values and key order stay as they are in the PLIST, so the lines read in the same order as the source. Both XML and binary property lists are accepted.
How values change
JSON has no date or data types, so these two are written as text. Dates become ISO 8601 text. Data becomes base64 text.
When it fails
A file that cannot be parsed stops the conversion with
input_corrupted. This happens when the PLIST is damaged or is not a valid property list.To go the other way, use JSONL to PLIST.
PLIST and JSONL.What each format is.
The formats
Property List
Apple property lists, XML or binary, that hold app settings and metadata.
- Extensions
- .plist
- MIME type
- application
/x -plist - Kind
- Text and data
JSON Lines
JSON Lines, one JSON object per line, the format of logs and datasets.
- Extensions
- .jsonl .ndjson
- MIME type
- application
/jsonl - Kind
- Text and data
In your code.The same PLIST to JSONL conversion through the API, for your app or your agent.
$ cv convert report.plist report.jsonl$ cv convert report.plist report.jsonlQuestions.What people ask about PLIST to JSONL.
Yes, when the top level is a list. Each entry becomes one line of compact JSON. Any other top-level value becomes a single line.
Dates become ISO 8601 text. Data becomes base64 text.
Yes. Values and key order are kept in the output.
The file could not be parsed. The conversion stops with input_corrupted when that happens.