Julian Day Number Converter

How the Julian Day Number Converter works

Unlike a civil calendar, which resets its day count every January 1st and complicates arithmetic with leap years and variable month lengths, the Julian Day Number is one uninterrupted integer count, with day 0 defined as noon Universal Time on January 1, 4713 BC in the proleptic Julian calendar. Because it never resets, finding the number of days between any two dates — however far apart, spanning any number of centuries — is just subtraction of their two JDNs, with no calendar-aware logic required at all.

This library, like every other calculator on this site, computes JDN using the proleptic GREGORIAN calendar throughout — meaning Gregorian leap-year rules are extended backward mathematically even for dates before 1582, when the Gregorian calendar didn't yet exist. A source that instead switches to the older Julian calendar for pre-1582 dates (following the actual historical adoption boundary) will report a different JDN for those older dates than this tool does; this is a genuine convention difference between sources, not a bug in either one.

A subtlety worth being precise about: the Julian Day ticks over at NOON Universal Time, not midnight, an astronomical convention dating back to when astronomers observed through the night and didn't want a single night's observations split across two different day numbers. That's why midnight at the start of a civil date is always JD (that date's noon-anchored JDN) minus 0.5 — the fractional .5 marks midnight sitting exactly half a day before that date's own noon anchor point.

Worked example

July 16, 2026 converts to Julian Day Number 2,461,238 (noon UT anchor). Checking that figure against a well-known reference point: January 1, 2000 at noon UT is JDN 2,451,545 exactly — a widely used astronomical epoch called J2000.0. The difference, 2,461,238 − 2,451,545 = 9,693 days, should equal the actual number of days between those two dates: 26 full years (2000 through 2025) contain 7 leap years (2000, 2004, 2008, 2012, 2016, 2020, 2024), giving 26 × 365 + 7 = 9,497 days to reach January 1, 2026, plus 196 more days from January 1 to July 16, 2026 — 9,497 + 196 = 9,693, confirming the two figures agree.

Compare that to the Unix timestamp, a completely different epoch used across computing: January 1, 1970 at 00:00 UT is JD 2,440,587.5 (not a round number, since midnight sits half a day before that date's noon-anchored JDN of 2,440,588). The Unix epoch is a 20th-century computing convention measuring seconds since 1970; the Julian Date is a 16th-century astronomical convention measuring days since 4713 BC — two genuinely unrelated numbering systems that happen to both be usable to timestamp the same instant.

Edge cases this tool handles correctly

JD ticks over at noon, not midnight

A Julian Date's fractional part represents elapsed time since the PREVIOUS noon, not since midnight — so a Julian Date ending in .0 corresponds to noon UT, one ending in .5 corresponds to midnight UT at the start of the next civil date, and this offset is a deliberate, permanent feature of the convention, not an inconsistency to correct.

Proleptic Gregorian only, unlike some historical sources

This tool computes every JDN using Gregorian leap-year rules extended backward through all of history, even before the Gregorian calendar's actual 1582 adoption — a source using the real historical Julian-to-Gregorian switchover will report different JDNs for dates before that boundary, a genuine convention mismatch rather than an error in either calculation.

Distinct from the Unix timestamp

The Unix Timestamp Converter measures seconds elapsed since January 1, 1970 — a computing-era epoch with no astronomical meaning. The Julian Date measures days elapsed since 4713 BC on an entirely different numbering convention; the two scales share no common reference point beyond both being usable to timestamp the same real instant, and converting between them requires going through an actual calendar date as the intermediate step.

Distinct from the ordinal day-of-year

The Day of Year Calculator's ordinal (1 through 365 or 366) resets to 1 every January 1st, making it useless for measuring a span across a year boundary without extra calendar-aware arithmetic. The Julian Day Number never resets at all, which is precisely why it exists — subtracting two JDNs directly gives an exact day span with zero calendar-boundary logic needed, unlike subtracting two day-of-year ordinals from different years.

Negative or very large Julian Day Numbers

Dates far enough in the past compute a JDN smaller than the day-0 reference point and are represented as negative numbers; dates far in the future simply continue counting upward with no upper limit built into the JDN scale itself, unlike the Unix timestamp's well-known year-2038 32-bit overflow boundary.

Half-integer Julian Dates for exact midnight and noon

A Julian Date's fractional part is exactly 0.0 only for an instant at noon UT and exactly 0.5 only for an instant at midnight UT — any other time of day produces a fraction strictly between those two values, computed as the elapsed seconds since the most recent noon divided by 86,400 seconds in a full day.

Frequently asked questions