No, X has not disabled Hebrew translation for posts on its platform - here's what we know

If you spent any time scrolling through X recently, you likely stumbled upon a rather alarming claim gaining traction among users. A screenshot circulating widely, specifically from an account named Red Pill Media, alleged that the platform had completely removed the ability to translate Hebrew text.

The post claimed this was a deliberate move to curb “calls for genocide,” igniting a firestorm of confusion and anger. But before everyone runs with that narrative, we need to look at what is actually happening, because the reality is much simpler than a conspiracy to silence a language.

The entire controversy appears to stem from a single, isolated post that refused to cooperate with the platform’s translation tools. The tweet in question came from the account @Hakufsah and was actually just a harmless promotional update about “I Butterfly,” a new girl group starring in a series on HOT.

When users tried to translate this specific post, they were apparently hit with an error message stating Hebrew was not currently supported. Naturally, someone grabbed a screenshot, added a sensational caption, and the misinformation spread like wildfire.

Things got significantly messier when Grok entered the chat. Users began asking X’s own AI chatbot why the translations were disabled. Because these large language models often function like sophisticated autocomplete engines, Grok simply scraped the ongoing conversations — which were full of the false rumor — and regurgitated them as fact. It initially confirmed the “ban” and even fabricated a justification about policy violations.

However, the bot eventually corrected itself. When accounts like HonestReporting pressed Grok on whether it was a glitch regarding mixed languages, the AI changed its tune, clarifying that there is no global disablement of the language.

I decided to check this out myself rather than taking a screenshot at face value. In my own testing, I went to that exact same account and could translate dozens of other Hebrew posts without a single hitch. The feature is clearly fully functional.

The likely culprit for the error on that specific post is a technical glitch where the auto-detection software gets confused, possibly due to a mix of English and Hebrew characters or just a bug in the system. In my brief testing, the former possibility seems to be the culprit here.

A quick search for the word “hot” from the same account brought up multiple other promotional posts. And much like the post that started the firestorm, none of those posts could be translated. So the whole conspiracy falls flat, and instead, it just seems to be that Grok can’t translate posts when multiple languages are mixed. Check these screenshots out for reference. There’s no option to translate the post because there’s an English word in the mix.

Furthermore, the screenshot that’s circulating shows a pop-up saying, “Hebrew is not currently supported for translation.” But what the poster didn’t mention is that the pop-up isn’t even from X. In fact, when a translation isn’t available, you simply won’t see any option to translate a post on X. There are no pop-ups.

Instead, the screenshot shows Apple’s Translate pop-up, which currently does not support Hebrew. Check this screenshot I captured for reference:

In the screenshot, you can clearly see that Grok is available to translate the post on X. However, if I manually select the text and try using Apple Translate, I got the same pop-up as highlighted in the viral screenshot.

While xAI hasn’t issued a formal statement, it serves as a solid reminder that asking a chatbot for breaking news verification is rarely a good idea. The feature works, the rumors are false, and it takes about thirty seconds of manual checking to prove it.