There’s a ridge I know above the Cascades where the view runs maybe 180 degrees on a clear morning. The first time I set up there, I tried to capture it in a single frame. I had a 14mm lens on my Sony A7R IV. I shot it, got home, and opened the file. Technically correct. Completely lifeless. The scene had been compressed into something small and forgettable, robbed of the very scale that made standing there feel like something. That was the moment I stopped treating panoramas as a workaround and started treating them as a compositional choice.

Why a Single Frame Lies to You

Your eye doesn’t work like a lens. When you stand on a ridgeline or beside a wide river bend at first light, your eye is constantly moving, assembling a continuous impression of the world. A single wide-angle frame collapses that experience into one static geometry. The result often looks smaller than reality, not larger.

A stitched panorama, done right, does something closer to what the eye actually does. It captures more total light data, preserves a longer focal length across a wide field of view, and produces a file large enough to print at wall scale without compromise. My A7R IV’s 61 megapixels sounds impressive until you compare a single frame to a 7-image horizontal stitch at 70mm, which I’ve measured in Lightroom at over 400 megapixels of usable data. That’s not a number for its own sake. That’s what lets a 40x120 inch print hold sharp at six inches.

The Setup That Actually Works in the Field

I shoot panoramas in portrait orientation with the camera rotated on a nodal point head, usually an Acratech GP ballhead with a leveling base underneath it. Getting the nodal point dialed in matters more than most tutorials admit. When the entrance pupil of your lens isn’t sitting over the pivot point of the head, foreground elements shift between frames and the stitching software has to work too hard or simply fails. It’s worth spending an hour in your garage once, aligning your specific lens body combination, then marking the rail position with a paint marker.

For the actual shooting, I set everything manually: ISO 100, f/11, and I meter off a mid-tone in the scene and lock exposure there. I never let the camera meter each frame independently. If the exposure shifts even slightly between frames, the stitching software has to blend across tonal inconsistencies and the seams become visible, especially in skies. I also disable optical image stabilization when the camera is on a tripod, something I’ve seen even experienced shooters forget. The stabilizer can introduce micro-movement as it hunts, and that movement shows.

My overlap is 30 to 40 percent per frame, never less. Lightroom’s Merge to Panorama handles that overlap easily. I shoot a reference frame with my hand in front of the lens at the start and end of each sequence so I can sort them quickly in post without guessing which files belong together.

Where Most Panoramas Fall Apart in Post

The stitching itself is usually the easy part. Lightroom’s Boundary Warp and Photoshop’s Photomerge both do a solid job on clean sequences. I use Lightroom for most jobs, set to Cylindrical projection for wide sweeping scenes and Perspective for anything under about 60 degrees of total arc. I check the Auto Crop box, then immediately undo it and use Boundary Warp at around 60 to 80 percent instead, because straight auto crop cuts too aggressively into the frame.

The harder part is color and tonal consistency across the final merged file. I make all my major global corrections on the DNG that Lightroom generates before I go anywhere near local adjustments. Graduated filters applied after the fact to a merged panorama often produce banding where the gradient crosses a stitch line. Working globally first, then using the Healing and Masking tools with AI-based subject selection, keeps the edit cleaner.

The Fog Trip and the One Shot That Made It Worth It

I drove six hours to the Oregon Coast one January to shoot a sea stack sequence I’d been planning for three months. Fog sat on the water for two full days. Dense, unmoving, indifferent to my schedule. My mentor used to say the mountain doesn’t care about your schedule, and he was right, but that’s a kinder thought in memory than it is at 5am when you’re standing in wet sand watching nothing.

On the morning of the third day, an hour before I was going to pack and leave, the fog thinned just at the horizon. For about eleven minutes, the stacks were separated from the sky by a single luminous band of warm light. I shot a 9-frame panorama at 85mm. The final merged file came in at just under 300 megapixels. That image has become my best-selling print, and I’ve sold it as large as 48x144 inches. I would never have had that file if I’d been shooting single frames. The resolution, the compression of the 85mm focal length, the separation between elements: none of it would exist.

I now work backwards from the intended print size when I plan a panoramic sequence. A rough rule: for a gallery-quality print at 300 PPI, you divide your total pixel count along the long axis by 300 to get maximum print inches. A 7-frame horizontal stitch at 61 megapixels per frame gives me roughly 18,000 pixels on the short axis and upwards of 50,000 on the long. That’s 60 inches tall and 166 inches wide at 300 PPI, more resolution than I’ll ever need. But knowing that going in means I can afford to crop for composition without losing print viability.

The best panorama I ever shot wasn’t the one I planned most carefully. It was the one where the light did something unexpected and I already had the tripod leveled, the nodal point set, and my exposure locked before the moment arrived. All the preparation disappears in that situation, and you’re just shooting.