The short answer

A Julian Day Number (JDN) is a single integer assigned to every day, counting up from noon on 1 January 4713 BC in the Julian calendar. That starting day is JDN 0. Every day since has the next integer, with no months, leap years, eras or calendar reforms interrupting the sequence.

On 30 October 2026 the number is 2,461,344. The Julian Day Number for a date is the integer the day carries at noon; the Julian Date (JD) is the same count with a fraction attached — .0 at noon, .5 at midnight — and the Modified Julian Date (MJD) is the Julian Date minus 2,400,000.5, which keeps the numbers smaller.

Where the count comes from

The system was proposed by the French scholar Joseph Justus Scaliger in 1583, and named after his father, Julius Caesar Scaliger — not after Julius Caesar, whose calendar reform of 45 BC is a different thing. The name causes a persistent mix-up; the count has nothing to do with the Julian calendar's leap-year rule except that its starting day is expressed in that calendar.

Scaliger chose his starting point so that three old cycles all began together: the 28-year solar cycle, the 19-year Metonic (lunar) cycle and the 15-year indiction cycle. Multiplied together they give the Julian period of 7,980 years (28 × 19 × 15), and 1 January 4713 BC is the year all three cycles restart. A date inside the period is therefore fixed by one number instead of three cycle positions.

The day starts at noon, not midnight, because astronomers work through the night: a night of observation must not be split by a midnight date change. Noon on 1 January 4713 BC is JDN 0; midnight at the start of that day would be JD −0.5, which is why the Julian Date carries fractions.

How the count works

The rule is deliberately boring: each day gets the next integer. There are no month lengths to remember, no leap-year exceptions and no eras. The interval between two dates is a subtraction. The number for 30 October 2026 minus the number for 1 January 2000 — 2,461,344 minus 2,451,545 — is 9,799 days, which is also the count of days since the J2000 epoch.

The count is applied to Gregorian dates proleptically, meaning it is extended backwards before the Gregorian calendar existed. That is why a date like 1 January in the year 1 has a number (1,721,426) even though nobody used the Gregorian calendar then.

The numbers never skip. When the Gregorian calendar replaced the Julian calendar, Thursday 4 October 1582 (Julian) was followed by Friday 15 October 1582 (Gregorian). The labels jumped ten days; the count did not: the first day carries JDN 2,299,160 and the second JDN 2,299,161. The ten dates in between never existed as labels, but no number is missing.

Converting a date to its number

Converting a Gregorian date to its number is a fixed piece of arithmetic, usually called the Fliegel–Van Flandern algorithm. In outline: months January and February are treated as months 13 and 14 of the previous year (so the leap day sits at the end of the counted year, not in the middle of it); the year, month and day are then combined with the Gregorian leap-year corrections — a leap day every four years, except centuries, except centuries divisible by 400. The converter on this site runs that arithmetic and checks every result against an independent day count.

Going the other way — a number back to a date — reverses the same steps. The converter accepts whole numbers from 1,721,426 (1 January in the year 1) to 5,373,484 (31 December 9999); outside that range it has no date to return, because the supported calendar stops there.

Two details decide whether a conversion is right. First, the calendar: the algorithm uses the Gregorian rules for every date, including dates before 1582, so a historical Julian-calendar date must be converted to its Gregorian equivalent first. Second, the time of day: the integer belongs to noon. A date at midnight carries the previous integer plus a half — which is exactly what the .5 in a Julian Date means.

Worked examples

30 October 2026 → JDN 2,461,344. It was a Friday, 9,799 days after the J2000 epoch (noon on 1 January 2000), and its Modified Julian Date was 61,343.0 at midnight and 61,343.5 at noon.

1 January 2000 → JDN 2,451,545. A Saturday, and the J2000 epoch itself: the Julian Date at noon that day is exactly 2451545.0, the reference point astronomers still use for star positions and orbits.

15 October 1582 → JDN 2,299,161. The first day of the Gregorian calendar, a Friday. The day before it in the count, JDN 2,299,160, was Thursday 4 October in the Julian calendar.

17 November 1858 → JDN 2,400,001. The Modified Julian Date counts from midnight on this date, so MJD 0.0 is the start of 17 November 1858 and MJD 61,343.0 is the start of 30 October 2026.

1 January 1970 → JDN 2,440,588. The Unix epoch — the moment computer clocks start counting seconds — began at midnight on this date, when the Julian Date was 2440587.5.

1 January in the year 1 → JDN 1,721,426, and 31 December 9999 → JDN 5,373,484. Those two numbers bound the converter's range: every date it accepts falls between them.

