A Julian Date is a continuous count of days from January 1, 4713 BC in the proleptic Julian calendar, starting at noon Universal Time. It was introduced by astronomers in the 1800s so they could record observations without dealing with calendar reforms, varying month lengths, or the year zero problem. For September 2, 2026 at noon UTC, the Julian Day Number is 2461286.
The confusing part is that the word Julian gets used for three different things. The Julian Date is the full count including fractions of a day. The Julian Day Number is the integer part, which changes at noon. The Modified Julian Date is a smaller version that starts at midnight in 1858. They are all the same timeline, just shifted and rounded differently.
JD, JDN, and MJD explained
The Julian Date (JD) is a decimal number. The integer part is the day, and the fractional part is the time of day, measured from noon UTC. JD 2461285.5 is September 2, 2026 at 00:00 UTC, and JD 2461286.0 is September 2, 2026 at noon UTC. The half-day offset is the historical convention, because astronomers worked at night and wanted the date not to change in the middle of an observing session.
The Julian Day Number (JDN) is the integer part of JD, so it changes at noon rather than midnight. For most of September 2, 2026, the JDN is 2461286. The Modified Julian Date (MJD) is JD minus 2400000.5, which moves the epoch to November 17, 1858 at midnight and makes the numbers small enough to fit comfortably in 32-bit floating point. The MJD for September 2, 2026 at 00:00 UTC is 61285.
- JD 2461285.5 = September 2, 2026 at 00:00 UTC
- JD 2461286.0 = September 2, 2026 at 12:00 UTC
- JDN 2461286 = the integer day for September 2, 2026 (changes at noon)
- MJD 61285 = September 2, 2026 at 00:00 UTC (JD minus 2400000.5)
Why the noon start matters
Astronomical observations happen at night, and a single session can cross local midnight. If the date changed at midnight, a 10 PM to 2 AM observing run would span two Julian Day Numbers and split across two log entries. By starting the day at noon, the whole night falls inside one JDN. This is why JD values for evening observations always end in a small fraction like 0.7, while morning observations end near 0.9, and the integer rolls over while most observers are asleep.
A researcher at the Paranal Observatory in Chile logs an exposure taken at 23:00 local time on September 2, 2026. Chile in September is on UTC-3, so the exposure is at 02:00 UTC on September 3. The JD is 2461286.583, and the JDN is still 2461286, because noon has not yet passed. The whole night's run shares one JDN, which is the point of the convention.
The other Julian dates to watch for
In manufacturing and logistics, a Julian date often means the day-of-year number, a three-digit count from 1 to 365 starting on January 1. Under that convention, September 2, 2026 is day 245 of the year, sometimes written as 2026245 or 26245. This has nothing to do with the astronomical Julian Date, but the shared name causes constant confusion. If a supplier sends a Julian date of 245, they mean the 245th day of the year, not JD 245.
There is also the Julian calendar itself, the system introduced by Julius Caesar that preceded the Gregorian calendar. The Julian calendar drifts by about 3 days every 400 years relative to the seasons, which is why most of the world switched to the Gregorian calendar. The Julian Date system uses a proleptic (extended backward) version of the Julian calendar for early dates and the Gregorian calendar for modern ones, with the switch at October 15, 1582.
Converting in code
Most languages can convert without writing the formula by hand. In Python, jd = datetime(2026, 9, 2, tzinfo=timezone.utc).timestamp() / 86400 + 2440587.5 gives the JD, where 2440587.5 is the JD for the Unix epoch of January 1, 1970 at 00:00 UTC. In JavaScript, the same logic applies: take the Unix milliseconds, divide by 86400000, and add 2440587.5. To go the other way, subtract 2440587.5 and multiply by 86400 to get Unix seconds.
The constant 2440587.5 is the bridge between Unix time and Julian Date. It is the JD at the Unix epoch, and the 0.5 reflects the noon-to-midnight offset between the two systems. Get that offset wrong and every converted instant is 12 hours off.
If your converted date is exactly 12 hours off, you mixed up the noon and midnight epoch. Julian Date starts at noon UTC, Unix time starts at midnight UTC, and the bridge constant is 2440587.5, not 2440588.
Related tools for date conversion
The Julian Date Converter reads and writes JD, JDN, and MJD alongside calendar dates. The Unix Timestamp converter handles the epoch-seconds system used in software. The Excel Date Converter handles the spreadsheet serial system. The Astronomy Dashboard ties date conversions to sky events for observing planning.