Why your DJI Mini 5 Pro skips photos on mapping flights (and how to fix it)
On our first mapping flight with a DJI Mini 5 Pro, the route planned 154 photos. We got 89. Front overlap fell from the planned 85% to 57%, and nothing warned us: not DJI Fly, not the remote controller, not the flight log.
Here is what happened, how to check whether it has happened to you, and the simple rule that fixes it, whichever planning tool you use.
Short answer: with 50 MP photos, the Mini 5 Pro needs about 5 seconds to save each one (we measured 5.2 s). If your route asks for photos faster than that, the drone skips the ones it has no time for. Keep the speed at or below distance between photos ÷ 5 s. With 8 m between photos, that is 1.6 m/s.
What happened on our first mapping flight
We planned a grid over a building plot in Norway: 154 photos, 7.3 m apart, with 85% front overlap, flown at 4 m/s. That works out to one photo every 1.8 seconds.
The drone flew the whole route and the mission looked normal. But the memory card held 89 photos, about 21 m apart, and the front overlap was 57%. We only found out when the photos were processed.
Why it happens: about 5 seconds per 50 MP photo
A full-resolution Mini 5 Pro photo is 8192 × 6144 pixels, about 32 MB as a JPG. Saving it takes about 5 seconds. Measured over the whole series, the interval was 5.17 s. (EXIF timestamps only have whole seconds, so a single pair of photos shows 5 or 6 s.)
DJI Fly does not slow the drone down to wait for the camera. The camera takes the next photo when it is ready, and the photos it has no time for are skipped without a warning. Our route asked for a photo every 1.8 s, so the drone got roughly every third one.
A later test with denser routes showed the same thing: the photos came every 5 seconds regardless of the waypoints, and only 45 of 108 waypoints got a photo. The camera’s rhythm decides where your photos end up, not the waypoint list.
How to tell if it happened to you
Look at the photos, not the flight log. There are three signs:
- Fewer photos than planned. Count the files and compare with the number of photos in your plan.
- A perfectly even rhythm. Read the capture time (DateTimeOriginal) of each photo. Photos taken at the waypoints have uneven intervals, because the distance changes at turns and transits. A steady 5-second rhythm, whether the drone covered 21 m or hovered, means the camera set the pace.
- Gaps that are whole multiples of the planned spacing. Our photos were about 21 m apart against a planned 7.3 m, roughly three times the spacing.
Any EXIF tool will show this. With ExifTool, for example:
exiftool -T -FileName -DateTimeOriginal -GPSLatitude -GPSLongitude -n /path/to/photosMini5Planner’s free Calibrate / check flight tool does the same from the photo folder. It shows the actual photo interval and the front overlap for every pair of photos, and marks the weak spots on the map.
The fix: let the camera set the speed
The rule is simple:
max speed = distance between photos ÷ time to save one photo
For the Mini 5 Pro with 50 MP photos, use 5 seconds. With 8 m between photos, 8 ÷ 5 = 1.6 m/s. The distance between photos follows from altitude and front overlap: the higher you fly, the larger each photo’s footprint, and the further apart the photos can be at the same overlap.
With the speed capped like this, we flew the same site again, once east–west and once north–south. Both flights delivered 105 of 105 photos, 8.2 m apart, with 84% measured front overlap against the 85% we planned.
| First flight | Speed set by the camera | |
|---|---|---|
| Photos | 89 of 154 planned | 105 of 105 (both flights) |
| Distance between photos | about 21 m (7.3 m planned) | 8.2 m |
| Front overlap | 57% (85% planned) | 84% (85% planned) |
Fly higher, not slower
Slowing down works, but it makes a long route even longer. Often the better fix is to fly higher. A larger footprint gives more distance between photos, which raises the speed limit and shortens the route. The trade-off is a coarser ground sampling distance (GSD), so check that it is still fine enough for the job.
What about other drones and photo modes?
Every camera has its own save time. We have only measured the Mini 5 Pro with 50 MP photos, not its other photo modes and not other drones. If you fly a Mini 4 Pro, an Air 3 or 3S or a Mavic, check the timestamps from your first mapping flight the same way. Mini5Planner uses an estimated 2 seconds for those drones until you calibrate them from your own photos.
How Mini5Planner handles it
- It works out the distance between photos from the camera, altitude and overlap, and caps the mission speed at that distance divided by the camera’s save time (5.2 s for the Mini 5 Pro), rounded down to the nearest 0.1 m/s.
- The speed written to the KMZ is the speed the drone can actually fly, and the flight time and battery estimates use it.
- When it lowers the speed you asked for, the statistics panel says so and explains why.
- After the flight, Calibrate / check flight reads the photo metadata and shows the real photo interval and overlap. If the camera was the bottleneck, you can save the measured interval as that drone’s camera limit.
The step-by-step process, from drawing the area to loading the route in DJI Fly, is in our guide to flying a grid mapping mission with the Mini 5 Pro. More about the app is on the Mini5Planner page.