Model delivery · Desktop and web

Viewing and Sharing DJI Terra Models: DJI Reality and TerraGS

Choose a practical route for reviewing Terra outputs on a PC, handing model files to clients or planning a custom browser viewer.

DJI Gaussian Splatting example showing a detailed temple model against a dark background
Official DJI Gaussian Splatting example. This illustrates a model type; it is not a screenshot of a hosted collaboration portal. Source: DJI Terra.

Choose how people need to access the model

Viewing a DJI Terra model on a workstation, sending model files to a client and offering a browser link are different delivery tasks. Choose the route by asking who will open the data, on which device and for what purpose.

Desktop review and browser delivery
Requirement Route to evaluate What to plan
A colleague reviews an exported model on a Windows PC DJI Reality A compatible export, local access to the model files and a suitable workstation.
A client navigates Terra-exported 3D Gaussian Splatting data in a browser A custom CesiumJS application using the TerraGS extension Development, hosting, browser testing and a clear model update process.
Contractors need comments, issue tracking or approvals A collaboration solution with those verified features Named users, permissions, annotation behaviour, revision tracking and a trial using the actual workflow.

On smaller screens, swipe the table horizontally to read every column.

DJI Reality is a PC model viewer. The TerraGS extension is a developer component for CesiumJS. Neither should be presented as a ready-made online collaboration portal with project accounts, comments and approvals.

Use DJI Reality for desktop model review

DJI describes Reality as a lightweight PC viewer. It currently supports Windows and can be used after installation without signing in. Its role is to open supported model data for review, including basic route roaming.

Model families supported by DJI Reality
Model family Documented formats Planning consideration
3D mesh B3DM, OBJ Keep the complete export and its associated resources together.
Point cloud LAS, PNTS Test a representative delivery on the recipient’s workstation.
3D Gaussian Splatting TerraGS Use a compatible Terra export and check the installed viewer version.

On smaller screens, swipe the table horizontally to read every column.

The documented loading rule is one data type per Reality project. Different formats within that type can be combined when their source data share the same coordinate system.

Compatibility and operation: DJI Reality User Manual. Platform and sign-in information: DJI Terra / Reality FAQ.

Prepare a dependable desktop handover

  1. Confirm the recipient’s workflow

    Ask whether the person needs visual review, engineering measurements or an editable model in another application. Agree which output is suitable before building a large delivery.

  2. Export and keep dependencies together

    Prepare the selected model family in Terra. Preserve the export folder and supporting resources, and include a note identifying the project, model revision and coordinate references.

  3. Test outside the production project

    Open a copy of the package on the intended review computer. Check placement, completeness, appearance and navigation, including locations important to the recipient.

  4. Deliver files with a short readme

    State which viewer and version were tested, how the package is organised and what the model is intended to support. Ask the recipient to acknowledge that the files open correctly.

A portable handover should be tested from its delivery location. A package that works only because it can find resources elsewhere on the production workstation is not ready for a client.

Start from our software download guide or DJI’s official download page. Keep release notes with the project record when version compatibility matters.

Use TerraGS when a web integration is required

The TerraGS 3D Gaussian Splatting Extension for CesiumJS is a rendering module for developers integrating Terra-exported 3DGS data into a CesiumJS web application. It is the integration component; a usable customer portal still needs to be designed, deployed and maintained.

Before commissioning development, agree on these responsibilities:

  • Hosting: where the model data and application will reside, and who manages capacity and ongoing costs.
  • Access: whether the model is public or restricted, who controls users and how access is withdrawn when a project ends.
  • Performance: which browsers, devices, network conditions and representative datasets will be tested.
  • Updates: how revisions are published, identified and checked without confusing a client about which model is current.
  • Extra functions: whether annotations, measurements, comments or approvals are required, and which component provides each one.

Do not assume that a desktop export automatically creates a public URL. Ask for a small working pilot that uses your own data and the intended recipient device.

Developer reference: TerraGS-CesiumJS Web Plugin documentation. Background: Gaussian Splatting workflow, licenses and outputs.

When clients need comments and approvals

For a construction review, specify the behaviour in plain language: “A contractor opens the current model, places a comment at a location, assigns an issue and sees whether it has been resolved.” Treat each part as something the proposed solution must demonstrate.

Use a short acceptance exercise: invite a test user, open the intended model revision, create a location-based issue, respond from another account and confirm how the record is retained after a model update. This reveals requirements that a simple rendering demonstration cannot settle.

Share that brief with us before selecting software. We can help clarify the Terra output and viewing requirements; any portal development or third-party collaboration capability should be confirmed in its own scope.

Keep visual review and survey acceptance distinct

A model can be persuasive to navigate while still being unsuitable for a particular measurement task. Specify the required tolerance, coordinate references and validation evidence separately from the viewing experience.

For engineering use, ask which deliverable should be assessed in the receiving application. Keep the relevant quality evidence with that dataset rather than treating the appearance of a mesh or Gaussian model as proof of accuracy.

These guides cover the supporting decisions: quality reports, coordinate systems and height references, and Terra outputs.

Model viewing and sharing: common questions

Can a client open DJI Reality in a browser?

Reality is documented as a Windows PC application. For browser delivery, evaluate a web application and a compatible data workflow.

Does TerraGS provide hosting and user accounts?

The documented TerraGS extension is a CesiumJS rendering component. Specify hosting, authentication, permissions and ongoing maintenance separately in the web project.

Can I mix meshes, point clouds and Gaussian data in one Reality project?

The documented project rule is one data type. Use the compatibility section above and the current manual when preparing the package.

Should I buy a Terra license just to send a client a model?

First define the output and how the client will access it. Check the entitlement required to produce that output separately from the software or service used to view it.

What information should I send for advice?

Describe the model type and size, intended viewers and devices, public or restricted access, update frequency and any requirements for comments, measurements or approvals.

How will your client use the model?

Tell Drone Emotions who needs access, which devices they use and whether the task is viewing, measurement or collaboration. We can help clarify the data workflow and software requirements.

Official DJI references

This guide provides practical planning advice alongside the linked manufacturer documentation. Software functions and license terms can change; check the documentation for the version you intend to deploy. DJI product images are credited to DJI.