Peak sun hours are not daylight hours

Choose a solar-resource input, identify its units and test how changing it affects the result.

By Kyle Bell · Original examples and linked primary references · November 17, 2026

Peak sun hours describe a quantity of solar energy as an equivalent number of hours at a reference intensity. They do not mean that the sun stays equally strong for that many clock hours, and they are not the time between sunrise and sunset. A long summer day may include weak early-morning light, clouds and periods when a particular roof is shaded.

The Department of Energy's solar-radiation overview explains that solar resource varies with location, time, season, landscape and weather. It describes photovoltaic resource data using energy per area, such as kWh/m². Those distinctions matter when selecting the input for a small production calculator.

Check the units before copying a number

An average daily resource of 4.5 kWh/m²/day corresponds numerically to 4.5 peak sun hours when expressed relative to 1 kW/m². An annual total of 1,642.5 kWh/m² is different: dividing by 365 gives a daily average of 4.5. Copying the annual total into a daily-input field would produce a meaningless answer.

A monthly total also needs conversion. If a hypothetical panel-plane resource is 135 kWh/m² in a 30-day month, the daily average is 135 ÷ 30 = 4.5 kWh/m²/day. Record whether the source number is daily, monthly or annual alongside the value.

Match the surface to the array

A horizontal-surface resource is not automatically the resource falling on tilted panels. The relevant array-plane value depends on orientation and geometry. A nearby regional map can help establish context, but it does not by itself measure the sunlight reaching a particular roof behind nearby trees.

If an installer provides a modeled panel-plane figure, ask for the location, tilt, direction, period and shading assumptions used to produce it. If those details are unavailable, use a range of plainly labeled scenarios instead of claiming that a single number is your property's verified resource.

See the effect of one changed assumption

Consider a 6 kW array with a 20% combined reduction. At 4.5 assumed peak sun hours per day, output is 6 × 4.5 × 0.80 = 21.6 kWh/day. At 3.5 hours, the same arithmetic produces 16.8 kWh/day. Over 30 days, those scenarios are 648 and 504 kWh: a 144 kWh difference caused entirely by the resource input.

The lower scenario is 22.2% below the higher one. It is not automatically a worst-case weather forecast or a statistical confidence interval. It simply shows how sensitive the estimate is to that assumption. Label scenarios by their inputs rather than names such as “guaranteed” or “expected maximum.”

Use monthly inputs when you have them

Twelve daily-average resource values can show seasonality. A month at 2.5 hours yields 12 kWh/day for this example system; a month at 5.5 hours yields 26.4 kWh/day. Multiply each daily estimate by that month's number of days before adding the year.

The PVWatts API documentation distinguishes monthly solar-radiation values from monthly AC energy output. Copying AC energy back into a peak-sun-hours field would confuse the model's input and output. Use the source's units, retain its date and location, and keep any illustrative default clearly marked until you replace it with a defensible input.

Keep learning

Build a monthly solar-production table without hiding the assumptions