Hebrew vs Gregorian calendar: a practical comparison
Compare month lengths, leap years, year boundaries and anniversaries, then learn how to keep both dates clear in everyday planning.
Two calendars describe the same days differently
The Gregorian calendar is solar, with twelve months and a leap-day correction. The Hebrew calendar is lunisolar, with twelve or thirteen months and a leap-month correction. Both can label the same event, but their month boundaries and year boundaries do not line up. A date conversion translates between the systems; it does not replace the original record.
For everyday use, keep both labels when both matter. A civil date may help you find a photograph, while a Hebrew date identifies an annual family remembrance or birthday. Neither label is more complete in isolation. The right record includes the calendar name and enough context to explain what the date is intended to track.
| Feature | Hebrew calendar | Gregorian calendar |
|---|---|---|
| Basis | Lunisolar | Solar |
| Months in a year | 12 or 13 | 12 |
| Month lengths | 29 or 30 days | 28 to 31 days |
| Leap adjustment | An extra Adar in 7 of 19 years | An extra day in February |
| Numbered year begins | 1 Tishrei | 1 January |
Source notes: Hebcal · Hebrew date and year structure · Hebcal · Gregorian calendar implementation
A leap month and a leap day solve different problems
A Hebrew leap year inserts Adar I and retains the following Adar as Adar II. A Gregorian leap year gives February 29 days. Hebcal’s Gregorian implementation uses the familiar rule: years divisible by four are leap years, except century years not divisible by four hundred. The word “leap” therefore describes different changes depending on which calendar you are using.
Do not assume that a Hebrew leap year must coincide with a Gregorian leap year, or that February 29 identifies anything about the Hebrew year. For planning, check each calendar separately. A journal that includes both dates can contain a Gregorian leap day in one part of a year and encounter two Adars in a different cycle, with each label doing its own work.
Source notes: Hebcal · Hebrew date and year structure · Hebcal · Gregorian calendar implementation
Why a fixed Hebrew date moves on a civil calendar
The twelve-month Hebrew year is shorter than a Gregorian year; a thirteen-month Hebrew year is longer. As those year shapes alternate, a fixed Hebrew month and day shifts across Gregorian dates. A reliable converter handles the actual year. An approximate seasonal association, such as Tishrei with September–October, cannot identify a particular day by itself.
Hebcal’s table gives a concrete sequence: 1 Tishrei 5786 is 23 September 2025, 1 Tishrei 5787 is 12 September 2026, and 1 Tishrei 5788 is 2 October 2027. Those dates show movement in both directions. If an annual reminder is meant to follow 1 Tishrei, a recurring event fixed to 12 September will match only one of those examples.
Source notes: Hebcal · Hebrew date and year structure · Hebcal · 1 Tishrei 5787 conversion
Date conversion needs a clear boundary
A Gregorian date commonly labels the midnight-to-midnight civil day. Hebrew calendar observance follows an evening boundary, so the evening and daytime portions of one Hebrew date span parts of two civil dates. Hebcal’s Gregorian conversion code explicitly returns the daytime civil date, and its web converter provides an after-sunset option when converting an event in the other direction.
For a birthday record, preserve the event’s known local time and place instead of treating the civil date as the whole story. For a future invitation, state both the civil day and the intended evening or daytime event time. A clear invitation should not force a guest to guess which part of the Hebrew date you mean. Exact scheduling and calendar labeling should be checked together.
Source notes: Hebcal · Gregorian calendar implementation · Hebcal · Hebrew Date Converter conventions
Older civil dates may need an additional check
Hebcal’s published Gregorian implementation applies Gregorian rules backward in time, using what is called a proleptic Gregorian calendar. That is a defined calculation convention. It does not establish that an old document’s local civil date was originally written under Gregorian rules. A historical record needs its calendar identified before its date is entered into a modern converter.
When working with family papers, begin with the document’s own information: where it was created, when it was created and how its dates were recorded. Preserve the original date before normalizing it. If you have already converted between an older civil calendar and Gregorian, note that step. Otherwise a correct Hebrew conversion can sit on top of an incorrectly interpreted civil input.
Source notes: Hebcal · Gregorian calendar implementation
Choose the recurrence you actually want
For a civil birthday, repeat the civil month and day. For a Hebrew birthday, carry the Hebrew month and day into the target Hebrew year, using an appropriate anniversary rule if the date is missing. These are distinct recurrence choices. Copying one year’s Gregorian equivalent into a permanently repeating civil event will not reliably produce future Hebrew anniversaries.
A practical record includes the original event date, both calendar labels, the boundary assumption and the recurrence system. If the event involves a community custom, add that convention as well. You can then share a current civil date for convenience while keeping the Hebrew anniversary intact. That approach makes a two-calendar life easier to manage because every label has a stated purpose.
Source notes: Hebcal · Hebrew date and year structure · Hebcal · Hebrew Date Converter conventions