The padding-inline-end property sets the inner padding on the inline-end edge of an element. In a horizontal left-to-right writing mode, that maps to the physical right — like padding-right.
With direction: rtl, it maps to the left. With a vertical writing-mode, it can map to top or bottom instead. It is one half of the padding-inline shorthand (with padding-inline-start). It is not inherited. The initial value is 0. Negative values are invalid.
Baseline · Widely available.
Not deprecated. Cross-browser since about January 2020. Prefer it over padding-right when direction or writing mode may change.
Logical tip.
Use padding-inline-end for space after the content on the inline axis. Pair with padding-inline-start when you need both sides separately.
Flip direction.direction: rtl makes text flow right to left.
End moves. Inline-end is now the physical left edge.
Padding stays logical.1.5rem still means after the content on the inline axis.
Why it matters. The same rule works for LTR and RTL without rewriting left/right.
Edge Cases & Pitfalls
If the wrong side gets padding, direction, writing mode, or a physical longhand is usually why.
physical
Not always right
In horizontal LTR it usually matches padding-right. In RTL it maps to the left. In vertical writing it can match top or bottom. Use physical longhands only for a fixed screen edge.
rtl
RTL does flip inline-end
In horizontal writing, inline-end is usually right in LTR and left in RTL. Prefer logical padding when both directions matter.
negative
Negative padding is invalid
Like all padding properties, negative lengths are not allowed. The declaration is ignored.
percent
Percentages use containing-block width
Percentage padding resolves against the containing block’s inline size (usually width), even on the inline-end side.
override
Later physical padding can override
A following padding-right still wins for that physical side. Keep logical and physical rules from fighting each other.
Compatibility
Browser Support
padding-inline-end is a browser CSS property for logical box spacing. Node.js, Deno, and Bun do not apply it.
✓ Baseline · Widely available
padding-inline-end
Chrome 69+, Firefox 41+, Safari 12.1+, Edge 79+. Widely available since January 2020. Not in Internet Explorer.
97%Logical padding support
Google Chrome69+
Full support
Mozilla Firefox41+
Full support
Apple Safari12.1+
Full support
Microsoft Edge79+
Full support
Opera56+
Full support
Samsung Internet10.1+
Full support
Internet ExplorerNot supported
Not supported
padding-inline-endWidely supported
Bottom line: Safe for modern sites. For Internet Explorer, fall back to physical padding-right. It is not a runtime API.
Remember
Key Takeaways
Role: logical inner spacing on the inline-end edge only.
Maps by direction: usually right in LTR; left in RTL; can be top/bottom in vertical text.
Shorthand partner: second value of padding-inline; pair with padding-inline-start.
Limits: no auto, no negatives; percentages use containing-block width.
One line:padding-inline-end sets inline-end padding that follows direction and writing mode — use a non-negative length or percentage.
Frequently Asked Questions
It sets inner spacing on the inline-end edge. In horizontal left-to-right writing, that is usually the right. The physical side can change with direction or writing-mode.
The default is 0, so there is no inline-end padding until you set one.
padding-right always means physical right. padding-inline-end follows direction and writing mode, so in RTL it maps to the left, and in vertical text it can map to top or bottom.
Yes. In horizontal writing, inline-end is usually right in LTR and left in RTL. That is the main reason to prefer logical inline padding for multilingual UI.
Use it when you need inner space only after the content on the inline axis and want that side to stay correct if direction or writing mode may change.
It is Baseline and widely available in modern browsers since about January 2020 (Chrome 69+, Firefox 41+, Safari 12.1+). It is a browser CSS property, not a Node.js feature.