Mesh Storage
Web upload
Drag and drop MCAP files into Mesh Storage from your browser
The fastest way to get a recording into Alloy: drag the .mcap file into Mesh Storage and walk away. No client to install, no device to provision.
Use this for ad-hoc files, recordings shared with you by a teammate, or a single mission you want to inspect without setting up an edge client.
Step 1: Open the upload modal
On the Mesh Storage → Data page, click Upload.
Step 2: Add files
Drag files or a folder into the drop zone, or click to open the file picker. To pick a whole folder, click Or pick a folder. You can add multiple files at once.
The uploader accepts .mcap files and sidecar metadata files (.json, .yml, .yaml). Other file types are skipped, and a warning lists the skipped files.
Step 3: Upload
Click Upload N files to start. Files upload one at a time, and each file shows a progress bar and a status icon:
| Icon state | Meaning |
|---|---|
| Waiting | Queued, hasn't started uploading yet |
| Uploading | Multipart upload in progress |
| Done | Successfully uploaded to object storage |
| Error | Upload failed. Try again or remove the file |
| Cancelled | Aborted before completion |
The overall progress bar shows total progress across all files.
You can click Cancel to abort all in-flight uploads. Cancelled multipart uploads are explicitly aborted on the backend so no orphaned parts are left behind.
If your organisation has reached its storage limit, the modal shows a banner and the upload does not start. Your files stay in the list. Click Upgrade to open billing, then upload again.
Step 4: Wait for ingest
Uploaded files land under uploads/web-uploads/ in Mesh Storage with a status badge:
- Queued: the file has landed in object storage and is waiting to be processed
- Ingesting: Alloy is parsing the MCAP and building queryable tables
- Ingested: the file is queryable in the SQL Workbench and external Iceberg clients
- Ingest failed: something went wrong. Hover the badge for the reason
Replay and Inspect work as soon as an MCAP file lands. You don't have to wait for ingest to finish.
What about large files?
Web uploads use multipart upload. Each file is split into parts, and the parts upload in parallel. The uploader sets no per-file size limit, but very large files (multi-GB) are usually faster to push from a device using Edge upload over a stable connection.
What about folder structure?
Single files land directly under uploads/web-uploads/. When you upload a folder, Alloy keeps its structure under uploads/web-uploads/<folder>/. Each file name gets a short upload-batch prefix, so uploads with the same name do not overwrite each other. If you want files organised by device automatically, use Edge upload.