> For the complete documentation index, see [llms.txt](https://multiset.gitbook.io/multiset/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://multiset.gitbook.io/multiset/basics/third-party-scans/360-videos.md).

# 360 Videos

MultiSet builds VPS maps from **360° video**, so a space can be mapped with a consumer camera and no LiDAR or SLAM hardware. One continuous recording produces one map, and 360 video is the only input that yields the complete set of [output assets](/multiset/basics/maps/output-asset.md): a mesh, a Gaussian Splat, and a navigable panoramic tour of the same space.

## Pick your route

| Capture                                         | What you upload                 | Guide                                                                                           |
| ----------------------------------------------- | ------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Hand-held Insta360** (X4, X5)                 | Raw `.insv`                     | [Insta360 Scans](/multiset/basics/third-party-scans/360-videos/insta360-scans.md)               |
| **Antigravity A1**, the 360° camera drone       | Raw `.insv`                     | [Antigravity A1 (Drone)](/multiset/basics/third-party-scans/360-videos/antigravity-a1-drone.md) |
| **Any other 360 camera**, ground based or flown | Stitched equirectangular `.mp4` | [Equirectangular MP4](/multiset/basics/third-party-scans/360-videos/equirectangular-mp4.md)     |

Upload the **raw `.insv`** wherever you have it. MultiSet stitches it server-side with its own parameters, which preserves more detail than re-ingesting a vendor's stitch. Every other camera exports a **stitched equirectangular `.mp4`** and uploads that instead.

## What every route shares

* **One video, one map.** Exactly one video file per `.zip`, and each `.zip` must stay **under 50 GB**. Split a large site into several captures and join the resulting maps with [MapSet : Multiple Maps](/multiset/basics/mapset-multiple-maps.md).
* **Continuous motion.** No stops, no pivots in place, no paused recordings mid-capture. Move steadily, turn in wide arcs, and **close the loop** by returning to where you started.
* **Locked exposure.** Fix the shutter (indoors) and the white balance before you press record. Auto exposure is the single biggest cause of grey, smeared reconstructions.
* **Metric scale.** Either include a printed **ChArUco marker** in the scene, or set the scale after processing with [Map Scale](/multiset/basics/rest-api-docs/map-scale.md). Drone and stitched-video captures use the second route, since a printed board cannot be resolved from the air.
* **360 mode only.** Flat, single-lens, and stereoscopic (over-under or side-by-side) footage is rejected.

Allow up to one hour for processing. You will receive an email notification once the map is ready.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://multiset.gitbook.io/multiset/basics/third-party-scans/360-videos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.