Is Your Roof Too Shaded for Solar? A Quote-Stage Decision Guide

If you are asking, “Is my roof too shaded for solar?”, the answer should come from measured or defensibly modeled shade—not a photo, a salesperson’s impression, or one universal cutoff.

A shaded roof is not automatically disqualified. An unshaded label does not automatically make a proposal good. The decision depends on where shade falls, when it falls, which module positions are affected, how the exact electrical design responds, how much usable area remains, and whether the resulting energy still fits the homeowner’s project goal and utility economics.

At quote stage, ask for comparable cases: the present roof without tree work, the best roof planes only, a smaller array, qualified tree work by others if lawful and desired, a different inverter architecture, a ground or accessory-structure option, and a pause case. This guide explains how to compare those cases without promising a production, savings or approval result.

Do not use one shade percentage as a verdict

“Your roof is 80% sunny” sounds precise but can describe different things. Ask what the number means.

Metric	What it may describe	Question to ask
Solar access	Available sun compared with an unobstructed reference over a stated period	At which point or roof area, using which time window and method?
Irradiance reduction	Sunlight energy blocked at the array plane	Is it monthly, hourly or annual, and is it spatially mapped?
Shade loss input	A model’s assumed energy loss from external shade	How was it derived from the survey and applied by plane or subarray?
Modeled energy difference	Change in annual/monthly kWh between two complete design cases	Which other inputs changed besides shade?
Shaded area	Physical portion covered by a shadow at one moment	How does that moment relate to the annual electrical result?

These values are related, not interchangeable. A small moving shadow can cross several module positions. A large shadow early or late in the day can have a different energy effect than the same footprint at another time. A single roof-average number can hide one strong plane and one weak plane.

Do not ask “What percentage is acceptable?” before defining the objective. A homeowner targeting the best-supported smaller project may make a different choice from one requiring a particular annual energy target. Utility compensation, price, financing and ownership horizon also affect whether a lower-output design is sensible. Shade evidence informs those decisions; it does not settle them alone.

Move from remote screening to a final shade case

Shade confidence should increase in stages:

1. Remote screen. Aerial imagery and a preliminary 3D model identify roof planes, nearby structures and obvious trees. Useful for deciding whether to investigate; not a final shade conclusion.
2. Site geometry. Roof dimensions, tilt/orientation and obstruction locations/heights are verified or documented with limitations.
3. Shade measurement/model. A named method produces results tied to roof locations, times or model surfaces.
4. Exact layout. Proposed modules are placed on the measured/modeled planes with usable-area constraints.
5. Electrical design. Strings, MPPT inputs, optimizers or microinverters are assigned to the layout.
6. Production cases. Shade and electrical response are combined with disclosed weather, equipment and non-shade losses.
7. Contract case. The final quote states which shade/tree/layout assumptions control and what requires revision.

Remote tools can be excellent preparation. They may still miss recent tree growth, changed roof features, a neighbor’s new structure, inaccurate building geometry, seasonal foliage or a narrow obstruction. Conversely, one site visit at noon cannot reveal the full annual sun path.

The South Carolina Energy Office’s system-selection guidance identifies trees, chimneys, nearby buildings, pipes, skylights and vents as common shade sources and notes that shading changes with daily and seasonal sun position. It recommends professional software analysis. Use that as the starting principle, not as a prescribed tool or pass/fail threshold.

The solar site-survey checklist explains how to record observed, modeled, assumed and unresolved conditions. On this page, the key is connecting that record to the exact energy model used in the quote.

Map shade by roof plane, module position and time

A useful shade package should let a second reviewer understand the source and location of the loss. Ask for an annotated roof/site plan showing:

• each candidate roof plane and its tilt/orientation;
• module positions and usable-area exclusions;
• chimneys, vents, dormers, ridges, parapets, roof equipment and neighboring structures;
• trees or vegetation by location, with relevant canopy/trunk geometry assumptions;
• shade pattern by meaningful time/month or an equivalent spatial model output;
• roof areas excluded because the model or site evidence is weak;
• any tree pruning/removal case as a separate scenario; and
• the exact subarray, string, MPPT or module-level assignment.

