Skip to content
TOOLS#Claude RTL#Claude RTL support#Hebrew in ClaudeUpdated: September 26, 2026

Claude in Hebrew RTL (Right-to-Left): Extensions and Patches for Every Surface (2026)

Claude showing you reversed Hebrew? As of mid-2026 there is no unified official RTL support, but there is a fix for every surface: a browser extension, a Desktop patch, mobile, Claude Code in the terminal and in VS Code, and prompt templates that force right-alignment. The complete step-by-step guide, with security warnings included.

Yaakov Tzedek
Yaakov Tzedek · AI expert·18 min read
Hebrew right-to-left in Claude: graphic showing the fix for every surface, browser, desktop, mobile and terminal
THE BOTTOM LINE
  • Claude displaying Hebrew backwards? Fix RTL on every surface: browser extension in one click, Claude Desktop patch, mobile, and Claude Code. Full guide for 2026.
520M+RTL-language speakers worldwide
Not yet (2026)Official RTL support
Browser extension / mobileSafest fix
Browser · Desktop · Mobile · Claude Code · TerminalSurfaces covered
DID YOU KNOW?

As of mid-2026, Claude has no unified official RTL support. Every existing solution (extensions and patches) is a community initiative. The issue reportedly affects more than 520 million speakers of right-to-left languages, and there are several open feature requests in Anthropic's repository (issues #38005, #72580, #16814, #11050).

As of mid-2026, Claude has no unified official RTL support, but there is a working solution for each platform, and most take under a minute to set up. In the browser (Claude.ai), you install an extension or apply CSS through Stylus; in Claude Desktop (Windows/Mac), there is a community patch; in the mobile app, support is already decent by default; in Claude Code, there is an extension for VS Code/Cursor and a dedicated Hebrew-friendly terminal; and for documents and Artifacts, there are prompt templates that force dir="rtl". This guide covers everything, step by step, with the important security warnings, as of September 2026.

September 2026 update: After re-testing, Claude still has no built-in official RTL support on any desktop platform. The open issues in the Anthropic repository, including #38005 for Desktop and #72580 for Claude Code, remain unresolved. The fastest and safest solution remains a browser RTL extension for Claude.ai (runs locally, touches no files), one click and a refresh; for Claude Desktop there is a community patch (see the security warning below); and for Claude Code, an extension for VS Code or an RTL-capable terminal. Every solution here was re-tested as of September 2026.

30-Second Fix: By Platform

Before diving deep, here is the quick answer for each platform. Find your row, apply it, and get back to work:

🌐 Claude.ai in the browser, 30-second fix: Install the Claude RTL extension (or RTL Responder) from the Chrome Web Store or Firefox Add-ons. One click, refresh the page, and Hebrew aligns right automatically. Touches no files on your computer.

🖥️ Claude Desktop (Windows/Mac), 30-second fix: There is no official fix. The community solution is a local patch (claude-desktop-rtl-patch on GitHub), but it modifies binary files, so read the security warning below first. If you would rather avoid the risk, just switch to the browser with an extension.

📱 Mobile (iOS/Android), 30-second fix: Usually nothing to fix. The app handles Hebrew in the correct direction by default. If something looks reversed: update the app to the latest version.

⌨️ Claude Code in VS Code/Cursor, 30-second fix: Install the community extension claude-code-rtl-extension. It aligns Hebrew and Arabic text to the right inside the Claude Code panel.

🖤 Claude Code in the terminal, 30-second fix: No magic here. Most terminals do not support RTL. On iTerm2 (Mac), enable the experimental option under Settings, General, Experimental; on Windows, the Kivun Terminal project provides a terminal that renders Hebrew correctly. Alternatively: ask Claude Code to write the Hebrew output to a file and read it in your editor.

📄 Documents and Artifacts, 30-second fix: Add this to your prompt: "Generate the output as HTML with dir="rtl" and text-align: right." For pasting into Word, select the text and press Ctrl+Right Shift to align the paragraph to the right.

Now, the full explanation: why this happens and how each fix actually works.

What Is "Claude RTL" and Why Does It Need a Guide?

