Back to Blog
solar design 30 min read

Solar Panel Layout Hip Roof: How to Design Hip-and-Valley Systems That Actually Fit

Hip-and-valley roof solar layout guide for installers: code setbacks, per-plane usable area, string design, and software workflows that maximize kW.

Keyur Rakholiya

Written by

Keyur Rakholiya

CEO & Co-Founder · SurgePV

Rainer Neumann

Edited by

Rainer Neumann

Content Head · SurgePV

Published ·Updated

Hip-and-valley roofs are the most common residential roof shape in North America, the UK, and across much of Europe. They are also the single biggest reason solar designs fall short of the kW the homeowner expected. The diagonal hip lines, multi-azimuth planes, and code-required fire setbacks combine to eat 30 to 50 percent of gross roof area before a single module is placed. This guide walks through every layer of the design problem: code, geometry, electrical topology, software workflow, and the trade-offs that turn a “this should fit a 10 kW system” first impression into a 7 kW reality.

TL;DR — Hip-and-Valley Roof Solar Design

Treat every plane as a separate sub-array with its own azimuth, tilt, MPPT, and shading profile. Apply 18-inch setbacks from hips and valleys, 36 inches from the main ridge, and a 36-inch firefighter pathway. Expect 50 to 70 percent of gross roof area to remain usable. Use portrait or landscape per plane based on which yields more modules. Group planes by orientation onto separate MPPT inputs, or switch to microinverters when planes are too small for string design.

Here is what this guide covers:

  • The geometry differences between gable, hip, and hip-and-valley roofs, and why those differences matter for module count
  • Exact code-required setbacks for hips, valleys, ridges, edges, and firefighter access pathways
  • A step-by-step site survey workflow for non-rectangular roof planes
  • How to calculate true usable area on each facet
  • Module orientation rules of thumb that change between hip-cut and gable-cut planes
  • String design and MPPT mapping when modules sit on three or more orientations
  • When to abandon string inverters and switch to microinverters or power optimizers
  • The eight mistakes that cost installers the most kW on hip-and-valley roofs
  • Software workflows that compress a four-hour layout into 25 minutes

This is written for solar designers, EPC engineers, and installers who are tired of losing kW to roof geometry they did not plan for.

What Makes Hip-and-Valley Roofs Different from Gable Roofs

A gable roof has two rectangular planes that meet at a single horizontal ridge. The geometry is forgiving. Place modules in a rectangular grid, apply edge setbacks, and most of the plane is usable. A 1,500 sq ft gable roof typically yields 75 to 85 percent usable area for solar design software to fill.

A hip roof replaces those rectangles with trapezoids and triangles. The four planes meet at a central ridge and four diagonal hip lines. Every plane has at least one diagonal edge, which means the rectangular grid of solar modules wastes space at every hip cut.

A hip-and-valley roof adds another layer of complexity. Two intersecting hip-roof volumes create valley lines where roof planes meet at a concave angle, plus secondary ridges where they meet at a convex angle. Most North American homes built between 1960 and today use this shape because it sheds water effectively and looks balanced from the street. The architectural choice that makes the home attractive is the same choice that makes solar design difficult.

The three geometric properties that separate hip-and-valley roofs from gable roofs:

PropertyGable RoofHip RoofHip-and-Valley Roof
Number of major planes246 to 12
Diagonal cut lines046 to 16
Distinct azimuths1 (or 2 if east-west)44 to 8
Typical usable area75 to 85 percent55 to 70 percent50 to 65 percent
Self-shading riskVery lowLow to moderateModerate to high

The implication for solar design software is structural. A tool built for rectangular grid optimization will under-fill hip-and-valley roofs because it cannot reason about which modules to remove when a hip cut creates short rows. The best results come from per-plane optimization with manual refinement on every cut edge.

A second implication is electrical. With a gable roof, you usually have one or two orientations and a single MPPT input handles the whole array. With a hip-and-valley roof, you can easily have four to six unique azimuth-tilt pairs. Each unique orientation needs its own MPPT input on a string inverter, or the design forces compromise voltage that drags down the whole string. This is the single most common source of underperformance on retrofitted hip roof systems.

