What is XML / MessagePack Converter?
XML and MessagePack Converter helps inspect queue, cache, and binary API payloads. Safe XML first becomes an ordinary object before a browser codec emits Base64 MessagePack. Decoding accepts only data that can safely form one XML root, preventing extensions or dangerous keys from being silently rewritten. Common workflows include the following. Generate MessagePack API fixtures. Decode Base64 logs into XML. Compare XML and binary object 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 API fixtures.
- Decode Base64 logs into XML.
- Compare XML and binary object structure.
How to use it
- Use complete XML for encoding.
- Use complete standard Base64 for decoding.
- Load an example to verify the root and nesting.
- Convert and read type-safety messages.
- Restore raw bytes only when required by the endpoint contract.
- 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><name>JSONLane</name><release><tools>60</tools><ready>true</ready></release></site>Example 2
gaRzaXRlgqRuYW1lqEpTT05MYW5lp3JlbGVhc2WiNjA=Input rules
- XML cannot contain dangerous declarations.
- Decoding requires complete standard Base64.
- Decoded data needs one valid XML root key.
- 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 carried as Base64.
Output rules
- MessagePack bytes use Base64.
- Attributes and text use the documented XML mapping.
- Extensions and source layout 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.
- Decoded data must contain one XML root key.
Limitations and cautions
- Binary output is carried as Base64.
- Decoded data must contain one XML root key.
- Extensions, namespaces, and mixed content need manual handling.
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.