Skip to content
Design Guide 12 min read

Hebrew Dates on Wedding Invitations: Getting the Calendar Right

The Hebrew date is the one line on an invitation that a hundred guests will check and a proofreader will miss. Here's how the sunset rule works, how to write the date and year properly, and how to fit both calendars on one page without clutter.

InviteLane Team September 2026

Almost every mistake we see on a frum wedding invitation is a date mistake, and almost every date mistake comes from the same source: the two calendars on the card do not change days at the same moment. The civil date rolls over at midnight. The Hebrew date rolls over at nightfall. A chasunah that begins at 6:30 on a Tuesday evening in November is, on the Hebrew calendar, already Wednesday — and if the invitation says otherwise, several hundred people will notice, because that is the date they will use when they write it into a Jewish calendar, when they daven for the couple, and when the family later engraves it on a bencher.

The Hebrew date is also the line most likely to be typeset by someone who cannot read it. English-speaking designers set Hebrew as an image or a copied string, get the letter order reversed, drop a geresh, or turn a final letter into a medial one. The proof looks beautiful, nobody in the room can check it, and it goes to press.

This guide walks through the mechanics: how sunset determines which Hebrew date belongs on the card, how the date is constructed from day, month and year, how Hebrew numerals and the abbreviated era form work, when a parsha or Rosh Chodesh reference belongs on the invitation, how to lay both dates out without visual noise, and which periods of the year rule the date out entirely.

1. The Sunset Problem

The Jewish day begins at nightfall, not at midnight. Practically, that means any Hebrew date printed alongside an evening civil date is one day ahead of the number most people would guess. Chuppahs are almost always in the evening, so this is not an edge case — it is the normal case, and it catches families every single season.

Work it through with a concrete example. A wedding is called for Tuesday, 10 November, with a kabbalas panim at 6:00 p.m. and the chuppah at 7:15. Sunset in the New York area in mid-November is around 4:40 p.m. By the time the first guest arrives, the Hebrew date has already advanced. The correct Hebrew date on that invitation is the one corresponding to Wednesday, 11 November — even though the invitation's English line says Tuesday.

This produces a card that looks internally inconsistent to anyone unfamiliar with the calendar and is perfectly correct to everyone who is. That is fine. Do not "fix" it by backing the Hebrew date up a day to match the English weekday. Nearly every mis-dated invitation we have seen was produced by exactly that instinct.

The One Question That Prevents This

Ask your designer, in writing: "Was the Hebrew date calculated for the evening of the event, after sunset?" If the answer is anything other than a clear yes, it was calculated from the civil date and is probably a day early. An afternoon Sunday wedding, by contrast, still falls on the daytime Hebrew date — so the rule only bites when the event begins after nightfall.

Two related traps. First, Motzoei Shabbos weddings: an event on a Saturday night belongs to Sunday's Hebrew date, and both dates should reflect that. Second, weddings that begin before sunset but run past it — an early-afternoon chuppah in the winter. There the chuppah itself takes place on the daytime Hebrew date, and that is the date to print, even though the seudah crosses into the following one.

2. Writing the Hebrew Date Correctly

A Hebrew date on an invitation is built from four elements, in this order, reading right to left: the day of the week, the day of the month, the month, and the year. Most invitations include all four; some omit the weekday when the layout is tight.

Full form

יום ג' כ״ז מרחשון תשפ״ז

Tuesday, 27 Marcheshvan 5787

Weekday, day, month, year. Note the geresh after the weekday letter and the gershayim inside the two-letter day and the year.

Compact form

כ״ז מרחשון תשפ״ז

27 Marcheshvan 5787

Weekday dropped. Common when the English line already names the day and space is limited.

Weekdays are written as letters, not words: יום א׳ for Sunday through יום ו׳ for Friday, with שבת קודש for Shabbos. Since weddings are not held on Shabbos or on Friday, in practice you are choosing among the first five.

Month names deserve care. Cheshvan is properly מרחשון (Marcheshvan) on formal invitations, though חשון appears widely. In a leap year, Adar becomes אדר א׳ and אדר ב׳ — printing a bare אדר in a leap year is a real ambiguity, not a stylistic choice, because the two months are a full month apart. Many families write מנחם אב rather than plain אב.

