Varjo has added 360 camera support to Teleport as a beta, accepting Insta360 .insv files and equirectangular video from any other 360 camera. Files from the Insta360 X4 and X5 go in exactly as they came off the camera, with Teleport handling the stitching and frame extraction. Every other 360 camera, including the Antigravity A1 and the DJI Osmo 360, needs an equirectangular video export first.
Varjo describes the capture as one continuous clip, walked at a relaxed pace with the camera held at varying heights to pick up floors, undersides and ceilings. The operator uploads the file unmodified, selects 360, and picks frame settings. Teleport masks the operator out of the footage automatically and reconstructs the space as a gaussian splat in the cloud.
Three further additions ship with it. A dual camera mode on iOS captures with both lenses at higher resolution, a shared capture can be locked behind a password, and Teleport.js loads and renders captures in any Three.js web app. It's a Spark.js wrapper that allows you to build custom 3DGS viewers and pull Teleport scenes into that custom viewer much more easily.
Teleport.js builds on the API that arrived with the Developer Plan in October 2025. It is at version 0.0.2, ships as a minified ESM module from Varjo’s CDN, and requires Three.js 0.180.0 or newer. A TELEPORT.Manager instance loads a capture by share ID into an existing Three.js scene, renders through the Spark.js renderer, streams chunked .rad files as level of detail geometry, parses gps_transform metadata into position arrays and quaternions, and exposes raycasting against splat volumes.
The fifth addition is a 3DGS drone guide covering flight paths, overlap and camera settings, which follows the Autopilot capture pipeline Teleport launched in May. One Teleport capture handles up to 10,000 images and up to 100 million splats.
What Varjo does not publish is a resolution ceiling for 360 footage, a frame count range for the 360 path, or a license for Teleport.js.
The 360 beta is live now.
