Knowing how many photos for drone mapping a site will take is a planning question you can answer before you leave the office. The count drives battery swaps, card space, upload time and how long the field day runs. There is no universal number, because the count depends on the site, the camera, the altitude and the overlap you choose. What you can do is estimate it with a simple, transparent calculation, then add a realistic allowance for edges, turns and repeat passes.
This post covers that estimate only. For choosing overlap percentages, see our guide to drone mapping overlap settings. For the math behind pixel size and altitude, see ground sampling distance (GSD) in drone mapping.
What decides how many photos a drone map needs?
Four inputs set the image count for a grid mission:
- Site size and shape. The area you must cover, plus a buffer past the boundary so the edges are fully captured.
- Image footprint on the ground. How much ground one photo covers. That comes from the camera's image width and height in pixels multiplied by your GSD, which depends on altitude, focal length and sensor.
- Front overlap. How much each photo shares with the next one along the flight line.
- Side overlap. How much neighboring flight lines share.
Pix4D's image acquisition guidance gives a general starting point of "at least 75% frontal overlap (with respect to the flight direction) and at least 60% side overlap (between flying tracks)," and recommends taking images in a regular grid pattern (Pix4D, Selecting the Image Acquisition Plan Type, checked Nov 9, 2026). The same page recommends higher overlap for forest and dense vegetation, at least 85% frontal and side overlap, because trees look different from image to image and are harder to match.
Step by step: estimate image count for a grid flight
The numbers below are example inputs chosen to show the math. They are not tied to a specific aircraft. Swap in your own camera's image size and your planned GSD.
- Example site: a rectangle 400 m long and 300 m wide (12 hectares, about 30 acres)
- Example image size: 5,472 × 3,648 pixels (a 20-megapixel, 3:2 image)
- Example GSD: 2.5 cm per pixel (0.025 m)
- Overlap: 75% front, 60% side
1. Work out the image footprint
Multiply each image dimension by the GSD. With the long side of the image across the flight line:
- Across track: 5,472 × 0.025 m = 136.8 m
- Along track: 3,648 × 0.025 m = 91.2 m
2. Convert overlap into spacing
The distance between photos is the part of the footprint that is not overlapped.
- Photo spacing along a line: 91.2 m × (1 − 0.75) = 22.8 m
- Line spacing: 136.8 m × (1 − 0.60) = 54.7 m
3. Count lines and photos per line
Fly the lines along the 400 m length. Round up each division, then add one for the starting line or starting photo:
- Flight lines: 300 ÷ 54.7 = 5.5, round up to 6, plus 1 = 7 lines
- Photos per line: 400 ÷ 22.8 = 17.5, round up to 18, plus 1 = 19 photos
- Grid estimate: 7 × 19 = 133 photos
4. Why the area shortcut undercounts
A quick shortcut divides site area by the new ground each photo adds: 22.8 m × 54.7 m is about 1,248 m², and 120,000 m² ÷ 1,248 m² is about 96 photos. That figure ignores the extra line and the extra photo at the ends of each line that you need to cover the boundary, so it comes in well under the grid count. Use the shortcut as a floor, not a plan.
5. Add an edge buffer
Edges are where maps go soft, because boundary ground appears in fewer photos than the middle of the site. Extending the grid one line past each side and a photo or two past each end is a common habit. In the example, going to 8 lines of 21 photos gives 168 photos, roughly a quarter more than the bare grid.
How overlap and altitude change the count
Overlap has a bigger effect than most people expect. Rerun the same example at the higher forest overlap of 85% front and 85% side:
- Photo spacing: 91.2 m × 0.15 = 13.7 m, so 400 ÷ 13.7 = 29.2, round up to 30, plus 1 = 31 photos per line
- Line spacing: 136.8 m × 0.15 = 20.5 m, so 300 ÷ 20.5 = 14.6, round up to 15, plus 1 = 16 lines
- Grid estimate: 16 × 31 = 496 photos, nearly four times the 75/60 plan before any edge buffer
Altitude works the other way. Halving GSD (flying lower for more detail) halves the footprint in both directions, which roughly quadruples the photo count for the same site and overlap. That is why it pays to pick the GSD the deliverable actually needs rather than the finest the camera can reach. Exposure and shutter choices also matter at lower altitudes, as covered in drone mapping camera settings.
What adds photos beyond the grid math
- Irregular boundaries. L-shaped parcels, corridors and odd polygons waste partial lines. Planning software clips some of that, but expect more photos per acre than a clean rectangle.
- Turns and line ends. Depending on the app and aircraft, some photos may be captured on approach or exit from a line.
- Terrain changes. If the ground rises toward the aircraft, GSD and footprint shrink and the effective overlap drops. Terrain-following or a second plan for high ground can add images.
- Tall structures and vertical faces. Buildings, stockpiles and tree lines often need oblique passes or a crosshatch on top of the nadir grid.
- Repeat passes. A battery swap mid-line, a gust that ruins a stretch, or a cloud shadow can mean reflying part of the grid. Plan cards and batteries for some reflight.
Photo count is not processing time
A photo estimate tells you about field time, storage and upload. It does not tell you how long processing will take. Processing time depends on the software, the computer, the image resolution, the output types you ask for and how hard the scene is to match. Two jobs with the same photo count can process at very different speeds, so treat any runtime as something to measure on your own setup rather than predict from image count alone.
A quick pre-flight check
- Confirm the GSD the client deliverable needs.
- Calculate footprint, spacing, lines and photos per line from your camera's real image size.
- Add an edge buffer and an allowance for irregular shape, terrain and obliques.
- Translate the count into batteries, cards and field time.
- After the flight, compare the actual count with the estimate and keep notes for the next similar site.
Estimating image count before you fly keeps quotes honest and field days predictable. When you're ready to keep jobs, flights and client deliverables in one place, see Pilot Ledger plans and pricing.