"Claude RTL" (Claude right-to-left) is a collective term for two things: the problem in which Claude aligns Hebrew to the left or displays it in reversed word order, and the community solutions that restore proper RTL direction. As of August 2026, Claude has no single official RTL setting, so the fix depends on which platform you are on: browser, desktop app, mobile, Claude Code in an editor, or Claude Code in the terminal.

Definition: RTL (Right-to-Left) is the writing direction used in Hebrew, Arabic, and Persian. An interface that does not support RTL aligns Hebrew to the left, places punctuation on the wrong side, and scrambles word order when text mixes Hebrew with English or code.

The questions "Hebrew in Claude," "how to fix Hebrew in Claude," and "Claude align right" are among the most common in the Israeli user community, and for good reason. Claude is considered the best Hebrew writer among current language models (more on that later), yet it runs inside interfaces that still cannot display that Hebrew correctly. This guide closes the gap.

Why Does Claude Display Hebrew Backwards? The Technical Explanation

To fix this properly it helps to understand what is actually breaking. Three distinct problems hide behind "reversed Hebrew":

1. Left Alignment (the cosmetic problem)

Claude's interfaces default to LTR (left-to-right). A Hebrew paragraph is pinned to the left instead of the right. The text itself is readable, but a Hebrew reader's eye looks for the start of a line on the right side, and that cognitive friction becomes exhausting over a long conversation. A simple text-align: right fixes this.

2. Punctuation Jumping to the Wrong Side (the BiDi problem)

This is the genuinely annoying one. The Unicode BiDi (Bidirectional) algorithm governs how characters are ordered when directions mix. When a text container does not declare direction: rtl, the algorithm assumes the paragraph is LTR, and "neutral" characters such as periods, commas, question marks, parentheses, and hyphens anchor themselves to the wrong base direction. The familiar result: a period that appears at the start of a sentence instead of the end, reversed parentheses, and a question mark stranded on the left side.

3. Reversed Word Order in Mixed Hebrew-English Text (the hard problem)

The classic example: a sentence like "I'm building a new project with Next.js and TypeScript" written in Hebrew can appear with the English segments in reversed order relative to the Hebrew, and numbers that drift to the wrong position. In technical conversations, where Hebrew, English, function names, and commands are constantly interleaved, this makes the text nearly unreadable. Setting the correct base direction (dir="rtl") solves most cases, because it gives the BiDi algorithm the right anchor point.

This is a documented and acknowledged limitation. Several open feature requests exist in the anthropics/claude-code repository, including issue #38005 (RTL support in Claude Desktop and Cowork mode), #72580 (RTL/Hebrew support in the Claude Code web interface), #16814, and #11050. According to the reports in those issues, this problem affects more than 520 million speakers of RTL languages worldwide.

💡 From the field: When I train organizations on Claude, the "reversed Hebrew" slide is always one of the first, because it is the first thing that stops people. The good news I give every group: the problem is display-only. Claude understands and writes excellent Hebrew; only the screen is rendering it wrong. Once you understand that, the fix is a matter of minutes.

Claude in Hebrew Right-to-Left: The Complete Solutions Table

Claude has several "faces," and each one requires a different RTL solution. Before installing anything, identify which platform you are on:

PlatformRTL StatusSolutionRisk Level
Claude.ai (browser)Not built inChrome/Firefox extension, Stylus, or userscriptSafe, runs locally in the browser
Claude Desktop (Windows)Not built inCommunity patch claude-desktop-rtl-patchRequires caution, modifies binaries
Claude Desktop (Mac)Not built inEquivalent patch for macOSRequires caution
Mobile appFairly goodUsually nothing neededSafe
Claude Code in VS Code/CursorNot built inExtension claude-code-rtl-extensionSafe
Claude Code in terminalDepends on terminaliTerm2 experimental / Kivun Terminal / write to filesSafe
Artifacts and documentsDepends on outputPrompt template with dir="rtl"Safe
Paste to Word/DocsDepends on targetCtrl+Right Shift / paste as plain textSafe

The bottom line: if you are on a browser, an RTL extension covers 90% of users and that is all you need. If you are on Claude Code, use a VS Code extension or an RTL-capable terminal. Only for the Desktop patch do you need to stop and read the security warning first.

Hebrew in Claude on the Web (Claude.ai): All the Options

If you work in the browser, you have the widest range of solutions available, and all of them are safe: they run locally in the browser, do not touch any files on your computer, and can be uninstalled in a single click.

