Growing Degree Days Calculator

Current heat total

{{ statusBadge.label }} {{ validRecordCount }} day{{ validRecordCount === 1 ? '' : 's' }} {{ modelLabel }} {{ methodLabel }}

Crop or pest model:

Start with the closest model, then edit thresholds or actions for your local extension guidance.

Temperature unit:

Changing units reloads the selected model's base, cap, and stage thresholds; it does not convert pasted weather rows.

Calculation method:

Use modified crop average for corn-style models; use simple average when your source already handles cutoffs.

Base temperature:

Common warm-season crop base is 50 F or 10 C.

Upper cap:

Many crop GDD workflows cap warm-season days around 86 F or 30 C.

Biofix date:

Rows before this date are ignored in the cumulative total.

Daily temperatures:

Accepted columns include date,tmin,tmax, date,tmean, or date,gdd. Valid rows are sorted by date; duplicate dates are counted and flagged.

Drop CSV, TSV, or TXT onto the textarea.

Stage thresholds:

Format: Stage name, target GDD, action. Targets should rise in the selected {{ gddUnitLabel }} unit.

Keep local cultivar, pest, and extension thresholds as your source of truth.

Rows or settings need review

{{ warning }}

Forecast pace window:

Short windows react faster to weather swings; longer windows smooth out cold or hot days.

days

GDD display precision:

Use one decimal for field notes; use two when comparing close models.

Date	Low	High	Daily GDD	Cumulative	Stage	Copy
{{ row.date }}	{{ row.minLabel }}	{{ row.maxLabel }}	{{ row.dailyLabel }}	{{ row.cumulativeLabel }}	{{ row.stageLabel }}

Stage	Target	Status	Remaining	ETA	Action	Copy
{{ row.stage }}	{{ row.targetLabel }}	{{ row.status }}	{{ row.remainingLabel }}	{{ row.etaLabel }}	{{ row.action }}

Source row	Date	Input type	Raw mean	Adjusted low	Adjusted high	Counted GDD	Method note	Copy
{{ row.sourceLabel }}	{{ row.date }}	{{ row.inputType }}	{{ row.rawMeanLabel }}	{{ row.adjustedMinLabel }}	{{ row.adjustedMaxLabel }}	{{ row.dailyLabel }}	{{ row.methodNote }}

Export to PDF Fullscreen

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Growing degree days measure how much useful heat has accumulated for a plant, insect, or other temperature-driven organism after a chosen starting point. Calendar dates can drift from year to year because a cool spring slows development and a warm spell speeds it up. A GDD total gives growers, gardeners, and scouts a way to compare that seasonal heat against growth stages, harvest checks, trap timing, or pest scouting windows.

The basic idea is simple: each day contributes heat above a biological base temperature, and some models also stop counting extra heat above an upper cap. A tomato transplant, sweet corn stand, squash vine borer flight window, and cool-season turf plan can all use different thresholds or action notes, so the total only makes sense when the base, cap, start date, and stage targets match the crop or pest being watched.

Bars of daily heat above a base temperature accumulating toward a stage threshold.

GDD totals are decision aids, not field guarantees. A threshold can point to a scouting window or management checkpoint, but local cultivar choice, pest pressure, soil temperature, shade, irrigation, weather-station distance, and actual field observations still decide what should happen next.

How to Use This Tool:

Use the calculator as a heat ledger: choose the biological model, paste the daily weather rows, then compare the cumulative total with stage thresholds that you trust for your location.

Choose Crop or pest model. The presets load a base temperature, upper cap, and editable stage thresholds for tomato growth, sweet corn growth, squash vine borer scouting, cool-season turf timing, or a generic warm-season crop.
Select Temperature unit before pasting weather rows. Changing units reloads the selected model's base, cap, and stage thresholds, but it does not convert pasted temperature data.
Pick a Calculation method. Modified crop average raises low temperatures below the base and clips highs above the cap. Upper-cap average clips high temperatures only. Simple average uses the daily mean without cutoff adjustments.
Set Base temperature, Upper cap, and Biofix date. Rows before the biofix date are ignored, so use the planting, transplanting, first trap catch, budbreak, or first sustained warm day that matches your model.
Paste or browse for Daily temperatures. Accepted rows include date, minimum, maximum; date, mean; or date, GDD. CSV, semicolon, tab, whitespace, and header rows are handled as long as the units match the selector.
Edit Stage thresholds as stage name, target GDD, and action note. Use local extension guidance, cultivar notes, pest advisories, or your own field records when the preset stages are only a planning starting point.
Check the summary and Accumulation Ledger first. Then use Stage Outlook for reached or pending stages, Heat Pace Curve for daily and cumulative heat, and Method Audit to see how each row was counted.

