Convert MSGPACK to JSON
Turn MSGPACK files into JSON. The same structure and key order: binary values become base64 text, timestamps become ISO 8601 text in UTC, keys that are not text become text, and several values in a row become a list.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop MSGPACK files on the dialor turn it to pick what to do
MessagePack as plain JSON text.The same structure and key order, written out as JSON.
What you get
One JSON file with the same structure and key order as the MSGPACK file. Maps, lists and values keep their places.
If the MSGPACK file holds several values in a row, they become a list in the JSON file.
What changes
JSON has no binary type, so binary values become base64 text. Timestamps become ISO 8601 text in UTC.
JSON keys must be text. Keys in the MSGPACK file that are not text become text in the JSON file.
When it fails
If the file cannot be parsed, the conversion stops with
input_corrupted.Going back
To turn JSON into MessagePack again, use JSON to MSGPACK. Other JSON conversions are listed under every JSON conversion.
MSGPACK and JSON.What each format is.
The formats
MessagePack
Binary JSON: the same values as JSON in a compact byte encoding.
- Extensions
- .msgpack .mpk
- MIME type
- application
/msgpack - Kind
- Text and data
JSON
JSON, the data format of every API.
- Extensions
- .json
- MIME type
- application
/json - Kind
- Text and data
In your code.The same MSGPACK to JSON conversion through the API, for your app or your agent.
$ cv convert report.msgpack report.json$ cv convert report.msgpack report.jsonQuestions.What people ask about MSGPACK to JSON.
Yes. The JSON file keeps the key order of the MSGPACK file.
Binary values become base64 text, because JSON has no binary type.
As ISO 8601 text in UTC.
Several values in a row become a list in the JSON file.