Matterport Capture for iOS

This article is about the Matterport Capture app for iOS. If you’re looking for release details or a Beta for the Capture on Android, please look here.


Latest Version

More Info


Current App Store Release: 4.3

iOS App Store


Current: 4.4

Via Test Flight

See instructions below

What's new in version 4.4?

• Added support for seven new languages (now 14 total): Chinese (traditional, simplified), Korean, Japanese, Brazilian Portuguese, Russian, Dutch, Italian
• New user quick start tutorial to help create your first model
• General improvements and bug fixes

What’s new in version 4.2?

This release primarily focuses on two things:

  • The Cortex 3D conversion engine is now included within the application when it is installed or updated from the app store. This eliminates the need to first have an account before trying to scan with your iPhone or iPad or with a connected 360 camera.
  • You can now more easily export projects from your iOS device and import projects to your iOS device. Use this to free up space from your iOS device (after having uploaded for processing and processed successfully) - or to move a project from one device to another. Previously this kind of activity required 3rd party desktop software tools and could risk errors since the internal file structure wasn’t designed for user editing.

In addition, this release continues to improve support for Lidar with the iPhone 12 Pro and iPhone 12 Pro Max. It also includes bug fixes and stability improvements.


Export and Import Scan Projects (Jobs) from your iOS Device.

If you are running out of space on your iOS device, but want to keep a backup of the raw project files as a precaution, you can easily have Capture package up and export it as a *.zip file. The resulting file will have the same name as your project and will include the files needed to restore the project to an iOS device. Note that if the project is a duplicate (a ‘child’ of a parent project), Capture will include the data shared with that parent in the export.

Do NOT edit the files within the *.zip package, or add or delete content to it. The contents are cross-indexed and are not meant to be manually edited. 

If you want to free up space on your iOS device, after successfully exporting the project and saving the file elsewhere, delete the project within Capture. Deleting files manually using iExplorer or iMazing (3rd party desktop tools) could confuse Capture’s job database.

Example export flow:


Sample import flow:



Prior Updates in 4.1.2

Lidar on the iPhone 12 Pro, iPhone 12 Pro Max, and iPad Pro (2020)

  • The default mode for capturing uses the Lidar sensor to detect depth. In areas not captured by Lidar, we’ll continue to synthesize depth using our Cortex AI engine.
  • Currently Lidar-based capture is a single-rotation “Simple” mode. The Lidar sensor has a narrower field of view than the ultrawide camera as you can see below. We provide a lightweight preview of where active depth data is present.
  • The Lidar-based method takes more time than the prior non-Lidar method. You can still choose non-Lidar (Simple, Complete) methods to experiment and compare for your needs.

Aim_at_next_dot.png           Scan_Options.png

  • If you select a 360 Capture when in Lidar mode we will use the Lidar data to try to improve image stitching.
  • For best imagery and depth, try to rotate your body around the device (as if it was on a monopod or broomstick). This minimizes parallax errors, which in turn can cause issues in the space. Unfortunately this is the opposite of how you would normally capture a regular panorama shot. We’ll pop a warning after a scan that we think might have had too much movement from the initial starting point.


Lidar FAQs:

  • Why does the image and Lidar field of view differ so much? We are using a custom approach so that you can capture HDR imagery from the ultra wide camera and Lidar in the same rotation. Native iOS 14 (at the moment) does not support HDR or the ultrawide camera while capturing Lidar. This is why you don’t see the ‘live mesh’ that is common in other iOS Lidar apps. The benefit of this approach is that you get the best imagery and depth with fewer capture points.
  • Can I paint up and down to get more Lidar coverage? Yes - we’ll use Lidar data where we have it. However, too much motion away from a fixed point can introduce stitching errors in the imagery, so you will need to be very careful.
  • Can I get a MatterPak (point clouds, mesh) or order a schematic floor plan with Lidar-based models? Not yet - we’re working on optimizing and characterizing the capture process and results first.
  • This will make it easier to backup or remove to make more room on your iOS device. If you are working with Matterport Customer Support and need to send scan data to us, this should make it much easier than having to completely rely on iExplorer or iAmazing. (They are still very helpful)
  • Important:
    • The exported folder(s) will have a long alphanumeric name. We recommend placing this in a folder with a friendly name. If you alter the name of the job folder and delete part of the UUID (unique identifier), it will not reimport properly in the future. 
    • New in 4.1: we automatically trace and copy parent/grandparent data to make a duplicate job ‘whole’ in the export. This means that the *.zip file may contain several folders to ensure that all the required data is in place.
  • Not implemented yet:
    • Assistance with importing prior exports is in a future update
    • Downloading prior models from the Matterport Cloud directly within Capture is slated for a future release (“Cloud Restore”).

