Left-to-Right Mark U+200E

The left-to-right mark (LRM, U+200E) is an invisible, zero-width Unicode character that behaves like a left-to-right letter. Its only job is to steer how the Unicode Bidirectional Algorithm sets text direction.

It was made for text that mixes left-to-right languages (English, French, German) with right-to-left ones (Arabic, Hebrew, Persian), but it's best known as the character most often suggested for blank WhatsApp messages.

How to Send a Blank Message on WhatsApp

1. Copy the LRM character. Click the copy button at the top of this page to copy U+200E.
2. Open WhatsApp. Open the chat or group you want to message.
3. Paste the character. Tap the message field and paste (long-press > Paste on mobile, Ctrl+V on desktop).
4. Send. If WhatsApp accepts it, the recipient sees a blank message.

Why LRM Works for WhatsApp

WhatsApp needs at least one character to send a message. It strips regular spaces and may filter zero-width spaces. Users report that LRM gets through, producing a message that contains a character but displays nothing. WhatsApp does not document this behavior.

Alternatives If LRM Stops Working

WhatsApp occasionally changes its text processing. If LRM stops working, try:

• Braille Pattern Blank (U+2800)
• Hangul Filler (U+3164)
• Zero-Width Space (U+200B)

Common Uses

• Sending blank WhatsApp messages.
• Fixing direction in mixed-script text. In an English sentence with Arabic or Hebrew words, or the reverse, LRM keeps numbers, punctuation, and neutral characters on the correct side.
• Correcting numbers in RTL text. Western-digit numbers and dates in Arabic text can land on the wrong side. An LRM before or after the number fixes it.
• Emails with mixed scripts. Emails mixing English and Arabic often use LRM to prevent garbled direction.
• File paths and URLs in RTL interfaces. Paths with mixed Latin and Arabic folder names can display out of order. LRM forces left-to-right display.

How to Type

How Bidirectional Text Works

The Unicode Bidirectional Algorithm (UBA) decides how to display text that mixes LTR and RTL characters:

1. Strong characters have a fixed direction. Latin letters are LTR. Arabic and Hebrew letters are RTL.
2. Weak characters (numbers, some punctuation) take their direction from surrounding strong characters.
3. Neutral characters (spaces, most punctuation) also take direction from context.

Weak and neutral characters cause the trouble. In "The price is 100 ريال", the number 100 has to sit correctly relative to both the English and the Arabic text, and without LRM the algorithm may put it on the wrong side. LRM acts as an invisible strong LTR character that anchors nearby neutral and weak characters to left-to-right.

Example Problem

Without LRM, this mixed text:

"Call 555-1234 for المعلومات"

might render with the phone number in the wrong position relative to the Arabic word. Adding LRM after the phone number fixes the position:

"Call 555-1234[LRM] for المعلومات"

Technical Details

• Unicode category: Cf (Format). No visible representation.
• Width: Zero. No glyph, no horizontal space.
• Bidirectional class: L (Left-to-Right).
• Line breaking: Does not create or prevent line breaks.
• Effect on surrounding text: Forces adjacent neutral and weak characters to resolve as LTR.

In code:

// Detect LRM in texttext.includes('‎')
// Remove all LRM characterstext.replace(/‎/g, '')
// Remove all bidirectional marks (LRM and RLM)text.replace(/[‎‏]/g, '')

Security Considerations

• URL and path manipulation. LRM inserted into URLs or file paths can change how they display in RTL interfaces without changing where they point. This has been used in phishing attacks targeting Arabic and Hebrew speakers.
• Display spoofing. In mixed-script text, a well-placed LRM can make text display in a misleading order and change its apparent meaning.
• Trojan Source. LRM isn't used in Trojan Source attacks, which rely on overrides like the Right-to-Left Override, but it belongs to the same bidirectional family.

LRM vs Related Characters

For developers: use LRM for quick inline fixes, LRI (U+2066) for isolated LTR runs in modern code, and avoid the override and embedding characters unless you have a specific technical reason.

For blank messages and invisible text on other platforms, see Hangul Filler (best for Among Us and Twitter/X), Zero-Width Space (best for Fortnite), and Braille Pattern Blank (best for Discord).