Code-Required Setbacks: The Numbers Every Installer Must Know

The International Fire Code Section 605 and the corresponding residential code adopted in most US jurisdictions impose specific setbacks designed to give firefighters access during a roof fire. The same code framework has been adopted with local amendments in most of Canada, Australia, and parts of Europe. The numbers below are the federal default. Always confirm with the local Authority Having Jurisdiction because state and city amendments are common.

BoundarySetbackPurpose
Main horizontal ridge36 inchesAllow firefighters to walk along the peak
Diagonal hip line18 inches each sideAllow ventilation cuts on either side of the hip
Valley line18 inches each sideSame as hip — ventilation cut access
Eave (gutter edge)18 inches OR 1/3 of eave-to-ridge depth, whichever is lessEdge access
Rake (gable edge)18 inchesEdge access
Skylights and roof hatches36 inches on three sidesEgress and rescue
Vent pipes and obstructions12 inchesMaintenance access

The firefighter access pathway is the rule that catches most designers off guard. IFC 605.11.3 requires at least one 36-inch-wide clear pathway from eave to ridge on every roof slope where modules are installed. Some jurisdictions require two pathways on roofs over 1,000 sq ft. The pathway must be clear of modules and racking, located along a structurally strong portion of the roof, and not on the ridge itself.

On a hip roof, this pathway typically runs along one of the diagonal hip lines, but local AHJs sometimes interpret the rule as requiring a vertical pathway from eave to ridge on each plane, even if that path is shorter than the diagonal. Always read the local code or call the AHJ before final layout. A wrong interpretation can void the design and force a re-layout that costs days.

Pro Tip

Before you start a hip-and-valley layout, screenshot the relevant section of your local fire code and pin it to the project. Setback enforcement varies by city even within the same state. The Larimer County, Colorado solar layout guide updated in January 2026 is a good template for what AHJ documentation looks like, but Denver, Boulder, and Fort Collins each enforce slightly different pathway rules.

The numerical impact of setbacks on a representative hip-and-valley roof:

  • Gross roof area: 1,800 sq ft
  • Edge setbacks (4 sides): -180 sq ft
  • Hip setbacks (4 hips × 18 inches × average length): -150 sq ft
  • Valley setbacks (2 valleys): -75 sq ft
  • Ridge setbacks (main + secondary): -90 sq ft
  • Firefighter pathway (1 × 36 inches × 25 ft): -75 sq ft
  • Net usable area before obstructions: 1,230 sq ft (68 percent)

Subtract chimneys, vents, skylights, and shading exclusions and the realistic usable area falls to 950 to 1,100 sq ft, or 53 to 61 percent of gross. At 22 sq ft per modern 440 W module installed, that is 43 to 50 modules, or 19 to 22 kW DC.

In practice, hip-and-valley homes rarely reach 22 kW because azimuth-driven exclusions remove modules from the north-facing planes. The realistic ceiling on most US suburban homes is 8 to 12 kW even when gross math suggests 20+ kW.

How to Conduct an Accurate Site Survey for Hip-and-Valley Roofs

The site survey is where most hip-and-valley designs fail. A two-plane gable roof survives a quick measurement; a hip-and-valley roof does not. Every plane needs its own dimensions, pitch, and azimuth, and obstructions need to be plotted to within a few inches because they interact with setbacks.

There are three valid approaches. Pick one based on the roof complexity, your software stack, and whether you can climb the roof safely.

Approach 1: Aerial imagery with manual measurement

Use a tool that pulls high-resolution satellite imagery (typically Nearmap, EagleView, or Google Maps high-zoom). Trace each roof plane as a polygon, measure ridges and hips with the tool’s measurement function, and use the local property records or LiDAR overlay for pitch. This works well for roofs in well-mapped suburbs and takes 10 to 15 minutes per home.

Approach 2: LiDAR-derived 3D model

