PVWatts Review: Features, Pricing & Pros vs Cons (2026)

PVWatts helps you estimate electricity production when the proposed system is still described by a few inputs. It is useful for screening a site and checking assumptions before detailed design. The result is modeled AC energy, not a measured yield, a roof layout, an electrical approval or a guaranteed saving.

This is a documentation-based review, not a timed software test. SurgePV publishes it and sells solar software. We checked the official calculator and API documentation on 11 October 2026; we have not independently validated PVWatts against a monitored installation. Older resources use NREL’s name; the current laboratory website identifies the organization as the National Laboratory of the Rockies (NLR).

What PVWatts Actually Produces

The PVWatts calculator estimates grid-connected PV production from a location and system configuration. Its simplified input approach is helpful before final equipment selection. The estimate still needs a defensible capacity, orientation and loss allowance; a convenient interface does not make uncertain site inputs reliable.

The official V8 API documentation distinguishes annual and monthly AC energy from hourly AC power. That distinction matters when copying results into a spreadsheet or customer proposal.

Source: PVWatts V8 response-field documentation. These are modeled outputs, not field measurements. Downloaded data should travel with its weather dataset, system inputs and model version.

Inputs That Deserve Your Attention

PVWatts uses generic module categories and array configurations. It also exposes a DC-to-AC ratio and inverter efficiency. Saying the tool has “no inverter modeling” is therefore inaccurate: it models conversion behavior without selecting a specific commercial inverter and checking its complete electrical operating envelope.

Start with the proposed DC nameplate capacity. A roof’s area does not establish its installed capacity until you have a feasible layout. Keep tilt and azimuth consistent with the intended array, and split materially different orientations into appropriately documented cases rather than silently treating the roof as one plane.

The API documentation lists bifaciality, albedo and monthly soiling inputs. A bifacial option does not justify an assumed rear-side gain. Use the module’s published bifaciality and a defensible ground-reflectance assumption. Preserve the inputs so another reviewer can reproduce the scenario.

Keep System Losses Separate From Inverter Efficiency

A loss percentage is an assumption about mechanisms outside the explicitly modeled conversion behavior. Do not describe it as a universal system-efficiency rating. The PVWatts documentation handles inverter efficiency separately; placing the inverter loss into the general loss allowance as well can distort the estimate.

A site with nearby trees also needs more than a convenient default. A simplified loss allowance does not describe each obstruction’s position, seasonal shadow or impact on string mismatch. Use a site-specific assessment and a suitable shading workflow when those effects could change the decision. Our shading-analysis overview explains the next design-stage questions.

How to Interpret Accuracy

This review does not assign a universal percentage accuracy to every PVWatts project. Accuracy depends on the weather reference, input quality, equipment behavior and the comparison period. A typical-weather estimate and a measured calendar year’s generation answer different questions.

When actual production is available, compare equivalent periods and explain downtime, curtailment, soiling and configuration changes. An apparent modeling error can come from a mismatch between the modeled system and the installed system. A close annual match can also hide monthly errors that cancel out.

Use the result as preliminary evidence. For a lender, performance contract or equipment guarantee, obtain the required modeling method and review criteria from the party relying on the estimate. Software branding alone does not establish acceptance.

Developer Access: Check the Response, Not Just the Number

The V8 endpoint requires an API key and returns errors, warnings, inputs and weather-station information alongside outputs. Save those fields. A production integration should handle missing data and invalid requests instead of displaying a blank response as zero generation.

The official API documents a limit of 1,000 requests per hour. Check the current developer terms before planning a larger service, and keep private keys out of public browser code. The documented dataset options include nsrdb, tmy2, tmy3 and intl; nsrdb is an option name, not a promise that every location uses one identical weather vintage.

No private API request or live project simulation was performed for this review. The discussion describes the published interface.

PVWatts, SAM and a Design Platform Serve Different Jobs

Choose the next tool from the missing output, rather than assuming a paid product must produce a better estimate.

SAM’s official overview documents both performance and financial models. It should not be dismissed as unsuitable for commercial work simply because it is free. PVGIS provides an independently documented resource and performance workflow; agreement between calculators does not remove uncertainty when they share similar assumptions.

For the design stage, prepare a representative project and evaluate SurgePV’s documented design workflow. Ask to see the required output and its assumptions. We do not claim a measured time saving or automatic code compliance from this documentation review.

A Practical Handoff Checklist

Before forwarding a PVWatts estimate:

1. Save the location, resource dataset and model version.
2. Label the capacity as DC and the production as AC energy.
3. Record orientation, mounting, inverter and loss assumptions.
4. Explain what is preliminary and which site measurements are pending.
5. Keep the estimate separate from an installation-ready layout and electrical drawings.
6. State which additional review the customer’s decision requires.

This preserves the estimator’s usefulness without asking it to provide documents it does not produce.

Frequently Asked Questions

Is PVWatts free?

PVWatts is offered as a free production estimator. The web calculator and developer interface serve different access needs; the API requires a key. Check current access terms for integrations. This review does not promise that a government service’s future terms or availability will never change.

Can PVWatts design strings or generate an SLD?

PVWatts estimates production from a simplified system description. Its documented interface is not an equipment-specific string-design or single-line-diagram generator. Use a suitable design workflow and qualified review for operating limits, protective devices, conductors and the documentation required by the project jurisdiction.

Is the annual result a guaranteed saving?

No. Annual energy is a modeled production estimate. Bill savings also depend on consumption timing, tariffs, export compensation, operating costs and financing. A production total should not be copied directly into a savings promise or treated as measured performance.

Does PVWatts provide support?

The official calculator and developer documentation publish contact and feedback routes. “No support” is too broad. Those routes do not establish a paid service-level agreement; confirm the support arrangements if your application depends on continued API availability.