Loading MessagePack Formatter...
Please wait a moment

How to Format MessagePack - Step by Step Guide

Step 1

Input Your MessagePack Data

Let's get your MessagePack data into the formatter! You have several convenient options:

•
Paste directly: Copy your MessagePack data as Base64 or Hex from an API, a log or a binary tool. Hex vs Base64 is detected for you
•
Upload a file: Click "Upload" to select a .msgpack or .bin file from your computer
•
Try the sample: Click "Sample" to load example data and see how the formatter works

Example: MessagePack Binary Data (Base64)

Here's what encoded MessagePack looks like:

g6RuYW1lpEpvaG6jYWdlHqZhY3RpdmXD
Step 2

Automatic Decoding & Formatting

About half a second after you stop typing, the formatter:

•
Decodes binary data: Converts MessagePack Base64 or Hex to readable JSON format
•
Adds proper indentation: Makes nested objects and arrays easy to read
•
Keeps numbers exact: 64-bit integers keep every digit, binary values become Base64 text

Example: Decoded and Formatted Output

The MessagePack data decoded to readable JSON:

{
  "name": "John",
  "age": 30,
  "active": true
}
Step 3

Choose Format Options

There are two layouts for the decoded JSON:

•
Pretty format: Default beautified JSON with proper indentation (2 spaces)
•
Minify option: Click "Minify" to put the JSON on a single line
•
Syntax highlighting: Color-coded elements make it easy to spot different data types
Step 4

Export Your Formatted JSON

When the JSON looks right, take it with you:

•
Copy to clipboard: One-click copying for quick pasting into your code editor or application
•
Download as file: Save as a .json file for later use or sharing with your team
•
Status badge: Shows whether the input was decoded from Base64 or Hex (or was JSON), and a plain-English message when it can't be read

Frequently Asked Questions

How do I format MessagePack binary data?

Paste the bytes as Base64 or Hex, or upload the .msgpack / .bin file. The formatter decodes them in your browser and shows the result as JSON indented with two spaces. If you paste JSON instead, it is simply re-indented.

Do I have to tell it whether my data is Base64 or Hex?

No. Text made only of hex digits (spaces, colons and 0x prefixes are fine) is read as Hex if it decodes cleanly; anything else is read as Base64, including URL-safe Base64 and data: URIs. The badge above the output says which one was used.

Will large integer IDs come out exactly?

Yes. 64-bit MessagePack integers such as 8901240544102066246 are decoded as BigInt and written into the JSON with every digit, instead of being rounded the way a plain JavaScript number would round them. Binary values are shown as Base64 text and timestamps as ISO 8601.

Can I get the output on one line?

Click Minify for single-line JSON. Copy and Download always give you exactly what is shown in the output panel.

What does an error like "the data ends too early" mean?

The MessagePack value is incomplete, which usually means the Base64 or Hex was only partly copied. Other messages point at a character that can't be Base64, an "=" in the middle of the text, or a byte that is not a MessagePack type at all.

Is my data uploaded anywhere?

No. Decoding and formatting happen in your browser, nothing is sent to our server, and nothing is kept: a reload starts with an empty editor. Very large inputs depend on your device memory and can make the editor slow.

To check MessagePack without formatting it, try the MessagePack Validator, or turn JSON into MessagePack with JSON to MessagePack.