Julian Date Converter

Julian Date Converter

Convert Gregorian dates to ordinal Julian dates, reverse YYYY-DDD back to a calendar date, and calculate astronomical Julian Day Number and decimal Julian Day.

📌Presets
⚙Converter Inputs
Used directly in Gregorian mode.
Decimal JD uses UTC day fraction.
Accepts YYYY-DDD, YYYYDDD, or YYYY DDD.
JD 2451545.0 is 2000-01-01 12:00 UTC.
Used for neighboring date and JDN rows.
📊Results
Gregorian Date 2026-07-28 Tuesday, UTC civil date
Ordinal Julian Date 2026-209 day 209 of 365
Julian Day Number 2461250 integer day label
Decimal Julian Day 2461249.500000 at selected UTC time
🧭Calendar Summary
🔁Comparison Grid
📆Month Day Ranges
MonthDaysOrdinal StartOrdinal EndSelected Status
🔭Julian Day Neighbors
OffsetGregorian DateOrdinalJD at 00:00 UTCJulian Calendar
📘Formula Reference
ConversionFormula CoreUse It ForWatch Point
Gregorian to day-of-yearordinal = days since Jan 1 + 1YYYY-DDD file labelsLeap years add day 060
Day-of-year to Gregoriandate = Jan 1 + DDD - 1Reverse Julian date lookupDDD must be 1 to 365/366
Gregorian to JDND + floor((153m+2)/5) + 365y + floor(y/4) - floor(y/100) + floor(y/400) - 32045Astronomy day labelsJDN is tied to noon UTC
Gregorian to JDJD = JDN - 0.5 + UTC fractionExact time stampsUse UTC, not local time
Julian calendar dateSame month shift, no century leap correctionOld-style calendar comparisonNot the same as YYYY-DDD
📍Preset Reference Dates
PresetGregorian InputWhy It Is UsefulExpected Julian Clue
Today 20262026-07-28 00:00 UTCCurrent working example2026-209
Leap Day2024-02-29 00:00 UTCChecks day 060 handling2024-060
Day 0012026-001Reverse ordinal boundaryJan 1
Day 3662024-366Leap-year final dayDec 31
J2000 Epoch2000-01-01 12:00 UTCAstronomy reference epochJD 2451545.0
Unix Epoch1970-01-01 00:00 UTCComputing timestamp anchorJD 2440587.5
GPS Epoch1980-01-06 00:00 UTCNavigation time anchor1980-006
Apollo 111969-07-20 20:17:40 UTCTime fraction sanity check1969-201
Gregorian Reform1582-10-15 00:00 UTCCalendar-system comparisonJDN 2299161
✅Practical Tips
Label precisely. Write "ordinal Julian date 2026-209" when you mean day-of-year, and "JD 2460879.5" when you mean astronomical Julian Day.
Check the time zone. Decimal Julian Day uses UTC. A local evening timestamp can move to the next UTC date before you calculate the fraction.
Validate leap years. Day 366 only exists when the year is divisible by 4, except century years not divisible by 400.
Mind the noon rule. Astronomical Julian Days begin at noon UTC, so civil midnight has a decimal part of .5.

There is confusion about Julian dates because in each field the term refer to something different. To a warehouse, it’s a serial number used to track when items expire. To an observatory, it’s a daily count of how many day have elapsed since ancient times.

When attempting to match a record from one system (an astronomical event) to another (a supply chain manifest), the result will probably be error. Everyone calls their system by the same name but they mean entirely distinct things. Their Julian date is your calendar date, and that discrepancy mean money and time lost.

How to Know Which Julian Date to Use

Before you convert, there are three primary idea to understand. The ordinal date is also known as YYYY-DDD, and it is just the day of the year (beginning with 001 on January 1). It is linear, clean, and ideal to use in logistics software or for filename purposes.

The Julian Day Number is also called JDN. Astronomers uses this integer to measure time unimpeded by years or months. The decimal Julian Day adds fractional accuracy to that integer tally.

Once you know what date and time to calculate, you don’t really need to remember the offset constants for each calendar reform throughout human history; the calculator do all the math for you.

Noon is the most obvious one. Astronomical Julian Days start at noon rather than midnight. This is an oddity because when astronomers established it, they decided to have the day begin midway between two observation during the night. Therefore, civil midnight has a decimal fraction of point five. If you use local time different than UTC when converting a timestamp for a scientific experiment, you’ll be off by hours. Use the tool on this page to apply that fraction, which makes your decimal JD accurate down to the second.

There’s also that leap year issue. In an ordinal system, assuming each year has 365 days doesn’t work. Day 060 isn’t in February unless the year is divisible by four, except for century years. If your software simply adds one to the day number then February 28 become March 1, and the whole sequence skip forward. The converter checks those bounds for you. You can enter “2024-060” and be assured you have entered February 29, or enter “2025-060” and discover there is no such day. It is a little thing but it is important when you are doing this on autopilot from ingesting other people’s data.

Why do we mess around with all of this? Because, as I said, regular calendars suck. They has weird months, with some being shorter and some longer. There is a special rule about leap years. There are also little history quirks where they jumped forward or backward, like in the Gregorian calendar reform. Julian calendars fix that. They make it so that what was once an uneven timeline becomes a straight line.

It’s much simpler for astronomers to look at two big numbers and subtract them to compare two dates hundreds of years apart. And if you’re a warehouse manager looking at inventory until 209, it’s quicker to scan “2026. 209” then to figure out which abbreviation each month is.

In the end, it comes down to who you’re communicating with. If it’s a computer, say JD. If it’s a human being who only cares about whether something will expire before they go grocery shopping, say the ordinal.

Some of the preset buttons are useful as anchors, too. For instance, you can check the epoch of the Unix date, which shows how computer time lines up with astronomy. You can examine what they call the J2000 epoch, to learn more about the basis for today’s solar system ephemerides. Those reference points serve as a reminder that all this time we keep is arbitrary. We set a zero somewhere and go from there. The calculator translates your zeros back and forth for you.

In conclusion, it is clearer. Get clear about what date format you’re writing. If you write a day of year then label it as such. Use ordinals for the day of the year. Use astronomical counts as JD. Don’t mix and match in the same sentence. This rule should of not apply if you are writing this article.

There are tools out there to help close the gap, but it’s up to you to define what you mean by your dates. Then once you know which one, it’s simple math to convert. And now that you have everything lined up numerically, maybe you’ll stop asking yourself why your logs don’t match.

Julian Date Converter