Punctuation Is Not Decoration

The single quote (geresh, ׳) marks a one-letter numeral; the double quote (gershayim, ״) sits before the final letter of a multi-letter numeral. They are not apostrophes and not quotation marks — a designer's "smart quotes" setting will silently substitute the wrong characters, and it is one of the most common typographic errors on printed invitations.

Check the proof at high zoom, character by character, with someone who reads Hebrew.

3. Hebrew Numerals and the Year

Hebrew numbers are written with letters. Units run א through ט (1–9), tens י through צ (10–90), and hundreds ק through ת (100–400). A number is assembled from largest to smallest, with the gershayim inserted before the last letter.

Days of the month you will actually use

1א׳Single letter, geresh.
14י״דTen plus four.
15ט״וNine plus six — not yud-hey, which spells a Divine Name.
16ט״זNine plus seven, for the same reason.
20כ׳Single letter, geresh.
27כ״זTwenty plus seven.
30ל׳Only in a 30-day month.

The fifteenth and sixteenth are the classic trap. Written by naive arithmetic they would be יה and יו; both are avoided, and the convention is ט״ו and ט״ז. Automated tools handle this; a designer typing letters by hand may not.

The year is usually written in the abbreviated era form, dropping the thousands digit: 5787 becomes תשפ״ז, not ה׳תשפ״ז. Both are correct — the short form is standard on invitations, and the long form with the leading ה׳ appears on more formal or rabbinic documents. Pick one and use it consistently across the invitation, the bencher and the seating cards.

Never Retype a Hebrew Date

Copy and paste it as a text string from a source you trust, or generate it from a calendar tool that takes the sunset into account. Retyping is where reversed letters and substituted quotes enter. If your invitation is set in a design program, ask the designer to send back a text export of the Hebrew line so you can compare characters rather than shapes.

Set the Hebrew Date Once, Reuse It Everywhere

Build your invitation with the Hebrew and English text side by side, so the same verified date carries into the invitation, the RSVP page and every message you send.

4. Parsha and Rosh Chodesh References

Many families add a line naming the week's parsha, and some add a phrase from it that resonates with the simcha. The parsha of a weekday is the parsha of the coming Shabbos — the sedra that will be read at the end of that week, not the one just read. A Tuesday-night wedding in the week whose Shabbos reads Chayei Sarah is בשבוע פרשת חיי שרה.

Parsha line

Written as בשבוע פרשת … and set below the date, usually in a smaller size. In a week with a double parsha, name both. Families with a connection to a phrase in the sedra sometimes lift a few words as a header — do this sparingly; one quoted line is elegant, three is a drasha.

Rosh Chodesh

When the date falls on Rosh Chodesh, say so — ראש חודש כסלו — instead of, or alongside, the numeric day. A two-day Rosh Chodesh is א׳ דראש חודש or ב׳ דראש חודש. Weddings are commonly scheduled on Rosh Chodesh, so this comes up frequently.

Other markers worth naming when they apply: Chanukah, Tu B'Shvat, Lag BaOmer (a heavily used wedding date), Rosh Chodesh Nisan, and the days between Yom Kippur and Sukkos. Naming the occasion adds warmth and, incidentally, gives a second independent check on the date — if the parsha and the day of the month disagree, one of them is wrong.

5. Both Dates on One Invitation

Once the date is right, the design problem begins: two calendars, two scripts, two reading directions, one card. The layouts that work fall into three patterns.

Stacked. Hebrew date centred above the English date, separated by a thin rule or a small ornament. The most common approach and the most forgiving, because each line gets its own baseline and neither has to align to the other. Set the Hebrew slightly larger — Hebrew letterforms sit lower and read smaller at the same point size.

Mirrored panels. A full Hebrew invitation on one side or one face, a full English invitation on the other, each internally complete. This is the cleanest solution for a bilingual card and avoids mixed-direction lines entirely. It costs space, so it suits a folded or double-sided piece rather than a single flat card.

Inline pairing. Hebrew and English on the same line, separated by a bullet or slash. Tempting, and the hardest to execute — bidirectional text reorders punctuation in unpredictable ways, and a slash placed after a Hebrew string frequently jumps to the wrong end. If you go this route, have the final line rendered as it will print and check the punctuation positions specifically.

