Convert PLIST to TOML
Turn PLIST files into TOML. The same keys and values as TOML, with plain values written before tables, and a top-level list is written under the key items, as [[items]] tables when its entries are objects.
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 TOML.Keys and values carry over. Top-level lists go under the key items.
What you get
A TOML file with the same keys and values as the PLIST. Plain values are written before tables.
If the top level of the PLIST is a list, it is written under the key items. When its entries are objects, they become [[items]] tables.
What changes
Dates become ISO 8601 text. Data becomes base64 text.
A null inside an object is dropped, and the conversion gives a warning. The rest of the object is kept.
When it stops
A null inside a list fails the conversion. So does an integer beyond the signed 64-bit range. TOML can hold neither of them.
A file that cannot be parsed stops with
input_corrupted. This applies to XML and binary property lists alike.To go the other way, use TOML to PLIST.
PLIST and TOML.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
TOML
TOML configuration files, the format of Cargo and pyproject.
- Extensions
- .toml
- MIME type
- application
/toml - Kind
- Text and data
In your code.The same PLIST to TOML conversion through the API, for your app or your agent.
$ cv convert report.plist report.toml$ cv convert report.plist report.tomlQuestions.What people ask about PLIST to TOML.
Yes. The source can be XML or binary.
In an object, the key is dropped and a warning is given. In a list, the conversion fails.
Dates are written as ISO 8601 text. Data is written as base64 text.
The file could not be parsed as a property list.