If a warning appears, fix the named input before using the stage outlook. Common causes are an invalid weather row, an invalid stage row, an upper cap at or below the base temperature, an invalid biofix date, or stage targets that were entered out of ascending order.

Interpreting Results:

The headline total is the cumulative heat after the biofix date, reported in F-day or C-day units. Treat the Stage Outlook as the main decision view: a stage is Reached when the cumulative total is greater than or equal to its target, and Pending when more heat is still needed.

How to read growing degree day outputs
Output	What to trust	What to verify
Accumulation Ledger	Shows each counted date, daily GDD, cumulative GDD, and the reached stage label.	Check that the first counted date is on or after the intended biofix and that units match the weather rows.
Stage Outlook	Compares the current cumulative total with each target and estimates remaining GDD.	Confirm stage targets against local crop, pest, cultivar, and extension guidance before acting.
Heat Pace Curve	Shows whether daily heat is speeding up, slowing down, or crossing listed thresholds.	Do not read a smooth trend into a short weather sample or a forecast window with only a few warm days.
Method Audit	Explains whether a row used min/max, daily mean, or direct GDD, and whether a cutoff changed the counted value.	Use this view when totals differ from another source, because method choices can change the result.

A near threshold does not prove a field is ready for treatment, harvest, or pruning. It means the expected window deserves attention. Verify with plant stage, trap counts, pest size, crop condition, soil moisture, and label or extension instructions before making a management decision.

The estimated date for a pending stage comes from the recent average daily GDD. If recent days are cold enough to add no heat, the ETA will say it needs recent pace instead of inventing a date.

Technical Details:

Degree-day models treat development as accumulated heat above a lower threshold. Below that base temperature, the organism is assumed to make no measurable progress for the model. Above an upper cap, many crop-style models limit the counted contribution because extra heat no longer increases development at the same rate, or may stress the organism instead of advancing it.

Daily minimum and maximum temperatures are a practical approximation of the temperature curve through the day. They are easier to obtain than hourly observations, but they cannot reproduce every short warm or cold period. That is why two tools can differ if one uses a simple average, one clips daily highs and lows, and another uses a sine-curve method from a weather network.

Formula Core:

The daily min/max calculation starts with an adjusted low and adjusted high, then subtracts the biological base from their average.

\begin{array}{rcl} {GDD}_{d} & = & \max (0, \frac{T_{low adjusted} + T_{high adjusted}}{2} - T_{base}) \\ {GDD}_{total} & = & \sum_{d = biofix}^{last counted day} {GDD}_{d} \end{array}

For a modified crop average with base 50 F and cap 86 F, a day with low 61 F and high 88 F uses 61 and 86. The daily GDD is ((61 + 86) / 2) - 50 = 23.5 F-day. Negative daily values are floored to zero, so a cold day does not subtract from the seasonal total.

Calculation method behavior for weather row types
Weather row type	Simple average	Upper-cap average	Modified crop average
Minimum and maximum	Uses the raw daily mean, then subtracts the base.	Clips the high to the upper cap, leaves the low unchanged, then subtracts the base.	Raises lows below the base and clips highs above the cap before averaging.
Daily mean	Subtracts the base from the supplied mean.	Clips the mean at the upper cap before subtracting the base.	Uses the same mean cap behavior; a zero floor handles means below the base.
Direct GDD	Uses the supplied nonnegative daily GDD value.	Uses the supplied nonnegative daily GDD value.	Uses the supplied nonnegative daily GDD value.

Direct GDD rows are useful when a weather service, pest bulletin, or station report has already calculated daily heat units with the exact method you want. Mixing direct GDD rows with raw temperature rows can be valid, but only when the outside source uses the same unit scale, base, cap, and method assumptions.

Stage and forecast rules for growing degree day outputs
Rule	Boundary	Result effect
Biofix filter	Date must be on or after the biofix date.	Earlier weather rows are skipped. If the biofix date is invalid, all valid rows are counted and a warning appears.
Stage status	Cumulative GDD >= target GDD.	The stage is marked Reached; otherwise it remains Pending.
Remaining heat	Target GDD minus current cumulative GDD, floored at zero.	Shows how many F-day or C-day units remain before the listed stage.
ETA	Remaining GDD divided by recent average daily GDD, rounded up to whole days.	Projects a date from the last counted row only when the recent pace is above zero.
Display precision	0, 1, or 2 decimals.	Changes rounded values in the summary, tables, chart data, and structured output without changing the underlying daily calculation path.