Known Issues in 4.2:

  • Lidar scans:
    • If you see the “Something went wrong” message and cannot scan any further after that error, kill Capture (swipe up) and re-launch to continue.
  • Leica BLK360
    • Taking high density and/or HDR4 or HDR5 scans with iOS devices with only 3GB of RAM may lead to the “Unable to Complete Scan” error message. For the highest density/HDR scans we’d recommend an iOS device with 4GB of RAM or higher.
    • We’ve noticed the reported battery state of charge can fluctuate more than expected and are investigating.
    • There may still be instances where the BLK360 is not responding to commands; usually acknowledging the warning and re-trying the scan works. Worst case, turning the BLK360 off and on again resolves the issue.
  • Insta360 ONE R: 
    • There may be instances where the ONE R freezes or is not responding to Capture commands. Restart the ONE R and if needed close and re-open Capture. 
    • Early production versions of camera firmware (1.2.16, 1.2.17) are incompatible with Matterport Capture.
    • If you had the prior beta firmware installed (v.7.1.45) you will need to manually change to the latest release. The ONE app will not automatically update from the beta because it is a higher version number. Go to, download the firmware file, and copy it to the root directory of your ONE R’s SD Card. Turn the ONE R off and on again to trigger the firmware update process.
  • Insta360 ONE X:
    • The “Enterprise Edition” of this camera includes on-camera image stitching. Matterport Capture has not been updated yet to request this and will still do hemisphere stitching and HDR on the iOS device, not the camera.
  • Insta360 ONE X2:
    • Please ensure that your camera’s firmware is up to date for the best performance.
  • Ricoh Theta SC2: 
    •  You may get a 'something went wrong message'.  In this scenario, iOS devices can connect to the SC2's wifi signal,  and Capture recognizes the connected SC2, but any scan attempts will give the progess circle that stays there, then the 'something went wrong' message occurs.  This issue is under investigation and will be resolved in the future.  
  • Matterport for iPhone/iPad:
    • iOS devices with only 2GB of RAM are more prone to crash, especially with Complete scans (versus Simple).
  • Large job crashes:
    • In some cases Capture crashes with very large scan jobs (hundreds of scans) - this issue still exists from Capture 4.0.2 and we are using the improvements in crash analytics in this beta to try to trace root cause(s).


Beta releases: Ongoing public beta via Test Flight

Want to try the latest version of Matterport Capture to experience the newest features and fixes? Install the Capture beta using our public Test Flight program. Here's how: 

  • On your iOS device, open the Safari web browser
  • It's important to only use Safari, as the simple act of doing so eliminates the need for Test Flight access codes.
  • Follow the instructions on the page to install Test Flight. 
  • If you are asked for an access code, make sure you've opened the link on the Safari web browser on your phone or tablet. 
  • Open Test Flight
  • Tap Install to get the latest beta release 

If prompted, we recommend allowing Test Flight to send you notifications every time new beta builds become available. In the latest version of Test Flight, we recommend accepting the offer to auto-install updates to the beta program to ensure that you have the most stable build.


Return to a Production Version of Capture 

When the beta period is over (or if you want to return to a normal production version of Matterport Capture) open the App Store and search for Matterport Capture and install it.

The App Store listing will appear as if you do NOT have it installed, but it will install over the Test Flight version. You will not receive app store updates to Capture while a Test Flight version is installed.

Have more questions? Submit a request