Rewrite margin-left, padding-top, width and the rest as logical properties, so a layout flips correctly in right-to-left and vertical writing modes.
The mapping is correct for horizontal writing modes, which covers Latin, Arabic, Hebrew and most of the world's text. In a vertical writing mode, block and inline swap axes entirely — margin-top is not margin-block-start there.
Waiting for CSS
Rewrites left and right as inline-start and inline-end, and top and bottom as block-start and block-end.
The rewritten CSS appears here
Your own stylesheet with the property names changed and nothing else touched.
CSS Logical Properties Converter runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Logical properties describe position relative to the text flow rather than the screen. `margin-inline-start` is the margin before the text begins — on the left in English, on the right in Arabic or Hebrew, and on the top in vertical Japanese. One declaration covers every case, which is the entire reason they exist.
The alternative is maintaining a mirrored stylesheet, and that is worse than it sounds. Flipping left and right automatically is nearly right and fails on the details — an icon that should not mirror, a shadow that should, a text-align that should — and every one of those failures has to be found by someone who reads the language.
The mapping is not one-to-one, and the honest output says so. `width` becomes `inline-size` and `height` becomes `block-size`, which swap in a vertical writing mode. `top` and `bottom` become `inset-block-start` and `inset-block-end`. But a few physical properties have no logical form at all, and shorthands such as `margin: 0 auto` sit awkwardly between the two systems — those are reported rather than converted into a guess.
This is a conversion of the CSS you paste and nothing more. It does not know your document's direction or writing mode, cannot tell whether a particular left margin was meant to be physical, and does not fetch or inspect a live page. For the cases where physical really is correct — a decoration keyed to the screen rather than the text — the conversion is the wrong answer and only you can tell.
Inline is the direction text runs — horizontally in English, vertically in vertical Japanese. Block is the direction lines stack, perpendicular to it. So inline-start is where a line of text begins and block-start is where the first line sits.
Because flipping every left and right is nearly right and wrong in the details. Some icons should not mirror, some shadows should, and each exception has to be found by someone who reads the language. Logical properties make the correct behaviour the default instead of a patch.
In a horizontal writing mode, yes. In a vertical one they swap: inline-size follows the text direction, so it becomes the element's visual height. That is the point of the rename, and it is why the two are not interchangeable in general.
The individual properties are supported in every current browser. A few of the newer shorthands have patchier support, so a shorthand is worth checking against the browsers you care about before relying on it.
No, and it does not need to — that is the advantage. It converts the CSS you paste; the browser resolves the logical properties against the document's actual direction and writing mode at render time.