Uploading is the only step that needs you. Drop in raw files or folders, check how they'll be grouped into recordings, and start the upload. As soon as the files arrive, the project's workflow starts processing them on its own, with no scripts to run.
Upload recordings
Open the upload page
In a project, open Recordings and click Upload data at the top right. You can also choose Upload from the ⋯ menu of a project row on the Projects page. Uploading needs the Owner, Editor or Uploader role on the project.
Set the data source and task
Source type shows the formats you can upload; formats that aren't open yet are listed as coming soon and can't be picked. A robot project also asks for a Task: say what the robot does in this upload, such as Put the sausage skewer on the grill. Leave it empty to use the project's default task. If the project has no default task, the field is required.
Add files or folders
Drag files or folders onto Drop recordings here, or click Add files or Add folder. Each folder becomes one recording, and so does each standalone robot MCAP file. If you add several loose files, you can merge them into one recording before you upload.
Check the plan
The page reads your files and shows what it will create, for example "Will create 1 recording from 1 file". Format for this import shows the format it picked, such as Robot MCAP; when files fit more than one format, choose the one that matches your recording. Under Recordings to upload, each recording has an editable Recording name. If a recording with the same name already exists, click Add date or Add number to make it unique.
The Estimate panel below shows roughly how long processing will take, what it will cost and how much storage it uses. If the upload would go over your quota, it can't start.
Start the upload
Click Start upload. The progress bar shows how many files have arrived. When they're all in, the recordings are created and a green Processing started notice appears with a View runs link and the new recording under Created recordings.
What happens after the upload
You don't need to set anything up. The project's workflow converts the raw files to LeRobot v3, checks them, blurs faces and prepares episodes. A robot recording becomes exactly one episode. Click View runs to watch each step, or open the recording once it's ready. Every upload is also kept under Upload batches at the bottom of the page, in progress first.
Supported formats
Each project accepts the formats of its kind. Anything marked coming soon is visible in the list but can't be uploaded yet.
| Kind | Format | What to upload | Status |
|---|---|---|---|
| Robot | MCAP | .mcap files with the robot topics, cameras and joints. Each file becomes one recording. | Available |
| Robot | LeRobot folder | One folder per recording with meta/info.json, data and videos at its root. Add meta/episodes.jsonl if your workflow needs episode metadata. | Available |
| Robot | ROS bag, ROS 2 db3, HDF5 | .bag, .db3, .h5 or .hdf5 files. | Coming soon |
| Human | MCAP | One folder per recording with the .mcap, its metadata.yaml, the device's device_meta.json (required) and the status folder if there is one. | Available |
| Human | LeRobot folder | The same folder layout as a robot LeRobot folder. | Available |
| Human | Video, BVH, Aria VRS, UMI GoPro | Fixed-camera video, motion capture and other rigs. | Coming soon |
First-person recordings with audio are refused, and a human MCAP without its device_meta.json is refused too. If the upload says first-person human ingest is off, ask your team admin.
When files are not added or the upload stops
A file the project can't take is skipped, and the page tells you why, for example not a type this upload accepts or not a valid MCAP file. Problems with the folder layout, such as a LeRobot folder without meta/info.json, appear under Issues to review and must be fixed before you can start.
If some files fail to arrive, click Retry failed or pending files; files that already arrived aren't sent again. If every file arrived but the recordings weren't created, click Retry creating recordings.
Upload from the command line
For large batches or automated collection, the embodiflow CLI uploads the same way the browser does. For example, embodiflow recordings upload ./recordings/rec-0001 --project <team>/<project> --name rec-0001 uploads one named recording. See the CLI reference for the folder upload and the other options.
The recordings list
Recordings in the project sidebar lists every recording. Each row shows its status, source, upload time, episode count and privacy state. Search by name, or filter by processing, segmentation, data source, upload date and episode count.
| Status | What it means |
|---|---|
| Uploading | Files are still arriving. |
| Processing | The project workflow is working on the recording. |
| Ready | Processing finished; the row then shows the check result. |
| Failed | Processing failed. Open the recording to see the step and the reason. |
| Stalled | No progress for over an hour. Reprocess it, or delete it and upload it again. |
| Cancelled | The run was cancelled. |
Once a recording is ready, its chip shows the check result: Checks passed, Warnings, Checks failed, Check error, Not checked or No checks apply. Only Checks passed is green; every other result needs a look before you count the recording as good. See Quality checks.
Reprocess runs the project workflow again on a recording; select several rows to reprocess them together. Earlier results are kept. Move to trash in the row's ⋯ menu removes a recording from the list, and you can restore it for 30 days.