You processed it in DJI Terra.
Now how do you deliver it?

Short version: DJI Terra has no sharing feature. None. It is Windows desktop software that writes files to a folder and stops there, and its default 3D export formats are built for specialist software rather than for the person who paid you. Of the three common processing tools, this is where the gap between "finished" and "delivered" is widest — and where picking the wrong export format costs you the most.

Start from the awkward fact: Terra cannot share anything

WebODM can publish a task if you host it. Pix4D has a cloud with share links. DJI Terra has neither. There is no "share" button, no public project URL, no viewer your client can open. Terra reconstructs, writes to disk, and its job ends.

That is not a flaw — Terra is a processing application, not a delivery platform — but it does mean something concrete for you: 100% of your delivery is export decisions. There is no shortcut link to fall back on. What you choose to export, in what format, is exactly and only what your client will ever see.

It also means your client cannot open Terra themselves. The licence is tied to your account and device, so "I'll send you the project" is not an option that exists here.

Step 1 — Know which reconstruction you ran

Terra's output structure follows the reconstruction type you chose in the mission, and each type has a different delivery problem:

Results land in the output directory you set for the mission, with the orthomosaic under a map subfolder and the reconstructions under models, split by format. Terra's folder naming has shifted between versions, so open the output directory once and confirm before you script anything around it.

Step 2 — Do not deliver OSGB or B3DM to a client

This is the single most consequential choice on this page, and Terra makes it easy to get wrong because both formats sit in the export dialog looking equally reasonable.

• OSGB is a tiled mesh format from the OpenSceneGraph world. It is efficient and it is used seriously in the industry — by people running specific GIS and reality-mesh software. A general contractor, a housing association or a roofing client has no way to open it whatsoever.
• B3DM is a 3D Tiles format meant to be streamed by a web viewer, not opened as a file. Handing someone a folder of B3DM tiles is handing them the ingredients of a website without the website.
• OBJ is the one a human might manage — provided the .obj, its .mtl and the texture images stay together. Split them and your client opens an untextured grey shape.
• PLY is fine for a technical recipient and meaningless to anyone else.

The workable pattern for a 3D reconstruction: export B3DM or OSGB only if a specific technical recipient asked for it by name, and separately produce something viewable — publish the model to a web viewer and deliver the embed, so the client explores the reconstruction in a browser instead of downloading a format they cannot open.

Step 3 — The orthomosaic is your most deliverable output

For most inspection and survey clients the 2D map is what actually gets used, and it is the easiest thing Terra makes to hand over well. Terra writes a GeoTIFF that can run to several gigabytes at low GSD, so the same three-way split applies as with any large raster:

1. An interactive map for the client who wants to look around — served as tiles in a viewer, not sent as a file.
2. A Cloud Optimized GeoTIFF for the surveyor or GIS user:

   gdal_translate -of COG -co COMPRESS=DEFLATE result.tif ortho_cog.tif

3. A flat JPEG for the report, the email and the site meeting:

   gdal_translate -of JPEG -outsize 4000 0 -co QUALITY=88 result.tif preview.jpg

State the EPSG code and the GSD. If you flew with RTK or PPK, say so and say what the reference was — that sentence is what separates a map from a measurement, and Terra will not write it for you.

Step 4 — Thermal is a separate job from Terra

Worth stating plainly, because it catches people out with the M3T and M30T: Terra's 2D and 3D reconstructions are not a radiometric thermal product. A thermal mosaic looks like temperature but is not measurable temperature — the per-pixel radiometry lives in the original R-JPEG files, and stitching them into a mosaic is not the same as preserving it.

If your client's question is "how hot is that connector", the answer comes from the original radiometric images and DJI's thermal analysis tooling, not from a Terra mosaic. Deliver both if the job calls for it, and be explicit about which one carries the measurement. Presenting a stitched thermal image as if it were measurable data is the kind of mistake that surfaces later, in front of someone who checks.

Step 5 — Assemble the delivery

Because Terra gives you no link at all, this step is not a convenience here — it is the entire hand-over. You have an orthomosaic in two or three forms, possibly a viewable 3D model, maybe a point cloud for a specialist, your annotated stills and your findings. All of it has to become one address.