Many design platforms now offer a LiDAR roof model that returns a fully meshed 3D surface from drone or aircraft scans. Pitch is calculated automatically per plane, and obstructions appear as elevation anomalies. The accuracy is typically within 2 inches per pitch and 0.5 degrees per azimuth. Cost ranges from $25 to $75 per home, paid back on the first design that does not require a re-roof visit.

Approach 3: Manual on-roof survey

When aerial data is unavailable, missing, or outdated (recent re-roof, addition, dormer added), the only valid survey is a physical climb. Use a digital pitch gauge for tilt, a compass corrected for local magnetic declination for azimuth, and a measuring wheel or tape for plane dimensions. Photograph every plane corner, every obstruction, and every junction. Plan for two hours per home.

Whichever approach you use, the site survey output for each plane must include:

  1. Length along the eave (in feet, to the nearest 0.5 ft)
  2. Length up the slope (eave to ridge, in feet, to the nearest 0.5 ft)
  3. Pitch in degrees (or pitch ratio like 6/12, but degrees is unambiguous)
  4. Azimuth in compass degrees (180 = south in the northern hemisphere)
  5. Plane shape: rectangle, trapezoid, triangle, or pentagon
  6. List of obstructions with location and dimensions: chimneys, vents, skylights, satellite dishes, antennas, dormer cuts
  7. Roof material: composite shingle, tile, metal standing seam, slate
  8. Roof age and condition (if older than 15 years, flag for re-roof discussion before solar)
  9. Photographs of each plane and every obstruction

The most important field is azimuth. A compass reading that is 5 degrees off translates to a 1 to 2 percent annual production error and, more importantly, to wrong MPPT grouping decisions. Always correct for magnetic declination at the project location. Declination ranges from -16 degrees in Maine to +20 degrees in Alaska in 2026, and getting this wrong invalidates the entire design.

Per-Plane Analysis: Calculating Usable Area on Each Facet

Once the survey is complete, calculate usable area for every plane independently. The arithmetic is simple but the order matters: apply setbacks first, then obstructions, then shading exclusions, then check whether the remaining area can hold a viable module count.

Step 1 — Apply setbacks to the plane polygon. Inset each edge by the appropriate setback distance. Edges that meet at a hip or valley get the 18-inch hip/valley setback. Edges that meet at the main ridge get the 36-inch ridge setback. Eaves and rakes get their respective edge setbacks. The result is a smaller polygon, not a smaller rectangle, and diagonal cuts stay diagonal.

Step 2 — Subtract obstruction footprints with their own setbacks. Each obstruction has a 12-inch perimeter setback at minimum. Skylights need 36 inches on three sides. Chimneys typically need a shading exclusion zone south of the chimney (in the northern hemisphere) at least three times the chimney height to avoid morning shading on the modules.

Step 3 — Subtract shading exclusions. Run a 3D shading study or a qualitative shading analysis for the location’s solar geometry. Mark zones where annual production loss exceeds your threshold. Most installers use 15 to 20 percent annual loss as the cutoff for excluding a module entirely. Smaller losses in the 5 to 15 percent range warrant module-level power electronics rather than exclusion.

Step 4 — Test module placement at the chosen orientation. A “usable area” of 200 sq ft does not mean nine 22 sq ft modules will fit. The modules need to align in rows with consistent racking spacing. If the usable polygon is shaped like a triangle, only 60 to 70 percent of its raw area will hold modules. Hip-cut planes commonly show this gap between geometric area and module-fitting area.

The output of per-plane analysis is a table:

PlaneGross AreaAfter SetbacksAfter ObstructionsAfter ShadingModule CapacitykW DC
South480 sq ft350 sq ft320 sq ft320 sq ft14 modules6.16
East280 sq ft195 sq ft195 sq ft175 sq ft8 modules3.52
West280 sq ft195 sq ft175 sq ft175 sq ft7 modules3.08
North280 sq ft195 sq ft195 sq ft0 sq ft0 modules0
Total1,3209358856702912.76

This table is the foundation of every downstream decision: inverter selection, string mapping, production estimate, and proposal pricing. Skipping it and going straight to module placement is the single largest source of design rework on hip-and-valley projects.

