SpeedyDrone Canada · Living reference
DJI Enterprise Payload Matrix
Matrice 400, Matrice 350 RTK and Matrice 300 RTK support for H30/H30T, L3, L2, P1, H20 Series, S1, V1 and third-party payload routes.
DJI product image via SpeedyDrone
A checkmark is only the starting point. The correct mount, remote controller, firmware, app functions and mission workflow can still differ. Use the notes in each row before moving a payload between aircraft.
This page is designed as a reference, not a one-time launch comparison. It separates what DJI currently lists, what works only with a stated condition, and what is absent from the current support documents reviewed. Recheck it whenever aircraft, controller, payload or Payload SDK firmware changes.
Quick-reference DJI Enterprise payload compatibility matrix
Start here when deciding whether a DJI payload belongs on Matrice 400, Matrice 350 RTK or Matrice 300 RTK. The table treats “compatible” as an officially documented platform relationship, not merely a connector that can be attached.
| DJI payload | Matrice 400 | Matrice 350 RTK | Matrice 300 RTK | Deployment note |
|---|---|---|---|---|
| Zenmuse L3 | ⚠️ Conditional | — Not listed | — Not listed | M400 only. Use the dedicated L3 single-gimbal connector and connect it to E1 for the documented accuracy path. |
| Zenmuse H30 | ✅ Official | ✅ Official | ⚠️ Conditional | M300 deployment requires DJI RC Plus and current compatible firmware. |
| Zenmuse H30T | ✅ Official | ✅ Official | ⚠️ Conditional | The camera can move across all three platforms, but aircraft-specific inspection and transmission functions do not automatically move with it. |
| Zenmuse L2 | ⚠️ Conditional | ⚠️ Conditional | ⚠️ Conditional | M350/M300 use single downward mounting and the specified right-side underside USB-C connection for the documented mapping-accuracy path. M300 also requires RC Plus. |
| Zenmuse P1 | ✅ Official | ✅ Official | ✅ Official | Supported across the three platforms; validate the lens, mission settings, storage and processing workflow separately. |
| Zenmuse H20 | — Not listed | ✅ Official | ✅ Official | Legacy H20 documentation may emphasize M300, while the current M350 aircraft specification lists H20. |
| Zenmuse H20T | — Not listed | ✅ Official | ✅ Official | Do not infer M400 support from the H30 Series. The current M400 compatibility list does not include H20T. |
| Zenmuse H20N | — Not listed | ✅ Official | ✅ Official | The current M350 platform specification includes H20N; older H20N pages may still be written around M300. |
| Zenmuse L1 | — Not listed | ✅ Official | ✅ Official | L1 remains a legacy M300/M350 path. M400 buyers should evaluate L2 or the M400-only L3 rather than assume migration. |
| Zenmuse S1 | ✅ Official | ⚠️ Conditional | ⚠️ Conditional | DJI specifies RC Plus for M350/M300 use and current firmware. Lighting performance also varies by aircraft. |
| Zenmuse V1 | ✅ Official | ⚠️ Conditional | ⚠️ Conditional | RC Plus/current firmware conditions apply to the older platforms; real-time broadcasting and some audio functions vary by aircraft. |
Interpret “—” narrowly: DJI did not list the combination in the current official documents reviewed on the verification date. It does not prove that an adapter can never be engineered, and it is not approval to fly an undocumented combination.
Mounting architecture: compatibility is not just a model name
Aircraft support tables hide the physical architecture. Matrice 400 replaces the older upward-gimbal path with an M400-specific third connector and a dedicated L3 connector. Matrice 350 RTK and Matrice 300 RTK retain upward and combined mounting configurations. That difference affects line of sight, clearance, weight distribution and which mission combinations are practical.
| Mounting option | Matrice 400 | Matrice 350 RTK | Matrice 300 RTK |
|---|---|---|---|
| Single downward gimbal | ✅ | ✅ | ✅ |
| Dual downward gimbals | ✅ | ✅ | ✅ |
| Upward gimbal | — DJI says no | ✅ | ✅ |
| Third gimbal connector | ✅ M400-specific | — | — |
| Dedicated L3 single connector | ✅ Connect through E1 | — | — |
This table describes DJI's published mount families, not approval for every payload combination. Total mass, individual mount limits, clearance, power, centre of gravity and endurance still require system-level validation.
A deployable system needs all four layers. A technically supported camera can still be the wrong choice if it blocks the required second payload, changes the controller, removes an aircraft-specific function or produces data your team cannot process. Treat the matrix as a shortlisting tool, then validate the complete operating system.
The same payload does not create the same workflow
The H30/H30T, L2, P1, S1 and V1 span more than one aircraft, but the operational experience is not identical. Four examples explain why a procurement team should avoid describing compatibility as “plug and play.”
H30/H30T: one payload family, three aircraft generations
DJI lists the H30 Series for Matrice 400, Matrice 350 RTK and Matrice 300 RTK. On M300, DJI specifically requires the RC Plus path. The M400 also adds platform functions that do not become M350/M300 features simply because the same H30T is attached. For example, DJI's current power-line inspection workflow is documented for Matrice 400 with H30 Series. Plan the aircraft, controller, application and function together.