That is where DronePortal sits. It processes nothing — Terra remains your reconstruction engine and your workflow is untouched. What it provides is the thing Terra structurally cannot:

• A page your client can actually open, with the map or 3D viewer embedded in it
• Your original radiometric thermal images kept behind the client login, where per-pixel temperature stays available instead of being flattened into a picture
• Stills, findings and downloadable files beside the model rather than in a separate email
• One access code, and an address that still works next year

In practice: the actual clicks

1. First, create a public viewer URL — Terra gives you none. For the 3D reconstruction, export OBJ (with its .mtl and textures, see step 2) and publish it to an embeddable viewer such as Sketchfab or Polycam; copy that model page URL. Do not try to deliver OSGB or B3DM here — neither is a URL and neither opens for your client. For the orthomosaic, publish it to a tiled map viewer; the raw result.tif is a download, not something an iframe can show.
2. Paste the ordinary page URL; it gets converted on save. A Sketchfab model page, a Matterport /models/ link, a Kuula /post/ link and a Polycam capture page all refuse to be embedded as-is. DronePortal rewrites them to their embed form when you save, so you do not have to hunt for the embed code. One exception: skfb.ly short links are refused with a message — paste the full Sketchfab URL.
3. Dashboard → "+ New project". Pick an existing client or type a name and e-mail straight into the form. Give the project a name and a type, and name the first unit. On save DronePortal creates the client, the project and the unit, generates an 8-character access code, and drops you into that unit's edit screen.
4. Section 🗺 Viewers — one row per viewer. Choose the type (3D Visual, 3D Thermal, 2D Map, 360° Tour), write a label your client will read, and paste the URL. For Terra: the published mesh goes under 3D Visual, the orthomosaic viewer under 2D Map. Use "+ Add viewer" for the next one. Underneath, pick the Main viewer — the one that opens first — or leave it on "Automatic (first viewer)".
5. Section 📋 Documents & media — add the written part. "+ Add a document or link", set the type to File and use "↑ Upload" for your inspection report or findings PDF (pdf, jpg and png are accepted). Terra writes no quality report of its own, so whatever accuracy statement you provide is one you wrote — say what the GSD and the EPSG code were, and name the RTK/PPK reference if you used one. The NL/FR/EN label fields are the button text your client sees.
6. Section 📷 Photos — upload the originals, not a flattened copy. Thermal, visual and zoom. This matters more here than anywhere else: the original R-JPEGs from an M3T or M30T keep their per-pixel radiometry behind the client login, which is exactly what a Terra thermal mosaic cannot give you (step 4). Upload a selection, not the full card.
7. Section Portal — open it up. Set the status to Active, choose the language, fill in the capture date and, if the job needs one, an expiry date. The access code sits in this same section.
8. Hand over one link. The client URL is https://{your-subdomain}.droneportal.app/app/portaal/?code={ACCESSCODE}. One address plus one code — no account for your client, nothing to install, and no DJI software anywhere in the chain.

Open that link yourself in a private browser window before you send it. It is the only way to see what your client sees rather than what your logged-in session shows you.

Before you send: a checklist

• Nothing in the delivery is OSGB or B3DM unless a named recipient asked for that format
• If you exported OBJ, the .mtl and textures are in the same package
• EPSG code and GSD stated in writing; RTK/PPK reference named if used
• Thermal: it is explicit which files carry measurable temperature and which are illustration
• Every file has been opened by you on a machine without DJI software installed
• The client has a viewer, not just a download
• It is clear what is not included

Five ways a DJI Terra delivery goes wrong

1. Sending OSGB to a non-specialist. Technically the model, practically an unopenable folder.
2. A B3DM tile folder with no viewer. The ingredients of a website, delivered as a download.
3. An OBJ without its textures. A grey blob, and it reads as sloppy work rather than a missing file.
4. A thermal mosaic presented as measurement. It is not, and it will be checked eventually.
5. Assuming a link exists. Terra has none. If you have not exported it, it is not delivered.

Same workflow for other tools: delivering a WebODM project · delivering a Pix4D project. Related reading: delivering radiometric thermal images and why a PDF falls short for thermal.

Frequently asked questions

Ready to start?

Try step 5 on your next DJI Terra job

Try DronePortal free — no credit card required.