A Hebrew Extension for Claude (RTL Extension for Claude): The Simple Route

This is the solution that fits the vast majority of users. The three standout extensions as of September 2026:

  • Claude RTL: A Chrome extension (there is also a Firefox version called Claude RTL, Hebrew & Arabic Support) that automatically switches text direction for Hebrew responses, with automatic language detection and a manual toggle. It works with a MutationObserver that detects new messages as the conversation unfolds, and applies language detection per paragraph individually, so English paragraphs stay LTR while Hebrew/Arabic paragraphs flip to RTL.
  • RTL Responder for Claude AI: Automatic language detection, right-to-left alignment for responses, support for Artifacts and mixed-language text.
  • Claude AI RTL Support: Full RTL layout for Hebrew and Arabic on claude.ai; a clean, free solution if RTL is the only thing you need.

Installation is the same for all of them: extension store, click "Add to Chrome," refresh your claude.ai tab. Removal: one click. One general principle to keep in mind with extensions: favor open-source ones, check the permissions they request (an RTL extension should need access to claude.ai only, not "all websites"), and prefer those that explicitly state they do not collect data.

Stylus: Manual CSS, No Third-Party Extension

If you would rather not install a dedicated extension, you can use Stylus, a well-established, open-source CSS style manager, and apply your own CSS rule to claude.ai. This is the most transparent approach: you see exactly everything that runs. A basic style looks like this:

/* RTL for Hebrew on claude.ai, apply via Stylus to the domain claude.ai */
div[data-testid="user-message"],
.font-claude-message p,
.font-claude-message li {
  direction: rtl;
  text-align: right;
}
.font-claude-message pre,
.font-claude-message code {
  direction: ltr;
  text-align: left;
}

Two important notes: first, claude.ai's selectors change occasionally with interface updates; if the style stops working, re-inspect the class names (F12, then Inspect). Second, the second part of the rule is essential: code blocks must stay LTR, otherwise commands and code lines will render in reverse. This is precisely the advantage of the dedicated extensions: they already handle that for you.

Userscript: Tampermonkey / Violentmonkey

A third option in the same family: a userscript running through a script manager such as Tampermonkey or Violentmonkey. A community script (claude-rtl.user.js) is available on GitHub and works in any browser with a userscript manager: Chrome, Edge, Firefox, and Safari. The advantage over plain CSS: a script can detect language dynamically for each message, exactly like the extensions do.

A Permanent Instruction in Your Profile: The Zero-Installation Option

There is also a path that requires no installation at all. Under Settings, then Profile, on claude.ai there is a personal preferences field that gets injected into every conversation. It cannot change the direction of the interface, but it can improve the output: ask Claude to prefer continuous Hebrew paragraphs (without opening a line in English), to minimize punctuation marks that break in LTR (parentheses at the end of a line, colons before English), and to add dir="rtl" to any HTML output. This does not align the chat window, but it dramatically reduces the number of "broken" lines. A ready-made prompt template is in the next section, in the prompt templates chapter.

Claude Desktop RTL Patch: The Fix for the Desktop App

Searching "claude desktop rtl patch" leads to the central community project in this space, and it deserves a thorough explanation, including exactly what it does to your computer. New to the desktop app? Start with the complete Claude Desktop guide to understand what it offers beyond the browser.

Windows: shraga100/claude-desktop-rtl-patch

For the Claude Desktop app on Windows there is an open-source patch (MIT license) in the repository shraga100/claude-desktop-rtl-patch. As of August 2026 it is actively maintained, with a README in Hebrew. What it delivers:

  • Automatic detection of Hebrew and Arabic, with right-to-left alignment in real time, even while a response is still being written (streaming).
  • The input box automatically switches direction based on the language you are typing.
  • Code blocks and formulas stay LTR and do not break commands.

Requirements: Windows 10/11 with Claude Desktop installed, Node.js (so that npx is available), and administrator privileges (UAC). Installation steps: open Windows PowerShell, run the installation script from the repository (patch.ps1), confirm the UAC prompt, choose "Install" from the menu. The script backs up the original files, injects the RTL support, and then you reopen Claude Desktop.