Shade from a chimney crossing two positions should not be averaged across the whole roof without showing where it occurs. A tree shading the west plane in late afternoon should not be treated as though it blocks the east plane in the morning. For a ground array, row-to-row self-shading is also distinct from external shade caused by trees or buildings.

NREL’s System Advisor Model distinguishes external-object shading from array self-shading. NREL also maintains a PV Shading Database because partial-shade energy effects depend on array and electrical behavior, not only the visible shadow area. You do not need to require one particular software package; you do need the method, inputs and mapping necessary to reproduce or audit the conclusion.

If the model produces only an annual shade-loss value, ask for the underlying spatial/seasonal evidence. An annual summary can support comparison, but it should not erase the pattern that affects layout and electrical architecture.

Require reproducible model inputs

Two proposals can report different production even if their shade studies are similar because other inputs differ. Ask each bidder to disclose:

• model name and version;
• weather-data source and location;
• system DC size and exact module;
• array planes, tilt, azimuth and module count by plane;
• inverter, optimizer or microinverter models and quantities;
• string and MPPT or branch assignments;
• shade method and resulting input by plane/subarray/module as supported;
• mismatch treatment and bypass-diode/electrical assumptions;
• soiling, wiring, availability, temperature and other losses kept separate from shade;
• inverter efficiency, DC/AC relationship and clipping treatment;
• degradation assumptions if a multi-year view is shown;
• tree-work and future-growth assumptions; and
• monthly and annual modeled kWh with stated uncertainty/limitations.

NREL’s current PVWatts V8 calculator states that its predictions contain assumptions and uncertainty and only capture site-specific characteristics represented in the inputs. PVWatts can be a useful screening or reasonableness run when the input set is disclosed. It cannot decide exact roof shade from an address alone or turn a production estimate into a promised result.

If one proposal folds shade, soiling, snow, availability and wiring into one unexplained “system loss,” ask for separation. You need to know which loss a design or tree change is supposed to address.

Compare alternatives with every other input held constant

Build a shade decision matrix. Use the same weather data, module, non-shade losses and project objective where feasible so the difference between cases is visible.

Case	Layout/tree assumption	Electrical architecture	Modeled monthly/annual kWh	Scope and unresolved items
A: existing site	No tree work; current roof conditions	Exact base design
B: best roof planes	Weak planes/module positions omitted	Same design basis
C: smaller array	Only stronger positions	Re-sized exact design
D: tree work by others	Named pruning/removal assumption	Same design basis		Permissions, arborist, price and remeasurement
E: alternate architecture	Same module positions and shade	Exact alternate string/MLPE design
F: ground/accessory site	Verified alternate geometry/shade	Exact alternate design		Land, structure, trench, zoning and access
G: pause	No installation	None		Preserve roof/trees/property priorities

Do not compare a larger microinverter system after tree removal with a smaller string system before tree removal and attribute the difference to inverter type. Normalize the layout and tree assumptions first.

Use monthly results as well as annual totals. They can reveal whether the design depends on favorable foliage assumptions or concentrates losses in seasons that matter to the homeowner’s load. Monthly kWh still does not predict the exact future month; weather and site conditions vary.

Use the strongest roof planes first

Many roofs have mixed conditions. One plane may have clear solar access while another sits behind a mature canopy or building. The strongest design may omit the weak plane rather than maximize panel count.

For each plane, compare:

• usable dimensions after applicable access/layout constraints;
• tilt/orientation;
• shade pattern and shade evidence quality;
• module count and electrical grouping;
• modeled kWh per installed kW for the defined case;
• construction complexity, wire route and equipment implications;
• appearance/HOA constraints; and
• future shade or building-change risk.

Modeled kWh per installed kW is a diagnostic, not a universal minimum. It helps explain why one plane contributes differently when system sizes vary. If a weak plane materially lowers the figure, ask what buyer objective it serves and whether its incremental price/scope is justified.