Stop Losing Hours to Manual Hip-Roof Layouts

SurgePV automates per-plane setbacks, multi-MPPT string mapping, and 3D shading on hip-and-valley roofs in one workflow. Designs that took four hours now take 25 minutes.

Book a Demo

No commitment required · 20 minutes · Live project walkthrough

Module Selection and Orientation: Portrait vs Landscape on Hips

Module orientation is one of the few free variables on a hip-and-valley roof. Pitch is fixed, azimuth is fixed, and setbacks are fixed by code. Whether modules sit portrait (long edge vertical, ridge to eave) or landscape (long edge horizontal, parallel to eave) is a per-plane choice that often decides whether a project hits its target kW.

The standard rule from gable roofs (pick the orientation that aligns with the longer plane dimension) does not transfer cleanly. On a hip-cut plane, the diagonal hip eats more space at the top of each row than at the bottom. Landscape modules are about 1.1 m tall and 2.3 m wide; portrait flips that. The geometry of the wasted triangular zone at the top of the plane changes the module count significantly.

A practical example. Consider a triangular hip plane with an 18 ft eave and a 14 ft eave-to-apex distance.

OrientationModule DimensionsModules in Row 1Modules in Row 2Modules in Row 3Total
Landscape2.3 m × 1.1 m75315
Portrait1.1 m × 2.3 m146020

In this specific case, portrait wins because the plane is taller than it is wide and portrait fits more modules per linear eave foot. Reverse the dimensions (a 14 ft eave with an 18 ft slope), and landscape wins.

The rule of thumb: use portrait when the eave-to-ridge distance is longer than 1.5× the eave length, and landscape when the eave is more than 2× the slope distance. Between those bounds, run both options in your design tool and compare module counts.

Module size also matters. The shift from 60-cell modules (1.65 m × 1.0 m) to 72-cell modules (2.0 m × 1.0 m) to 144 half-cell modules (2.3 m × 1.1 m) changes the math every two years. The 2026 standard for residential is the 132-cell or 144-cell module in the 430 to 460 W range. Using older module dimensions in your fitting calculations consistently underestimates capacity by 10 to 15 percent.

For hip-and-valley work, smaller modules sometimes pack better than the highest-wattage option. A 380 W 60-cell module at 1.65 × 1.0 m can fit on a small hip plane where a 460 W 144-cell module at 2.3 × 1.1 m cannot. The kW per square foot is similar, but the option to use a smaller module class on tight planes adds 5 to 8 percent to total system size on complex roofs.

String Design and MPPT Strategy for Multi-Plane Arrays

Electrical design on hip-and-valley roofs is the part most installers underestimate. The geometry tells you what fits; the electrical design decides whether it produces.

The fundamental rule: every unique azimuth-tilt combination needs its own MPPT input. A south-facing string at 30 degrees and an east-facing string at 30 degrees produce voltage curves that peak at different times. If both strings share an MPPT, the algorithm finds a compromise voltage that is wrong for both. The east string clips in the morning, the south string clips at noon, and total production drops 5 to 12 percent.

Inverter TypeMPPT InputsBest Use Case
Single-MPPT string1Gable roofs with one orientation
Dual-MPPT string2Gable + dormer or simple east-west split
Triple-MPPT string3Hip roof with 3 main orientations
Quad-MPPT string4Complex hip-and-valley up to 4 orientations
6+ MPPT string6 to 12Large hip-and-valley with valley sub-arrays
MicroinvertersOne per moduleAny roof, any orientation, no string limit
Power optimizersOne per module + central inverterAny roof, central inverter behavior

The decision tree for hip-and-valley electrical topology:

  1. Count distinct azimuth-tilt pairs after the per-plane analysis.
  2. If 3 or fewer pairs and each plane has 6+ modules, use a string inverter with at least that many MPPT inputs.
  3. If 4 or more pairs, or any plane has fewer than 6 modules, use microinverters or power optimizers.
  4. If module-level shading varies across the day (typical for hip roofs with chimneys or trees), use module-level power electronics regardless of pair count.