Typography Notes That Save a Reprint

  • Set the Hebrew block with dir="rtl" so punctuation lands correctly; do not fake it with right alignment.
  • Increase the Hebrew size 10–15% relative to the English for optical balance.
  • Use a Hebrew face that actually contains gershayim and final letters — many display fonts do not, and the renderer will substitute.
  • Never letterspace Hebrew to fill a line. It breaks the letterforms and reads as an error.

For a fuller treatment of laying out a card that carries both languages — not just the date, but names, venue and the RSVP line — see our guide to bilingual Hebrew and English invitation design. And for the wording that surrounds the date, our guide to Jewish wedding invitation wording covers the standard formulations and how families are named.

6. When Weddings Are Not Held

Whole stretches of the Hebrew year are unavailable for weddings, and the specific boundaries vary by minhag. This is a rav's question, not a designer's, but knowing the shape of the calendar prevents a family from falling in love with a date that cannot work.

Sefiras HaOmer

The weeks between Pesach and Shavuos are largely closed, with communities observing different portions of the period and Lag BaOmer standing out as a widely used date. Which segment your family observes follows your minhag — confirm before booking, not after.

The Three Weeks

From 17 Tammuz through Tisha B'Av weddings are not held, with the Nine Days more stringent still. Halls know this and their calendars reflect it, which is also why the weeks immediately after fill up very fast.

Add to those the Yamim Noraim and the days around them, Chol HaMoed (where practice differs), and Shabbos and Yom Tov themselves. Between the closed periods and the halls' own booking pressure, the practical wedding calendar is narrower than it looks, which is the real reason dates get fixed twelve to eighteen months out.

Why this matters for the invitation specifically: a date error that lands the printed Hebrew date inside a closed period is instantly visible to every recipient. Nobody has to check a calendar to know that a chasunah is not taking place on the tenth of Av. It reads as carelessness about the thing the invitation exists to announce.

7. Proofing the Date Before You Print

Treat the date line as a separate proofing pass from the rest of the card. Everything else — names, venue, times — is checked by people who read the language it is written in. The Hebrew date frequently is not.

  1. 1Confirm the civil date and the start time, then determine whether the event begins after nightfall. Everything downstream depends on this one fact.
  2. 2Generate the Hebrew date from a calendar source using the correct evening, and copy it as text — never retype it.
  3. 3Check the day-of-month numeral against the list above, paying attention to 15 and 16.
  4. 4Check the year form, and make sure the same form appears on the bencher, the seating cards and the invitation.
  5. 5Check the parsha independently. If parsha and date disagree, stop.
  6. 6Have someone fluent in Hebrew read the printed proof aloud, at size, in the final font.
  7. 7Confirm the date falls outside sefirah, the Three Weeks and Yom Tov — the family will know, but confirm anyway.

Check the Digital Version Too

A printed proof and a digital invitation can disagree. If the same date is being used on a web invitation, an RSVP page and text messages, verify the Hebrew line renders correctly on a phone — small screens and unusual fonts are where missing glyphs show up as boxes. Send yourself the real thing on a real device before it goes to the list.

Bringing It All Together

The Hebrew date is short, and the number of ways to get it wrong is not. Almost all of them collapse into three: the sunset was ignored, the numerals were typed by hand, or the punctuation was auto-corrected. Handle those three and the rest is layout.

Concretely: decide the date from the evening of the event, not the calendar square. Build the line as weekday, day, month, year, with ט״ו and ט״ז written the conventional way and the year in the abbreviated era form. Add the parsha or Rosh Chodesh where it fits, and use it as a cross-check. Stack the two dates rather than fighting bidirectional text on one line, set the Hebrew slightly larger, and use a font that has the glyphs. Then proof the date on its own, with someone who reads it.

Get it right and nobody says a word — which is exactly the outcome you want from a date line. It quietly does its job for four hundred people who will each write it down somewhere.

Related Articles

One Verified Date, Everywhere It Appears

Enter your Hebrew and English details once and reuse them across your invitation, RSVP page and guest messages — no retyping, no copy drift.