Do not assume a north-facing, east/west or nonstandard plane is automatically unacceptable or acceptable. Local sun path, tilt, shade, module layout, electrical design, utility value and project economics must be modeled together. The state Energy Office correctly notes that orientation, tilt, shade and system efficiency all influence output; old generic directional percentages should not replace a site-specific case.

A smaller array can be the better-supported design

Adding panels in shade does not create the sunlight they lack. A smaller array using stronger module positions can sometimes produce fewer total kWh but more modeled energy per installed kW, reduce equipment/scope, and make the proposal easier to understand. Whether it is financially preferable still depends on the actual price and utility model.

Ask bidders to compare:

1. all physically buildable positions;
2. stronger positions only;
3. the marginal kWh and marginal installed scope for the last group of modules; and
4. any utility/program or electrical design constraint affected by the change.

Do not resize by counting panels alone. The solar system-sizing guide owns the full travel from verified household kWh and future loads to target annual energy, roof/site yield and final module arithmetic. This shade page simply determines which positions deserve to enter that sizing process.

If the smaller design no longer supports the homeowner’s energy or financial objective, that is useful information. It may support another site, a changed goal or no project rather than a larger weak layout.

Module-level electronics manage mismatch, not sunlight

Microinverters and DC optimizers can let module-level channels respond independently or reduce how one module’s electrical condition influences others. A string design may use multiple MPPT inputs, deliberate string grouping, bypass diodes and product-specific shade-management behavior. These are design tools, not universal cures.

No inverter architecture restores irradiance to a shaded module. It cannot remove a tree shadow, create usable roof area or make persistent deep shade economically sensible by itself.

Require two exact-design production cases using the same modules, positions, shade data, weather and non-shade losses. Ask:

• Which modules share a string or MPPT input?
• How are unlike roof planes separated?
• What bypass-diode/module behavior is modeled?
• Which module-level devices are included, if any?
• Does the model represent the actual device and shade pattern or apply a generic premium?
• What roof service points, monitoring and replacement scope differ?
• Does the architecture change module count, inverter AC capacity or clipping?

The microinverter-versus-string guide owns the full architecture choice, including rapid shutdown, monitoring, failure domains, storage path, warranties and replacement. Use it after the shade cases reveal whether electrical mismatch is a meaningful design differentiator.

Reject a fixed “microinverters recover X%” claim. Results depend on shade geometry, electrical configuration, module behavior, equipment and model method. The same architecture can have different value on two roofs.

Treat tree work as its own property decision

Do not let a solar proposal casually assume “trim trees” without naming the trees, work, owner, permissions and long-term plan. Tree work can affect safety, tree health, neighbor relations, privacy, cooling, storm exposure, landscape value and local/HOA compliance.

For every proposed tree action, document:

• tree location and likely ownership;
• species/condition assessment by the appropriate qualified party;
• exact limbs/canopy or removal assumed by the solar model;
• whether the tree is on the homeowner’s property, a boundary, neighboring property, common area, right of way or utility corridor;
• municipal, county, HOA, easement or utility permission required;
• qualified arborist/tree-service scope;
• work near overhead conductors or structures;
• access, rigging, debris, stump and landscape restoration;
• price and party responsible;
• expected regrowth and maintenance responsibility; and
• post-work shade verification before the final production case is accepted.

Clemson Extension’s tree-pruning guidance treats pruning near lines or structures as specialist work best performed by a professional arborist. Charleston’s current tree-removal information shows how rules can turn on tree size/type, zoning, buffer and property circumstances. It is an example, not a statewide rule; verify the address’s actual authority and covenants.

Do not ask a homeowner to climb, cut near power lines or enter a neighbor’s property. Do not prune or remove a tree merely because a sales model assumes it. The owner should receive a no-tree-work case before deciding.

Sunburst’s repository supports roof/shading review and custom solar modeling at a high level. It does not verify that Sunburst performs tree trimming/removal, provides arborist services or maintains vegetation. The signed proposal must name the tree-work party if that scope exists.

Evaluate ground mount or an accessory structure without assuming a win

If roof shade blocks the best positions, a yard, detached garage or other structure may deserve a separate study. It is not automatically clearer, cheaper or approvable.

For a ground option, evaluate:

• exact buildable area and external shade;
• array tilt/orientation and row-to-row self-shading;
• property survey, easements and setbacks;
• septic, well, drainage and underground utilities;
• soil/foundation and wind design;
• trench/electrical route and voltage considerations;
• equipment, mowing and service access;
• flood/site conditions;
• fencing/security as applicable;
• zoning, HOA and permit path; and
• future trees, buildings and property use.

If digging or stump work is involved, South Carolina 811’s safe-digging guidance explains the locate process for member utilities and notes the separate issue of private lines. A locate does not establish property boundaries, easements or complete subsurface conditions.

The rooftop-versus-ground-mount guide owns the full siting comparison. A060’s role is to trigger that comparison when the measured roof-shade case is weak—not declare the ground case superior.

Put future shade assumptions in writing

Today’s shade map is dated evidence. Trees grow, limbs fail or are pruned, neighbors add structures, and the homeowner may build an addition. Ask the quote to state which future conditions it assumes and what is outside the seller’s control.

Record:

• survey/model date and imagery date;
• leaf condition/season and how other seasons were represented;
• tree dimensions and growth/maintenance assumptions;
• planned tree work and completion gate;
• owner-disclosed neighboring plans;
• roof/building projects already planned;
• monitoring baseline after commissioning; and
• who the owner contacts when future shade changes production.

Avoid a promise that one pruning event keeps the array clear for its entire operating life. Avoid assuming continued access to a neighbor’s tree. If ongoing vegetation work is important, the owner needs a separate lawful maintenance plan with a qualified provider.

A production statement should define exclusions and the measurement/model basis. Shade-related underperformance, an equipment fault and a monitoring-data problem require different diagnosis. Do not infer the cause from one low month.

Keep shade output separate from savings and “worth it”

A shade model estimates how site conditions affect energy. A financial model also needs installed price, financing, current utility tariff/export treatment, self-consumption, future-load assumptions, maintenance/service and ownership horizon.

Do not convert a shade percentage directly into a bill-savings percentage. Some production is used in the home and some may be exported under utility-specific rules. Timing can matter. Fixed charges and non-bypassable items may remain. Future rates and weather are uncertain.

Use the shade study to produce defensible energy cases, then take the chosen case to the South Carolina solar worth-it guide. That page owns the complete utility, production, cost, financing, tax and ownership-horizon decision.

This separation also prevents circular sales logic: “solar is worth it because the roof works” and “the roof works because the savings graph looks good.” Site evidence should feed the production case; the production case should feed transparent economics.

Score competing shade packages

Use one worksheet across proposals:

Required evidence	Quote A	Quote B	Quote C
Shade method, operator and date stated
Roof/site geometry verified with limitations
Shade tied to planes/module positions and time
Seasonal foliage and future conditions disclosed
Exact module and electrical layout shown
Shade separated from other model losses
Monthly/annual outputs and uncertainty supplied
Best-planes and smaller-array cases modeled
Tree work expressly included/excluded/by others
Alternate architecture uses normalized inputs
Ground/accessory or pause case addressed
Final quote/change triggers match the shade case

The strongest proposal is not necessarily the one with the highest modeled kWh. It is the one whose layout, assumptions, exact design, scope and uncertainty are coherent enough for you to compare with the price and utility case.

If you are comparing a shaded-roof proposal for residential solar installation, bring the shade outputs, roof layout, tree/property records and competing model cases to a property-specific solar assessment. Ask the signed proposal to identify the actual shade method, deliverables and tree-work boundary; this article does not state that Sunburst provides arborist or tree services.

Red flags in a shaded-roof quote

Pause when:

• the roof is called suitable from an aerial image alone;
• one shade percentage has no definition, location, date or method;
• a noon photograph is used as an annual shade study;
• all roof planes receive one unexplained loss factor;
• shade is combined with every other loss in one number;
• the production model does not match the final module layout;
• a tree-removal case is shown without a no-removal case;
• tree work is absent from scope, permissions and price;
• neighbor or public trees are treated as homeowner-controlled;
• microinverters or optimizers are said to eliminate shade loss;
• an architecture premium is claimed without same-input model cases;
• more panels are added to compensate without showing marginal kWh and scope;
• the ground alternative ignores row shade, land, trench or approvals;
• modeled kWh is described as certain production;
• production is translated directly to certain savings; or
• the proposal has no pause path if the viable layout is too weak.

