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 }}

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Calendar dates are a rough guide for gardens, fields, turf, and pest scouting because living organisms respond to temperature as well as time. A cool spring can hold back emergence even when the planting date looks normal. A warm spell can move insect activity forward before a date-based reminder would notice it. Growing degree days, often shortened to GDD, turn daily warmth into a running total that can be compared with crop, pest, or phenology milestones.

A degree day is a heat unit above a chosen lower threshold. If a crop or insect model uses a 50 F base temperature, a day with an average temperature of 65 F contributes 15 F-day. Days below the base add nothing in that model. Many agricultural models also use an upper cap because development may slow, level off, or become heat stress rather than faster progress once temperatures climb too high.

Base temperature: The lower threshold below which the model counts no development.
Upper cap: The temperature ceiling used by capped methods so very hot days do not keep adding extra heat.
Biofix: The biological or calendar start point for accumulation, such as planting, transplanting, budbreak, or first trap catch.
Stage threshold: The GDD total tied to a growth, scouting, or management milestone.

The same weather can produce different totals when the model changes. Sweet corn, tomatoes, squash vine borer scouting, and cool-season turf timing can all use different thresholds and action notes. Pest models may start from a first trap catch, while crop models may start from planting, transplanting, or a defined growth stage. A GDD total is useful only when the base, cap, calculation method, biofix, and stage table come from guidance that matches the organism and location being watched.

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

GDD totals are timing cues, not direct proof that a crop is ready or a pest treatment is needed. Weather-station distance, shade, soil temperature, cultivar, irrigation, plant stress, trap counts, and local advisories can all move real-world development away from the estimate. A threshold crossing should prompt a field check, not replace one.

Unit discipline matters as much as the formula. A threshold calibrated in F-day should not be compared with a C-day total without conversion, and a model built from one calculation method may not line up with totals from another weather service. Keeping the same unit scale and method across a season makes the accumulated total more useful than chasing extra decimal places.

How to Use This Tool:

Use the calculator as a heat ledger: choose the model assumptions, provide daily weather rows, then compare the cumulative total with stage thresholds from local guidance.

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 data. Changing units reloads the selected model's base, cap, and stage thresholds, but it does not convert already pasted weather rows.
Do not paste Fahrenheit temperatures while the page is set to Celsius, or compare C-day totals with F-day thresholds.
Pick a Calculation method. Modified crop average raises lows below the base and clips highs above the cap. Upper-cap average clips high temperatures only. Simple average uses the raw daily mean before subtracting the base.
Set Base temperature, Upper cap, and Biofix date. Rows before the biofix date are ignored, so choose a start such as planting, transplanting, first trap catch, budbreak, or the model's named calendar date.
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 when the columns are recognizable.
Edit Stage thresholds as stage name, target GDD, and action note. Replace draft stages with extension guidance, cultivar notes, pest advisories, or field records when you have a better local threshold table.
Review 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 when totals need checking.
Warnings usually point to an unparsed weather row, invalid stage row, cap at or below the base, invalid biofix date, duplicate date, sorted date, or non-ascending stage target.

Interpreting Results:

The headline total is cumulative heat after the biofix date, shown as F-day or C-day. The Stage Outlook is the main action 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 it tells you	What to double-check
Accumulation Ledger	Lists each counted date, daily GDD, cumulative GDD, and the latest reached stage label.	Confirm that the first counted row is on or after the intended biofix and that the weather values use the selected unit.
Stage Outlook	Compares the current cumulative total with each target and estimates remaining GDD.	Verify target values against local crop, pest, cultivar, label, and extension guidance before acting.
Heat Pace Curve	Plots daily GDD bars, cumulative GDD, and listed thresholds so acceleration or delay is visible over time.	A short weather sample or an unusual warm spell can make the pace look more certain than it is.
Method Audit	Shows whether each row used min/max, mean, or direct GDD, and whether a cutoff changed the counted value.	Use this table when totals differ from another calculator, bulletin, or station report.

Estimated dates for pending stages come from the recent average daily GDD over the selected forecast pace window. If the recent pace is zero, the estimate says it needs recent pace instead of inventing a date from a cold stretch.