Important to know: every Claude Desktop update overwrites the patched files. After every update you need to run the patch again. This is an explicitly declared workaround until official support arrives, not a permanent solution.

Mac (macOS): Two Parallel Projects

Mac users have, as of August 2026, two community repositories that do similar work:

  • toboly/claude-desktop-rtl-patch-mac: Single-script installation from Terminal; automatic direction detection, code blocks stay LTR.
  • soguy/claude-desktop-rtl-mac: Real-time Hebrew/Arabic detection in both the input box and the responses.

The actual behavior is similar to the Windows version: the input box switches direction as you type, Hebrew responses align to the right, and code stays left-aligned. The same security caveats apply (see the warning below); this also involves modifying application files.

How Does the Patch Work Under the Hood? (Technical)

Claude Desktop is a digitally signed Electron application, so directly editing the interface code breaks the integrity checks. The Windows patch works around this in three steps, with an automatic rollback on failure:

  1. Injection into ASAR: The user interface lives in an app.asar archive. The script extracts it, adds the RTL detection code to the renderer files, repacks it, and computes a new SHA-256 for the archive header.
  2. Hash replacement in claude.exe: A byte-level replacement of the original hash with the new one.
  3. Certificate replacement in cowork-svc.exe: The Anthropic certificate is replaced with a self-signed one, the file is re-signed, and the certificate is added to the system's trusted root store.

The original files are backed up as .bak, and the installation validates an RSA-4096 signature before running.

Warning: Required Reading Before Installing the Desktop Patch

The patch modifies binary files, replaces the Anthropic certificate with a self-signed one, adds it to the trusted root store, and bypasses the integrity check. Keep the following in mind:

  • Use it at your own risk entirely; modifying binaries can cause instability.
  • Modifying the application may not comply with Anthropic's Terms of Service. Read them and use your judgment.
  • Running an installation script as administrator runs code with full privileges. Always read the script and verify the source before running it. Install only from the original GitHub repository, not from secondary links.
  • In an enterprise environment with a security policy, a self-signed certificate in the trusted root store is exactly the kind of thing security teams do not like. Inform the right people before proceeding.
  • This is a temporary solution that gets overwritten with every version update.

If you are unsure, the safer choice is to stay in the browser with an extension, or use mobile, since neither option touches system files.

💡 From the field: In Yaakov Tzedek's Daily AI Tip WhatsApp group in Israel, this is one of the most common questions, and my recommendation is consistent: for everyday work, start with the safe option, a browser extension or mobile, and only consider the patch if you must have the desktop app (for example, for Cowork or local MCP). One more iron rule from the field: never run any installation script as administrator without opening it first and reading what it does. Even when the intentions are good, that habit saves you.

Claude Code RTL: Hebrew in Claude Code

"Claude Code RTL" and "Hebrew in Claude Code" are two separate questions: the first is about display (how Hebrew looks on screen), the second is about workflow (how you write Hebrew content and projects with Claude Code). We'll cover both. New to the tool? Start with the complete Claude Code guide and how to install Claude Code.

Claude Code in VS Code / Cursor: There's an Extension

If you're running Claude Code inside VS Code or Cursor (via the official "Claude Code for VS Code" extension), there's a ready-made display solution: the community extension claude-code-rtl-extension (yechielby) on GitHub adds RTL alignment for Hebrew and Arabic inside the Claude Code panel. Installation is straightforward and safe, it's a standard editor extension with no system file modifications. After installing, Hebrew questions and answers align right inside the panel, while code stays LTR.

Claude Code in the Terminal: The Unpleasant Reality of RTL in Terminals