String length math on hip-and-valley roofs is also constrained. The minimum string length is set by the inverter MPPT minimum voltage divided by module Vmp at the highest expected operating temperature. For a typical residential string inverter, that is 6 to 8 modules per string. A small east-facing plane that holds only 4 modules fails the minimum string length test and either needs to combine with another east-facing plane (rare on hip roofs) or switch to MLPE.

The maximum string length is set by inverter maximum input voltage divided by module Voc at the lowest expected ambient temperature. The “lowest expected” ambient is the ASHRAE Extreme Annual Mean Minimum, which is colder than most installers assume. In Minnesota, this is -34°C; in Phoenix, +0°C. Voc rises about 0.3 percent per degree below 25°C, so a Minnesota string of 12 modules at room temperature can violate the inverter limit at the coldest hour of the year. Always validate with the lowest design temperature, not the year-round average.

For multi-plane hip designs, the cleanest approach is to run auto-stringing in your design tool with per-plane MPPT mapping enabled, then inspect the result. The tool should refuse to combine planes with more than 5 degrees of azimuth difference into the same string and should warn when minimum string length is violated.

When to Use Microinverters or Power Optimizers Instead

Microinverters and power optimizers solve three problems specific to hip-and-valley roofs that string inverters cannot solve cleanly.

Problem 1 — Too many distinct orientations. A hip-and-valley roof can easily have six unique azimuth-tilt pairs. Most string inverters cap at four MPPT inputs, and the larger inverters with six or more inputs are commercial-class and overkill for a 10 kW residential system. Microinverters give every module its own MPPT, so orientation grouping becomes irrelevant.

Problem 2 — Small planes with viable module counts but invalid string lengths. A north-northeast plane with 4 modules cannot form a string. With microinverters, those 4 modules run independently and contribute their full output (small as it is). With a string inverter, those 4 modules cannot connect at all and the homeowner loses the production.

Problem 3 — Interplane shading and time-of-day shading. When a chimney shades 2 modules in the morning, a string inverter forces the entire string to operate at the shaded module’s current. Production loss is 30 to 40 percent of the string output during the shaded period, not just the shaded modules. Power optimizers and microinverters isolate the loss to just the shaded modules.

The cost difference is the trade-off. Microinverters add roughly $0.15 to $0.20 per watt to system cost in 2026. Power optimizers add $0.10 to $0.15 per watt. On a 10 kW system, that is $1,000 to $2,000 in additional hardware. The break-even depends on how much production the MLPE recovers. On a true gable roof with no shading, MLPE rarely pays back. On a hip-and-valley roof with multiple orientations and any shading, MLPE typically recovers its cost in 2 to 4 years through higher annual production.

Code factors push the decision further toward MLPE. NEC 2017 and later require module-level rapid shutdown on residential roofs, which microinverters and most power optimizers provide natively. String inverter installs need a separate rapid shutdown device per string, adding cost that closes part of the MLPE price gap.

The decision rule used by most experienced solar designers: default to microinverters or DC optimizers on hip-and-valley roofs unless the home has a single dominant south-facing plane that holds 80 percent or more of the system, in which case a string inverter with two or three MPPT inputs is acceptable.

Common Mistakes Installers Make on Hip-and-Valley Roofs

Eight mistakes account for most of the underperformance and rework on hip-and-valley installations. Each is preventable with a few minutes of upfront design discipline.

Mistake 1 — Treating the roof as a single plane. The fastest way to overestimate system size is to measure total roof area and apply a 70 percent usable factor. On a hip-and-valley roof, the per-plane breakdown reveals that some planes have zero usable area (north-facing) while others are near the maximum. The total comes out 15 to 25 percent below the single-plane estimate.

Mistake 2 — Mixing orientations on a single MPPT. Already covered in detail. Repeated here because it is the most common electrical design error on hip roofs and the hardest to detect after install. The system passes commissioning, the homeowner sees production data, and only after a year of comparing to NREL PVWatts does anyone notice the system underperforms by 8 to 15 percent.

