PIX4Dmatic Standard vs Analyst vs Pro — Which Should You Choose?

Choose Standard for photogrammetric image processing, Analyst for terrain and survey-data analysis inherited from PIX4Dsurvey, and Pro when one user needs the combined image-to-survey workflow. The correct team configuration may mix tiers; selecting by old product names alone can create unnecessary cost or missing capabilities.

Technical content reviewed against official sources · 16 November 2026
01

What changed in 2026

PIX4Dmatic 2.0 unified the former PIX4Dmatic and PIX4Dsurvey desktop experience. New purchases use Standard, Analyst and Pro. Standard retains the core PIX4Dmatic processing role. Analyst carries the PIX4Dsurvey-oriented terrain, vectorisation and CAD workflow. Pro combines both feature sets in one plan.

This is more than a visual rebranding. Existing subscriptions, rentals and one-time-charge licences have transition conditions involving Support & Updates and timing. Organisations with both legacy products should review seats before consolidation: PIX4D’s guidance distinguishes retaining separate Standard and Analyst access from moving to Pro.

02

Compare by the work each person performs

A processing operator and a survey analyst may not need the same licence. Start with representative inputs and deliverables, then identify where each role begins and ends.

Workflow questionStandardAnalystPro
Calibrate aerial or terrestrial images?YesNot its core roleYes
Generate dense cloud, DSM, orthomosaic or mesh?YesUses survey data rather than replacing processingYes
Classify terrain and produce TIN/DTM/contours?Not its core roleYesYes
Perform advanced survey vectorisation?Basic project functionsYesYes
Complete processing and analysis in one seat?Complement with another routeComplement with another routeYes
03

Three practical team configurations

A drone-mapping team producing orthomosaics and meshes but handing analysis to another department can begin by evaluating Standard. A survey or CAD team receiving point clouds and producing terrain, contours and vectors can evaluate Analyst. A practitioner responsible for the entire route—from source imagery to CAD-oriented outputs—should evaluate Pro.

A mixed team can combine tiers. For example, several Standard processing seats may feed a smaller number of Analyst users, while a technical lead uses Pro. This is a workflow illustration, not a licence quotation; actual feature and seat requirements should be confirmed against the current matrix.

04

Migration checks for PIX4Dsurvey and legacy PIX4Dmatic users

Do not start migration by uninstalling the working environment. Inventory the licence type, S&U status, active devices, project versions and recurring deliverables first.

  • Test opening representative existing projects in PIX4Dmatic 2.X.
  • Confirm feature access after transition and whether two separate access levels are still needed.
  • Check whether a Pro consolidation changes the number of seats.
  • Review operating-system and GPU compatibility for the target release.
  • Export and archive critical deliverables before changing the production environment.
  • Document recurring templates and validate them before phasing out legacy software.
05

What the licence does not decide

A higher tier does not improve poor capture or remove the need for QA. Control and checkpoints, camera geometry, reconstruction quality, coordinate handling and independent acceptance checks are project decisions. Likewise, the ability to generate a DTM or DXF does not make the output a certified survey drawing.

What to carry into the project.

Standard = photogrammetry processing.

Analyst = survey-data analysis and vectorisation.

Pro = combined workflow in one plan.

Review legacy seats and S&U before migration.

Continue the technical review.

PIX4Dmatic technical pagePIX4Dmapper migration guide
PIX4D · Official unification and transition guidancePIX4D · Current licence matrixPIX4D · Upgrade to Pro guidance

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.