Here's the honest truth: the problem isn't Claude Code's, it's the terminals'. Terminal emulators are built on a unidirectional character grid, and BiDi support in them has been an open problem for decades. The state of things as of August 2026:

  • iTerm2 (Mac): Starting with version 3.6.0, there is experimental RTL support: Settings › General › Experimental › "Enable support for right-to-left scripts". Clean Hebrew renders reasonably well; mixed Hebrew-English text can still flip. Worth enabling and testing against your own work.
  • Windows Terminal: No RTL support at all; Hebrew renders backwards. There is an open feature request (microsoft/terminal #20302), with no timeline.
  • Konsole (Linux/KDE): Considered to have the best BiDi support of any terminal, including RTL rendering from the right edge of the window.
  • Kivun Terminal: An Israeli project (noambrand/kivun-terminal-wsl) built specifically for this: a terminal for Claude Code that renders Hebrew, Arabic, and Persian correctly, including mixed RTL+LTR text. On Windows it runs via WSL2 + Konsole with a one-click installer, and includes a status bar, folder picker, and right-click launch. If you're working with Claude Code in Hebrew on Windows, this is the most practical solution available today.

The Approach That Sidesteps the Problem Entirely: Files Instead of Chat

And here's the tip that changes day-to-day life most: don't read long Hebrew in the terminal, ask for it as a file. Claude Code writes files excellently, and every modern editor (VS Code, Cursor, even Notepad) renders Hebrew correctly. In practice:

  • Instead of "write me a post in Hebrew" in chat, say "write the post to a file called post.md" and open it in your editor.
  • Short Hebrew responses (a line or two) are readable even in a reversed terminal; longer ones get routed to files.
  • Your instructions to Claude can be in Hebrew freely, he understands perfectly even when the display on your end is reversed. The problem is only in your eyes, not in his comprehension.

💡 From the field: In workshops I see people give up on Claude Code in Hebrew after five minutes of a reversed terminal, which is a shame, because they're walking away from the most powerful work tool available today. The habit I teach: long Hebrew goes to a file; management and questions go to chat. Anyone who adopts this forgets about the RTL problem within a day. And when working through VS Code with the RTL extension, the chat itself sorts itself out too. All of this gets practiced hands-on at the Claude Code workshop, including Hebrew setup from step one.

How to Get Claude to Write Right-to-Left: Ready-to-Use Prompt Templates

Up to this point we've fixed the interface. But there's a second layer: output, documents, HTML, Artifacts, tables. There you can solve a lot with the prompt itself, no installation needed. Here are templates ready to copy:

Template 1, a standing instruction for preferences (Settings › Profile on claude.ai):

When you answer in Hebrew: write continuous Hebrew paragraphs and don't open a sentence with an English term.
When you create an Artifact, HTML, or document in Hebrew, always add dir="rtl" to the top element,
and text-align: right to the text. Code blocks always LTR.

Template 2, a right-aligned HTML document (for Artifacts):

Create an HTML page in Hebrew. Required: <html dir="rtl" lang="he">, a readable Hebrew font,
all text aligned right, numbers and dates in Israeli format, and code blocks (if any) in LTR.

Template 3, a table that doesn't fall apart:

Build the table so that the main subject column is the rightmost, and all headings are in Hebrew.
Don't mix English and Hebrew in the same cell, if an English term is needed, place it in parentheses after the Hebrew.

Template 4, output meant to be pasted into Word:

Write the document as continuous Hebrew text only, no emojis, no special formatting characters,
with each heading on its own line. The document will be pasted into Word and formatted there.

The principle behind all of them: Claude knows how to produce correct RTL output, he just doesn't do it by default. Once the instruction is explicit (and even better: saved permanently in preferences or in the project's CLAUDE.md file in Claude Code), the output arrives properly aligned from the source. Working with Claude Code on a Hebrew website? One line in CLAUDE.md, "all Hebrew content is written RTL with dir='rtl' in every HTML template", saves the correction every single time.

Artifacts and Documents: Hebrew Aligned Right in the Output Itself

Artifacts (the output panel in claude.ai) run real HTML, so that's actually where the cleanest solution lives: HTML understands RTL perfectly, you just have to ask. A few rules that work:

  • Always dir="rtl" on the top element (<html> or the wrapping <div>), not just text-align: right. Alignment without direction only addresses the cosmetic problem; direction is what fixes punctuation and word order.
  • lang="he" helps fonts and hyphens behave correctly.
  • Code inside a Hebrew document: wrap it in <div dir="ltr"> so it doesn't flip.
  • Documents for printing/PDF: also request @media print with the same rules, so printing doesn't revert to LTR.

This is especially relevant for anyone generating professional Hebrew materials with Claude: worksheets, lesson plans, presentations, and summaries. Teachers and lecturers will find complete examples of these templates in the Claude for Teachers guide, which is built entirely around Hebrew output.

How to Fix Hebrew Alignment in Claude Output After Pasting into Word or Google Docs