Mistake 3 — Forgetting to correct for magnetic declination. A compass reading is magnetic north, but solar geometry uses true north. The difference can be 16 degrees in the northeastern US or +12 degrees in California. A 16-degree error means a “south-facing” plane is actually southwest, with all the production-loss implications.

Mistake 4 — Underestimating valley shading. Valley lines create a concave roof shape. In the morning and afternoon, modules near a valley shade other modules near the same valley. This self-shading is invisible in 2D layouts and only appears in proper 3D shading analysis.

Mistake 5 — Skipping the firefighter pathway. AHJ rejections on hip roofs almost always come down to missing or incorrectly placed pathways. The fix usually requires removing 2 to 4 modules on a single plane, which is a 1 to 2 kW reduction the proposal already promised.

Mistake 6 — Using outdated module dimensions in fitting calculations. Cost estimates that assume 1.65 × 1.0 m modules will not fit current 2.3 × 1.1 m inventory. The reverse error is also common: assuming the largest available module fits a small hip plane that actually needs a 60-cell or 120-cell module to pack properly.

Mistake 7 — Ignoring valley line setbacks. The 18-inch valley setback applies to both planes meeting at the valley, which means 36 inches total are removed across the two planes. Many designers apply only one side of the setback and lose the layout to AHJ review.

Mistake 8 — Quoting capacity before the proposal stage shading analysis. Pre-sale capacity quotes based on satellite imagery alone consistently overshoot by 15 to 30 percent on hip-and-valley roofs. The fix is a two-stage quote: a non-binding initial range based on roof area, then a binding system size after the full per-plane analysis.

These mistakes share a root cause: applying gable-roof workflows to hip-and-valley geometry. The discipline that solves them is treating every plane as its own project and only summing at the end.

Software Workflows That Save Hours on Complex Roofs

Manual hip-and-valley design takes three to four hours per home for an experienced designer. Software-driven workflows compress that to 20 to 40 minutes by automating the parts that do not require judgment and surfacing the parts that do.

The workflow that consistently wins:

  1. Import roof imagery. High-resolution satellite imagery, drone scan, or LiDAR mesh. The tool should detect roof planes automatically and let you adjust plane boundaries by dragging.
  2. Auto-segment planes by pitch and azimuth. Modern tools use roof segmentation algorithms to detect plane boundaries within a few inches. Manual cleanup takes 2 to 5 minutes per home.
  3. Auto-apply setbacks per plane. The tool should know the local AHJ rules and apply hip, valley, ridge, and edge setbacks automatically. Override for unusual conditions like thermal solar coexisting with PV.
  4. Auto-detect obstructions. Chimneys, vents, and skylights show as elevation anomalies in LiDAR data and as shadows in satellite imagery. The tool flags them; the designer confirms each.
  5. Run 3D shading study. The tool calculates annual irradiance per square foot across the year. Modules below a configurable threshold (typically 75 to 80 percent of the best plane) are excluded automatically.
  6. Auto-fill modules per plane. Module placement optimization tries portrait and landscape per plane and picks whichever yields more modules. The designer reviews and removes any modules that overlap obstructions or look impractical for racking.
  7. Auto-string with per-plane MPPT mapping. String map auto-generation creates strings that respect minimum and maximum string length, refuses to mix orientations, and assigns each unique pair to its own MPPT input.
  8. Generate proposal with per-plane production split. The proposal should show production by plane, not just system total, so the homeowner sees that the north-facing zone has zero modules and the south-facing zone carries the system.

The tools that handle all eight steps in one workflow are cloud-based design platforms built specifically for residential PV. SurgePV is one example; competitors include Aurora Solar, OpenSolar, and Pylon Observer. The differentiator is how each tool handles per-plane MPPT mapping and 3D shading on hip-and-valley geometry. The newer tools handle it cleanly. Older 2D tools force manual work on every plane.

The ROI of switching from a 2D tool to a 3D per-plane tool on hip-and-valley work is substantial. A designer who handles 60 hip-and-valley designs a year saves roughly 200 hours, or one full month of design labor. At an average designer cost of $40 per hour fully loaded, that is $8,000 in saved labor, more than the annual cost of any cloud design tool on the market.

