Typing Hebrew: Keyboard, Niqqud and Bidi Traps

At some point you will want to answer an Israeli in Hebrew, and you will discover that nothing about typing it is obvious. This page is the practical answer: where the letters live, what to do about niqqud, and why a sentence you typed correctly can render on screen looking wrong.

The standard Israeli layout

Every keyboard in Israel — and every phone — uses the same arrangement, and it is not phonetic. There is no attempt to put ב under B. Hunting for a key that matches the sound is the first thing to unlearn.

Four things in that table are worth reading twice.

Only ר lines up with its Latin counterpart. ג and ד sit on D and S — next to each other and swapped from what you would guess, which is the single most common source of typos for beginners.

The five final letters have their own keys: ן on I, ם on O, ך on L, ף on semicolon, ץ on full stop. Nothing converts them for you. If you type the ordinary letter at the end of a word, you get the ordinary letter and the word is misspelled.

The punctuation moved. The comma is on the apostrophe key and the full stop on the slash key — because the physical comma and full-stop keys were taken over by ת and ץ. Reaching for a comma out of muscle memory produces a ת in the middle of your sentence, and this happens to everybody.

The geresh ׳ and gershayim ״ are missing from the layout most people use, and that is why Israeli text is full of ASCII marks. On the long-standing Windows Hebrew layout there is simply no key for either one — W gives a plain ASCII apostrophe — so a writer who wants ג׳ינס, צ׳יפס or כיתה א׳ reaches for ' and " because nothing else is within reach. The newer Hebrew (Standard, 2018) layout finally added them: geresh sits on the ; key and gershayim on the ' key — but note that is a different layout: on the classic one in the table above, ; is ף and ' is the comma. Everywhere else you are looking at a character picker, a keyboard shortcut or copy-paste — which is the whole reason the wrong marks are so common in real Hebrew writing. See גרש and גרשיים.

How do I type niqqud?

This is the question every learner asks and almost no course answers. The honest answer has two halves.

No default layout puts the vowel signs on plain keys. They are not letters; they live on a modifier layer or nowhere at all. The practical routes:

And the second half: you almost certainly do not need it. Israelis essentially never type niqqud. Text messages, emails, news sites, official forms and novels are all unpointed, and a learner who writes to a friend in ktiv male with no dots is writing exactly what an Israeli writes. Niqqud is for dictionaries, children's books, poetry and language teaching.

Bidi: why a correct line looks broken

Here is the part that makes people give up. Hebrew text is stored in the order you say it and displayed right to left, and when Latin letters, digits or punctuation join in, the display rules get complicated. The reading side of this is one thing; editing is another, because your fingers and your eyes disagree.

The paragraph picks a direction from its first strong character. In most apps a line that starts with an English word is laid out left to right as a whole, even though the Hebrew inside it still reads right to left. The commonest symptom: you begin a WhatsApp message with a brand name and the whole message flips alignment. Starting the line with a Hebrew word fixes it.

Punctuation has no direction of its own. Commas, full stops, quotation marks, dashes and slashes are neutral: they take their side from whatever is around them, and at the end of a line from the paragraph direction. This is why a full stop can appear at the far left of a Hebrew sentence. Nothing is broken — the character is exactly where you put it, and the layout engine placed it by rule.

Brackets are mirrored on purpose. In a right-to-left run, the opening bracket is drawn on the right. You press the key marked "(" and see ")" on screen. That is correct behaviour, not a wrong key.

Digits run left to right inside Hebrew. A phone number or a price keeps its own internal order, which is what you want. The friction is only at the seams, where the number meets punctuation.

The cursor and Backspace work on logical order. In most editors, arrow keys and Backspace move through the text in the order it is stored, not the order it looks. Across a Hebrew–Latin seam the caret therefore appears to jump, and Backspace can delete a character that visually sits on the other side of it.

Four habits that make it painless

1. Type each Latin or numeric run in one go. Dipping back into the middle of a foreign run is where the caret games start.
2. Trust the rendered line, not the keystrokes. The bidi algorithm is deterministic, so if it looks right to you it looks the same to your reader.
3. Keep punctuation with the run it belongs to — type the full stop straight after the word it ends.
4. If a line genuinely renders wrong, fix it with direction, not retyping. Set the paragraph direction, or insert a directional mark (RLM / LRM) at the seam. Retyping the same characters produces the same layout.

Common Mistakes

1. Ending a word with the ordinary letter. Nothing switches it for you; the final form is a separate key.

2. Reaching for the comma key. On the Hebrew layout it types ת.

3. Reaching for the full-stop key. It types ץ.

4. Settling for the ASCII apostrophe because you cannot find the geresh. On the layout most people use it genuinely is not there — that is why so much real Hebrew text carries ASCII marks — but ׳ and ״ are different characters from ' and ", and search, sorting and screen readers all treat them differently.

5. Typing the letters backwards. The screen does the reversing; you do not.

Key Takeaways

• The Israeli layout is not phonetic: א is on T, ש on A, י on H, ב on C, ח on J. Only ר matches its Latin key.
• The five final letters have their own keys (ן ם ך ף ץ on I, O, L, semicolon and full stop) — nothing converts them automatically.
• Punctuation moved: comma on the apostrophe key, full stop on the slash key. The geresh ׳ and gershayim ״ are absent from the classic layout altogether; the 2018 Hebrew (Standard) layout puts them on ; and '.
• No default layout has niqqud on plain keys — use a modifier layer, an on-screen keyboard, an automatic pointing tool or copy-paste. And you rarely need it: Israelis write unpointed.
• Bidi display is rule-driven, not random. Paragraph direction comes from the first strong character, punctuation is neutral and takes its side from its neighbours, brackets mirror deliberately, and digits run left to right inside Hebrew.
• The cursor and Backspace move in logical order, so they appear to jump at a Hebrew–Latin seam.
• A line that renders oddly is usually typed correctly — fix it with paragraph direction or a directional mark, never by retyping.