What is TOML / MessagePack Converter?
TOML and MessagePack Converter supports configuration payloads, cache samples, and binary API debugging. Safe TOML becomes ordinary data before the browser MessagePack codec emits Base64. Decoding accepts only values that can return safely to TOML. Extensions, dangerous keys, unsafe integers, comments, and original formatting are not presented as a lossless round trip. Common workflows include the following. Generate MessagePack configuration. Decode binary log samples. Compare TOML and binary structure. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.
When to use it
- Generate MessagePack configuration.
- Decode binary log samples.
- Compare TOML and binary structure.
How to use it
- Choose encode or decode.
- Use complete TOML or standard Base64.
- Convert and inspect warnings.
- Decode Base64 separately when raw bytes are needed.
- Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
- Review the output, status message, and documented limits; copy, download, or continue only after the result matches your expectation.
Runnable examples
The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.
Example 1
site = "JSONLane"
[release]
tools = 70
ready = trueExample 2
gqRzaXRlqEpTT05MYW5lp3JlbGVhc2WCpXRvb2xzRqVyZWFkecM=Input rules
- TOML must follow supported syntax.
- Base64 must be complete.
- Extensions and unsafe integers are rejected.
- Text input is counted before processing and is limited to 1,500,000 characters on this page; file modes apply the separate file limit shown in the workspace.
- MessagePack bytes are displayed as Base64.
Output rules
- Bytes use Base64.
- Tables and arrays map to ordinary data.
- Comments and formatting are not retained.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- Extensions and unsafe integers are rejected.
Limitations and cautions
- MessagePack bytes are displayed as Base64.
- Extensions and unsafe integers are rejected.
- TOML comments and formatting are not retained.
How your data is handled
All parsing, conversion, Base64 work, and intermediate data remain in the current browser tab. JSONLane does not upload the input or retain it after refresh or close.