What is YAML / MessagePack Converter?
YAML and MessagePack Converter helps inspect queue, cache, and binary API payloads. Safe YAML becomes ordinary data before a browser-side codec emits MessagePack bytes as Base64; decoding validates the carrier and accepts only values that can map safely back to YAML without silently rewriting extensions or large integers. Common workflows include the following. Generate MessagePack test payloads. Decode Base64 payloads from logs. Compare YAML and binary structures. 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 test payloads.
- Decode Base64 payloads from logs.
- Compare YAML and binary structures.
How to use it
- Choose encode or decode.
- Use safe YAML for encoding or complete Base64 for decoding.
- Load the example to inspect objects and arrays.
- Convert and review type-safety messages.
- Decode Base64 separately when raw bytes are required.
- Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
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: 50
ready: true
tags: [local, browser]Example 2
gqRzaXRlqEpTT05MYW5lpXRvb2xzMg==Input rules
- Encoding requires safe YAML.
- Decoding requires complete standard Base64.
- Extensions, unsafe integers, and excess depth 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.
- Binary output is represented as Base64.
Output rules
- MessagePack bytes use Base64.
- Decoded output is ordinary YAML data.
- YAML styles and anchors 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.
- Extension types and unsafe integers are rejected.
Limitations and cautions
- Binary output is represented as Base64.
- Extension types and unsafe integers are rejected.
- YAML comments, anchors, and scalar styles are not retained.
How your data is handled
All parsing, format 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.