A near threshold deserves attention, not automatic treatment. Check plant stage, trap counts, pest size, crop condition, soil moisture, and product labels or extension instructions before making a management decision.

Technical Details:

Degree-day models assume development has a useful temperature range. Below the lower threshold, the model counts no development. Between the lower and upper thresholds, warmer daily temperatures add more heat units. Above the upper threshold, capped methods stop crediting extra heat because development may level off, the organism may be stressed, or the original model was calibrated with a cutoff.

Daily maximum and minimum values approximate the temperature curve through a 24-hour day. They are easy to get from weather stations and home thermometers, but they do not reproduce how long the canopy, soil surface, or insect habitat spent above the base. That is why the same raw weather can produce different totals under simple average, modified average, sine-wave, or station-specific methods.

Formula Core:

The min/max calculation adjusts the low and high according to the selected method, averages them, subtracts the biological base, and floors negative daily values at zero.

\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. A cold day cannot subtract from the running total because the daily contribution is floored at zero.

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 capped mean path; the 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 appropriate when a trusted bulletin, weather station, or spreadsheet has already calculated daily heat units with the exact method you want. Mixing direct GDD rows with raw temperature rows only makes sense when the outside values use the same unit scale, base, cap, and method assumptions.

Stage, biofix, precision, and estimate 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 recent pace is above zero.
Display precision	0, 1, or 2 decimals.	Changes rounded values in summaries, tables, chart data, and structured output without changing the calculation path.

F-day and C-day totals are not numerically interchangeable. A temperature difference of 1 C equals 1.8 F, so a model calibrated in one scale should be compared with thresholds in that same scale. Converting units after the fact is less reliable than keeping weather rows, base temperatures, caps, and stage targets in one consistent system.

Accuracy and Privacy Notes:

GDD output depends on the weather data, model thresholds, calculation method, and biofix choice behind it. The calculator does not fetch weather records, verify station quality, or confirm current pest advisories.

Use a weather station close to the field, garden, greenhouse, or turf area when possible. A shaded yard, paved microclimate, slope, or distant airport can move daily heat totals away from the plant canopy.
Keep the same calculation method when comparing totals with extension bulletins, seed guides, pest advisories, or crop models. Method differences are a common reason totals disagree.
Use action notes as reminders, not treatment instructions. Pesticide, herbicide, harvest, irrigation, and fertility decisions still need current labels, local guidance, and field observations.
Pasted rows and uploaded 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 build the accumulation table.

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.

Advanced Tips:

Use Load sample to confirm the selected model and method before replacing the sample with your own station rows.
Keep Forecast pace window short when recent weather changed quickly, and use a longer window when you want a smoother ETA for the next stage.
Set GDD display precision to one decimal for field notes and two decimals only when comparing close model runs or checking another source.
Use Method Audit when totals differ from a bulletin, spreadsheet, or weather service; it shows whether a row was min/max, mean, or direct GDD and whether a cutoff changed it.
Replace preset Stage thresholds with local extension, cultivar, pest, or label guidance before using the action notes for management timing.

Worked Examples:

Tomato transplant heat

A gardener keeps the tomato model, Fahrenheit units, modified crop average, base 50 F, cap 86 F, and a May 1 biofix. 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 the remaining heat 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 why the two totals diverge.

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 identifies the GDD column. The Accumulation Ledger uses 18.4 as the daily value, and the Method Audit labels the row as direct GDD. The scout should only mix that row with temperature-derived rows when both sources use the same base, cap, method, and unit scale.

Troubleshooting a warning-heavy result

If rows cannot 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 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 outside model's method 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.

Are pasted or uploaded weather rows sent away?

Rows are read in the browser for the calculation. The page can build the accumulation ledger, stage outlook, method audit, and chart from pasted or uploaded text without sending those weather rows to a weather service.

References:

Growing Degree Days, Midwestern Regional Climate Center.
Using Degree Days to Time Treatments for Insect Pests, Utah State University Extension.
Utilizing Growing Degree Days for Corn Production, Utah State University Extension.
Growing Degree Days for Insect Pests, Iowa State University Extension.
Vegetable degree-day models: An introduction for farmers and gardeners, Oregon State University Extension, January 2021, reviewed 2025.