Load a custom map into DJI Pilot 2

The need

A fire plan, a site plan, an archive orthophoto: the information often exists only as an image, and it is not in DJI's basemap. Pilots fall back on paper or a second screen.

What DJI does not allow

No documented protocol lets you push a basemap to a remote controller. Offline map distribution exists on the dock side, not the controller side. Importing stays a manual step inside Pilot 2.

How we know. Exhaustive search across the 234 files of DJI's official cloud API documentation, English and Chinese versions, on 31 August 2026. The patterns mbtiles, geopdf, offline map, raster and basemap appear only in the dock branch: zero occurrences on the controller side.

This is not a documentation gap, it is an absent protocol. If DJI adds one, this page will age: its date and method are here so you can check for yourself.

⚠️ An honest nuance: even on the dock side, the protocol is described only in the FAQ, with no dedicated API page.

What works today

1. Convert your georeferenced PDF into an .mbtiles file.
2. Copy the file into the Download folder on the remote controller, by cable or microSD card.
3. Import it from DJI Pilot 2: it becomes a custom basemap.

Which hardware

Only controllers running DJI Pilot 2 accept a custom map: RC Plus, RC Plus 2 and RC Pro Enterprise.

⛔ Consumer aircraft fly with DJI Fly and do not support it. A Mini, an Air or a non-enterprise Mavic will load no MBTiles, whatever the file.

What about vector?

A raster basemap is frozen: it shows the ground, not today's mission. An operation perimeter, an exclusion zone or points of interest belong to another route, that of map elements, which travel both ways between a platform and Pilot 2.

That is a separate subject, and raster stays useful for what exists only as an image: a scanned plan, an archive orthophoto, a plan supplied by a client.