Reading the Shadows: How a Solar Shading Analysis Works

Homeowners tend to hold one of two beliefs about shade, and both are wrong in ways that cost money. The first is that a little shade means solar won’t work at all, which scares people off roofs that would have performed perfectly well. The second, more expensive one, is that shade doesn’t really matter because “the panels still get light,” which sets a buyer up to accept a production estimate the roof will never actually hit. The accurate picture sits between the two: shade absolutely reduces production, sometimes substantially, but it’s a measurable, model-able quantity that a competent installer pins down before quoting, and modern system design can soften its impact without pretending it away. A solar shading analysis is how that quantity gets measured, and understanding what it does is the difference between a production estimate you can trust and one that quietly overpromises for as long as you own the system.

What a shading analysis measures, and reading it in your quote

At its core, the analysis answers one question for every spot on your roof: over a full year, how much of the available sunlight actually reaches that point, and how much gets blocked by something, a tree, a chimney, a neighboring roofline, a vent stack, the ridge of your own house? The output is usually expressed as a solar access percentage. A location with 100% solar access sees the sun the entire time it’s above the horizon; a location at 80% loses a fifth of its potential sunlight to obstructions across the year. Installers often report an annual figure alongside seasonal ones, and there’s a real reason for that, because shade isn’t constant through the year. The sun rides low across the sky in winter and high in summer, so a tree that clears your panels entirely in July can throw a long shadow across them all through December. A single annual number hides that swing, which is why a good shade report breaks the figure out by season and, ideally, by individual panel position, so you can see not just how much sun the array loses but when it loses it.

What lifts this above eyeballing the roof and guessing is the sun path itself. The analysis overlays the sun’s arc across every day of the year onto a map of your specific obstructions, then calculates exactly when and where shadows fall on each part of the roof. That’s why it’s sometimes called a sun path analysis: it’s literally tracing the sun’s yearly track against the things that get in its way, hour by hour and month by month, rather than taking a single snapshot on a single afternoon. The distinction matters because a snapshot taken at the wrong time of day, or the wrong season, can be wildly misleading, showing a roof bathed in sun in June that spends half of December in shadow. Only the full-year path captures the truth of what a fixed array will collect.

The method an installer uses to produce that figure tells you something about the rigor behind their estimate, and it’s worth knowing the two broad approaches. For decades the standard was a handheld instrument placed at the proposed array location that captures the surrounding skyline, the trees, buildings, and horizon, and reflects the sun’s path onto it to compute solar access at that exact spot. Modern versions of the same idea use a phone camera and a fisheye lens to do the identical job. Because the reading is taken from the actual roof plane, it captures near obstructions accurately, a low branch or a close chimney shows up exactly as it will affect the panels, but the trade-off is that someone has to physically climb up there to take it. Increasingly, installers instead build a three-dimensional model of your roof and its surroundings from aerial imagery, LIDAR, or drone photography, then run the sun path against that model in software. This can generate a per-panel shade map without anyone touching a ladder, and it’s fast enough to compare several possible layouts in an afternoon. Its accuracy depends heavily on how current and detailed the underlying imagery is, though, so a fast-growing tree or a neighbor’s recently built second story may not appear in the model at all, which is why the best assessments still cross-check the software against reality rather than trusting the model blindly. Whichever method produces it, the goal is identical: a per-location solar access figure that feeds directly into the production estimate. When you run a first-pass estimate yourself with the solar panel calculator, you’re leaning on a simplified stand-in for exactly this measurement, and a professional shade report is the detailed version an installer should be able to put in front of you on request.

That per-location figure only earns its keep once it reaches the quote, and a production estimate is only as honest as the shading derate baked into it, which is where quotes quietly diverge. Two bids for the same roof can differ by fifteen to thirty percent in projected annual output purely because one assumed a lightly shaded roof and the other measured a heavily shaded one. The panels are identical, the roof is identical, but the number at the bottom of the quote, and therefore the payback the salesperson promises, moves by a third depending on an assumption you were never shown. So when you receive a quote, the question to ask is direct: what solar access percentage was assumed, and how was it obtained? An installer who measured it can tell you. One who guessed will change the subject.

