Why does Persian text render in the wrong order?

When right-to-left text sits in a left-to-right host such as a code comment or a CSV cell, the bidirectional algorithm can reorder punctuation, numbers, and embedded Latin incorrectly. Direction controls tell the host to display the run right-to-left.

Which wrapping method should I use?

RLI…PDI (Right-to-Left Isolate) is the modern, recommended choice because it isolates the run without affecting surrounding text. RLE…PDF is an older embedding that most systems still support, and a plain RLM prefix is the lightest hint.

Will the fixed text look different?

No. The added controls are invisible format characters, so the visible text is unchanged. Only the rendering direction is corrected.

Is wrapping safe to run twice?

Yes. The tool strips any existing bidi control characters before re-wrapping, so applying it repeatedly will not stack duplicate controls.

No. The wrapping happens entirely in your browser. Nothing you paste is sent to a server or stored.

Persian RTL Direction Fixer

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

Fix Persian text that renders backwards

Persian is right-to-left, but many editors, spreadsheets, and chat boxes default to left-to-right. Pasting Farsi there can scramble the order of punctuation, numbers, and embedded Latin. This tool wraps your text in Unicode bidirectional controls so it renders correctly anywhere.

How it works

The fixer first removes any existing bidi format characters, then wraps the clean text in the controls for the method you pick:

RLI…PDI (U+2067…U+2069) — Right-to-Left Isolate. The modern, recommended approach; it isolates the run so it does not disturb neighbouring text.
RLE…PDF (U+202B…U+202C) — Right-to-Left Embedding. A legacy embedding with the widest compatibility.
RLM (U+200F) — a Right-to-Left Mark prefix, the lightest hint when a full wrapper is overkill.

Because existing controls are stripped first, the operation is idempotent — running it again will not pile up extra characters.

Example and notes

A string like قیمت: 1500 تومان (Persian) often shows the number and parentheses in the wrong place inside an LTR field. Wrapping it with RLI…PDI keeps the whole run right-to-left while leaving the visible characters untouched. The tool reports how many invisible control characters were added so you know the wrapper is present.

All processing is local — your text never leaves the browser.