Skip to converter

MessagePack binary records to COCO bounding-box annotations JSON (restricted) Converter.

Convert MessagePack binary records to COCO bounding-box annotations JSON (restricted) locally between basic object-detection annotation files and common spreadsheet/data formats.

Featured resources

App or project

NGSpeak: Language Learning App

Learn English and Bengali with 160 offline-first lessons across CEFR A1–C2, including speaking, writing, pronunciation practice, and progress tracking.

Download Now

Convert your file

INPUTMessagePack binary records
OUTPUTCOCO bounding-box annotations JSON (restricted)
Files stay on your device

Up to 2 MiB · 1–1,000 boxes, one image · Local conversion

Choose a compatible source file to begin.
Private processingYour source file stays in your browser
Original stays intactDownload a new output file
Real formatsUnsupported conversions show an error

STEP BY STEP

How to convert MessagePack binary records to COCO bounding-box annotations JSON (restricted)

  1. Choose a source file. Select a real MessagePack binary records file from your device.
  2. Run the local converter. The converter checks the input and processes it locally using the appropriate browser engine.
  3. Download the result. Save the generated COCO bounding-box annotations JSON (restricted) file. Your original file is unchanged.

FORMAT GUIDE

Why convert MessagePack binary records to COCO bounding-box annotations JSON (restricted)?

Review object-detection labeling data in spreadsheets or exchange a limited single-image annotation set between COCO and Pascal VOC tools without uploading private files.

  • Reviewing detected object bounding boxes in a CSV or XLSX file.
  • Preparing a single-image Pascal VOC XML from a compatible COCO JSON annotation.
  • Moving rectangular annotations to a portable structured data table.

UNDERSTAND YOUR FILES

MessagePack binary records vs. COCO bounding-box annotations JSON (restricted): what changes?

Input · MessagePack binary records

MessagePack is a compact binary data format. These tools support flat text-based record maps, not arbitrary nested or typed binary values.

Output · COCO bounding-box annotations JSON (restricted)

COCO object detection JSON stores image details, class categories and boxes. Only a strict single-image box subset is supported. No masks, keypoints or dataset metadata.

Review object-detection labeling data in spreadsheets or exchange a limited single-image annotation set between COCO and Pascal VOC tools without uploading private files. Choosing an output format changes how another app reads the file; it does not restore detail missing from your source.

Before you share the output

Check column headings, escaped characters, delimiters and empty values. Data type information and spreadsheet formulas may not survive a plain-text format change.

Your files and privacy

Your selected file is converted on your device. You can download the new file while keeping the original unchanged.

Some formats work differently across browsers and devices. Check the converted result before using it for important work. Advertising and other optional website services may have separate privacy practices.

Format compatibility and limitations

This is an offline converter of annotation metadata, not image pixels or a labeling application. Sources must contain exactly one image, 1–1,000 axis-aligned integer-pixel rectangles and no more than 2 MiB of annotation content. The structured table columns must appear exactly in this order: image_name, image_width, image_height, class_name, xmin, ymin, xmax, ymax. All rows must describe the same image and dimensions; bounding-box coordinates start at the top-left and satisfy 0 ≤ xmin < xmax ≤ width and 0 ≤ ymin < ymax ≤ height. COCO accepts a minimal one-image JSON subset: images, annotations, categories, with [x, y, width, height] boxes and optional rectangular area and iscrowd=0. Pascal VOC accepts one annotation XML with filename, size and plain objects; depth=3, segmented=0, pose=Unspecified, truncated=0 and difficult=0 when present. Unsupported segmentation masks, keypoints, polygons, multi-image datasets, crowd flags, rotated boxes, duplicate categories, advanced metadata, noninteger or out-of-bounds boxes are rejected. Generated category and object IDs are reassigned as internal references. No source image files are altered; retain originals and confirm import compatibility.

Actual output behavior depends on the input file, your browser, device resources and the converter engine. Check important files before sharing or replacing them.

HELP & ANSWERS

MessagePack binary records to COCO bounding-box annotations JSON (restricted) questions

Does it convert or modify the image itself?

No. Only annotation metadata is converted; the image pixels are unchanged.

Can I convert complete multi-image COCO datasets?

No. This strict release supports one annotated image per file and rejects multi-image sources.

Which columns do tables need?

Exactly: image_name, image_width, image_height, class_name, xmin, ymin, xmax, ymax.