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.
Hardware planning | Drone Emotions
Build a practical processing setup for drone mapping, 3D reconstruction, LiDAR and Gaussian Splatting. Check the official requirements, understand what each component does and choose a workstation around your real projects.
Define what you need to deliver, how much data you process and how often the computer will run. These three answers make the hardware discussion far more useful.
Identify the exact computer, Windows edition, graphics card and installed Terra version. A powerful computer still needs the supported graphics architecture and a suitable driver.
Count the source data, required outputs, intermediate files and retained projects. A machine selected for occasional small jobs may need a different configuration for daily production.
Budget for memory, graphics, storage, cooling and expansion together. Evaluate a representative dataset before deciding which component deserves the next upgrade.
Check the current manual for the release you intend to install. Older articles can describe different memory, operating-system and graphics requirements.
| Component | Current DJI guidance |
|---|---|
| Operating system | Windows 10 or later, 64-bit |
| Processor | Intel Core i5 or later |
| Graphics card | NVIDIA GPU with compute capability 6.1 or higher; GTX 1050 Ti or later preferred |
| Graphics memory | At least 4 GB VRAM |
| System memory | At least 32 GB RAM |
| Available storage | At least 200 GB free; an SSD is recommended |
On smaller screens, swipe the table horizontally to see every column.
Reference: DJI Terra User Manual — Hardware Configuration.
Use the baseline to check compatibility. For frequent production, allow additional capacity for the operating system, other software and your largest planned jobs. The workstation profiles below are our planning suggestions and carry no DJI hardware certification or processing-time guarantee.
Choosing Windows for a new machine: we suggest Windows 11, 64-bit, on compatible hardware. Microsoft ended standard Windows 10 support on 14 October 2025; confirm any existing Windows 10 edition or extended-support arrangement with your IT team.
Reference: Microsoft Windows support lifecycle.
Planning your workflow from a Mac? Read our DJI Terra for Mac guide before choosing a processing setup. It explains the Windows workstation route, remote access considerations and what to check before relying on a virtual machine.
Select a starting profile, then adjust it to the largest project you expect to process. A laptop, compact desktop and full workstation with similar headline specifications can behave differently under sustained load.
For regular mapping jobs and moderate reconstruction workloads, with room to expand as your projects grow.
For a team processing regularly, retaining several active jobs and producing more than one deliverable per project.
For unusually large datasets or intensive scene workflows, after a test has established the actual resource requirement.
These are capacity-based buying guides prepared by Drone Emotions. The suggested numbers are not official DJI requirements or tested benchmark results. Ask the supplier to confirm the exact parts, compatibility, upgrade limits and suitability for your dataset before committing to a configuration.
Use the capacity references alongside your own job history. Record the software version, processing mode, source size and available memory so that comparisons remain meaningful.
System RAM serves the processing software, Windows and other applications. Check available memory before starting a large job. Installed capacity and immediately available capacity are different values.
For example, a computer with 64 GB installed and 8 GB already in use has approximately 56 GB available. This is an illustrative calculation, not a Terra performance measurement.
VRAM belongs to the GPU. Treat it as a separate specification when comparing computers: a large amount of system RAM does not turn a smaller graphics card into one with more dedicated VRAM.
Ask for the exact GPU model and its dedicated memory. A retailer’s total “graphics memory” figure may include shared system memory.
For visible-light reconstruction, DJI gives the following standalone references. They describe dataset capacity, with no completion-time promise.
| Available RAM | Standalone photo reference |
|---|---|
| 32 GB | 12,800 photographs |
| 64 GB | 25,600 photographs |
| 128 GB | 51,200 photographs |
On smaller screens, swipe the table horizontally to see every column.
In Terra 5.2.0 and later, standalone High Efficiency Mode with a custom core count can reach the manual’s cluster photo-capacity reference. Check the applicable mode before estimating the limit.
| Available RAM | Raw point-cloud input reference |
|---|---|
| 32 GB | 30 GB |
| 64 GB | 60 GB |
| 128 GB | 120 GB |
On smaller screens, swipe the table horizontally to see every column.
Terra 5.1 and later can process larger LiDAR inputs using block reconstruction, with a speed trade-off. Plan disk space separately.
Reference: DJI RAM and data-volume reference tables.
Look beyond a single headline specification. The processor, platform and cooling system should fit the duration and frequency of your processing work.
Compare the exact CPU generation, core configuration and cooling arrangement. The label “Core i5” alone cannot describe the performance of every processor sold under that name.
For a production machine, ask the supplier how it sustains long workloads and how its configuration has been evaluated with your intended software.
Check maximum supported RAM, usable memory slots, SSD connections and the power supply before choosing a motherboard or finished computer.
Leave a realistic upgrade route. Replacing a limited platform later can cost more than allowing for extra memory and storage at the beginning.
Our purchasing approach is to request a balanced, clearly specified system and validate it with a representative reconstruction. Avoid converting a CPU core count or a gaming benchmark directly into a promised Terra processing time.
Choose a supported graphics card with appropriate dedicated memory, then keep the card, driver and installed Terra release documented together.
Confirm the GPU architecture as well as its memory. NVIDIA’s compute-capability tables identify the architecture level of each listed model. Compute capability, CUDA core count and VRAM capacity are separate specifications.
Reference: NVIDIA CUDA GPU compute-capability tables.
DJI’s driver guidance specifies version 527.41 or later. A newer GPU may require a newer driver. Use the official NVIDIA driver selector for the exact card and Windows version.
Reference: Official NVIDIA driver downloads.
Check which GPU Terra actually detects, particularly on a laptop with integrated and dedicated graphics. A valid dedicated GPU must be available to the application.
DJI’s support guidance excludes AMD graphics cards from its CUDA-based processing requirement.
DJI describes multi-GPU reconstruction, while explaining that speed does not scale linearly with the number of cards. CPU, memory and disk performance also matter.
Before adding a second card, check slot spacing, cooling, power and the result of a suitable test.
Reference: DJI driver and GPU-detection guidance.
Use free space available at the time of processing. A drive’s advertised capacity must also accommodate Windows, installed software and the work already stored on it.
DJI recommends reserving project space using these source-data multipliers. When requesting several output types, add the corresponding reservations.
| Source and output | Recommended reservation |
|---|---|
| Photos → 2D reconstruction | 4 × source-data size |
| Photos → 3D reconstruction | 4 × source-data size |
| Photos → Gaussian Splatting | 6 × source-data size |
| LiDAR → 3D reconstruction | 6 × source-data size |
| LiDAR → Gaussian Splatting | 4 × source-data size |
On smaller screens, swipe the table horizontally to see every column.
Example: 50 GB of photos with both 2D and 3D outputs gives a 400 GB project-space reservation: 50 × (4 + 4). Keep room for the originals, cache, backups and other applications separately. DJI recommends at least 20 GB for local cache.
Reference: DJI storage and cache planning guidance.
Keep active projects on storage sized for the job. Plan where source data, intermediate results and final exports will live before reconstruction starts.
When comparing SSDs, discuss sustained write performance, capacity and the number of simultaneous active projects with your supplier.
Decide which intermediate files you need for reprocessing and how long to retain them. Archive finished jobs according to your client and business requirements.
Keep a separate backup strategy. Additional free space on the processing drive does not provide a second copy of the dataset.
Workstation planning becomes clearer when the quote names a workflow rather than only a drone model. Send the source-data type, largest job and required output list.
Start with image count, geographic coverage and the outputs you need. Include the software used for checking and delivering the orthomosaic or elevation result.
Test a sample that resembles the normal overlap, image quality and terrain in your jobs. Keep the reconstruction settings with the test record.
Plan for the reconstruction and the later viewing or editing stage. List the required mesh, point-cloud and export formats before calculating project retention.
A dense urban scene and an open site can create different workloads. Use a representative scene for the workstation evaluation.
Use the size of the raw input and the desired point-cloud products to prepare the hardware discussion. Include ground classification, elevation outputs and any later editing tools in the workflow description.
When large jobs are common, discuss the practical balance between memory, block processing and working storage.
DJI provides Preview, High and Extra High quality options. Plan for the selected quality, block count, output formats and retained intermediate files; these affect the processing and storage workload.
Evaluate a scene with the intended deliverable settings, then choose the workstation and appropriate Terra entitlement.
Choose the form factor around where you work and how long processing runs. The best specification is the one you can operate and maintain reliably.
A laptop can suit field review and mobile work when its exact configuration supports Terra. Check the dedicated GPU, memory expansion limits, SSD capacity and power arrangement.
Request a sustained-load evaluation. Portability, fan noise, temperature and limited upgrade space are practical considerations for a machine that also handles reconstruction.
A desktop usually provides more flexibility for cooling, storage and future upgrades. Check the finished configuration rather than assuming every tower has spare slots or a suitable power supply.
For daily processing, discuss service access, replacement parts and the time needed to recover the workstation after a component failure.
A useful comparison includes the exact parts, the same Terra dataset and settings, total purchase cost and the upgrade path. Compare results from equivalent tests rather than processor and GPU names alone.
Consider a cluster when your job sizes or throughput targets justify the additional infrastructure. Its performance depends on the deployment as a whole.
DJI cluster reconstruction uses LAN communication and shared storage. The manual recommends stable IP addressing, read access to source data, read/write access to project outputs and local SSD cache on each device. Cache must not be placed on a NAS or network drive.
Reference: DJI cluster network and shared-folder configuration.
Ask your IT team to document device names, network paths and folder permissions. Confirm that every participating computer can access the required data and project location.
Test the shared-storage arrangement with a real sample before loading a production dataset.
Compare network and storage throughput alongside worker specifications. An additional computer adds resources, but also adds administration and data movement.
Record the installed versions and measure a comparable task before deciding whether to expand the cluster or upgrade one workstation.
Verify the current processing entitlement and the supported project type in our DJI Terra License Guide. For a proposed deployment, send us the computer count, source-data size and network/storage arrangement.
Use a repeatable test to turn a hardware discussion into an informed decision. Keep the data and settings so you can evaluate future changes.
Write down the CPU, GPU model and dedicated VRAM, installed RAM, Windows edition, driver and Terra version. This gives the supplier or support team a useful starting point.
Use a job that reflects normal image quality, scene complexity and output needs. A small sample can confirm the workflow; use a suitably sized trial to assess production capacity.
Keep quality, processing mode, requested formats and output paths consistent. Changing these settings between computers makes the comparison less useful.
Review free memory, project space and background applications before the run. Confirm that the GPU is detected and that the output location can be written to.
Save the completion status, elapsed time, outputs and any resource or error observations. Inspect the result quality as well as the processing duration.
Identify the limiting resource from the test and logs, then compare the relevant upgrade options. Retest a production release or driver change with the same reference job.
Check the specific message before buying an upgrade. A storage permission issue and an exhausted resource call for different actions.
For a step-by-step investigation, use our DJI Terra reconstruction errors and troubleshooting guide. Work through the relevant checks for memory, GPU drivers, storage and project data before deciding whether a hardware change is needed.
| Code | First item to check |
|---|---|
| 1012 | NVIDIA driver version |
| 1018 | Free project-storage space |
| 4002 | Available RAM |
| 4003 | Dedicated GPU memory |
| 74 | Storage read/write permissions |
On smaller screens, swipe the table horizontally to see every column.
These codes identify a starting check, not a complete diagnosis. Preserve the exact error and logs before changing the setup.
Reference: DJI Reconstruction Exception Guidelines.
When requesting help, send the error text, Terra version, workstation specifications, project type and the stage at which processing stopped. Include a recent change, such as a driver update or a new output path, if it is relevant.
Open a question for a short, practical answer. Use the earlier tables when preparing a specification or reviewing an existing computer.
The official requirements specify 64-bit Windows. Plan a compatible Windows workstation or discuss access to one; do not assume that a Mac configuration or a virtual machine has been validated for your intended workflow.
Reference: Supporting documentation.
Use the minimum for compatibility screening, then consider your available memory, largest dataset and other applications. The suggested profiles above allow headroom; validate the final amount against a representative job.
More capacity can help a job fit into memory, but it does not guarantee a particular speed increase. Keep the dataset and settings consistent when evaluating a memory upgrade.
Treat RAM and dedicated VRAM separately in the quote. Check both capacities and the exact graphics card; adding system memory does not increase the dedicated memory installed on the GPU.
DJI support describes NVIDIA CUDA-based processing and excludes AMD graphics cards. Confirm the dedicated GPU model before purchase. The graphics-card requirement is separate from choosing a processor.
Reference: Supporting documentation.
Evaluate the whole computer and the failing or slow processing stage. A GPU purchase alone will not resolve a full project drive, insufficient system memory or an unsuitable platform.
The profiles describe capacity and planning priorities. Ask a supplier to provide exact component specifications, support arrangements and an evaluation appropriate to your data before choosing a model.
Use the output-specific reservations above, add them when combining outputs and include the source data, cache and retained jobs in your overall storage plan. Review free space before each large run.
DJI requires local cache storage for the cluster and recommends a local SSD. Shared source and output folders serve a different purpose. Ask IT to confirm the final storage arrangement.
Reference: Supporting documentation.
DJI’s support guidance says the remote setup must let Terra access GPU resources. Test the actual remote session, graphics detection and representative reconstruction rather than assuming every remote-access configuration behaves identically.
Reference: Supporting documentation.
A larger workstation provides resources for processing. Evaluate accuracy through your acquisition, control, coordinate-system and quality-checking workflow; a hardware upgrade by itself is not an accuracy guarantee.
Send the largest typical job, source-data type, required outputs, project frequency, existing specifications and whether you need a laptop, desktop or cluster. Include your budget and any IT restrictions through our contact page.
Explore our complete DJI Terra FAQ for additional software and processing questions.
Match the edition and deployment to your intended work before activating a processing computer.
Use official installers and review the release documentation before changing a production installation.
Review the tools and tutorials so that your hardware plan includes the outputs and processing stages you actually need.
Send us your current specifications, largest dataset and required deliverables. We can help clarify the software requirements and the questions to address with your workstation supplier.
Original guide prepared by Drone Emotions. Official requirements are linked to DJI documentation; the workstation profiles and purchasing checklists are our editorial suggestions. Documentation reviewed on 2 October 2026. Verify the applicable release and exact computer configuration before purchase. About Drone Emotions.