About

Decimal dates express calendar dates as a continuous numerical value where the integer part represents the year and the fractional part represents the proportion of the year elapsed. A date of 2024.5 indicates exactly halfway through 2024 (approximately July 2nd at noon). This format eliminates discontinuities inherent in calendar systems, making it essential for regression analysis, time-series modeling, and astronomical calculations where uniform time intervals matter. The conversion accounts for leap years: a standard year contains 365 days while leap years contain 366, affecting the decimal precision of each day's contribution to the annual fraction.

Incorrect decimal date conversion introduces systematic errors in longitudinal studies. A common mistake involves treating all years as 365 days, which accumulates 0.25 day error annually - significant when correlating events across decades. This tool implements the astronomical convention where January 1st at 00:00:00 equals year.0 and December 31st at 23:59:59 approaches year.9999. Time components (hours, minutes, seconds) contribute to sub-day precision, critical for satellite tracking and seismological event timing.

Formulas

The decimal date conversion expresses any calendar date as a continuous real number. The integer component equals the Gregorian year, while the fractional component represents elapsed time within that year as a proportion of total annual days.

D decimal = Y + DOY - 1 + h 24 + m 1440 + s 86400 N

Where D_decimal = decimal date result, Y = four-digit year, DOY = day of year (1 to 365 or 366), h = hours (0 - 23), m = minutes (0 - 59), s = seconds (0 - 59), and N = total days in year (365 or 366).

Leap year determination follows the Gregorian calendar rule:

isLeap (Y) = {TRUE if (Y mod 4 = 0) \land ((Y mod 100 \neq 0) \lor (Y mod 400 = 0)) FALSE otherwise

The day of year calculation sums days from preceding months plus the current day:

DOY = d + M - 1 \sum i = 1 days i

Where d = day of month, M = month number (1 - 12), and days_i = days in month i, accounting for February having 28 or 29 days.

Reference Data

Date	Decimal Date	Day of Year	Notes
January 1, 2024 00:00	2024.0000	1	Year start (leap year)
January 15, 2024 12:00	2024.0396	15	Mid-day precision
February 29, 2024 00:00	2024.1612	60	Leap day
March 20, 2024 03:06	2024.2176	80	Vernal equinox 2024
July 1, 2024 00:00	2024.4973	183	Near mid-year
July 2, 2024 12:00	2024.5014	184	Exact mid-year (leap)
September 22, 2024 12:44	2024.7260	266	Autumnal equinox 2024
December 31, 2024 23:59	2024.9999	366	Year end (leap)
January 1, 2025 00:00	2025.0000	1	Non-leap year start
July 2, 2025 00:00	2025.4986	183	Mid-year (non-leap)
December 31, 2025 23:59	2025.9999	365	Year end (non-leap)
January 1, 2000 00:00	2000.0000	1	Y2K / Century leap
February 28, 1900 00:00	1900.1589	59	No Feb 29 (not leap)
March 1, 1900 00:00	1900.1616	60	Century rule exception
June 21, 2024 20:51	2024.4722	173	Summer solstice 2024
December 21, 2024 09:20	2024.9739	356	Winter solstice 2024
April 15, 2024 00:00	2024.2869	106	US Tax Day
October 31, 2024 18:00	2024.8333	305	Halloween evening
August 15, 2024 06:30	2024.6202	228	Quarter-day example
November 11, 2024 11:00	2024.8627	316	Veterans Day

Frequently Asked Questions

The converter dynamically detects leap years using the Gregorian rule: divisible by 4, except century years must also be divisible by 400. This means 2024 and 2000 are leap years (366 days), while 1900 and 2100 are not (365 days). The denominator in the decimal fraction adjusts accordingly, so June 30th yields a slightly different decimal in leap versus non-leap years. For example, June 30, 2024 equals approximately 2024.4945 while June 30, 2025 equals approximately 2025.4932.

For most research purposes, 4 decimal places provide day-level precision (0.0001 year ≈ 0.88 hours). Astronomical applications often require 6-8 decimal places to resolve sub-minute timing. Seismology and satellite tracking may need 8+ decimals for second-level accuracy. The tool supports up to 10 decimal places. Note that beyond 6 decimals, floating-point arithmetic limitations may introduce rounding artifacts of approximately ±0.5 seconds.

This converter operates on local time as entered. For UTC-based decimal dates (standard in astronomy), input the UTC time directly. The difference matters: 2024.5000 in UTC versus EST represents a 5-hour offset (approximately 0.0006 in decimal terms). Published astronomical decimal dates typically use UTC or Julian Date, which has a different epoch (noon on January 1, 4713 BCE).

Use the reverse conversion mode. The algorithm extracts the integer part as the year, multiplies the fractional part by N (365 or 366), then iteratively subtracts month lengths to find the month and remaining day. Time components derive from the sub-day fraction: multiply by 24 for hours, take the remainder times 60 for minutes. Accumulated floating-point errors may cause ±1 second deviation in round-trip conversions.

Decimal date uses the Gregorian year as its integer component (e.g., 2024.5), while Julian Date counts continuous days since January 1, 4713 BCE (e.g., JD 2460494.5 for July 2, 2024 noon). Julian Date is preferred in astronomy for its unambiguous continuity across calendar reforms. Decimal dates remain useful for human-readable year-relative positioning in publications and databases where annual patterns matter.

The astronomical convention treats the start of January 1st as the year boundary. The formula uses (DOY - 1) rather than DOY to achieve this: on January 1st, DOY equals 1, so (1-1)/N = 0. Some systems use a "day 0" convention where January 1st noon equals year.0014; this tool follows the more common "day 1 start" convention used in most scientific software.

The converter handles years from 1 CE onward using the Gregorian proleptic calendar. For BCE dates, astronomical convention uses year 0 (1 BCE) and negative years (2 BCE = -1). Enter these as negative values. Note that the historical Julian calendar differed from Gregorian before October 15, 1582; dates before this point represent proleptic Gregorian calculations, not historical calendar readings.