An installer may legitimately use proprietary software or a remote-first process. The important questions are whether its inputs are current and property-specific, whether limitations are disclosed, and whether the final quote is reconciled to the exact field/layout evidence.

How Sunburst handles a shaded roof

Mature live oaks and pines are part of what makes Lowcountry and Midlands neighborhoods worth living in, and they are also the most common reason a South Carolina roof does not support the array a homeowner imagined. Sunburst measures shade by roof plane and module position, keeps every other model input constant when comparing alternatives, and presents the smaller, better-supported design when that is the honest outcome. Where module-level electronics genuinely help, we say so; where they are being used to sell past a shading problem, we say that too.

Tree work stays your decision, made on arboricultural and property grounds rather than as a condition of a solar sale, and we will not model production on the assumption that trees will be removed unless you have decided to remove them.

If the roof cannot carry a viable layout, a ground mount may be the better route. Read next: array placement and HOA constraints, inverter architecture for shaded roofs and system sizing. See our residential solar service, solar installers by city, or book a free assessment.

Frequently asked questions

How much shade is too much for solar panels?

There is no responsible universal percentage. Define the metric, map shade to the proposed positions and time periods, model the exact electrical design, and compare the resulting energy with price, utility treatment and homeowner goals. A strong plane and weak plane should not be hidden in one average.

Can solar panels work in partial shade?

They can generate when irradiance is available, but shade reduces the sunlight reaching affected cells/modules and can create electrical mismatch. The result depends on the shade pattern, module design, string/MPPT layout, bypass behavior, module-level electronics where used and the model assumptions. Request a site-specific energy case, not a generic percentage.

Do microinverters fix a shaded roof?

No. Module-level operation can manage some mismatch and limit how one module’s electrical condition affects other channels. It cannot restore blocked sunlight. Compare exact microinverter and string/optimizer cases with the same positions and shade inputs before attributing a difference to architecture.

Should I remove trees to install solar?

That is a property, safety, ecological and financial decision—not an automatic solar step. First request a no-tree-work design. If tree work remains an option, verify ownership, tree health, qualified arborist scope, local/HOA/utility rules, permissions, price, landscape effects, future maintenance and the updated shade result.

Can I just add more panels to offset shade?

More nameplate capacity does not prove a better project. Model the marginal energy from the added positions and compare the added equipment/scope, electrical and utility constraints, and economics. Sometimes a smaller strong array is better supported; sometimes the target is not achievable on the roof.

Is ground-mounted solar better for a shaded roof?

It may offer a clearer solar location, but it requires its own shade, property, zoning, structural, wind, drainage, trench, access and cost assessment. Compare complete roof and ground cases rather than assuming the yard is open or approvable.

Can a shade report promise annual production?

No. It can improve the site-specific inputs to a production estimate. Weather, vegetation, equipment, soiling, outages, curtailment, installation details and model uncertainty still affect actual results. The proposal should clearly separate an estimate from any separate contractual performance term.

Sources and methodology

This article was researched and fact-checked August 10, 2026. Shade/site guidance relies on the South Carolina Energy Office’s system-selection and solar-operation pages, NREL’s PVWatts V8 limitations and PV Shading Database, and NREL System Advisor Model shade-method documentation.

Tree-scope guidance uses Clemson Extension, the City of Charleston’s current tree-removal page as a local example, and South Carolina 811. Charleston’s rules do not establish statewide permission. Electrical-architecture treatment follows DOE/NREL principles and defers the full product/design decision to the dedicated local comparison.

Before relying on a proposal, recheck current roof/site geometry, vegetation and ownership, local/HOA/utility tree rules, exact equipment and compatibility, model/tool/version/weather data, utility program, price and contract assumptions. Shade analysis is decision evidence, not a production, savings, tree, system-size or approval promise.