Export formats and source inclusion

Choose a representation that preserves the required annotation contract.

Export format determines which Unitlab structures remain native and which require mapping. Source inclusion determines how a consumer locates media, documents, groups, and protected data.

Working converters include:

Data family	Supported formats
Image	COCO, YOLOv8, YOLOv5, UUEF
Video	COCO, YOLOv8, YOLOv5, UUEF
Medical	COCO, YOLOv8, YOLOv5, UUEF
Document/PDF	UUEF only
Text	JSONL, UUEF
Audio	Audio JSON, RTTM, UUEF

Native single-family formats apply to one compatible family. A release containing more than one family must use UUEF or Standard Bundle.

• UUEF is the universal full-fidelity format. It preserves properties, attributes, relations, item properties, tags, page/frame context, and the richer annotation graph.

• Standard Bundle creates one ZIP containing a native output per selected family plus a manifest describing the release, source scope, selected types, split ratios, written files, and omitted empty combinations.

Default Standard Bundle choices are COCO for image/video/medical, JSONL for text, and Audio JSON for audio. Document data uses UUEF.

Use this in production

• Inventory classes, geometry, masks, keypoints, segments, spans, relations, properties, Item Properties, temporal state, and Data Group context before choosing a format.

• Prefer the platform-native representation when another format would lose required structure.

• Document any lossy mapping or post-processing step.

• Choose source bundling, references, stable URLs, and tokens according to downstream runtime and security requirements.

• Validate a sample with the real parser before releasing full volume.

---

Continue with Unitlab: multimodal data curation