A common scenario: the response looks reasonable in chat, but after a Copy-Paste into Word everything jumps. The reason: the paste carries formatting and direction from the browser, and the document ends up with paragraphs that have the wrong base direction. The fixes, from fastest to most thorough:

  1. Word: Select the text and press Ctrl+Right Shift, the keyboard shortcut that sets the paragraph direction to right (Ctrl+Left Shift reverses it back to left). This is the most important shortcut for anyone working in Hebrew, and it also fixes jumping punctuation, because it changes the base direction rather than just the alignment.
  2. Clean paste: Paste with Ctrl+Shift+V (paste without formatting), so the text adopts your document's direction instead of dragging the browser direction with it. In Word: Paste Special › Unformatted Text.
  3. Google Docs: Make sure Format › Paragraph styles includes RTL paragraph direction, or enable the direction buttons: Settings › Show right-to-left controls. After that a paragraph direction button appears in the toolbar, select everything and click the right direction button.
  4. Fix it at the source: If you produce documents like this frequently, use Template 4 from the previous section (clean text without formatting), or ask Claude directly for a right-aligned Word/HTML file instead of copying from chat.

Claude Right-to-Left Alignment: Mobile (iOS/Android)

Mobile is actually where things work best: by all accounts, the Claude mobile app (iOS and Android) handles Hebrew and Arabic in the correct direction by default, with no additions needed. The device's Hebrew keyboard dictates input direction, and responses display reasonably well aligned. This makes mobile the most convenient option for Hebrew conversations on the go, and the fastest "fix" for anyone who gets stuck: just continue the conversation on your phone.

If a direction issue does appear, make sure the app is updated to the latest version from the App Store / Google Play, and that the device language (or at least the Hebrew keyboard) is configured. Conversations sync between mobile and browser, so you can start on your phone and continue on your computer after installing the extension.

Why Claude Is Considered the Best Hebrew Writer: And How to Get the Most Out of It

It's worth separating these things: all the RTL issues in this guide are display problems. At the level of the language itself, Claude is considered by many Israeli users (and by me, after thousands of hours of work) to be the best Hebrew writer among the large language models: natural, flowing Hebrew with no "translatese", that Hebrew that sounds like English translated word-for-word, with a register you can tune, phrasing that's sensitive to Israeli context, and consistent gender and number agreement across long text. See a full comparison in the Claude in Hebrew guide.

A few style instructions that lift Claude's Hebrew up another level:

  • Set the register: "Write in everyday, natural Hebrew, not too formal or elevated", or conversely, "formal Hebrew for a legal document". Claude follows this with impressive consistency.
  • Ban translatese: "No Anglicisms and no English-translated syntax; if a technical term is necessary, Hebrew first followed by the English term in parentheses".
  • Set gendered address: "Address the reader in neutral plural" or "in the feminine", and you'll get consistency throughout the entire text.
  • Give an example: One paragraph in the style you want is worth more than ten instructions. Paste your own text and ask Claude to "write in the same voice".
  • Request a separate proofread: After a draft, ask "now go through this as a language editor: correct errors, gender agreement, and punctuation". Two stages beats one stage.

These instructions, combined with the RTL templates from the earlier sections, give you the complete package: quality Hebrew and correct display. Anyone who wants to learn this in a structured way, the free courses at the Academy include a full Claude course in Hebrew, step by step.

Claude RTL Support: When Will Official Support Arrive?

As of August 2026, there is no official timeline. Several open feature requests exist in the anthropics/claude-code repository, most notably #38005 (RTL for Hebrew and Arabic in Claude Desktop and Cowork) and #72580 (RTL for Hebrew in the Claude Code web interface). All existing solutions, patches and extensions, are community initiatives, not official Anthropic products.

The best way to accelerate a built-in solution is to add your voice (a 👍 and a substantive comment) to the open requests on GitHub and in Anthropic's feedback channels. The more documented demand there is, the higher the chance of prioritization. In the meantime, the solutions in this guide cover every real-world scenario.