A few rules of thumb help you interpret whatever figure comes back. Solar access in the mid-to-high 90s is essentially unshaded, and you can trust an optimistic production figure that goes with it. Numbers in the 80s indicate meaningful shade that a good design works around, and the production estimate should visibly reflect that loss rather than reading as if the roof were clear. Numbers dropping into the 70s or below signal that shade is a first-order problem for that roof, and the honest response is not to fill the roof and hope, but to do something structural about it: aggressive tree trimming, a different roof plane, or a smaller, better-placed array that skips the worst positions entirely. The specific warning sign to watch for is a quote that shows a visibly shaded roof in its own site photos while reporting production as if the roof were clear glass in open sky. That gap between the photo and the projection is one of the most common ways real-world output ends up below the sales estimate, and it’s entirely avoidable if you catch it before signing. The fix is simple to ask for and hard for an installer to refuse: get the assumed solar access percentage and the derate it produces written into the quote, so the number you’re being sold is the number you can hold them to. A production figure with no shading assumption attached to it isn’t an estimate; it’s a hope, and hopes don’t show up on your bill.

Why one shaded panel doesn’t sink the array, and turning shade into a fair number

The scariest shade myth, that a single shadowed panel drags the entire array down to its level, comes from how older string systems genuinely behaved. Panels wired in a series string can be limited by their weakest member, much like a hose kinked at one point restricts the whole flow, so shade on one module could disproportionately cut the output of the entire string it belonged to. That was real behavior, and over the years it calcified into a general belief that any shade at all is catastrophic for solar. Modern electronics changed the calculus substantially. Microinverters put a small inverter on each individual panel, and power optimizers add per-panel electronics ahead of a shared string inverter, so in both cases each module produces independently of its neighbors. A shaded panel still underperforms, but it no longer drags its unshaded neighbors down with it, which is a meaningful difference on any roof with complexity. That’s why module-level electronics are so often recommended for roofs with dormers, multiple planes, or unavoidable obstructions, and the trade-offs between the approaches are laid out in the comparison of string inverters and microinverters and the middle-ground option of power optimizers, which recover much of the benefit at lower cost.

How much these devices actually buy you depends entirely on how much mismatch there is to fix, which is worth understanding before you pay a premium for them. On a genuinely clear roof where every panel sees the same sun, module-level electronics recover very little, because there was no mismatch loss to eliminate in the first place, and the money spent on them is buying monitoring and peace of mind more than production. On a roof where shade falls unevenly, one string with a couple of panels dropping into a chimney’s shadow each afternoon while the rest stay bright, the mismatch loss on an old-style string system could be a meaningful chunk of that string’s output, and per-panel electronics claw most of it back. The honest way to decide, then, is to let the shade report drive the hardware choice rather than buying optimizers or microinverters reflexively. If the report shows uniform high solar access across the whole array, a well-designed string system may lose almost nothing and cost less; if it shows scattered or partial shade that can’t be designed away, module-level electronics start paying for themselves. Matching the hardware to the measured shade, instead of to a salesperson’s default, is where the shade report translates directly into money kept rather than spent.

The nuance worth holding onto is that these devices mitigate shade; they don’t defeat it. A panel sitting in shadow still makes very little power regardless of what inverter it’s attached to, because it’s the sunlight that’s missing, not the electronics. What module-level hardware actually recovers is the losses that a shaded panel used to inflict on the rest of the array, not the losses on the shaded panel itself. So the correct response to a shaded roof is still, first and foremost, to reduce the shade or place panels where the shade isn’t, and then to use the electronics to protect the good panels from the few compromised ones. Order matters here: hardware is the second move, not the first. Once you have a credible per-panel shade map in hand, the production estimate becomes a matter of arithmetic, because each panel contributes according to its own solar access and the array total is simply the sum of the individual contributions. This is exactly where a thoughtful design earns its keep, because dropping the two or three worst-shaded positions can sometimes raise the whole system’s efficiency and payback more than keeping them for the sake of a bigger nameplate number that never actually materializes as production.

The most useful way to think about a shading analysis is as a negotiating tool every bit as much as a technical one. A real shade report lets you ask pointed, specific questions instead of vague ones: which panels does the report flag as weakest, what would trimming a particular tree recover in kilowatt-hours, and does the proposed layout put any panels in positions the report already marks as poor performers? An installer who can answer those questions from an actual shade report is estimating your production from measured data; one who waves the questions away is guessing and hoping you won’t notice the difference until the first year’s numbers come in low. Pair the shade figures with the rest of your roof’s characteristics, its pitch and its orientation, and you’ll have the full geometric picture of what your roof can genuinely deliver, which is the only foundation on which a payback estimate is worth anything at all. Do that work before you sign rather than after, because a shade report is cheap to request and easy to reason about while you’re still comparing installers, and nearly impossible to argue with once the panels are already bolted to the positions the report would have told you to avoid.