Convert PLIST to BSON
Turn PLIST files into BSON. One BSON document with the same keys in order; a top-level list is wrapped under the key items and any other value under value.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop PLIST files on the dialor turn it to pick what to do
A property list as one BSON document.Keys keep their order and their types. Dates and data become text.
What you get
One BSON file holding one document. The keys come out in the same order as in the PLIST, whether the PLIST is XML or binary.
Integers, floats, booleans, null, text, nested objects and lists keep their types.
Wrapping rules
A BSON file holds a document, so the top level must be a document. If the PLIST starts with a list, the list is wrapped under the key items. Any other top-level value is wrapped under the key value.
What changes
Dates stay text. Each date becomes ISO 8601 text, not a BSON date. Data fields become base64 text, not BSON binary.
Integers beyond the signed 64-bit range become floats.
To go the other way, use BSON to PLIST.
PLIST and BSON.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
BSON
MongoDB's binary document encoding, JSON with dates and binary fields.
- Extensions
- .bson
- MIME type
- application
/bson - Kind
- Text and data
In your code.The same PLIST to BSON conversion through the API, for your app or your agent.
$ cv convert report.plist report.bson$ cv convert report.plist report.bsonQuestions.What people ask about PLIST to BSON.
Yes. The document has the same keys in the same order as the PLIST.
No. Dates become ISO 8601 text.
They become base64 text. They are not stored as BSON binary.
The list is wrapped under the key items. Any other top-level value that is not a document is wrapped under the key value.