Where Julian Day Numbers are actually used

Astronomy first. An observation log records the Julian Date of each measurement, so the time between two observations — even observations years apart, across a calendar reform — is one subtraction. Ephemeris software, which predicts where planets and satellites will be, still works in Julian Dates internally for the same reason: the arithmetic never has to ask what month it is.

Programmers inherited the trick. Date libraries that need an unambiguous day count — for scheduling, for astronomical calculations, for converting between calendar systems — often convert to a Julian Day Number first, do the arithmetic, and convert back. It is the same reason this site's converter exists: one integer is easier to trust than a month, a day and a year that each carry their own rules.

One confusion to clear up: the five- or seven-digit 'Julian date' printed on food packaging and some industrial labels is not a Julian Day Number. That code is a year plus a day-of-year — 26303 means day 303 of 2026, which is 30 October 2026 — while the Julian Day Number for the same day is 2,461,344. Same word, different system, different number.

JD, JDN and MJD — don’t mix them up

Julian Date (JD) is the continuous count with a fraction: 2461344.0 at noon on 30 October 2026, 2461343.5 at the previous midnight. Julian Day Number (JDN) is the integer part at noon: 2461344 for that day. Modified Julian Date (MJD) is the Julian Date minus 2,400,000.5: 61343.5 at noon on 30 October 2026, 61343.0 at midnight.

The practical rule: if a value has a decimal, it is a JD or an MJD, never a JDN; if it is an integer near 2.4 million, it is a JDN; if it is near 61,000, it is an MJD. The converter on this site shows all three for every conversion, so a mismatch between two sources is usually one of these three being mistaken for another.

Related calculators

The converter below does both directions of this guide: a date to its number, and a number back to its date, with the Julian Date, Modified Julian Date and weekday for every conversion.

Julian Day Number Converter
Date LabJulian Day Number ConverterConvert any Gregorian date to its Julian Day Number, or any number back to its date — with the Julian Date, Modified Julian Date and weekday.
Counted on the page: all eight reference values in this guide were computed with the standard day-count algorithm and cross-checked against the converter's own range — including 2,461,344 for 30 October 2026 and 2,299,161 for 15 October 1582.

Frequently asked questions

What is a Julian Day Number?

A single integer for every day, counting from noon on 1 January 4713 BC (Julian calendar). That day is JDN 0, and every later day is the next integer — 30 October 2026 is JDN 2,461,344.

How do I convert a date to its Julian Day Number?

Use the converter above: enter a Gregorian date and it returns the JDN, the Julian Date at noon, the Modified Julian Date and the weekday. The underlying arithmetic is the Fliegel–Van Flandern algorithm, with the Gregorian leap-year rules applied to every date.

What is the difference between a Julian Date and a Julian Day Number?

The Julian Date is continuous and carries a fraction — .0 at noon, .5 at midnight — while the Julian Day Number is the integer the day carries at noon. On 30 October 2026 the Julian Date at noon is 2461344.0 and the JDN is 2461344.

What is the Modified Julian Date?

The Julian Date minus 2,400,000.5, chosen so the numbers are smaller and the day starts at midnight instead of noon. MJD 0.0 is midnight at the start of 17 November 1858; on 30 October 2026 the MJD is 61343.0 at midnight and 61343.5 at noon.

Why does the count start at noon instead of midnight?

Because astronomers work through the night, and a night of observation must not be split by a midnight date change. Starting the day at noon keeps each night inside a single date.

Why 1 January 4713 BC?

Joseph Justus Scaliger proposed the system in 1583 and picked the year in which three old cycles restart together: the 28-year solar cycle, the 19-year Metonic cycle and the 15-year indiction cycle. Their product, 7,980 years, is the Julian period.

What happened to 5–14 October 1582?

Those dates never existed as calendar labels: the Gregorian reform skipped from Thursday 4 October (Julian) to Friday 15 October (Gregorian). The count did not skip — JDN 2,299,160 was followed by JDN 2,299,161.

Is the 'Julian date' on food packaging the same as a Julian Day Number?

No. Packaging codes combine a year with a day-of-year — 26303 means day 303 of 2026, which is 30 October 2026 — while that day's Julian Day Number is 2,461,344.

What is J2000?

The standard astronomical epoch: noon on 1 January 2000, when the Julian Date was exactly 2451545.0. Star positions and orbits are commonly quoted relative to it; 30 October 2026 is 9,799 days after J2000.

What date range does the converter cover?

Gregorian dates from 1 January in the year 1 (JDN 1,721,426) to 31 December 9999 (JDN 5,373,484).