For projects that need ROI modeling alongside the layout, the generation and financial tool inside a single platform removes the export-import cycle that adds 30 minutes per project. For shading-heavy hip roofs, solar shadow analysis software that runs in the same project as the layout is the single biggest time saver. The solar proposal software inside the same platform pulls per-plane production into the customer-facing PDF without manual reformatting.

Real-World Example: Designing a 7 kW System on a Hip-and-Valley Roof

To make the workflow concrete, here is a complete walkthrough of a recent project. Names and addresses are anonymized; the geometry and numbers are real.

Project context. A 1980s ranch home in suburban Charlotte, North Carolina. Total conditioned space 2,100 sq ft on a single story. Hip-and-valley roof with a south-facing main rectangle, an east-facing wing, a west-facing wing, and a small north-facing front gable. Roof material: composite shingle, 8 years old, in good condition. Local AHJ: Charlotte-Mecklenburg with standard IFC 605 setbacks.

Site survey. Aerial imagery from Nearmap with LiDAR overlay. Total survey time: 12 minutes.

PlaneLength (ft)Slope (ft)Pitch (deg)Azimuth (deg)Gross (sq ft)
South main321827178576
East wing18142788252
West wing181427268252
North gable141227358168
Total1,248

Per-plane analysis.

PlaneSetbacksObstructionsShading Excl.Net UsableModule Capacity
South-120-25 (vent)043118 modules
East-550-25 (tree)1727 modules
West-55-15 (chimney)-30 (chimney)1526 modules
North-450-123 (excluded)00 modules
Total75531 modules

At 440 W per module, the maximum capacity is 13.64 kW. The homeowner’s electrical panel is 200 A and the meter base supports up to 20 kW solar without an upgrade, so capacity is not the constraint.

Production-based system sizing. The homeowner uses 9,800 kWh per year. At Charlotte’s irradiance, a south-facing array produces about 1,400 kWh per kW per year. Targeting 100 percent offset requires 7.0 kW. The customer wants headroom for an EV in 2027, so the design targets 8.0 kW.

Final layout. 18 modules total at 440 W = 7.92 kW DC.

  • South: 12 modules in two rows of six, portrait orientation
  • East: 4 modules in one row of four, landscape orientation
  • West: 2 modules in one row of two, landscape orientation
  • North: 0 modules

Inverter selection. The west plane holds only 2 modules, which is below string minimum for any inverter on the market. The east plane at 4 modules also fails minimum string length on most inverters. This rules out a string inverter without major workarounds.

The decision: Enphase IQ8M microinverters, one per module. Total inverter capacity 18 × 330 W = 5.94 kW AC, with the IQ8M’s 330 W AC clipping at peak production. The DC-to-AC ratio is 1.33, which clips less than 1 percent of annual production in this climate.

Production estimate.

PlaneModuleskW DCPlane PRAnnual kWh
South125.280.846,210
East41.760.741,820
West20.880.71875
Total187.920.818,905

The 8,905 kWh covers 91 percent of the homeowner’s current usage and leaves room for slight EV adoption. The design is binding.

Time spent. Site survey 12 min, per-plane analysis 8 min, layout 6 min, electrical design 4 min, proposal generation 10 min. Total: 40 minutes.

For comparison, the same project in a 2D legacy tool with manual per-plane setbacks took the same designer 3 hours and 20 minutes the prior year. The bottleneck in the legacy workflow was per-plane shading analysis, which had to be exported to PVsyst and re-imported as a static result.

Conclusion

Hip-and-valley roofs reward the design discipline that gable roofs let installers skip. Three rules separate the designs that hit kW targets from the ones that miss:

  • Run per-plane analysis before quoting capacity. Total roof area times 70 percent is wrong on hip-and-valley roofs. Per-plane usable area, summed, is correct.
  • Match electrical topology to plane count. Three or fewer orientations with viable string lengths can use a multi-MPPT string inverter. Four or more orientations, or any plane with fewer than 6 modules, switch to microinverters or power optimizers.
  • Use software that handles 3D geometry natively. Manual hip-and-valley layouts in 2D tools cost three to four hours per home. Cloud-based 3D tools with per-plane MPPT mapping and integrated shading analysis cut that to 25 to 40 minutes.

