Additional
Shade, trees and chimneys: what actually costs you output
Two authorities arrived at the same cut-off from opposite directions, and almost nobody quotes it.
Written by HyreSolar Research team Research and analysis
Audited by HyreSolar Research team Data audit and fact check
The short answer
The threshold, and why the convergence matters
Shading is usually discussed qualitatively: some is bad, more is worse, get a site survey. There is a number, and two independent bodies reached it separately.
A state building code defines Total Solar Resource Fraction, a measure of how much of the available solar resource a surface actually receives once obstructions are accounted for. It then uses 80% as a cut-off: below that, a roof is excused from the solar-ready construction requirements that would otherwise apply. The regulator's position is that at that point the roof is not worth requiring readiness on.
A national laboratory's methodology for estimating national rooftop solar potential uses the same figure for the opposite purpose. It excludes from its estimates any roof area that cannot "produce 80% of the energy produced by an unshaded system of the same orientation". Area below that is not counted as potential at all.
Neither cites the other, and they are doing different jobs. One is deciding what to require of new construction; the other is deciding what to count in a resource estimate. That they land on the same figure is the strongest available signal that 80% is where usefulness genuinely falls away rather than an arbitrary line.
What that gives you is a way to ask a specific question. Not "is my roof shaded" but "what is the solar resource fraction on the planes you propose to use, and how much of the array falls below 80%". A site survey produces that number, and if nobody will give it to you, nobody has measured it.
The vocabulary, because two of these are measurements
- Total Solar Resource Fraction
- How much of the available solar resource a surface actually receives once obstructions are accounted for, as a percentage of an unshaded surface. A measurement produced by a site survey, and the quantity the 80% threshold is expressed in.
- Azimuth
- The compass direction a roof plane faces, in degrees. The laboratory methodology excludes planes between 292.5 and 67.5 degrees outright, which is the northerly arc.
- Self-shading
- Rows of tilted panels shading each other, which happens on flat roofs where the array is racked up to an angle. Accounted for by packing a flat roof to about 70% rather than filling it.
- Shading analysis
- The site survey that measures obstruction across the year from the array position. This is what produces a resource fraction, and it is what the modelling default is not.
- Solar-ready
- Construction requirements that make a new roof capable of taking solar later. The threshold matters because a regulator decided that below 80% resource fraction the requirement is not worth imposing.
The other exclusions, which rule out more roof than shade does
The same laboratory methodology applies several other filters before shade is considered, and they are worth knowing because together they exclude more roof than shading typically does.
North-facing planes are excluded outright, specifically those with an azimuth between 292.5 and 67.5 degrees. Not derated: excluded. In the northern hemisphere a north-facing plane receives too little direct sun to be worth counting.
Anything steeper than 60 degrees is excluded. A very steep plane sees the sun too obliquely through the productive part of the day.
Planes smaller than 10 square metres are excluded, on a contiguous basis. That is roughly 108 square feet, which is around five modern modules. Below that, the fixed costs of getting an array onto a plane outweigh what it can carry.
And on flat roofs a module-to-roof ratio of 0.70 is applied, accounting for roughly 2.5% self-shading between rows. Panels on a flat roof are tilted and therefore shade each other, so a flat roof cannot be filled the way a pitched one can.
One more filter is worth naming because it is the one homeowners apply themselves and get wrong. People tend to rule out a plane because it faces east or west, on the belief that only south counts. The methodology does not: it excludes only the northerly arc, which leaves east and west firmly inside what is worth counting. An east or west plane produces less than a south one and it produces it at different hours, which on a time-of-use tariff can be worth more rather than less. Ruling it out by instinct is the most common way a homeowner shrinks their own system.
The practical use of this list is as a sanity check on a proposal. If a design puts modules on a north-facing plane, on a very steep plane, or on a small isolated section, that is not necessarily wrong, but it is outside what a national laboratory counts as usable and it deserves a specific explanation.
What gets excluded before shade is even considered
| Filter | Threshold | Why |
|---|---|---|
| Solar resource fraction | Below 80% of an unshaded system of the same orientation | The convergence point. Two authorities, two purposes, one number |
| Orientation | Azimuth between 292.5° and 67.5° excluded outright | North-facing planes receive too little direct sun to count |
| Tilt | Greater than 60° excluded | Too oblique through the productive part of the day |
| Plane size | Minimum 10 square metres contiguous | Roughly five modules. Below that the fixed costs dominate |
| Flat roof packing | Module-to-roof ratio of 0.70 | Tilted rows on a flat roof shade each other, around 2.5% self-shading |
From a national laboratory’s rooftop technical potential methodology and a state building code’s solar-ready provisions. Read 3 September 2026.
These are the filters used to decide what counts as usable roof at national scale. They are not rules binding your installer, and they are a reasonable standard to hold a design to.
Your estimate almost certainly assumed you have no trees
The modelling tool behind most residential estimates applies a default shading loss of 3%. Its own documentation is explicit about what that represents: an unshaded horizon, accounting for the general obstruction of the sky, and not shading from the homeowner's own trees or nearby buildings.
So if your roof has a tree near it and nobody modelled it specifically, the projection assumed the tree away. Not underestimated it: assumed it away, because the default was never meant to represent it.
This is the single most common reason a system with a real shading problem still receives an optimistic projection. Ask directly: was shading modelled from a site survey, or was the default used? Those are different answers and only one of them describes your roof.
What we are not going to tell you
There is a claim made constantly in this area that we went looking for and could not verify, and it is worth being explicit because it is the claim most likely to be made to you.
How much a module-level architecture recovers from partial shading. Microinverters and power optimizers are sold on the basis that a shaded module no longer drags down its whole string, and the mechanism is real. What we could not find is a primary source quantifying the recovery.
We looked. It is precisely the figure a manufacturer would benefit from publishing and precisely the figure we could not locate in laboratory work.
So we state the mechanism and decline the number. If your roof has shading that varies across it, per-panel management has a real argument behind it. If someone tells you it recovers a specific percentage, ask where that figure comes from, because we could not find its source.
And we give no rule of thumb about a single shaded panel. The old advice was that one shaded module drags an entire string down to its level, which was a reasonable description of an older architecture and is not a description of a modern one with per-panel electronics. How much of that original penalty remains, and under what shading patterns, is exactly the unpublished quantity above. Anyone still repeating the original rule as though nothing has changed is describing equipment nobody is selling you.
We also give no figure for what shade costs in general, because the question is malformed. Shade at nine in the morning in winter costs almost nothing; shade across midday in summer costs a great deal. The quantity that matters is the resource fraction on the specific planes, which is what a survey measures and what the 80% threshold speaks to.
The four obstructions, and how differently they behave
Shading is treated as one problem and it is at least four, distinguished by whether the obstruction moves, grows, or can be removed.
Fixed obstructions on your own roof: a chimney, a vent stack, a dormer, a satellite dish. These cast a shadow that sweeps predictably and they are permanent, but they are also small and close, which means their shadow is sharp and moves quickly. A survey captures them exactly, and the design works around them by leaving that area empty.
Fixed obstructions off your property: a neighbour's roofline, a tall building, a hill. Permanent, not yours to change, and the reason a site can simply be unsuitable. These are the ones worth establishing before you get attached to the idea.
Removing a tree is the one response that is not purely technical. It is irreversible, it can be governed by a local tree ordinance or a preservation order, and the tree may not be yours to cut. Nothing in the codes and methodologies we read grants a solar owner any right to remove or trim vegetation on another property, and nothing obliges a neighbour to keep a view clear. Establish who owns the tree and what the local ordinance says before the array design assumes the shadow will disappear.
Trees, which are the difficult case, because they are the only obstruction that grows. A survey measures the shadow that exists on the day it is done. The system is expected to run for decades, and nothing in a standard analysis models the tree at maturity. A young tree south of the array is a future problem that today's measurement will not show.
And seasonal or transient shading: a deciduous tree that is bare in winter and dense in summer, or snow lying on a lower row. These vary through the year in ways an annual figure averages away, and the direction matters, because summer shading costs far more than winter shading does.
The useful question about any obstruction is which of these four it is, because the answer determines whether the response is design around it, accept it, remove it, or plan for it to get worse.
How to handle shading properly
- 1 Ask for the solar resource fraction on each proposed plane
Not a description of shading, a number. A site survey produces it, and it is the quantity both the code threshold and the laboratory exclusion are expressed in. If nobody can give it to you, nobody has measured it.
- 2 Ask whether the estimate used a survey or the default
The default represents an unshaded horizon and excludes your own trees by design. This one question separates a projection built for your roof from one built for a generic one.
- 3 Check the design against the exclusions
Anything on a north-facing plane, steeper than 60 degrees, or on an isolated section smaller than about five modules is outside what a national laboratory counts as usable. It may still be right for you; it needs a reason.
- 4 Think about the tree in twenty-five years, not today
Trees grow. A survey measures the shading that exists now, and the system is expected to run for decades. If a young tree sits south of the array, its shadow at maturity is the relevant one and nobody models it.
- 5 Identify what is fixed and what is removable
A chimney, a vent stack, a neighbour’s roof and a protected tree are permanent constraints to design around. Your own tree may be a choice, and it is a different kind of decision with its own value attached.
- 6 Do not accept a percentage recovery claim without a source
Per-panel electronics genuinely help with varying shade. We could not find a primary source quantifying by how much, and neither, in our experience, can the people quoting a figure.
Method and limitations
What was read
A state building code's solar-ready construction provisions, for the definition of Total Solar Resource Fraction and the 80% threshold below which the requirements are excused.
A national laboratory's methodology for estimating rooftop photovoltaic technical potential, for the 80% exclusion of roof area relative to an unshaded system of the same orientation, and for the azimuth, tilt, minimum plane area and flat-roof packing filters.
The modelling tool's manual for the 3% shading default and its documented meaning.
What the 80% convergence is and is not
It is two authorities independently using the same figure for different purposes, which is a genuine signal and is how we present it.
It is not a standard, a rule, or a threshold anyone is required to apply to your installation. Neither source binds your installer. What they establish is a defensible line for what counts as usable, and it is a reasonable standard to hold a proposal to.
The number we could not find
No primary source quantifying how much module-level electronics recover from partial shading. We searched for it specifically because it is the central marketing claim for those architectures. The mechanism is not in doubt; the magnitude is unpublished as far as our searching reached.
We would rather say that than repeat a figure whose origin we cannot trace, and we would encourage the same scepticism when the figure is quoted at you.
Questions
How much shading is too much?
Did my estimate account for my trees?
What is Total Solar Resource Fraction?
Why would a north-facing roof be excluded entirely?
Is a small roof section worth using?
Do microinverters or optimizers fix shading?
Should I cut down a tree for solar?
What about shade that only happens in winter?
Written and audited by
HyreSolar Research
Primary-source research, data analysis and fact checking
We are a research desk, not a sales floor. We read the statute, the tariff, the code section, the federal filing or the manufacturer data sheet ourselves, and we publish the figure with the document it came from and the date we retrieved it. Where a number cannot be traced to a primary source, we publish the shorter page and say what we could not verify. That rule has cost us whole sections, and it is the reason the rest can be trusted.
- 160
- primary sources read and cited
- 220
- figures with a retrieval date
- 115
- federal and state government sources
- 66
- researched pages published
How this desk works
- Primary sources only. Statutes from the legislature’s own publishing system, federal data from the agency that collects it, code text from the adopted edition, manufacturer claims from the data sheet. We do not cite an article that cites a source; we go and read the source.
- Every figure carries its provenance. A named document and the date we retrieved it, so you can check it and so you know how old it is. Retrieval dates are not decoration: an EIA rate from May is a different fact from an EIA rate from August.
- We publish what we could not verify. Every research page carries a section naming the things we tried to establish and could not, and why. A paywalled standard, a state website that refused the request, a manufacturer that publishes no figure at all.
- We separate measurement from modelling from our own reasoning, and label which is which on the page. A laboratory measurement, an assumption inside a modelling tool and our own inference are three different kinds of claim and they are never presented as one.
- We do not sell solar, and we take no payment for placement, ranking or a favourable mention. Nobody buys a position on this site.
Data as of Building code text and laboratory methodology read on 3 September 2026. Authorship on this site is organisational: the analysis belongs to the desk rather than to a named individual, and we do not publish credentials we do not hold. Our editorial policy sets out how we source, date and correct what we publish.
Sources & retrieval dates
- State building code, solar-ready construction provisions — Source for the definition of Total Solar Resource Fraction and for the 80% threshold below which a roof is excused from solar-ready construction requirements. Retrieved 3 September 2026.
- NREL, Rooftop Solar Photovoltaic Technical Potential in the United States, NREL/TP-6A20-65298 — Source for the exclusion of roof area that cannot produce 80% of the energy produced by an unshaded system of the same orientation, for the exclusion of planes with azimuth between 292.5 and 67.5 degrees, for the exclusion of tilts greater than 60 degrees, for the 10 square metre minimum contiguous plane area, and for the 0.70 module-to-roof ratio applied to flat roofs accounting for roughly 2.5% self-shading. Retrieved 3 September 2026.
- PVWatts Version 5 Manual, NREL/TP-6A20-62641 — Source for the 3% default shading loss and for the documentation that it represents an unshaded horizon and does not account for shading from the homeowner’s own trees or nearby buildings. Retrieved 3 September 2026.
Not sure how much your trees are costing you?
Send us the proposal and ask your installer for the solar resource fraction on each plane. We will tell you what the estimate assumed and whether it describes your roof.
HyreSolar is an independent analysis and matching service. We are not an installer, lender or utility. When a reader asks to be introduced, installers may pay us a referral fee. That fee never buys ranking, scores or placement in research. Our editorial policy sets out the rules.