DJI Terra License Guide
Match the software entitlement to your required outputs and processing setup. Review license options and deployment considerations before preparing a new workstation.
Compatibility guide | Drone Emotions
DJI Terra Supported Drones & Sensors
Find the right processing route for your drone, camera or LiDAR payload. Explore RGB mapping, Zenmuse point-cloud reconstruction, multispectral and thermal workflows, with the data requirements and limits that matter before you capture or import a project.
What “supported” means in DJI Terra
Compatibility is a relationship between the sensor, its recorded data and a particular Terra function. Use this guide to identify that relationship before planning a project.
Identify the data source
Start with the exact camera or mapping payload and the files it records. The aircraft name alone does not describe every possible processing workflow.
Write down whether you need photographs, a complete LiDAR recording, multispectral bands or radiometric thermal images.
Identify the required workflow
Separate post-flight reconstruction, video import and inspection-route planning. A device can appear in one supported list without providing every other function.
Check the project type and intended deliverables before choosing a software edition or flight method.
Check the complete setup
Record the aircraft, payload, controller, firmware and Terra version together. For a purchase or upgrade, ask for confirmation of the exact combination.
Test representative original data before committing to a larger capture campaign.
Supported drones and sensors at a glance
Choose the row that matches your actual data. Follow the linked section for the exact model list, required files and relevant DJI reference.
| Equipment or data | Processing route | Read the details |
|---|---|---|
| Matrice 4E; Mavic 3E; Phantom 4 RTK; Zenmuse P1 | RGB photogrammetry | RGB mapping and camera checks |
| Matrice 4D / 4TD | RGB workflow; thermal for 4TD | Documented video import / Thermal requirements |
| Zenmuse L1 | Native LiDAR point-cloud workflow | L1 data and license notes |
| Zenmuse L2 / L3 | Native LiDAR reconstruction | Host aircraft / Raw-data requirements |
| Mavic 3 Multispectral / Phantom 4 Multispectral | Native 2D multispectral reconstruction | Required image sets |
| Listed DJI thermal cameras | Native 2D thermal reconstruction | Exact supported models |
| Other cameras and consumer drones | Evaluate the photographs and calibration | Conditional image compatibility |
| Third-party LAS point clouds | Import for the documented project workflow | LAS import and scope |
On smaller screens, swipe the table horizontally to see every column.
Use this as a workflow guide. The dedicated sections identify current documented models and requirements. A file-format match or a general payload interface does not establish support for every reconstruction feature.
RGB mapping drones and photogrammetry cameras
Use the actual survey camera and original photographs for the compatibility assessment. Multi-camera aircraft can record several data streams that serve different purposes.
DJI Matrice 4E
DJI documents a mapping workflow with Terra, including camera-distortion handling for the Matrice 4E. The Terra import manual also identifies its embedded photo-positioning information.
For a new workflow, check the selected camera, photo mode and saved survey data. Keep a reference dataset with the planned outputs.
DJI Mavic 3E
The Mavic 3E is the mapping-oriented model in the Mavic 3 Enterprise family, with a mechanical-shutter wide camera and an RTK-module option.
Record the camera and RTK configuration used for the job. Evaluate the output in the coordinate system and delivery software required by your client.
DJI Zenmuse P1
The P1 is a dedicated full-frame photogrammetry payload. DJI documents its use for 2D and 3D mapping and publishes Terra downloads with the product resources.
Include the lens and host-aircraft configuration when requesting workflow advice. Keep original images and accompanying positioning records together.
Phantom 4 RTK: DJI documents its use for mapping reconstruction. For an existing fleet, check the installed Terra release and workflow separately from older flight-control instructions.
Photo input: the current visible-light import manual lists JPG and JPEG. Preserve the original files and their metadata when preparing a test.
Reference: DJI visible-light data import.
For each job, list the required orthomosaic, surface, mesh or point-cloud deliverable before selecting processing settings. A compatible camera provides a starting point; image quality and project validation still need attention.
Reference: DJI visible-light reconstruction overview.
Matrice 300 RTK, 350 RTK and 400: check the payload
Host-aircraft compatibility and Terra data compatibility are two parts of the same setup. Confirm both when assembling or changing a payload configuration.
| Aircraft | Examples of supported mapping payloads | Important condition |
|---|---|---|
| Matrice 300 RTK | Zenmuse P1, L1 and L2 | L2 requires DJI RC Plus; verify the prescribed mount |
| Matrice 350 RTK | Zenmuse P1, L1 and L2 | Check the current payload, mount and firmware guidance |
| Matrice 400 | Zenmuse P1, L2 and L3 | L3 requires its dedicated single-gimbal connector |
On smaller screens, swipe the table horizontally to see every column.
Reference: DJI P1 and Matrice 300 RTK guidance.
Reference: DJI L2 host-aircraft and mounting requirements.
Reference: DJI Matrice 350 RTK payload FAQ.
Reference: DJI Matrice 400 supported products.
Reference: DJI L3 aircraft and connector requirements.
Check the payload as well as the aircraft. A rangefinder or obstacle-sensing specification does not establish a compatible LiDAR mapping-data source. For point-cloud reconstruction, identify the actual mapping payload and the dataset it records.
Zenmuse L1, L2 and L3 in DJI Terra
Native LiDAR reconstruction starts with the original recording, not merely an exported point cloud. Match the payload, release and intended outputs when checking licensing and processing options.
Zenmuse L1
DJI documents native LiDAR post-processing in Terra for L1 data. Its current FAQ describes basic point-cloud output as free, with Standard or higher required for the listed advanced processing and additional-output functions.
Confirm the requested outputs and installed release when evaluating an existing L1 workflow.
Zenmuse L2
The current Terra manual states that L2 LiDAR reconstruction projects can be processed without a software license.
Keep the native recording intact and verify the host/controller arrangement. On Matrice 300 RTK, the L2 FAQ specifies DJI RC Plus.
Zenmuse L3
The current manual also lists L3 reconstruction without a software license. DJI identifies Matrice 400 as the compatible host, with the specified L3 connector.
DJI distinguishes its real-time preview from the point cloud reconstructed in Terra. Validate the post-processed result for the intended job.
Reference: Current DJI LiDAR reconstruction and license note.
Reference: DJI L1 processing entitlement guidance.
Import the complete native dataset
The LiDAR import manual describes raw LDR data alongside positioning, IMU, calibration and supporting files. Import the recorded data folders; missing required files can prevent reconstruction.
Reference: DJI LiDAR data preparation and import.
Copy the complete flight dataset before reorganizing it. Keep source data separate from generated results and record which flight folders were included in each project. This makes later quality checks and support requests easier to reproduce.
Mavic 3 Multispectral and Phantom 4 Multispectral
Use the native multispectral project for the documented DJI models. Plan the image-set integrity and the intended index or reflectivity outputs before the flight.
| Aircraft | Images per complete capture set | Workflow |
|---|---|---|
| Mavic 3 Multispectral — M3M | 5: RGB + 4 multispectral images | 2D multispectral reconstruction |
| Phantom 4 Multispectral — P4M | 6: RGB + 5 multispectral images | 2D multispectral reconstruction |
On smaller screens, swipe the table horizontally to see every column.
Reference: DJI multispectral overview and applicable aircraft.
Keep the complete image sets
The import manual requires visible-light JPG/JPEG and single-band TIFF images. RGB images are used for alignment; an NDVI preview is not a substitute.
Terra checks the required bands. Missing images can prevent an index from being generated correctly.
Define the vegetation deliverables
DJI describes vegetation-index and band-map outputs, including NDVI and NDRE, with optional radiometric correction for reflectivity-based results.
For repeat surveys, record the acquisition and calibration method so that the interpretation can be assessed consistently.
For a different multispectral camera, request a specific compatibility check. A set of TIFF files alone does not establish the native camera, calibration and band-layout support needed by this workflow.
Thermal cameras supported by DJI Terra
A drone having a thermal camera does not establish native thermal-map compatibility. Match the exact model, original data and supported capture mode. Device names follow the current DJI manual.
| Aircraft or payload | Required processing route |
|---|---|
| Mavic 3T / 3TA | Thermal Infrared project with paired visible and thermal images |
| Matrice 3TD | Thermal Infrared project with paired visible and thermal images |
| Matrice 4T / 4TD | Thermal Infrared project with paired visible and thermal images |
| Zenmuse H20N / H20T | Thermal Infrared project with paired visible and thermal images |
| Zenmuse H30T | Thermal Infrared project with paired visible and thermal images |
On smaller screens, swipe the table horizontally to see every column.
Scope: DJI lists 2D thermal output. The current manual excludes M30T, Zenmuse XT-series cameras and third-party devices from this native thermal-reconstruction workflow.
Reference: DJI thermal supported-camera list and limitations.
Use original radiometric data
Import the visible-light JPG/JPEG photographs and original thermal R-JPEG files containing temperature data. The import manual requires at least ten images of each type.
Keep the matching image pairs and original names. A coloured screenshot cannot supply the temperature information embedded in the original recording.
Check the capture mode
DJI specifies High Gain or Low Gain for thermal reconstruction and excludes images captured in Super Clear mode.
Before a large job, test a sample from the exact model and settings you intend to use. Include the temperature-map and measurement requirements in the project brief.
Video import, Matrice 4D and Dock-derived data
For Dock projects, identify the aircraft and camera that captured the files. Describe how the original data will reach the processing workstation, then check the relevant photo, video or thermal requirements.
The current visible-light import manual lists video import for Mavic 3E, Mavic 3T, Matrice 4E, Matrice 4T, Matrice 4D and Matrice 4TD, using MP4 or TS. Terra extracts frames for subsequent reconstruction.
Reference: DJI supported video-import models and formats.
Evaluate the extracted frames
Check sharpness, scene coverage and useful overlap in the resulting image set. Smooth capture and a clear view of the subject help prepare a meaningful test.
Document whether your evaluation used photographs or extracted video frames, so later comparisons use equivalent inputs.
Prepare the intended output
For a reconstruction intended for measurement, review the positioning and quality checks associated with the dataset. Do not infer survey accuracy from a successful video import.
Use the target output settings and inspect the exported result before accepting the workflow for production.
Video-import support applies to the listed workflow. It does not mean that every video from any DJI or third-party camera will provide the same metadata or supported processing path.
RTK, PPK and positioning-data compatibility
Check the data and reference systems as carefully as the camera model. Plan the positioning workflow during acquisition rather than discovering missing observations afterwards.
RTK: preserve the recorded context
Keep positioning metadata and flight records alongside the captured data. Record the correction source, survey reference and the status reported during acquisition.
A drone carrying an RTK label does not by itself demonstrate the accuracy of a finished deliverable. Validate the result using the checks required for the project.
PPK: check the recorded observations
The DJI manuals describe local PPK using aircraft observations and corresponding base-station records. Supported file and protocol requirements vary with the selected project workflow.
Confirm that the necessary source files exist before relying on a later PPK calculation.
For P1, DJI describes a task folder containing photographs, GNSS observations and the TimeStamps.MRK image log for PPK post-processing.
Reference: DJI P1 positioning-data FAQ.
Keep the input and output coordinate references with the project record, including the vertical reference and units. Review a reference dataset before combining results from different sensors or survey dates.
Third-party cameras, consumer drones and LAS files
Use a specific test for equipment outside the documented native lists. File extensions, hardware brands and processing guarantees answer different questions.
Other cameras and consumer drones
DJI describes visible-light processing as potentially usable with other cameras, while withholding a guarantee for every dataset and requiring correct camera parameters.
For Mini, Air, consumer Mavic or non-DJI systems, evaluate original photographs, camera information and positioning data for the exact output you need.
Keep the test result as evidence for that configuration, rather than treating it as certification of the whole product family.
Existing LAS point clouds
DJI documents third-party LAS import in its detailed-inspection guidance. Confirm the coordinate system and intended project operation.
An existing LAS file and a native Zenmuse raw recording are different inputs. LAS import does not establish support for reconstructing the raw data of a third-party LiDAR payload.
Send a sample and the required processing stage when requesting a compatibility assessment.
Ground-based photographs need a separate assessment. DJI’s FAQ describes non-aerial photographs as theoretically usable for 3D with possible quality limitations, and excludes them from its 2D reconstruction guidance. Define the intended output before testing a handheld dataset.
For an unfamiliar camera, document the lens, image dimensions, metadata and any calibration information supplied by the manufacturer. Keep a representative dataset available so that a compatibility discussion can examine real files.
Flight planning and detailed inspection are separate checks
A supported reconstruction dataset does not automatically establish a direct control connection to that aircraft. Confirm the flight application and specialized mission workflow independently.
Check mission control and reconstruction separately. DJI’s current guidance limits Terra 5.x flight missions to specialized detailed-inspection and agricultural applications. Use the appropriate acquisition application for the aircraft and operation.
Reference: DJI Terra flight-function scope.
Detailed-inspection aircraft
DJI’s documented list includes:
- Phantom 4 RTK, with the controller arrangement specified by DJI.
- Mavic 2 Enterprise Advanced and Mavic 3E / 3T.
- Matrice 30 Series.
- Matrice 300 RTK with Zenmuse H20-Series payloads.
- Matrice 4E / 4T / 4D / 4TD.
Reference: DJI detailed-inspection model list.
Plan a Dock workflow
Dock 3 is paired with Matrice 4D or 4TD, with FlightHub 2 described for remote operations. Terra compatibility should be checked against the files captured by the aircraft.
Define acquisition, data transfer, reconstruction and result review as separate stages when planning a repeatable operation.
Check older mission instructions
Older support material may describe controller connections or general flight functions from earlier Terra releases. Match those instructions to the installed version before relying on them.
For a specialized inspection deployment, confirm the aircraft, controller, route format and release together.
A practical sensor-compatibility checklist
Use this sequence for a new drone, a payload replacement or a processing service. It turns a broad “is it compatible?” question into a clear assessment.
-
Name the exact equipment
Record the aircraft, camera or payload, lens, controller and firmware. Include the Terra release you will use. This avoids treating similar model names as identical configurations.
-
Describe the actual input
Identify original photos, complete LiDAR folders, multispectral image sets, radiometric thermal pairs or video. Record how the files were transferred and whether they were altered.
-
Choose the required deliverables
List the map, mesh, point cloud, vegetation index or temperature output required by the project. Include the downstream software and coordinate reference.
-
Check entitlement and workstation
Match the Terra edition and authorization mode to the intended tools. Check RAM, GPU and storage for the largest planned dataset, rather than only for a sample.
-
Process a representative sample
Test original data with the intended settings. Inspect import status, alignment, coverage, reports and exports. Preserve the test record and any unresolved issue.
-
Confirm before extending the workflow
Review the evidence before a larger capture campaign or hardware purchase. For an uncertain combination, send the sample description and requirements through our contact page.
DJI Terra drone and sensor compatibility FAQ
Open a question for a quick answer. The earlier sections provide the model lists, input requirements and official references.
Which drones should I consider for RGB mapping with Terra?
This guide covers the mapping workflows of Matrice 4E, Mavic 3E, Phantom 4 RTK and Zenmuse P1. Check the actual camera, saved data and required outputs, then evaluate a representative job.
Are Matrice 4E and Matrice 4T interchangeable for mapping?
Check the exact camera and workflow. The models serve different acquisition priorities, and the thermal route has its own camera and capture requirements. Use the relevant section rather than assuming a shared series name means identical capabilities.
Can I process Zenmuse L1, L2 and L3 data?
DJI documents these LiDAR workflows. Keep the original recording and check the applicable output and entitlement conditions. The L1, L2 and L3 notes above identify the differences.
Does Zenmuse L3 work on Matrice 350 RTK?
DJI’s current L3 FAQ names Matrice 400 as its compatible aircraft and specifies the L3 connector. Confirm the exact hardware combination before purchase.
Reference: Supporting DJI documentation.
Can I use Zenmuse L2 on Matrice 300 RTK?
DJI lists that combination with DJI RC Plus and the specified mounting arrangement. Review the current L2 instructions for the full setup.
Reference: Supporting DJI documentation.
Does Terra support M30T thermal reconstruction?
The current thermal-reconstruction manual excludes M30T. Its support in another function, such as detailed inspection, does not establish native thermal-map support.
Reference: Supporting DJI documentation.
Can I import only thermal photographs?
Native thermal reconstruction requires both visible and radiometric thermal inputs. Keep the matched original dataset and follow the import checks.
Reference: Supporting DJI documentation.
Can multispectral processing use only band images?
The native workflow requires RGB photographs along with the multispectral data. Check the complete capture sets and the bands needed by the chosen indices.
Reference: Supporting DJI documentation.
Can I use MicaSense RedEdge or Altum data in the native multispectral project?
The current DJI model list identifies Mavic 3 Multispectral and Phantom 4 Multispectral. RedEdge and Altum are not listed there. Request a specific workflow check before assuming TIFF files will provide native compatibility.
Reference: Supporting DJI documentation.
Does LAS import mean every LiDAR sensor is supported?
Check the processing stage. Importing an existing point cloud and reconstructing a native raw LiDAR recording are different workflows. Confirm the operation you need before selecting the sensor.
Can Terra import videos from any drone?
Use the exact supported video models and formats listed above. A video extension alone does not establish the camera metadata or documented import workflow.
How can I check a configuration that is not listed?
Send the exact equipment, Terra release, original-data description and required output list through our contact page. Include a representative sample description and any import or processing message.
For more processing and software questions, explore our complete DJI Terra FAQ.
Continue planning the complete workflow
Prepare the processing setup
Plan the workstation and installation before loading a large dataset from the selected drone or sensor.
Match the software to the job
Review the edition, deployment and reconstruction tools needed by the required deliverables.
Plan the equipment and resources
Discuss a proposed configuration with our team and use the official manuals for the selected hardware.
Check your drone, sensor and deliverables together
Send us the exact equipment and the output you need. We can help identify the documented processing route and the points that require a representative test.
Original guide prepared by Drone Emotions. Compatibility references were reviewed on 2 October 2026. Model lists refer to specific functions; confirm the applicable hardware, firmware, Terra release and entitlement for your project. Current manual requirements take precedence over older workflow descriptions. About Drone Emotions.