CAPTD

Panorama Overlap Calculator

This calculator tells you how many frames a single-row panorama needs and exactly how far to rotate the camera between them, from your lens, sensor format, camera orientation and the overlap you want — using the same field-of-view maths as the Field of View Calculator.

mm
%
°

Frames needed

5

Rotate between frames

31.7°

One frame covers

53.1° wide

Panorama height

73.7°

5 frames rotated 31.7° apart cover 180° with 40% overlap — spaced evenly, so the overlap comes out at or above the 30% you asked for.

Pano planned?

Once it's stitched, turn it into a ready-to-post caption, hashtags and matching audio — free to try, no signup.

How to use this

What it does

Works out one frame's angle of view along the direction you'll sweep — from focal length, sensor size and whether the camera is landscape or portrait — then fits frames across the sweep so each overlaps its neighbour by at least the percentage you set. Frames are spread evenly, so the rotation between them is one number you can dial in on a panoramic head or count off on a tripod's degree scale.

What you'll need

  • Focal length in mm — the lens's actual focal length, not a 35mm-equivalent.
  • Sensor format — sets the sensor's physical dimensions.
  • Camera orientation — landscape sweeps with the long side, portrait with the short side (taller result, more frames).
  • Overlap — 30% is the usual stitching-software recommendation; 20-25% on a proper panoramic head, 40% for wide lenses or hand-held.
  • Total sweep in degrees — 180 for a half-circle, 360 for a full one, or whatever the scene needs.

Steps

  1. Enter your focal length and sensor format, and pick landscape or portrait.
  2. Set the overlap you want and the total angle you need to cover.
  3. Read the frame count and rotation angle — level the tripod, lock exposure and focus, then rotate by that angle between shots.

Reading the result

'Frames needed' is how many shots to take; 'Rotate between frames' is the angle to turn between each one. 'One frame covers' is the width of a single shot along the sweep, and 'Panorama height' is the angle of view across it — the vertical field of the finished panorama. The sentence underneath gives the overlap you'll actually get: frames are spaced evenly, so it's always at least what you asked for, often a little more.

Tips

  • Portrait orientation is the usual choice for landscape panoramas: more frames, but a taller result that survives the crop stitching software applies to the wavy edges.
  • Rotate around the lens's no-parallax point (roughly the front of the lens barrel) rather than the camera's tripod socket — otherwise near objects shift between frames and refuse to stitch. A panoramic head or nodal rail does this; for distant scenes it matters much less.
  • Lock everything before the first frame: manual exposure, manual white balance, manual focus. Anything that changes between frames shows up as a seam.

Learn more

What is panorama overlap?

A stitched panorama is a row of overlapping frames merged into one wide image. Stitching software finds matching features in the shared region of neighbouring frames and uses them to align, warp and blend the pair — so the overlap isn't waste, it's the data the software needs. Too little and it can't find enough matches (or finds them only in featureless sky); too much and you shoot far more frames than necessary.

The numbers behind it are just field of view: one frame covers a known angle along the sweep, and the rotation between frames is that angle minus the overlap. This calculator computes the angle from your lens and sensor and divides the sweep into evenly spaced frames.

Why photographers use it

Guessing the rotation is how panoramas fail — a gap in the middle of the sweep, or an odd last frame that doesn't overlap the first on a 360. Knowing the count and the angle before you start means you can dial the click-stops on a panoramic head, count evenly, and be sure the row closes. It also tells you before you rig up whether a 50mm at 30% needs 12 frames or 24 — and whether you'd rather shoot it portrait.

How much overlap should I use?

30% is the standard recommendation from every major stitching tool and works for almost everything. Drop to 20-25% when you're on a proper panoramic head with the no-parallax point set — alignment is precise, so the software needs less. Go up to 40% with very wide lenses (their edge distortion makes matching harder), when hand-holding, or when the overlap region is likely to be blank sky or water with nothing to match on. For multi-row panoramas the same overlap applies between rows.

Common mistakes

  • Rotating around the tripod socket. the camera's tripod thread is well behind the lens's no-parallax point, so nearby objects shift relative to the background between frames and the stitch tears or ghosts. Use a nodal rail or panoramic head for scenes with anything close; for distant landscapes the error is small enough to ignore.
  • Leaving exposure or white balance on auto. each frame meters a different slice of the scene, so auto settings drift across the row and the stitched sky changes brightness at every seam. Meter the brightest important frame, set it manually, and keep it for the whole sweep.
  • Shooting landscape orientation to save frames. the stitched result gets cropped top and bottom to straighten the edges, and a landscape-orientation row leaves very little height after that. Portrait costs more frames and gives a usable, taller panorama.
  • Not closing the loop on a 360. a full circle needs the last frame to overlap the first by the same margin as every other pair. Divide 360 evenly — as the calculator does — rather than rotating by a fixed angle and hoping the final gap works out.
  • Overlapping on nothing. 30% of a frame that's all clear sky gives the software nothing to match. Tilt slightly down so each overlap region contains ground or structure, or increase the overlap in those sections.

Example settings

Classic landscape pano

24mm, full-frame, portrait, 30% overlap, 180° sweep

Five frames 31.7° apart, each 53° wide, panorama 74° tall — 40% overlap once spaced evenly

Cityscape with a normal lens

50mm, full-frame, portrait, 30% overlap, 120° sweep

Six frames 18.6° apart, each 27° wide

Full 360° on APS-C

16mm, APS-C (1.5×), portrait, 30% overlap, 360°

Ten frames every 36° with 31% overlap, the last overlapping the first

FAQ

Why does portrait orientation need more frames?
Turning the camera puts the sensor's short side along the sweep, so each frame covers a narrower angle and it takes more of them to span the same sweep. In return, the panorama is as tall as the sensor's long side allows.
What angle does the calculator use for 'one frame covers'?
The angle of view along the sweep axis: the horizontal field of view for landscape orientation, the vertical one for portrait — the same figures the Field of View Calculator gives for your lens and sensor.
Why is the overlap I get slightly higher than the one I set?
Because the frames are spread evenly across the sweep. The count is the smallest whole number that meets your minimum overlap, and dividing the sweep by that count usually leaves a little extra — which only helps the stitch.
Does this handle multi-row panoramas?
It plans one row. For a second row, tilt by the 'panorama height' figure minus the same overlap and repeat the row — the frame count per row is the same.
Does it account for lens distortion or focus breathing?
No — it uses the nominal focal length. Wide lenses and zooms can differ a few percent from their marking, which is one reason 30% overlap is the norm rather than the bare minimum.