Frequently Asked Questions

How do you design a solar panel layout for a hip roof?

Treat each roof plane as a separate sub-array with its own azimuth, tilt, and string. Apply 18-inch setbacks from all hips and valleys, 36 inches from the main ridge, and the local edge setback. Map usable area per plane, choose portrait or landscape based on which fits more modules in the short rows that hip cuts create, then assign each unique orientation to its own MPPT input or use microinverters when planes are too small for viable string lengths.

What is the minimum setback for solar panels from a hip line?

The International Fire Code and most adopted residential codes require an 18-inch setback on each side of a hip ridge. The same 18-inch rule applies to valleys. The main horizontal ridge requires a 36-inch setback. Always confirm with the local Authority Having Jurisdiction because state and city amendments are common.

How much roof area do you lose to setbacks on a hip roof?

On a typical hip-and-valley residential roof, fire setbacks alone consume 20 to 30 percent of gross roof area. Add chimneys, vents, and shading exclusions and the loss often reaches 40 to 50 percent. Expect 50 to 70 percent of gross area to remain truly usable on a complex hip-and-valley roof.

Can you use string inverters on a hip roof or are microinverters required?

String inverters work on hip roofs if each plane has enough modules for a viable string length and the inverter has enough independent MPPT inputs to keep different orientations on separate trackers. When planes are too small for the minimum string length, or when more than three or four distinct orientations exist, microinverters or power optimizers are usually the cleaner choice.

Should solar panels be portrait or landscape on a hip roof?

Landscape orientation often wins on hip-cut planes because the diagonal hip line creates short triangular dead zones at the top of each row. Landscape modules are wider and shorter, so fewer modules are lost per row. On planes that are taller than they are wide, portrait still fits more modules. Run both orientations in your design tool and compare module counts before committing.

How do you handle shading from one roof plane onto another on a hip roof?

Hip roofs can self-shade because adjacent planes face different directions. Run a 3D shading study at your location’s solar geometry across the year. Exclude any modules that lose more than 5 percent of annual production from interplane shading or pair them with module-level power electronics so a shaded module does not drag down the rest of the string.

What software is best for designing solar layouts on hip-and-valley roofs?

Cloud-based design tools that combine satellite or LiDAR roof imagery, automated obstruction detection, per-plane setback rules, multi-MPPT string design, and 3D shading analysis are the most efficient for hip-and-valley work. SurgePV handles all of these in one workflow, including auto-stringing across multiple roof faces and generating the proposal in the same project.

How many solar panels fit on a typical hip roof?

A 1,800 to 2,200 sq ft single-story home with a hip-and-valley roof typically fits 16 to 22 modern 400 to 440 W modules after setbacks and obstructions, equivalent to a 6.4 to 9.7 kW system. The exact count depends on roof complexity, chimney and vent placement, and how aggressively the local AHJ enforces fire pathways.

Sources

About the Contributors

Author
Keyur Rakholiya
Keyur Rakholiya

CEO & Co-Founder · SurgePV

Keyur Rakholiya is CEO & Co-Founder of SurgePV and Founder of Heaven Green Energy Limited, where he has delivered over 1 GW of solar projects across commercial, utility, and rooftop sectors in India. With 10+ years in the solar industry, he has managed 800+ project deliveries, evaluated 20+ solar design platforms firsthand, and led engineering teams of 50+ people.

Editor
Rainer Neumann
Rainer Neumann

Content Head · SurgePV

Rainer Neumann is Content Head at SurgePV and a solar PV engineer with 10+ years of experience designing commercial and utility-scale systems across Europe and MENA. He has delivered 500+ installations, tested 15+ solar design software platforms firsthand, and specialises in shading analysis, string sizing, and international electrical code compliance.

Get Solar Design Tips in Your Inbox

Join 2,000+ solar professionals. One email per week - no spam.

No spam · Unsubscribe anytime