PIX4Dcloud vs PIX4Dmatic: Processing, Analysis and Collaboration

PIX4Dcloud is primarily the online processing, review and collaboration environment; PIX4Dmatic is the desktop photogrammetry and survey-analysis application. Choose by processing governance, required analysis, reviewer access and team responsibility—not by assuming one product universally replaces the other.

Technical content reviewed against official sources · 16 November 2026
01

The short operational comparison

Both products can participate in a photogrammetry workflow, but their centres of gravity differ. Cloud reduces the friction of shared access; Matic provides local project control and the Standard/Analyst/Pro survey workflow.

Decision factorPIX4DcloudPIX4Dmatic
Processing environmentOnline, subject to plan and supported pipelineLocal desktop, Windows or macOS
Core strengthShared 2D/3D review, measurements and collaborationPhotogrammetric processing and survey-data analysis
Plan structureStarter, Pro; enterprise arrangements separatelyStandard, Analyst, Pro
Repeat construction sitesPro sites, timelines and comparisonsProject-specific desktop analysis and exports
Terrain and advanced vectorisationNot the equivalent of AnalystAnalyst or Pro
Restricted-data routeRequires approved hosting and sharingLocal processing can simplify governance; licence/IT needs remain
02

When cloud is the sensible centre

Choose a cloud-centred route when several authorised roles need browser access, field uploads should move quickly into review, and repeat-site collaboration is more important than advanced desktop vectorisation. Pro is the relevant plan for sites, timelines, design overlays and repeat comparisons.

03

When desktop is the sensible centre

Choose a Matic-centred route when imagery must remain within a controlled processing environment, when operators need detailed calibration and project control, or when Analyst/Pro terrain and CAD workflows are required. Reviewers can receive agreed exports without every reviewer needing a processing seat.

04

A combined workflow can be deliberate, not duplicative

Some teams process or inspect locally, then publish an approved dataset for stakeholder review. Others upload field captures to cloud and download supported results for desktop analysis. The combined route should identify the authoritative version at each step, processing credits and licence dependencies, file-transfer responsibilities and the point at which a shared model becomes an issued deliverable.

05

Evaluate using one representative project

Run the same project brief through the proposed route: capture, coordinate setup, processing, QA, analysis, review, export and archival. Record time, manual transfers, user roles, failure points and the exact output each role needs. This reveals operational fit more reliably than a feature checklist alone.

What to carry into the project.

Cloud centres collaboration; Matic centres desktop processing and analysis.

Pro means different things in the two product families.

Define the authoritative dataset at every transfer.

Data governance can determine the architecture before features do.

Continue the technical review.

Desktop versus cloud processingPIX4Dcloud product page
PIX4D · Cloud plansPIX4D · Matic plans

Features and availability can change. Confirm the exact version, plan, sensor and commercial scope before procurement or project issue.

Specify the working system, not only the licence.

Share your source data, required outputs, users and constraints. Easepect can scope product supply, a technical demonstration, implementation and training.