Julian Day Calculator

Computes the Julian Day Number (JDN) for a given calendar date. JDN is a continuous count of days since noon UTC on January 1, 4713 BC (proleptic Julian calendar). It's used in astronomy and chronology to avoid calendar irregularities.

The Modified Julian Date (MJD = JDN − 2,400,000.5) is more practical for modern dates, fitting comfortably in 32-bit integers.

Julian Day Number was proposed by Joseph Justus Scaliger in 1583 in Opus de Emendatione Temporum, naming it after his father Julius Caesar Scaliger rather than after Julius Caesar. The chosen epoch (noon UT on January 1, 4713 BC in the proleptic Julian calendar) was selected as the start of a 7980-year cycle combining three ancient periods: the 28-year solar cycle, the 19-year Metonic lunar cycle, and the 15-year indiction cycle. The cycle's start is the most recent year before recorded history where all three cycles align at year 1, ensuring all historical dates fall after the epoch with positive Julian day numbers.

A worked example: 2026-05-07 (today's date in the user context) corresponds to JDN 2,460,838 (rounded to the integer day starting at noon UTC). Modified Julian Date for the same: MJD 60,837 (subtracting 2,400,000.5 and noting that MJD starts at midnight, not noon, on November 17, 1858). The half-day offset between JDN and MJD (JDN integer at noon, MJD integer at midnight) is the most common source of confusion in software that mixes the two; deciding which is in use upfront and converting at I/O boundaries prevents drift bugs.

Applications are concentrated in astronomy and chronology. Astronomical observations, ephemerides, and orbital element calculations use Julian Date (with fractional days for time of day) because the continuous numbering avoids the discontinuities of calendar arithmetic. The 1582 Gregorian reform skipped 10 days (October 4, 1582 was followed by October 15, 1582 in Catholic Europe), but Julian Day Number flows through this transition continuously; computing days between dates that span the reform requires either Julian Day arithmetic or careful handling of the calendar shift.

Limitations are mostly notational and span multiple conventions. The astronomical year-numbering convention treats year 1 BC as year 0 and year 2 BC as year −1, eliminating the gap that historian-style numbering preserves (1 BC immediately followed by 1 AD with no year 0). The proleptic Gregorian calendar extends Gregorian rules backward indefinitely and is the modern computational standard, but historical documents may use Julian dating; converting between proleptic Julian and proleptic Gregorian requires the date-shift table that grows by 1 day each century not divisible by 400. Software libraries (Astropy, Skyfield, JPL Horizons) handle these conventions correctly when configured properly; manual calculation is error-prone for dates more than a few centuries from the present.

MJD is preferred for modern computation because integer values fit in 32-bit fields, the day boundary aligns with civil midnight, and the magnitude is small enough for direct human readability of recent dates.