# Exporting data

Mocap Studio exports captured skeletons, objects, and animation to a range of formats — pick the one that matches your downstream tool.

## Supported formats

| Format | Extension | Best for | Contains |
|--------|-----------|----------|----------|
| **FBX** | `.fbx` | Maya, Blender, Unreal, Unity | Skeletons, meshes, animation, blend shapes |
| **C3D** | `.c3d` | Biomechanics / mocap-standard tools | Marker & joint trajectories |
| **NPZ** | `.npz` | Python / ML pipelines | Pose arrays (incl. `positions_67`) |
| **SMPL-X** | `.npz` | Body+hands ML models | SMPL-X parameters |
| **glTF / GLB / DAE** | various | Web / general 3D (via Assimp) | Meshes + animation |
| **CSV** | `.csv` | Spreadsheets / quick analysis | Joint & object positions |
| **GR51** | `.gr51` | AR 51 native re-import | Recorded session (binary) |

## How to export

1. Select the recording in the captures/animation list.
2. Choose **Export** and pick a format.
3. Choose the destination folder and confirm.

:::tip
For ML / research, **NPZ** is usually the right choice — it's pure numeric pose data. The `positions_67` array has shape `(frames, 67, 3)` (25 body joints + 21 points per hand). See [Data model](/docs/sdk-api/data-model).
:::

## The `positions_67` layout

`67 = 25 body joints + (21 hand key points × 2 hands)`. Each entry is an `(x, y, z)` position in meters. This is the layout the bundled `read_synthetic_npz.py` plotting script expects.

:::note
Export *settings* (e.g. whether to include meshes/blend shapes for FBX, or the delimiter for CSV) are configurable per format. Keyboard shortcuts and preset management are covered in Presets & settings.
:::


## Related pages

- [Recording an FBX](/docs/mocap-studio/recording-fbx)
- [Biomechanical visualization](/docs/mocap-studio/biomechanical-visualization)
- [Unity SDK overview](/docs/unity-sdk/overview)