F-day and C-day totals are not numerically interchangeable. A difference of 1 C is equal to 1.8 F, so a model calibrated in one scale should be compared with thresholds in that same scale. The unit selector reloads preset thresholds for the selected model, but pasted weather values remain exactly as entered.

Accuracy and Privacy Notes:

GDD output is only as good as the weather data, model thresholds, and biofix choice behind it. The calculator does not fetch weather records or verify local pest advisories for you.

Use a weather station close to the field or garden when possible. A shaded yard, paved microclimate, greenhouse, or distant airport can move daily heat totals away from the crop canopy.
Keep the same calculation method when comparing totals with extension bulletins, seed guides, or pest models. Method differences are a common reason totals disagree.
Use the stage action notes as reminders, not treatment instructions. Pesticide, herbicide, and crop-management decisions still need current labels and local guidance.
Pasted rows and local text files are read in your browser for the calculation. The page does not need to send your weather rows to a weather service to produce the ledger.

When a threshold is close, field scouting matters more than another decimal place. Check actual plants, pest stages, trap catches, or turf condition before acting on the number.

Worked Examples:

Tomato transplant heat: A gardener keeps the default tomato model, Fahrenheit units, modified crop average, base 50 F, cap 86 F, and biofix date of 2026-05-01. The sample rows from May 1 through May 9 accumulate 190.5 F-day. The Accumulation Ledger marks Transplant establishment as reached because the total is above 180 F-day, and the Stage Outlook shows about 259.5 F-day remaining before First flower watch.

Hot sweet corn day: A sweet corn row reads 2026-06-14, 68, 94 with base 50 F and cap 86 F. Under Modified crop average, the high is clipped to 86 F, so the counted daily value is ((68 + 86) / 2) - 50 = 27 F-day. Under Simple average, the same row would count ((68 + 94) / 2) - 50 = 31 F-day. The Method Audit explains the difference instead of making the two totals look interchangeable.

Using a pest bulletin row: A scout receives station data that already lists daily heat units for squash vine borer. A row such as 2026-06-03, 18.4 can be entered as a direct GDD row when the header names the GDD column. The Accumulation Ledger uses 18.4 as the daily value, and the Method Audit labels it as a direct GDD row. The scout should only mix that row with temperature-derived rows if both sources use the same base, cap, and method.

Troubleshooting a blank or warning-heavy result: If the summary says weather rows are needed or the warning box says rows could not be parsed, check the first few lines for a recognizable date and numeric min/max, mean, or GDD value. A header such as date,tmin,tmax is accepted, but a row with a missing date or text where a temperature should be will be skipped until corrected.

FAQ:

What is a biofix date?

A biofix date is the start point for accumulation. It can be a planting date, transplant date, first trap catch, budbreak, or another biological event named by the crop or pest model. Rows before that date are ignored.

Should I use Fahrenheit or Celsius?

Use the scale that matches your weather rows and threshold guidance. The unit selector reloads preset base, cap, and stage values, but it does not convert pasted rows, so do not paste Fahrenheit temperatures while the page is set to Celsius.

Why does my total differ from an extension website?

The most common causes are a different weather station, start date, base temperature, upper cap, or calculation method. Compare the Method Audit with the method used by the outside model before treating either number as wrong.

Can I paste daily GDD values instead of temperatures?

Yes. A row with a date and GDD value is counted directly and floored at zero. Use that path when another trusted source has already calculated daily heat units with the method and unit scale you need.

Why does the stage ETA say it needs recent pace?

The ETA needs a recent average daily GDD above zero. If the latest counted rows add no heat, the page reports that it needs recent pace instead of projecting a stage date from a zero-growth stretch.

Glossary:

Growing degree days: Accumulated heat units above a biological base temperature, usually summed from a biofix date.
Base temperature: The lower threshold below which the model assumes development does not advance.
Upper cap: The high-temperature cutoff used by capped methods to limit how much heat a hot day can contribute.
Biofix date: The starting date or biological event used to begin summing daily heat units.
Stage threshold: A cumulative GDD target tied to a growth stage, scouting window, or management checkpoint.
Modified crop average: A daily average method that raises lows below the base and clips highs above the cap before subtracting the base.

References:

Degree-Days: About Degree-Days, University of California Statewide IPM Program, revised June 21, 2016.
Growing Degree Days for Insect Pests, Iowa State University Extension and Outreach, last reviewed May 1, 2022.
Calculating Degree Days, Iowa State University Extension and Outreach, April 17, 2008.
Using Degree Days to Time Treatments for Insect Pests, Utah State University Extension.
Using Growing Degree Days to Predict Insect Pests in the Landscape, University of New Hampshire Extension, April 27, 2023.