You will learn how handle:


Currently cloud processing is only compatible with Metashape version 1.6 and higher, using the previous versions of Metashape may cause errors. Please update Metashape regularly to have the best synchronization speed and stability when working with the cloud.

Processing errors


Project is locked for changes


This error may occur in two cases:


  • when the cloud version of the project is in the publication process and the project is locked for changes  to avoid possible inconsistency or project files corruption. Please cancel publication, wait until publication completion and try to run processing operation again.
  • when the user cancels project processing some time is needed to delete temporary files and ensure project consistency. In this case it is not available to schedule new processing of this project on the cloud or to publish the project. Please wait several minutes and try again. In case the project stays locked for a long time, please submit a support ticket.


Connection timed out


If there are "connection timed out" errors during the synchronization attempt, please check the firewall permissions. Cloud processing feature requires access to account.agisoft.com via HTTPS protocol (port 443) and to api.agisoft.com via port 8086


Unknown network error


In most cases this error is related to the Internet connection. Please open OS console and run the command bellow.
nslookup api.agisoft.com

When the command is executed, please submit a support ticket and include the command output into the ticket description, support team will reach you as soon as possible and instruct how to solve the problem.


Error transferring  


In most cases this error is caused when cloud processing start from Metashape version below 1.6.5. Please download and install most recent Metashape version and restart processing on the cloud. 


In case you use most recent Metashape version, the problem may occur because of project files or photos size. Currently the cloud upload has the following limitations:

  • 500 MB per source image file,
  • 40 GB per internal project file.



Empty extent 

Bounding box is misplaced during Build Tiled Model or Build Orthomosaic operation and doesn't contain any information or all the cameras for the related area are disabled. 


Open project in Metashape and make sure that Bounding box (region) contains tie points/dense cloud and cameras inside are enabled. Restart processing on the cloud.


Empty camera list

No cameras are pointing to the area of the orthomosaic generation.


Open project in Metashape and make sure that Bounding box (region) contains tie points/dense cloud and cameras inside are enabled. Restart processing on the cloud.


Empty surface 

Bounding box is misplaced during Build Mesh operation and doesn't contain any information.


Open project in Metashape and make sure that Bounding box (region) contains tie points/dense cloud and cameras inside are enabled. Restart processing on the cloud.


Null dense point cloud 

Missing dense cloud for the operation based on it (like mesh generation or classification). 


In case of using batch script, create tasks in the proper order - make sure that requirements for each processing operation are fulfilled on previous processing step  and restart processing on the cloud.


Null model 

Missing mesh model for the operation based on it (like mesh decimation).


In case of using batch script, create tasks in the proper order - make sure that requirements for each processing operation are fulfilled on previous processing step  and restart processing on the cloud.


Null point cloud 

Missing sparse cloud for the operation based on it (like mesh generation).


In case of using batch script, create tasks in the proper order - make sure that requirements for each processing operation are fulfilled on previous processing step  and restart processing on the cloud.


Zero resolution

Bounding box is misplaced prior to the Build Dense Cloud operation and doesn't contain any information (almost no tie points are present in the bounding box and therefore no depth maps can be generated).


Open project in Metashape and make sure that Bounding box (region) contains tie points/dense cloud and cameras inside are enabled. Restart processing on the cloud.


Vertical datum missing


Currently it is only available to process projects with geoids that are presented on Agisoft website: https://www.agisoft.com/downloads/geoids/


Synchronization error


In exceptional cases project may be corrupted while downloading from the cloud due to a network or other unexpected error. In this cases after synchronization procedure is finished, project may not open with errors like: 


Can't open file: the system cannot find the file specified....


To get the processed project from the cloud in such case, please try to download project copy from the cloud.  To download project from the Cloud, select Download Project...  option from Cloud submenu of File menu, select a project and click OK button, select a path to save the project and set the new name for it, downloading procedure will be started.


Publication errors


Clicking on Publication button leads to nothing


When the user cancels project processing some time is needed to delete temporary files and ensure project consistency. In this case it is not available to schedule new processing of this project on the cloud or to publish the project. Please wait several minutes and try again. In case the project stays locked for a long time, please submit a support ticket.


Non-georeferenced project 


Currently it is unavailable to publish non-georeferenced projects. 


Large 3D models


3D models large than 1 GB are not publish because of potential performance issues in web browser. This limitation is related to the fact that it will take quite a long time to transfer the data to the web-viewer and it may be hard to navigate such large models online. As a workaround a tiled model can be used or a low-poly model with the texture generated using Transfer Texture option (to transfer the texture from the original high-poly model).


OpenSSL problems


Only Metashape versions < 1.7  require OpenSSL to work with the cloud. We highly recommend you to update to most recent version of Metashape, and not install OpenSSL manually.


In case you are using Metashape version < 1.7 please follow the recommendations below to install OpenSSL and start working with the cloud:

  • OpenSSL version 1.0.1 or 1.0.2 can be found here:  https://wiki.openssl.org/index.php/Binaries
  • To install OpenSSL 1.0.1 or 1.0.2 from  zip-archive, unpack the zip-archive into Metashape installation directory and restart the application. 
  • If OpenSSL version 1.0.1 or 1.0.2 is installed on your computer but you still face OpenSSL error, please restart your computer.