🔄 Last updated, September 2026: We re-examined the state of Claude RTL across all surfaces, and there is no official change from Anthropic: there is still no built-in "Hebrew right-to-left" toggle, and the feature requests in the repository (#38005 for Desktop, #72580 for Claude Code, and others) remain open. What has become clearer in practice: the fastest and safest solution for Claude RTL in the browser remains a locally-running extension (Claude RTL / RTL Responder); for Claude Code users, the VS Code extension or a Hebrew-supporting terminal (Kivun/iTerm2); and for documents and Artifacts, dir="rtl" in the prompt. Until Anthropic provides official support, this is the status we maintain and update here every few weeks, and we recommend adding a 👍 to the open GitHub requests to help push prioritization.

The Limitations: Honestly

So you are not caught off guard, here are the things no solution in this guide solves perfectly as of August 2026:

  • There is no single solution for all surfaces. Each surface is fixed separately, and a browser extension does not help the desktop app and vice versa.
  • The Desktop patch breaks with every update. You need to re-run it after every new Claude Desktop version, and it involves real security trade-offs.
  • Browser extensions depend on claude.ai selectors. A major interface update can break them until the developer pushes a fix. A maintained extension beats an abandoned one.
  • RTL in the terminal remains partial. Even with experimental iTerm2 or Kivun, mixed Hebrew-English-code text will never be perfect in a terminal. That is a limitation of the technology, not of Claude.
  • Display direction does not improve the Hebrew itself. Right-alignment will not fix phrasing. That is what the style instructions in the previous section are for.
  • The claude.ai interface itself (menus, buttons) stays in English. The extensions align the conversation text, they do not translate the product.

Common Mistakes and How to Avoid Them

  • Installing the Desktop patch as a first resort. Most people do not need it. A browser extension covers 90% of use with zero risk. The patch is a last resort for those who genuinely need the desktop app.
  • Running scripts as administrator without reading them. A dangerous habit in general, and especially when the tool replaces security credentials.
  • Fixing alignment without direction. text-align: right alone leaves punctuation broken. The real fix is always direction: rtl (or dir="rtl"). Alignment comes along with it.
  • Giving up on Claude Code because of the terminal. The reversed terminal is a display annoyance, not a capability limitation. Writing to a file instead of chatting, or using VS Code with an RTL extension, solves it.
  • Pasting from chat into Word with formatting. A regular Ctrl+V drags the wrong direction with it. Ctrl+Shift+V (paste without formatting) followed by right Ctrl+Shift, and the document falls into place.
  • Forgetting the persistent instruction. Writing "align right" in every new conversation is a waste. Set it once in preferences (or in CLAUDE.md) and you are done.

Frequently Asked Questions

How do you set up Hebrew in Claude, in short?

By surface: browser, an RTL extension (one click); Desktop, a community patch (carefully); mobile, works out of the box; Claude Code, a VS Code extension or a Hebrew-supporting terminal; documents, a prompt with dir="rtl". The full decision table is at the top of the guide.

Claude Hebrew right-to-left: is it a setting you can switch on?

No. There is no official "Hebrew right-to-left" toggle in Claude as of August 2026. Direction comes from one of three places: an extension or CSS in the browser, a patch in the Desktop app, or an output instruction (dir="rtl") for generated content. That is exactly why this guide is organized by surface.

How do you get Claude to write right-to-left in documents it generates?

Add this to your prompt (or to your persistent preferences): "All HTML/Artifact output in Hebrew, with dir="rtl" on the top element and text-align: right". Claude follows this consistently. Ready-to-copy templates are in the templates section of the guide.

What is the difference between "Claude align right" and real RTL?

Right-alignment (text-align: right) only pushes the text to the right side of the container. Punctuation and word order in mixed text remain broken. Real RTL (direction: rtl) changes the base direction of the paragraph, which is what puts periods, brackets, and English segments back in the right place. All recommended solutions in this guide do the latter.

For most users: Claude RTL (Chrome/Firefox), lightweight, open-source, with per-paragraph language detection. Good alternatives: RTL Responder and Claude AI RTL Support. The principle matters more than the brand: a maintained, open-source extension that requests permission only for claude.ai.

Is there an RTL extension for Claude in Firefox too?

Yes, "Claude RTL, Hebrew & Arabic Support" is available on Firefox Add-ons. In addition, in any browser (including Safari) you can use a userscript via Tampermonkey/Violentmonkey or CSS via Stylus.

Claude Code in Hebrew: does it actually understand Hebrew well?

Excellently. You can give Claude Code instructions in free-form Hebrew, ask it to write content, documents, and websites in Hebrew, and manage the entire project in Hebrew. The only issue is how Hebrew displays for you in the terminal, and that is solved by a VS Code extension, a Hebrew-supporting terminal (Kivun/iTerm2/Konsole), or writing output to files. For beginners: Claude Code for beginners.

Claude Code RTL in the terminal: why isn't there just a setting?

Because terminals are built on a unidirectional character grid, and BiDi support in them has been an unsolved problem for decades. That is not something Claude Code can fix on its own. iTerm2 has experimental support (3.6+), Windows Terminal still does not (open request #20302), and Konsole is the best in this area. Kivun Terminal packages that solution specifically for Claude Code users.

Does the instruction "answer aligned to the right" in chat help?

In the claude.ai chat interface, not really: Claude does not control the CSS of the interface that renders it, so messages will stay LTR even if asked nicely. The instruction does help anywhere Claude generates the document itself, such as Artifacts, HTML, and files. There, dir="rtl" works perfectly.

I pasted an answer into Word and everything flipped: what do I do?

Select the text and press right Ctrl+Shift (flips paragraph direction to right-to-left). Going forward: paste with Ctrl+Shift+V (paste without formatting), or ask Claude to deliver the output as "plain text without formatting" up front. Full details are in the copy-paste section of the guide.

Claude RTL support: is there any official progress?

As of August 2026, still no. The open GitHub requests (#38005, #72580, and others) are accumulating support, but there is no official statement or timeline. All solutions in the guide are community-built, and the guide is updated whenever something changes.

I am deploying Claude in an organization with Hebrew-speaking users: what do you recommend?

A simple, safe path: an IT-approved browser extension for everyone, a persistent RTL instruction in preferences, and prompt templates for documents. No binary patches in an enterprise environment. For structured deployment support there are Claude Code workshops, and you are always welcome to talk to me directly.

The Bottom Line

There is no single button that activates Hebrew RTL everywhere, but after this guide you have a working solution for every surface: a browser extension (or Stylus/userscript) for Claude.ai, a community patch for Desktop on Windows and Mac (with eyes open), built-in support on mobile, an RTL extension for Claude Code in VS Code/Cursor, a Hebrew-supporting terminal (Kivun/iTerm2/Konsole) or simply writing to files, and prompt templates that enforce dir="rtl" in every document and Artifact.

The simple rule: day-to-day work in the browser or on mobile (safe); Claude Code, VS Code with an extension or write Hebrew to files; heavy Desktop work, the patch, carefully and knowing exactly what it does.

Want to go deeper? Start with the full Claude guide and the Hebrew Claude guide, the big picture of working in Hebrew beyond RTL. Desktop users have the Claude Desktop guide, and those building with Claude Code have the full Claude Code guide. For structured free learning, join the AI courses at the Academy or the practical AI course. An organization looking for hands-on training will find it at the Claude Code workshops, or simply talk to me.

Sources

Working with Claude in Hebrew in a specific profession? I also wrote a complete guide to Claude for lawyers, including the Bar Association's ethics rules and working safely with documents. Recently, guides for additional professions have been added: AI for accountants, AI for bookkeepers including connecting Claude to Hashavshevet, and AI for real estate appraisers. For anyone considering rolling this out organizationally: how much AI implementation actually costs, the mistakes that kill implementations and who in the organization needs AI training.

Once Hebrew is displaying correctly, the next step is connecting Claude to your systems: what is MCP (Model Context Protocol), explained in Hebrew, including setting up a first server in Claude Desktop and Claude Code. And if you want to go deeper, a free Claude Code course and Claude workshops are open to you.

This guide was written and is maintained by Yaakov Tzedek, an AI expert, based on daily hands-on work with Claude in Hebrew. Last updated: September 2026.

Frequently asked questions

Was this article helpful?
Share:WhatsAppLinkedInX
Yaakov Tzedek
WRITTEN BY

Yaakov Tzedek

An Israeli AI lecturer, consultant and implementer who has supported 100+ organizations in AI implementation and lectured for 200+. Official content partner of Meta, Google, Canva and TikTok, featured on Israel's Channel 13.

More about Yaakov →