You wrote a Hebrew word and got it backwards, or gibberish that looks like Hebrew from a distance. It is not a glitch and not something you are doing wrong. Here is why it happens, and the approach that actually works.
This is one of the most common frustrations for Israeli creators. You generate a gorgeous poster, everything is perfect, then you look at the caption and see Hebrew letters in reverse order, or a letter combination that looks like Hebrew but means nothing. So you try again. And again. And it does not improve.
An image model does not "write" text. It draws it. As far as it is concerned a letter is a visual shape, exactly like a tree or a face, and it tries to reproduce a shape it has seen before. Now consider how many billions of images with English text it saw during training, versus how many with Hebrew text. The ratio is not tenfold, it is orders of magnitude.
And on top of that comes a second problem: Hebrew is written right to left. The model learned writing direction left to right from hundreds of millions of examples. Even when it identifies the letters correctly, it arranges them in the direction it knows. That is why you get the right word in reverse order.
Worth knowing: Stop trying to "fix" this in the prompt. There is no magic phrasing that forces an image model to write correct Hebrew, and requests like "write right to left" change nothing. Every additional attempt is money burned on the same problem.
The real solution is to not ask the model for text at all. Generate a clean image with no words in it, and add the text afterwards on a separate layer, with a real font. That sounds like a compromise, but it is actually better on every axis: the text is perfectly sharp, in the font you chose, at a size you control, and editable tomorrow without regenerating anything.
Once you have solved the direction problem, a second problem remains that nobody talks about: where the text goes. A great many designs are ruined because the caption lands exactly on the thing that made the image beautiful, usually the face.
Our rule is absolute: text never goes on a face. Not with a transparent background, not with a shadow, not "just a little." A face is what draws the eye in an image, and a word sitting on it cancels out both. There is always somewhere else: above the head, below the shoulders, on the other side of the frame.
Worth knowing: If there is no free space in the image, do not add a grey plate behind the text to "solve" it. Regenerate the image with more air in it. A plate behind a caption is the single clearest sign of amateur design.
In video the problem is worse, because text has to stay stable across dozens of frames and the engine redraws every frame from scratch. The result is letters that dance and shift mid-shot. So the rule is even simpler: never ask a video engine for text. Subtitles and captions always go in the edit, where you have full control over timing, size and motion anyway.
Hebrew does not "break" in AI, it simply does not belong at that stage of the process. Let the model do what it is astonishing at, the picture, and leave the words to a tool built for them. The result looks better than any attempt to force both into the same moment.
עמוד הבית · בלוג · וידאו AI · תמונות AI · קול AI · כל המנועים · קרדיטים ולא מנוי · AI בעברית · קורס מתחילים · מדריכים