Exports and sharing
An export is a sealed, versioned copy of your accepted data in the format your trainer reads. Older versions are never changed.
Formats
| Format | For | What it holds |
|---|---|---|
annotation_bundle | annotation deliveries, first-person and video data | one folder per episode: annotations.json (caption, steps, actions, objects with outlines, tracks, metadata) and the dense files beside it (hand and body landmarks, depth, masks, point clouds, camera trajectory, 3D hands, telemetry), plus each layer’s QA and receipt |
lerobot_v3 | VLA and behaviour cloning | per-timestep data, video shards, task strings, success labels |
zarr_replay | diffusion policies | a replay buffer, resampled to the target’s rate |
webdataset | large-scale training | sample-per-key shards |
detection_coco | detectors | images with readiness-checked boxes and outlines |
coco_keypoints | pose models | images with keypoints |
image_folder | self-supervised encoders | media and a readiness manifest, no labels |
jsonl | anything else | one manifest row per episode |
The format picker in Datasets & export lists every format and greys out the ones that do not fit your use case.
What every export carries
- A README written from the export’s own files: what every file is, its schema, units, coordinate frame and time base, which layers are present and how much of the data they cover, the telemetry streams, what was withheld and why, and how to read it.
export_info.json: the format, the options and when it was built.- Readiness evidence: a readiness receipt per episode, a readiness summary and the project’s certificate as a page.
- No model names. Which model produced a layer is withheld by default (Export and delivery settings control it per workspace).
- Privacy. Location and face streams are never exported; telemetry is cut to each episode’s window. On first-person data, only the camera wearer’s hands are kept, and the README says so.
Choosing what goes in
- Episodes: accepted ones. The annotation bundle also carries episodes still awaiting review, with their decision; rejected episodes never ship.
- Layers: the layer picker in Datasets & export leaves any layer out
(
exclude_layers); its files, its keys and its receipts go, and the README says so. 3D hands (experimental) and telemetry can be left out the same way. - Embeddings:
include_embeddingsadds the stored caption and visual vectors for retrieval and deduplication. It is on by default except in the annotation bundle.
curl -fsS -X POST -H "Authorization: Bearer $EULER_TOKEN" -H "Content-Type: application/json" \
"$EULER_BASE_URL/v1/projects/$PROJECT/reexport" \
-d '{"format": "annotation_bundle", "exclude_layers": ["hands_3d"]}'
curl -fsS -H "Authorization: Bearer $EULER_TOKEN" "$EULER_BASE_URL/v1/projects/$PROJECT/exports"
curl -fsS -L -o export.zip -H "Authorization: Bearer $EULER_TOKEN" \
"$EULER_BASE_URL/v1/projects/$PROJECT/exports/<export_id>/download"A re-export reflects every accept and reject made since the run. Large archives are built on download.
Sharing a project read-only
A read-only link opens a project’s review screen for someone without an account: the clips with every layer painted on them, the 3D view, depth, the sensor streams and the evidence behind each check. Nothing can be changed through it, and no original file can be downloaded unless you allow it.
In Datasets and export, under Share links, choose New link, give the link a label, choose how long it lives (7, 30 or 90 days; 90 by default) and whether the original files may be downloaded, then Create and copy it. The link is shown once; what stays behind is a fingerprint, so a lost link is revoked and replaced rather than recovered. The same section lists every link of the project with its expiry, scope and status, and Revoke ends one. Engineers and admins create and revoke links. Revoking takes effect immediately, deleting the project revokes every link it had, and each link is rate-limited. The page the link opens is marked not to be indexed by search engines.
From code: POST /v1/projects/{id}/share creates a link, GET lists them,
DELETE /v1/projects/{id}/share/{share_id} revokes one. The reader side is
GET /v1/share/{token} plus the project’s read routes under the same prefix.
For a collaborator who needs more than a look, invite them as a viewer instead: a viewer sees episodes, receipts, overlays and exports and cannot touch sources or settings.
Next
- What the readiness numbers in the export mean: Readiness and certificate.
- What is not in an export yet: Limits.