L2: mounting can affect mapping accuracy
DJI's L2 FAQ publishes different mounting guidance by aircraft. On Matrice 350 RTK and Matrice 300 RTK, use the single downward mount and connect the specified USB-C cable to the aircraft's right-side underside port. On M400, L2 can use the single downward or either position of the dual downward connector, but DJI warns that carrying another payload on the dual mount may reduce mapping accuracy. “Compatible” therefore does not mean every mount produces the same result.
S1 and V1: multi-platform hardware, platform-dependent output
Zenmuse S1 and V1 are current multi-platform functional payloads, not M400-only accessories. But DJI publishes different output or feature behaviour by platform. S1's stated illumination at 100 metres is higher on M400 than on M350/M300. V1's M400 workflow includes aircraft-dependent capabilities such as real-time broadcasting, automatic gain control and different text-to-speech options. Confirm the exact feature needed by your public-safety or site-communication SOP.
P1: compatible hardware still needs a complete mapping chain
P1 appears across all three aircraft columns. That does not preserve the same endurance, mission-planning options, lens choice, base-station arrangement, storage or photogrammetry output. A fleet migration should include a representative capture and processing test, not only a successful power-on check.
Third-party payload support: why there is no single “yes”
All three aircraft families support third-party development routes, but the hardware generation and software requirements differ. A third-party payload should be identified by its exact mechanical interface, adapter generation, Payload SDK version, accessory firmware and required functions. “PSDK compatible” without those details is not a sufficient purchasing specification.
| Platform | Current integration routes | Main condition |
|---|---|---|
| Matrice 400 | E-Port V2 Development Kit, SkyPort V3, X-Port and PSDK; Manifold 3 for specified compute/advanced functions | Use the current M400 interface and capability matrix. Older X-Port/SkyPort V2 designs require specified accessory firmware and current PSDK migration work. |
| Matrice 350 RTK | E-Port Development Kit, X-Port, SkyPort V2 and certified PSDK payloads | Validate the certified payload, accessory firmware, PSDK version, aircraft firmware and the exact capability required. |
| Matrice 300 RTK | Older E-Port/OSDK-era connection routes, X-Port, SkyPort V2/SkyPort V1 and PSDK payloads | Generation and firmware matter. Do not assume an M300 integration can move directly to M350 or M400 unchanged. |
DJI's current developer documentation explicitly gives firmware thresholds for some X-Port and SkyPort V2 devices moving to M400, and its PSDK release notes continue to change. For a deeper architecture explanation, use SpeedyDrone's Matrice 400 E-Port V2, PSDK, SkyPort V3 and X-Port guide. It separates the physical connector, adapter, gimbal-development and software layers.
Should an existing M350 RTK owner move to Matrice 400?
Payload reuse can strengthen the M400 business case, but it should not be the only decision. Existing H30/H30T, L2, P1, S1 and V1 investments have a documented path to M400. L3 creates a new M400-only geospatial path. H20/H20T/H20N and L1, however, remain current M350/M300 payloads and are absent from the M400 list reviewed.
Record model, serial, current firmware, controller, mount and third-party adapter/PSDK version. Do not group H20 and H30 families together.
List required Pilot 2 functions, FlightHub 2 behaviour, live video, route types, RTK source, output format and processing software.
M400 uses its own battery, charger, controller and connector ecosystem. DJI says M400 and M350 accessories are not generally interchangeable.
Verify mounting, clearance, data, accuracy, transmission, endurance, failsafe behaviour and operator SOPs with the actual planned configuration.
If the fleet depends on H20T, H20N or L1 and the mission already works, keeping M350 RTK can be the lower-risk path. If the mission needs L3, the M400 connector architecture, heavier payload capacity or M400-specific workflows, the newer platform can justify a system change. SpeedyDrone's Matrice 400 vs Matrice 350 RTK buyer's guide covers the broader upgrade decision.
Current SpeedyDrone payload pages
These are the exact SpeedyDrone listings for current payloads referenced above. Availability, lead time and final enterprise configuration should be confirmed before ordering. H30T links to the standalone payload, not the separate sold-out M350 + H30T bundle.
Zenmuse H30TThermal and visual inspection payload →
Zenmuse L3Matrice 400 LiDAR payload →
Zenmuse L2Multi-platform LiDAR payload →
Zenmuse P1Full-frame photogrammetry payload →
Zenmuse S1Enterprise spotlight payload →
Zenmuse V1Enterprise loudspeaker payload →
For aircraft and mounting hardware, see the Matrice 400 collection, Matrice 350 RTK collection, Enterprise payload collection and DJI Enterprise accessories. The Matrice 400 SP Plus Combo is the exact current aircraft listing; batteries, charging, connectors and payloads must still be scoped as a complete system.
Frequently asked questions
Is Zenmuse L3 compatible with Matrice 350 RTK or Matrice 300 RTK?
No current DJI document reviewed lists L3 for M350 or M300. DJI specifies Matrice 400, the dedicated L3 single-gimbal connector and the E1 connection for the documented mapping-accuracy path.
Can Zenmuse H30T be used on Matrice 300 RTK?
Yes, with conditions. DJI lists H30T for M300, M350 and M400, and specifies DJI RC Plus/current compatible firmware for M300 use. Aircraft-specific functions still differ.
Does Matrice 400 support Zenmuse H20T?
H20T is not in DJI's current M400 compatible payload list reviewed on September 22, 2026. DJI currently lists H20T for M350 and M300. Do not treat the newer H30T's M400 support as proof of H20T support.
Does Zenmuse L2 work the same on M400, M350 and M300?
No. It is listed for all three, but DJI publishes different mounting guidance. M350/M300 use the single downward mount and specified USB-C connection for the documented accuracy path; M400 can use its single or dual downward mount, with a warning about mapping accuracy when another payload shares the dual connector.
Are Zenmuse S1 and V1 only for Matrice 400?
No. DJI lists both for M400, M350 and M300, with RC Plus/current firmware conditions on the older platforms. Output and feature behaviour can still vary by aircraft.
Can I move a PSDK payload from M350 to M400?
Potentially, but not automatically. DJI documents migration paths for specified X-Port and SkyPort V2 firmware/PSDK combinations. Confirm adapter hardware, payload firmware, PSDK version, mount, power and each required function before deployment.
Does a compatible payload preserve every Pilot 2 or FlightHub 2 function?
No. Hardware compatibility does not guarantee identical intelligent features, route types, video workflows, remote operations or data outputs. Validate the specific mission workflow on the target aircraft.
Which aircraft is best if I already own H20T, H20N or L1?
M350 or M300 remains the documented path for those legacy payloads. M400 may still be valuable for other reasons, but the current M400 list does not include them, so include a payload replacement and workflow test in the upgrade budget.
How often should this matrix be rechecked?
Recheck before purchase or deployment and after any relevant aircraft, controller, payload or PSDK firmware update. The verification date on this page is a snapshot, not a lifetime certification.
Change log
September 22, 2026: Initial matrix verified against current DJI aircraft, payload and Payload SDK documentation, plus current SpeedyDrone product routes.
Request a DJI Enterprise payload fit check
Send SpeedyDrone your aircraft, exact payload, controller, mount, firmware, required Pilot 2/FlightHub 2 functions and mission output. We can help map the documented product path and identify the questions that need a payload manufacturer or integration test before purchase.
Contact SpeedyDrone about your payload configuration →Primary technical sources
- DJI Matrice 400 FAQ and specifications: payload list, mounting options, third connector, L3 connector, accessories and developer ecosystem.
- DJI Matrice 350 RTK specifications and DJI Matrice 300 RTK product documentation: current and legacy payload/mount lists.
- H30 Series FAQ, L2 FAQ, L3 FAQ, S1 FAQ and V1 FAQ: platform-specific conditions.
- DJI PSDK development-platform compatibility list and aircraft port guide: third-party interface and firmware boundaries.