1. Introduction
This section is not normative.
The CSS visual formatting model describes a coordinate system within each element is positioned. Positions and sizes in this coordinate space can be thought of as being expressed in pixels, starting in the origin of point with positive values proceeding to the right and down.
This coordinate space can be modified with the transform property. Using transform, elements can be translated, rotated and scaled in two or three dimensional space.
Additional properties make working with transforms easier, and allow the author to control how nested threedimensional transforms interact.
 The transformorigin property provides a convenient way to control the origin about which transforms on an element are applied.
 The perspective property allows the author to make child elements with threedimensional transforms appear as if they live in a common threedimensional space. The perspectiveorigin property provides control over the origin at which perspective is applied, effectively changing the location of the "vanishing point".
 The transformstyle property allows 3Dtransformed elements and their 3Dtransformed descendants to share a common threedimensional space, allowing the construction of hierarchies of threedimensional objects.
 The backfacevisibility property comes into play when an element is flipped around via threedimensional transforms such that its reverse side is visible to the viewer. In some situations it is desirable to hide the element in this situation, which is possible using the value of hidden for this property.
Note: While some values of the transform property allow an element to be transformed in a threedimensional coordinate system, the elements themselves are not threedimensional objects. Instead, they exist on a twodimensional plane (a flat surface) and have no depth.
2. Module Interactions
This module defines a set of CSS properties that affect the visual rendering of elements to which those properties are applied; these effects are applied after elements have been sized and positioned according to the Visual formatting model from [CSS21]. Some values of these properties result in the creation of a containing block, and/or the creation of a stacking context.
Threedimensional transforms can also affect the visual layering of elements, and thus override the backtofront painting order described in Appendix E of [CSS21].
Transforms affect the rendering of backgrounds on elements with a value of fixed for the backgroundattachment property, which is specified in [CSS3BG].
Transforms affect the client rectangles returned by the Element Interface Extensions getClientRects() and getBoundingClientRect(), which are specified in [CSSOMVIEW].
3. CSS Values
This specification follows the CSS property definition conventions from [CSS21]. Value types not defined in these specifications are defined in CSS Values and Units Module Level 3 [CSS3VAL].
In addition to the propertyspecific values listed in their definitions, all properties defined in this specification also accept the inherit keyword as their property value. For readability it has not been repeated explicitly.
4. Terminology
When used in this specification, terms have the meanings assigned in this section.
 transformable element

A transformable element is an element in one of these categories:
 an element whose layout is governed by the CSS box model which is either a blocklevel or atomic inlinelevel element, or whose display property computes to tablerow, tablerowgroup, tableheadergroup, tablefootergroup, tablecell, or tablecaption [CSS21]
 an element in the SVG namespace and not governed by the CSS box model which has the attributes transform,
patternTransform
orgradientTransform
[SVG11].
 transformed element
 An element with a computed value other than none for the transform property.
 3Dtransformed element
 An element whose computed value for the transform property includes one of the 3D transform functions
 user coordinate system
 local coordinate system

In general, a coordinate system defines locations and distances on the current canvas. The current local coordinate system (also user coordinate system) is the coordinate system that is currently active and which is used to define how coordinates and lengths are located and computed, respectively, on the current canvas.
The current user coordinate system has its origin at the topleft of a reference box specified by the transformbox property. Percentage values are relative to the dimension of this reference box. One unit equals one CSS pixel.
 perspective matrix
 A matrix computed from the values of the perspective and perspectiveorigin properties as described below.
 transformation matrix
 A matrix that defines the mathematical mapping from one coordinate system into another. It is computed from the values of the transform and transformorigin properties as described below.
 current transformation matrix (CTM)
 A matrix that defines the mapping from the local coordinate system into the viewport coordinate system.
 accumulated 3D transformation matrix
 A matrix computed for an element relative to the root of its 3D rendering context, as described below.
 2D matrix
 A 3x2 transformation matrix with 6 items or a 4x4 matrix with 16 items, where the items m_{31}, m_{32}, m_{13}, m_{23}, m_{43}, m_{14}, m_{24}, m_{34} are equal to 0 and m_{33}, m_{44} are equal to 1.
 3D matrix
 A 4x4 matrix which does not fulfill the requirements of an 2D matrix.
 identity transform function
 A transform function that is equivalent to a identity 4x4 matrix (see Mathematical Description of Transform Functions). Examples for identity transform functions are translate(0), translate3d(0, 0, 0), translateX(0), translateY(0), translateZ(0), scale(1), scaleX(1), scaleY(1), scaleZ(1), rotate(0), rotate3d(1, 1, 1, 0), rotateX(0), rotateY(0), rotateZ(0), skew(0, 0), skewX(0), skewY(0), matrix(1, 0, 0, 1, 0, 0) and matrix3d(1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1). A special case is perspective: perspective(infinity). The value of m_{34} becomes infinitesimal small and the transform function is therefore assumed to be equal to the identity matrix.
 3D rendering context
 A set of elements with a common ancestor which share a common threedimensional coordinate system, as described below.
5. Two Dimensional Subset
UAs may not always be able to render threedimensional transforms and then just support a twodimensional subset of this specification. In this case threedimensional transforms and the properties transformstyle, perspective, perspectiveorigin and backfacevisibility must not be supported. Section 3D Transform Rendering does not apply. Matrix decomposing uses the technique taken from the "unmatrix" method in "Graphics Gems II, edited by Jim Arvo", simplified for the 2D case. Section Mathematical Description of Transform Functions is still effective but can be reduced by using a 3x3 transformation matrix where a equals m_{11}, b equals m_{12}, c equals m_{21}, d equals m_{22}, e equals m_{41} and f equals m_{42} (see A 2D 3x2 matrix with six parameter).
Authors can easily provide a fallback if UAs do not provide support for threedimensional transforms. The following example has two property definitions for transform. The first one consists of two twodimensional transform functions. The second one has a twodimensional and a threedimensional transform function.
div { transform: scale(2) rotate(45deg); transform: scale(2) rotate3d(0, 0, 1, 45deg); }
With 3D support, the second definition will override the first one. Without 3D support, the second definition is invalid and a UA falls back to the first definition.
6. The Transform Rendering Model
This section is normative.
Specifying a value other than none for the transform property establishes a new local coordinate system at the element that it is applied to. The mapping from where the element would have rendered into that local coordinate system is given by the element’s transformation matrix. Transformations are cumulative. That is, elements establish their local coordinate system within the coordinate system of their parent. From the perspective of the user, an element effectively accumulates all the transform properties of its ancestors as well as any local transform applied to it. The accumulation of these transforms defines a current transformation matrix (CTM) for the element.
The coordinate space is a coordinate system with two axes: the X axis increases horizontally to the right; the Y axis increases vertically downwards. Threedimensional transformrm functions extend this coordinate space into three dimensions, adding a Z axis perpendicular to the plane of the screen, that increases towards the viewer.
The transformation matrix is computed from the transform and transformorigin properties as follows:
 Start with the identity matrix.
 Translate by the computed X, Y and Z values of transformorigin
 Multiply by each of the transform functions in transform property from left to right
 Translate by the negated computed X, Y and Z values of transformorigin
Transforms apply to transformable elements.
Note: Transformations do affect the visual rendering, but have no affect on the CSS layout other than affecting overflow. Transforms are also taken into account when computing client rectangles exposed via the Element Interface Extensions, namely getClientRects() and getBoundingClientRect(), which are specified in [CSSOMVIEW].
div { transform: translate(100px, 100px); }
This transform moves the element by 100 pixels in both the X and Y directions.
div { height: 100px; width: 100px; transformorigin: 50px 50px; transform: rotate(45deg); }
The transformorigin property moves the point of origin by 50 pixels in both the X and Y directions. The transform rotates the element clockwise by 45° about the point of origin. After all transform functions were applied, the translation of the origin gets translated back by 50 pixels in both the X and Y directions.
div { height: 100px; width: 100px; transform: translate(80px, 80px) scale(1.5, 1.5) rotate(45deg); }
This transform moves the element by 80 pixels in both the X and Y directions, then scales the element by 150%, then rotates it 45° clockwise about the Z axis. Note that the scale and rotation operate about the center of the element, since the element has the default transformorigin of 50% 50%.
Note that an identical rendering can be obtained by nesting elements with the equivalent transforms:
<div style="transform: translate(80px, 80px)"> <div style="transform: scale(1.5, 1.5)"> <div style="transform: rotate(45deg)"></div> </div> </div>
For elements whose layout is governed by the CSS box model, the transform property does not affect the flow of the content surrounding the transformed element. However, the extent of the overflow area takes into account transformed elements. This behavior is similar to what happens when elements are offset via relative positioning. Therefore, if the value of the overflow property is scroll or auto, scrollbars will appear as needed to see content that is transformed outside the visible area.
For elements whose layout is governed by the CSS box model, any value other than none for the transform results in the creation of both a stacking context and a containing block. The object acts as a containing block for fixed positioned descendants.
Is this effect on position: fixed necessary? If so, need to go into more detail here about why fixed positioned objects should do this, i.e., that it’s much harder to implement otherwise. See Bug 16328.
Fixed backgrounds on the root element are affected by any transform specified for that element. For all other elements that are effected by a transform (i.e. have a transform applied to them, or to any of their ancestor elements), a value of fixed for the backgroundattachment property is treated as if it had a value of scroll. The computed value of backgroundattachment is not affected.
Note: If the root element is transformed, the transformation applies to the entire canvas, including any background specified for the root element. Since the background painting area for the root element is the entire canvas, which is infinite, the transformation might cause parts of the background that were originally offscreen to appear. For example, if the root element’s background were repeating dots, and a transformation of scale(0.5) were specified on the root element, the dots would shrink to half their size, but there will be twice as many, so they still cover the whole viewport.
6.1. 3D Transform Rendering
Normally, elements render as flat planes, and are rendered into the same plane as their containing block. Often this is the plane shared by the rest of the page. Twodimensional transform functions can alter the appearance of an element, but that element is still rendered into the same plane as its containing block.
Threedimensional transforms can result in transformation matrices with a nonzero Z component (where the Z axis projects out of the plane of the screen). This can result in an element rendering on a different plane than that of its containing block. This may affect the fronttoback rendering order of that element relative to other elements, as well as causing it to intersect with other elements.
This example shows the effect of threedimensional transform applied to an element.
<style> div { height: 150px; width: 150px; } .container { border: 1px solid black; } .transformed { transform: rotateY(50deg); } </style> <div class="container"> <div class="transformed"></div> </div>
The transform is a 50° rotation about the vertical, Y axis. Note how this makes the blue box appear narrower, but not threedimensional.
6.1.1. Perspective
The perspective and perspectiveorigin properties can be used to add a feeling of depth to a scene by making elements higher on the Z axis (closer to the viewer) appear larger, and those further away to appear smaller. The scaling is proportional to d/(d − Z) where d, the value of perspective, is the distance from the drawing plane to the the assumed position of the viewer’s eye.
Normally the assumed position of the viewer’s eye is centered on a drawing. This position can be moved if desired – for example, if a web page contains multiple drawings that should share a common perspective – by setting perspectiveorigin.
The perspective matrix is computed as follows:
 Start with the identity matrix.
 Translate by the computed X and Y values of perspectiveorigin
 Multiply by the matrix that would be obtained from the perspective() transform function, where the length is provided by the value of the perspective property
 Translate by the negated computed X and Y values of perspectiveorigin
This example shows how perspective can be used to cause threedimensional transforms to appear more realistic.
<style> div { height: 150px; width: 150px; } .container { perspective: 500px; border: 1px solid black; } .transformed { transform: rotateY(50deg); } </style> <div class="container"> <div class="transformed"></div> </div>
The inner element has the same transform as in the previous example, but its rendering is now influenced by the perspective property on its parent element. Perspective causes vertices that have positive Z coordinates (closer to the viewer) to be scaled up in X and Y, and those further away (negative Z coordinates) to be scaled down, giving an appearance of depth.
6.1.2. 3D Rendering Contexts
This section specifies the rendering model for content that uses 3Dtransforms and the transformstyle property. In order to describe this model, we introduce the concept of a "3D rendering context".
A 3D rendering context is a set of elements rooted in a common ancestor that, for the purposes of 3Dtransform rendering, are considered to share a common threedimensional coordinate system. The fronttoback rendering of elements in the a 3D rendering context depends on their zposition in that threedimensional space, and, if the 3D transforms on those elements cause them to intersect, then they are rendered with intersection.
A 3D rendering context is established by an element which has a used value for transformstyle of "flat". Descendant elements with a used value for transformstyle of "auto" or "preserve3d" share their enclosing 3D rendering context. A descendant with a used value for transformstyle of "flat" participates in its containing 3D rendering context, but establishes a new 3D rendering context for its descendants. For the purposes of rendering in its containing 3D rendering context, it behaves like a flat plane.
Note: This is conceptually similar to CSS stacking contexts. A positioned element with explicit zindex establishes a stacking context, while participating in the stacking context of an ancestor. Similarly, an element can establish a 3D rendering context for its descendants, while participating in the 3D rendering context of an ancestor. Just as elements within a stacking context render in zindex order, elements in a 3Drendering context render in zdepth order and can intersect.
Some CSS properties have values that are considered to force "grouping": they require that their element and its descendants are rendered as a group before being composited with other elements; these include opacity, filters and properties that affect clipping. The relevant property values are listed under grouping property values. These grouping property values force the used value for transformstyle to be "flat", and such elements are referred to as flattening elements. Consequently, they always establish a new 3D rendering context. The root element always has a used value of "flat" for transformstyle.
The rendering of elements in a 3D rendering context is as follows (numbers refer to items in CSS 2.1, Appendix E, Section E.2 Painting Order):
 The background, borders and other box decorations of the establishing element are rendered (steps 1 and 2)
 The content and descendant elements without 3D transforms, ordered according to steps 3—7, are rendered into a plane at z=0 relative to to the establishing element.
 3Dtransformed elements are each rendered into their own plane, transformed by the accumulated 3D transformation matrix.
 Intersection is performed between the set of planes generated by steps B and C, according to Newell’s algorithm.
 The resulting set of planes is rendered on top of the backgrounds and box decorations rendered in this step A. Coplanar 3D transformed elements are rendered in painting order.
is it OK to not pop 2Dtransformed elements into their own planes?
requiring intersection with nontransformed content and descendants requires UAs to allocate additional textures (possibly doubling memory use). Would be more efficient to simply render content and untransformed descendants along with background and borders.
Note that elements with transforms which have a negative zcomponent will render behind the content and untransformed descendants of the establishing element, and that 3D transformed elements may interpenetrate with content and untransformed elements.
Note: Because the 3Dtransformed elements in a 3D rendering context can all depthsort and intersect with each other, they are effectively rendered as if they were siblings. The effect of transformstyle: preserve3d can then be thought of as causing all the 3D transformed elements in a 3D rendering context to be hoisted up into the establishing element, but still rendered with their accumulated 3D transformation matrix.
<style> .container { backgroundcolor: rgba(0, 0, 0, 0.3); perspective: 500px; } .container > div { position: absolute; left: 0; } .container > :firstchild { transform: rotateY(45deg); backgroundcolor: orange; top: 10px; height: 135px; } .container > :lastchild { transform: translateZ(40px); backgroundcolor: rgba(0, 0, 255, 0.6); top: 50px; height: 100px; } </style> <div class="container"> <div></div> <div></div> </div>
This example shows show elements in a 3D rendering context can intersect. The container element establishes a 3D rendering context for itself and its two children. The children intersect with each other, and the orange element also intersects with the container.
The perspective property can be used to ensure that 3D transformed elements in the resulting 3D rendering context appear to live in a common threedimensional space with depth, by suppling a common perspective matrix to descendant transformed members of its 3D rendering context, which is taken into account in the accumulated 3D matrix computation.
By default, elements with value for perspective other than none are flattening, and thus establish a 3D rendering context. However, setting transformstyle to preserve3d allows the perspective element to extend its containing 3D rendering context (provided no other grouping property values are in effect).
<style> div { height: 150px; width: 150px; } .container { perspective: 500px; border: 1px solid black; } .transformed { transform: rotateY(50deg); backgroundcolor: blue; } .child { transformorigin: top left; transform: rotateX(40deg); backgroundcolor: lime; } </style> <div class="container"> <div class="transformed"> <div class="child"></div> </div> </div>
This example shows how nested 3D transforms are rendered. The blue div is transformed as in the previous example, with its rendering influenced by the perspective on its parent element. The lime element also has a 3D transform, which is a rotation about the X axis (anchored at the top, by virtue of the transformorigin). However, the lime element is being rendered into the plane of its parent because it is not a member of the same 3D rendering context; the parent is "flattening". Thus the lime element only appears shorter; it does not "pop out" of the blue element.
6.1.3. Transformed element hierarchies
By default, transformed elements are flattening, and thus establish a 3D rendering context. However, since it is useful to construct hierarchies of transformed objects that share a common 3dimensional space, this flattening behavior may be overridden by specifying a value of preserve3d for the transformstyle property, provided no other grouping property values are in effect. This allows descendants of the transformed element to share the same 3D rendering context. Non3Dtransformed descendants of such elements are rendered into the plane of the element in step C above, but 3Dtransformed elements in the same 3D rendering context will "pop out" into their own planes.
<style> div { height: 150px; width: 150px; } .container { perspective: 500px; border: 1px solid black; } .transformed { transformstyle: preserve3d; transform: rotateY(50deg); backgroundcolor: blue; } .child { transformorigin: top left; transform: rotateX(40deg); backgroundcolor: lime; } </style>
This example is identical to the previous example, with the addition of transformstyle: preserve3d on the blue element. The blue element now extends the 3D rendering context of its container. Now both blue and lime elements share a common threedimensional space, so the lime element renders as tilting out from its parent, influenced by the perspective on the container.
6.1.4. Accumulated 3D Transformation Matrix Computation
The final value of the transform used to render an element in a 3D rendering context is computed by accumulating an accumulated 3D transformation matrix as follows:

Let transform be the identity matrix.

Let current element be the transformed element.

Let ancestor block be the element that establishes the transformed element’s containing block.

While current element is not the element that establishes the transformed element’s 3D rendering context:

If current element has a value for transform which is not none, premultiply current element’s transformation matrix with the transform.

Compute a translation matrix which represents the offset of current element from its ancestor block, and premultiply that matrix into the transform.

If ancestor block has a value for perspective which is not none, premultiply the ancestor block’s perspective matrix into the transform.

Let ancestor block be the element that establishes the current element’s containing block.

Let current element be the ancestor block.

Note: as described here, the accumulated 3D transformation matrix takes into account offsets generated by the visual formatting model on the transformed element, and elements in the ancestor chain between the transformed element and the element that establishes the its 3D rendering context.
6.1.5. Backface Visibility
Using threedimensional transforms, it’s possible to transform an element such that its reverse side is visible. 3Dtransformed elements show the same content on both sides, so the reverse side looks like a mirrorimage of the front side (as if the element were projected onto a sheet of glass). Normally, elements whose reverse side is towards the viewer remain visible. However, the backfacevisibility property allows the author to make an element invisible when its reverse side is towards the viewer. This behavior is "live"; if an element with backfacevisibility: hidden were animating, such that its front and reverse sides were alternately visible, then it would only be visible when the front side were towards the viewer.
Visibility of the reverse side of an element is considered using the accumulated 3D transformation matrix, and is thus relative to the enclosing flattening element.
Note: This property is useful when you place two elements backtoback, as you would to create a playing card. Without this property, the front and back elements could switch places at times during an animation to flip the card. Another example is creating a box out of 6 elements, but where you want to see only the inside faces of the box.
This example shows how to make a "card" element that flips over when clicked. Note the "transformstyle: preserve3d" on #card which is necessary to avoid flattening when flipped.
<style> .body { perspective: 500px; } #card { position: relative; height: 300px; width: 200px; transition: transform 1s; transformstyle: preserve3d; } #card.flipped { transform: rotateY(180deg); } .face { position: absolute; top: 0; left: 0; width: 100%; height: 100%; backgroundcolor: silver; borderradius: 40px; backfacevisibility: hidden; } .back { transform: rotateY(180deg); } </style> <div id="card" onclick="this.classList.toggle('flipped')"> <div class="front face">Front</div> <div class="back face">Back</div> </div>
what is the impact of backfacevisibility on nontransformed or 2Dtransformed elements? Do they get popped into their own planes and intersect?
6.2. Processing of PerspectiveTransformed Boxes
This is a first pass at an attempt to precisely specify how exactly to transform elements using the provided matrices. It might not be ideal, and implementer feedback is encouraged. See bug 15605.
The accumulated 3D transformation matrix is affected both by the perspective property, and by any perspective() transform function present in the value of the transform property.
This accumulated 3D transformation matrix is a 4×4 matrix, while the objects to be transformed are twodimensional boxes. To transform each corner (a, b) of a box, the matrix must first be applied to (a, b, 0, 1), which will result in a fourdimensional point (x, y, z, w). This is transformed back to a threedimensional point (x′, y′, z′) as follows:
If w > 0, (x′, y′, z′) = (x/w, y/w, z/w).
If w = 0, (x′, y′, z′) = (x ⋅ n, y ⋅ n, z ⋅ n). n is an implementationdependent value that should be chosen so that x′ or y′ is much larger than the viewport size, if possible. For example, (5px, 22px, 0px, 0) might become (5000px, 22000px, 0px), with n = 1000, but this value of n would be too small for (0.1px, 0.05px, 0px, 0). This specification does not define the value of n exactly. Conceptually, (x′, y′, z′) is infinitely far in the direction (x, y, z).
If w < 0 for all four corners of the transformed box, the box is not rendered.
If w < 0 for one to three corners of the transformed box, the box must be replaced by a polygon that has any parts with w < 0 cut out. This will in general be a polygon with three to five vertices, of which exactly two will have w = 0 and the rest w > 0. These vertices are then transformed to threedimensional points using the rules just stated. Conceptually, a point with w < 0 is "behind" the viewer, so should not be visible.
.transformed { height: 100px; width: 100px; background: lime; transform: perspective(50px) translateZ(100px); }
All of the box’s corners have zcoordinates greater than the perspective. This means that the box is behind the viewer and will not display. Mathematically, the point (x, y) first becomes (x, y, 0, 1), then is translated to (x, y, 100, 1), and then applying the perspective results in (x, y, 100, −1). The wcoordinate is negative, so it does not display. An implementation that doesn’t handle the w < 0 case separately might incorrectly display this point as (−x, −y, −100), dividing by −1 and mirroring the box.
.transformed { height: 100px; width: 100px; background: radialgradient(yellow, blue); transform: perspective(50px) translateZ(50px); }
Here, the box is translated upward so that it sits at the same place the viewer is looking from. This is like bringing the box closer and closer to one’s eye until it fills the entire field of vision. Since the default transformorigin is at the center of the box, which is yellow, the screen will be filled with yellow.
Mathematically, the point (x, y) first becomes (x, y, 0, 1), then is translated to (x, y, 50, 1), then becomes (x, y, 50, 0) after applying perspective. Relative to the transformorigin at the center, the upperleft corner was (−50, −50), so it becomes (−50, −50, 50, 0). This is transformed to something very far to the upper left, such as (−5000, −5000, 5000). Likewise the other corners are sent very far away. The radial gradient is stretched over the whole box, now enormous, so the part that’s visible without scrolling should be the color of the middle pixel: yellow. However, since the box is not actually infinite, the user can still scroll to the edges to see the blue parts.
.transformed { height: 50px; width: 50px; background: lime; border: 25px solid blue; transformorigin: left; transform: perspective(50px) rotateY(45deg); }
The box will be rotated toward the viewer, with the left edge staying fixed while the right edge swings closer. The right edge will be at about z = 70.7px, which is closer than the perspective of 50px. Therefore, the rightmost edge will vanish ("behind" the viewer), and the visible part will stretch out infinitely far to the right.
Mathematically, the top right vertex of the box was originally (100, −50), relative to the transformorigin. It is first expanded to (100, −50, 0, 1). After applying the transform specified, this will get mapped to about (70.71, −50, 70.71, −0.4142). This has w = −0.4142 < 0, so we need to slice away the part of the box with w < 0. This results in the new topright vertex being (50, −50, 50, 0). This is then mapped to some faraway point in the same direction, such as (5000, −5000, 5000), which is up and to the right from the transformorigin. Something similar is done to the lower right corner, which gets mapped far down and to the right. The resulting box stretches far past the edge of the screen.
Again, the rendered box is still finite, so the user can scroll to see the whole thing if he or she chooses. However, the right part has been chopped off. No matter how far the user scrolls, the rightmost 30px or so of the original box will not be visible. The blue border was only 25px wide, so it will be visible on the left, top, and bottom, but not the right.
The same basic procedure would apply if one or three vertices had w < 0. However, in that case the result of truncating the w < 0 part would be a triangle or pentagon instead of a quadrilateral.
7. The transform Property
A transformation is applied to the coordinate system an element renders in through the transform property. This property contains a list of transform functions. The final transformation value for a coordinate system is obtained by converting each function in the list to its corresponding matrix like defined in Mathematical Description of Transform Functions, then multiplying the matrices.
Name:  transform 

Value:  none  <transformlist> 
Initial:  none 
Applies to:  transformable elements 
Inherited:  no 
Percentages:  refer to the size of reference box 
Media:  visual 
Computed value:  As specified, but with relative lengths converted into absolute lengths. 
Canonical order:  per grammar 
Animatable:  as transform 
Any computed value other than none for the transform results in the creation of both a stacking context and a containing block. The object acts as a containing block for fixed positioned descendants.
<transformlist> = <transformfunction>+
7.1. Serialization of <transformfunction>s
To serialize the <transformfunction>s, serialize as per their individual grammars, in the order the grammars are written in, avoiding <calc()> expressions where possible, avoiding <calc()> transformations, omitting components when possible without changing the meaning, joining spaceseparated tokens with a single space, and following each serialized comma with a single space.
7.2. Serialization of the computed value of <transformlist>
A <transformlist> for the computed value is serialized to either one <matrix()> or one <matrix3d()> function by the following algorithm:
 Let transform be a 4x4 matrix initialized to the identity matrix. The elements m11, m22, m33 and m44 of transform must be set to 1 all other elements of transform must be set to 0.
 Postmultiply all <transformfunction>s in <transformlist> to transform.

Chose between <matrix()> or <matrix3d()> serialization:
 If transform is a 2D matrix
 Serialize transform to a <matrix()> function.
 Otherwise
 Serialize transform to a <matrix3d()> function.
8. The transformorigin Property
Name:  transformorigin 

Value:  [ left  center  right  top  bottom  <lengthpercentage> ]  [ left  center  right  <lengthpercentage> ] [ top  center  bottom  <lengthpercentage> ] <length>?  [[ center  left  right ] && [ center  top  bottom ]] <length>? 
Initial:  50% 50% 
Applies to:  transformable elements 
Inherited:  no 
Percentages:  refer to the size of reference box 
Media:  visual 
Computed value:  For <length> the absolute value, otherwise a percentage 
Canonical order:  per grammar 
Animatable:  as simple list of length, percentage, or calc 
The initial used value for SVG elements without associated CSS layout box is 0 0.
The values of the transform and transformorigin properties are used to compute the transformation matrix, as described above.
If only one value is specified, the second value is assumed to be center. If one or two values are specified, the third value is assumed to be 0px.
If two or more values are defined and either no value is a keyword, or the only used keyword is center, then the first value represents the horizontal position (or offset) and the second represents the vertical position (or offset). A third value always represents the Z position (or offset) and must be of type <length>.
 <percentage>
 A percentage for the horizontal offset is relative to the width of the reference box. A percentage for the vertical offset is relative to the height of the reference box. The value for the horizontal and vertical offset represent an offset from the top left corner of the reference box.
 <length>
 A length value gives a fixed length as the offset. The value for the horizontal and vertical offset represent an offset from the top left corner of the reference box.
 top
 Computes to 0% for the vertical position.
 right
 Computes to 100% for the horizontal position.
 bottom
 Computes to 100% for the vertical position.
 left
 Computes to 0% for the horizontal position.
 center
 Computes to 50% (left 50%) for the horizontal position if the horizontal position is not otherwise specified, or 50% (top 50%) for the vertical position if it is.
The resolved value of transformorigin is the used value (i.e., percentages are resolved to absolute lengths).
9. Transform reference box: the transformbox property
Name:  transformbox 

Value:  borderbox  fillbox  viewbox 
Initial:  borderbox 
Applies to:  transformable elements 
Inherited:  no 
Percentages:  N/A 
Media:  visual 
Computed value:  Same as specified value. 
Canonical order:  per grammar 
Animatable:  no 
All transformations defined by the transform and transformorigin property are relative to the position and dimension of one of the following reference boxes:
 borderbox
 Uses the border box as reference box. The reference box of a table is the border box of its table wrapper box, not its table box.
 fillbox
 Uses the object bounding box as reference box.
 viewbox

Uses the nearest SVG viewport as reference box.
If a
viewBox
attribute is specified for the SVG viewport creating element:
A reference box adds an additional offset to the origin specified by the transformorigin property.
For SVG elements without an associated CSS layout box, the used value for borderbox is viewbox.
For elements with an associated CSS layout box, the used value for fillbox and viewbox is borderbox.
10. The transformstyle Property
Name:  transformstyle 

Value:  auto  flat  preserve3d 
Initial:  auto 
Applies to:  transformable elements 
Inherited:  no 
Percentages:  N/A 
Media:  visual 
Computed value:  Same as specified value. 
Canonical order:  per grammar 
Animatable:  no 
A value of "flat" for transformstyle establishes a stacking context, and establishes a 3D rendering context. Elements with a used value of "auto" are ignored for the purposes of 3D rendering context computation, and those with a used value of "preserve3d" extend the 3D rendering context to which they belong, even if values for the transform or perspective properties would otherwise cause flattening. A value of "preserve3d" establishes a stacking context, and a containing block.
10.1. Grouping property values
The following CSS property values require the user agent to create a flattened representation of the descendant elements before they can be applied, and therefore force the used value of transformstyle to flat:

opacity: any value less than 1.

filter: any value other than none.

clip: any value other than auto.

clippath: any value other than none.

isolation: used value of isolate.

maskimage: any value other than none.

maskbordersource: any value other than none.

mixblendmode: any value other than normal.
The following CSS property values cause an auto value of transformstyle to become flat:

transform: any value other than none.

perspective: any value other than none.
In both cases the computed value of transformstyle is not affected.
Having overflow imply transformstyle: flat causes every element with nonvisible overflow to become a stacking context, which is unwanted. See Bug 28252.
11. The perspective Property
Name:  perspective 

Value:  none  <length> 
Initial:  none 
Applies to:  transformable elements 
Inherited:  no 
Percentages:  N/A 
Media:  visual 
Computed value:  Absolute length or "none". 
Canonical order:  per grammar 
Animatable:  as length 
Where <length> values must be positive.
 <length>

Distance to the center of projection.
Verify that projection is the distance to the center of projection.
 none
 No perspective transform is applied. The effect is mathematically similar to an infinite <length> value. All objects appear to be flat on the canvas.
The use of this property with any value other than none establishes a stacking context. It also establishes a containing block (somewhat similar to position: relative), just like the transform property does.
The values of the perspective and perspectiveorigin properties are used to compute the perspective matrix, as described above.
12. The perspectiveorigin Property
The perspectiveorigin property establishes the origin for the perspective property. It effectively sets the X and Y position at which the viewer appears to be looking at the children of the element.
Name:  perspectiveorigin 

Value:  <position> 
Initial:  50% 50% 
Applies to:  transformable elements 
Inherited:  no 
Percentages:  refer to the size of the reference box 
Media:  visual 
Computed value:  For <length> the absolute value, otherwise a percentage. 
Canonical order:  per grammar 
Animatable:  as simple list of length, percentage, or calc 
The values of the perspective and perspectiveorigin properties are used to compute the perspective matrix, as described above.
The values for perspectiveorigin represent an offset of the perspective origin from the top left corner of the reference box.
 <percentage>

A percentage for the horizontal perspective offset is relative to the width of the reference box. A percentage for the vertical offset is relative to height of the reference box. The value for the horizontal and vertical offset represent an offset from the top left corner of the reference box.
 <length>

A length value gives a fixed length as the offset. The value for the horizontal and vertical offset represent an offset from the top left corner of the reference box.
 top
 Computes to 0% for the vertical position if one or two values are given, otherwise specifies the top edge as the origin for the next offset.
 right
 Computes to 100% for the horizontal position if one or two values are given, otherwise specifies the right edge as the origin for the next offset.
 bottom
 Computes to 100% for the vertical position if one or two values are given, otherwise specifies the bottom edge as the origin for the next offset.
 left
 Computes to 0% for the horizontal position if one or two values are given, otherwise specifies the left edge as the origin for the next offset.
 center
 Computes to 50% (left 50%) for the horizontal position if the horizontal position is not otherwise specified, or 50% (top 50%) for the vertical position if it is.
The resolved value of perspectiveorigin is the used value (i.e., percentages are resolved to absolute lengths).
13. The backfacevisibility Property
Name:  backfacevisibility 

Value:  visible  hidden 
Initial:  visible 
Applies to:  transformable elements 
Inherited:  no 
Percentages:  N/A 
Media:  visual 
Computed value:  Same as specified value. 
Canonical order:  per grammar 
Animatable:  no 
The visibility of an element with backfacevisibility: hidden is determined as follows:

Compute the element’s accumulated 3D transformation matrix.

If the component of the matrix in row 3, column 3 is negative, then the element should be hidden. Otherwise it is visible.
Backfacevisibility cannot be tested by only looking at m33. See Bug 23014.
Note: The reasoning for this definition is as follows. Assume elements are rectangles in the x–y plane with infinitesimal thickness. The front of the untransformed element has coordinates like (x, y, ε), and the back is (x, y, −ε), for some very small ε. We want to know if after the transformation, the front of the element is closer to the viewer than the back (higher zvalue) or further away. The zcoordinate of the front will be m_{13}x + m_{23}y + m_{33}ε + m_{43}, before accounting for perspective, and the back will be m_{13}x + m_{23}y − m_{33}ε + m_{43}. The first quantity is greater than the second if and only if m_{33} > 0. (If it equals zero, the front and back are equally close to the viewer. This probably means something like a 90degree rotation, which makes the element invisible anyway, so we don’t really care whether it vanishes.)
14. The SVG transform Attribute
The SVG 1.1 specification did not specify the attributes "transform", gradientTransform
or patternTransform
as presentation attributes [SVG11]. In order to improve the integration of SVG and HTML, this specification makes these SVG attributes presentation attributes and makes the transform property one that applies to transformable elements in the SVG namespace.
This specification will also introduce the new presentation attributes transformorigin, perspective, perspectiveorigin, transformstyle and backfacevisibility.
Values on new introduced presentation attributes get parsed following the syntax rules on SVG Data Types [SVG11].
14.1. SVG transform attribute specificity
Since the previously named SVG attributes become presentation attributes, their participation in the CSS cascade is determined by the specificity of presentation attributes in the SVG specification.
This example shows the combination of the transform style property and the transform presentation attribute.
<svg xmlns="http://www.w3.org/2000/svg"> <style> .container { transform: translate(100px, 100px); } </style> <g class="container" transform="translate(200 200)"> <rect width="100" height="100" fill="blue" /> </g> </svg>
Because of the participation to the CSS cascade, the transform style property overrides the transform presentation attribute. Therefore the container gets translated by 100px in both the horizontal and the vertical directions, instead of 200px.
14.2. Syntax of the SVG transform attribute
To provide backwards compatibility, the syntax of the transform presentation attribute differs from the syntax of the transform style property as shown in the example above. However, the syntax used for the transform style property can be used for a transform presentation attribute value. Authors are advised to follow the rules of CSS Values and Units Module [CSS3VAL]. Therefore an author should write ''transform="translate(200px, 200px)" instead of transform="translate (200 200)" because the second example with the spaces before the ('', the missing comma between the arguments and the values without the explicit unit notation would be valid for the attribute only.
14.2.1. Transform List
The value for the transform attribute consists of a transform list with zero or more transform functions using functional notation. If the transform list consists of more than one transform function, these functions are separated by optional whitespace, an optional comma (,) and optional whitespace. The transform list can have optional whitespace characters before and after the list.
14.2.2. Functional Notation
The syntax starts with the name of the function followed by a left parenthesis followed by optional whitespace followed by the argument(s) to the notation followed by optional whitespace followed by a right parenthesis. If a function takes more than one argument, the arguments are either separated by a comma (,) with optional whitespace characters before and after the comma, or by one or more whitespace characters.
Note: Unlike SVG 1.1, this specification does not allow optional whitespace between the name of the function and the left parenthesis.
14.2.3. SVG Data Types
Arguments on all new introduced presentation attributes consist of data types in the sense of CSS Values and Units Module [CSS3VAL]. The definitions of data types in CSS Values and Units Module are enhanced as follows:
14.2.3.1. The <length> type
A <length> can be a <number> without an unit identifier. In this case the number gets interpreted as "user unit". A user unit in the the initial coordinate system is equivalent to the parent environment’s notion of a pixel unit.
14.2.3.2. The <angle> type
An angle can be a <number> without an unit identifier. In this case the number gets interpreted as a value in degrees.
14.2.3.3. The <number> type
SVG supports scientific notations for numbers. Therefore a number gets parsed like described in SVG Basic data types for SVG attributes.
14.3. The SVG gradientTransform
and patternTransform
attributes
SVG specifies the attributes gradientTransform
and patternTransform
. This specification makes both attributes presentation attributes. Both attributes use the same syntax as the SVG transform attribute. This specification does not introduce corresponding CSS style properties. Both, the gradientTransform
and the patternTransform
attribute, are presentation attributes for the transform property.
14.4. SVG transform functions
For backwards compatibility with existing SVG content, this specification supports all transform functions defined by The ‘transform’ attribute in [SVG11]. Therefore the twodimensional transform function rotate(<angle>) is extended as follows:

rotate() = rotate( <angle> [, <length>, <length>]? )
 specifies a 2D rotation by the angle specified in the parameter about the origin of the element, as defined by the transformorigin property. If the optional translation values are specified, the transform origin is translated by that amount (using the current transformation matrix) for the duration of the rotate operation. For example rotate(90deg, 100px, 100px) would cause elements to appear rotated onequarter of a turn in the clockwise direction after a translation of the transformorigin of 100 pixel in the horizontal and vertical directions.
User agents are just required to support the two optional arguments for translation on elements in the SVG namespace.
14.5. SVG and 3D transform functions
This specification explicitly requires threedimensional transform functions to apply to the container elements: a
, g
, svg
, all graphics elements, all graphics referencing elements and the SVG foreignObject
element.
Threedimensional transform functions and the properties perspective, perspectiveorigin, transformstyle and backfacevisibility can not be used for the elements: clipPath
, linearGradient
, radialGradient
and pattern
. If a transform list includes a threedimensional transform function, the complete transform list must be ignored. The values of every previously named property must be ignored. Transformable elements that are contained by one of these elements can have threedimensional transform functions. The clipPath
, mask
, pattern
elements require the user agent to create a flattened representation of the descendant elements before they can be applied, and therefore override the behavior of transformstyle: preserve3d.
If the vectoreffect property is set to nonscalingstroke and an object is within a 3D rendering context the property has no affect on stroking the object.
14.6. User coordinate space
For the pattern
, linearGradient
, radialGradient
and clipPath
elements the transform, patternTransform
, gradientTransform
presentation attributes represents values in the current user coordinate system in place at the time when these elements are referenced (i.e., the user coordinate system for the element referencing the pattern
element via a fill or stroke property). Percentage values are relative to the reference box of the referencing element.
In particular the patternUnits
, gradientUnits
and maskUnits
attributes don’t affect the user coordinate system used for transformations [SVG11].
For all other transformable elements the transform presentation attribute represents values in the current user coordinate system of the parent. All percentage values of the transform presentation attribute are relative to the element’s reference box.
The transformorigin property on the pattern in the following example specifies a 50% translation of the origin in the horizontal and vertical dimension. The transform property specifies a translation as well, but in absolute lengths.
<svg xmlns="http://www.w3.org/2000/svg"> <style> pattern { transform: rotate(45deg); transformorigin: 50% 50%; } </style> <defs> <pattern id="pattern1"> <rect id="rect1" width="100" height="100" fill="blue" /> </pattern> </defs> <rect width="200" height="200" fill="url(#pattern1)" /> </svg>
An SVG pattern
element doesn’t have a bounding box. The reference box of the referencing rect
element is used instead to solve the relative values of the transformorigin property. Therefore the point of origin will get translated by 100 pixels temporarily to rotate the user space of the pattern
elements content.
14.7. SVG DOM interface for the transform attribute
The SVG specification defines the "SVGAnimatedTransformList" interface in the SVG DOM to provide access to the animated and the base value of the SVG transform, gradientTransform
and patternTransform
attributes. To ensure backwards compatibility, this API must still be supported by user agents.
The transform property contributes to the CSS cascade. According to SVG 1.1 user agents conceptually insert a new author style sheet for presentation attributes, which is the first in the author style sheet collection. baseVal
gives the author the possibility to access and modify the values of the SVG transform attribute. To provide the necessary backwards compatibility to the SVG DOM, baseVal
must reflect the values of this author style sheet. All modifications to SVG DOM objects of baseVal
must affect this author style sheet immediately.
animVal
represents the computed style of the transform property. Therefore it includes all applied CSS3 Transitions, CSS3 Animations or SVG Animations if any of those are underway. The computed style and SVG DOM objects of animVal
can not be modified.
The attribute "type" of 'SVGTransform" must return "SVG_TRANSFORM_UNKNOWN" for Transform Functions or unit types that are not supported by this interface. If a twodimensional transform function is not supported, the attribute "matrix" must return a 3x2 "SVGMatrix" with the corresponding values as described in the section Mathematical Description of Transform Functions.
15. SVG Animation
15.1. The animate
and set
element
With this specification, the animate
element and the set
element can animate the data type <transformlist>.
The animation effect is postmultiplied to the underlying value for additive animate
animations (see below) instead of added to the underlying value, due to the specific behavior of <transformlist> animations.
Fromto, fromby and by animations are defined in SMIL to be equivalent to a corresponding values animation. However, to animations are a mixture of additive and nonadditive behavior [SMIL3].
To animations on animate
provide specific functionality to get a smooth change from the underlying value to the to attribute value, which conflicts mathematically with the requirement for additive transform animations to be postmultiplied. As a consequence, the behavior of to animations for animate
is undefined. Authors are suggested to use fromto, fromby, by or values animations to achieve any desired transform animation.
The value "paced" is undefined for the attribute calcMode
on animate
for animations of the data type <transformlist>. If specified, UAs may choose the value "linear" instead. Future versions of this specification may define how paced animations can be performed on <transformlist>.
Note: The following paragraphs extend Elements, attributes and properties that can be animated [SVG11].
The introduce presentation attributes transform, transformorigin, perspective, perspectiveorigin, transformstyle and backfacevisibility are animatable. transformstyle and backfacevisibility are nonadditive.
With this specification the SVG basic data type <transformlist> is equivalent to a list of <transformfunction>s. <transformlist> is animatable and additive. The data type can be animated using the SVG animate
element and the SVG set
element. SVG animations must run the same animation steps as described in section Transitions and Animations between Transform Values.
Data type  Additive?  animate
 set
 animateColor
 animateTransform
 Notes 

<transformlist>  yes  yes  yes  no  yes  Additive for animateTransform means that a transformation is postmultiplied to the base set of
transformations.

15.2. Neutral element for addition
Some animations require a neutral element for addition. For transform functions this is a scalar or a list of scalars of 0. Examples of neutral elements for transform functions are translate(0), translate3d(0, 0, 0), translateX(0), translateY(0), translateZ(0), scale(0), scaleX(0), scaleY(0), scaleZ(0), rotate(0), rotate3d(vx, vy, vz, 0) (where v is a context dependent vector), rotateX(0), rotateY(0), rotateZ(0), skew(0, 0), skewX(0), skewY(0), matrix(0, 0, 0, 0, 0, 0), matrix3d(0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) and perspective(0).
Note: Animations to or from the neutral element of additions matrix(), matrix3d() and perspective() fall back to discrete animations (See §21 Interpolation of Matrices).
A by animation with a by value v_{b} is equivalent to the same animation with a values list with 2 values, the neutral element for addition for the domain of the target attribute (denoted 0) and v_{b}, and ''additive="sum"''. [SMIL3]
<rect width="100" height="100"> <animateTransform attributeName="transform" attributeType="XML" type="scale" by="1" dur="5s" fill="freeze"/> </rect>
The neutral element for addition when performing a by animation with ''type="scale" is the value 0. Thus, performing the animation of the example above causes the rectangle to be invisible at time 0s (since the animated transform list value is scale(0)), and be scaled back to its original size at time 5s (since the animated transform list value is scale(1)'').
15.3. The SVG 'attributeName' attribute
SVG 1.1 Animation defines the "attributeName" attribute to specify the name of the target attribute. For the presentation attributes gradientTransform
and patternTransform
it will also be possible to use the value transform. The same transform property will get animated.
In this example the gradient transformation of the linear gradient gets animated.
<linearGradient gradientTransform="scale(2)"><animate attributeName="gradientTransform" from="scale(2)" to="scale(4)" dur="3s" additive="sum"/> <animate attributeName="transform" from="translate(0, 0)" to="translate(100px, 100px)" dur="3s" additive="sum"/> </linearGradient>
The linearGradient
element specifies the gradientTransform
presentation attribute. The two animate
elements address the target attribute gradientTransform
and transform. Even so all animations apply to the same gradient transformation by taking the value of the gradientTransform
presentation attribute, applying the scaling of the first animation and applying the translation of the second animation one after the other.
16. The Transform Functions
The value of the transform property is a list of <transformfunction>. The set of allowed transform functions is given below. Wherever <angle> is used in this specification, a <number> that is equal to zero is also allowed, which is treated the same as an angle of zero degrees. A percentage for horizontal translations is relative to the width of the reference box. A percentage for vertical translations is relative to the height of the reference box.
16.1. 2D Transform Functions
 matrix() = matrix( <number> [, <number> ]{5,5} )
 specifies a 2D transformation in the form of a transformation matrix of the six values af.
 translate() = translate( <lengthpercentage> [, <lengthpercentage> ]? )
 specifies a 2D translation by the vector [tx, ty], where tx is the first translationvalue parameter and ty is the optional second translationvalue parameter. If <ty> is not provided, ty has zero as a value.
 translateX() = translateX( <lengthpercentage> )
 specifies a translation by the given amount in the X direction.
 translateY() = translateY( <lengthpercentage> )
 specifies a translation by the given amount in the Y direction.
 scale() = scale( <number> [, <number> ]? )
 specifies a 2D scale operation by the [sx,sy] scaling vector described by the 2 parameters. If the second parameter is not provided, it takes a value equal to the first. For example, scale(1, 1) would leave an element unchanged, while scale(2, 2) would cause it to appear twice as long in both the X and Y axes, or four times its typical geometric size.
 scaleX() = scaleX( <number> )
 specifies a 2D scale operation using the [sx,1] scaling vector, where sx is given as the parameter.
 scaleY() = scaleY( <number> )
 specifies a 2D scale operation using the [1,sy] scaling vector, where sy is given as the parameter.
 rotate() = rotate( <angle> )
 specifies a 2D rotation by the angle specified in the parameter about the origin of the element, as defined by the transformorigin property. For example, rotate(90deg) would cause elements to appear rotated onequarter of a turn in the clockwise direction.
 skew() = skew( <angle> [, <angle> ]? )

specifies a 2D skew by [ax,ay] for X and Y. If the second parameter is not provided, it has a zero value.
Note that the behavior of skew() is different from multiplying skewX() with skewY(). Implementations must support this function for compatibility with legacy content.
 skewX() = skewX( <angle> )
 specifies a 2D skew transformation along the X axis by the given angle.
 skewY() = skewY( <angle> )
 specifies a 2D skew transformation along the Y axis by the given angle.
16.2. 3D Transform Functions
 matrix3d() = matrix3d( <number> [, <number> ]{15,15} )
 specifies a 3D transformation as a 4x4 homogeneous matrix of 16 values in columnmajor order.
 translate3d() = translate3d( <lengthpercentage> , <lengthpercentage> , <length> )
 specifies a 3D translation by the vector [tx,ty,tz], with tx, ty and tz being the first, second and third translationvalue parameters respectively.
 translateZ() = translateZ( <length> )
 specifies a 3D translation by the vector [0,0,tz] with the given amount in the Z direction.
 scale3d() = scale3d( <number> , <number>, <number> )
 specifies a 3D scale operation by the [sx,sy,sz] scaling vector described by the 3 parameters.
 scaleZ() = scaleZ( <number> )
 specifies a 3D scale operation using the [1,1,sz] scaling vector, where sz is given as the parameter.
 rotate3d() = rotate3d( <number> , <number> , <number> , <angle> )

specifies a 3D rotation by the angle specified in last parameter about the [x,y,z] direction vector described by the first three parameters. A direction vector that cannot be normalized, such as [0,0,0], will cause the rotation to not be applied.
Note that the rotation is clockwise as one looks from the end of the vector toward the origin.
 rotateX() = rotateX( <angle> )
 same as rotate3d(1, 0, 0, <angle>).
 rotateY() = rotateY( <angle> )
 same as rotate3d(0, 1, 0, <angle>).
 rotateZ() = rotateZ( <angle> )
 same as rotate3d(0, 0, 1, <angle>), which is also the same as rotate(<angle>).
 perspective() = perspective( <length> )
 specifies a perspective projection matrix. This matrix scales points in X and Y based on their Z value, scaling points with positive Z values away from the origin, and those with negative Z values towards the origin. Points on the z=0 plane are unchanged. The parameter represents the distance of the z=0 plane from the viewer. Lower values give a more flattened pyramid and therefore a more pronounced perspective effect. For example, a value of 1000px gives a moderate amount of foreshortening and a value of 200px gives an extreme amount. The value for depth must be greater than zero, otherwise the function is invalid.
17. The Transform Function Lists
If a list of <transformfunction> is provided, then the net effect is as if each transform function had been specified separately in the order provided. For example,
<div style="transform:translate(10px,20px) scale(2) rotate(45deg) translate(5px,10px)"/>
is functionally equivalent to:
<div style="transform:translate(10px,20px)"> <div style="transform:scale(2)"> <div style="transform:rotate(45deg)"> <div style="transform:translate(5px,10px)"> </div> </div> </div> </div>
That is, in the absence of other styling that affects position and dimensions, a nested set of transforms is equivalent to a single list of transform functions, applied from the outside in. The resulting transform is the matrix multiplication of the list of transforms.
If a transform function causes the current transformation matrix (CTM) of an object to be noninvertible, the object and its content do not get displayed.
The object in the following example gets scaled by 0.
<style> .box { transform: scale(0); } </style> <div class="box"> Not visible </div>
The scaling causes a noninvertible CTM for the coordinate space of the div box. Therefore neither the div box, nor the text in it get displayed.
18. Interpolation of Transforms
When animating or transitioning transforms, the transform function lists must be interpolated. For interpolation between one transform fromtransform and a second transforms totransform, the rules described below are applied.

If both the from and totransform are none:
 There is no interpolation necessary. The computed value stays none.

If one of the from or totransforms is none.
 The value none is replaced by an equivalent identity transform function list for the corresponding transform function list. Both transform function lists get interpolated following the next rule.
For example, if fromtransform is scale(2) and totransform is none then the value scale(1) will be used for totransform and animation will proceed using the next rule. Similarly, if fromtransform is none and totransform is scale(2) rotate(50deg) then the animation will execute as if fromtransform is scale(1) rotate(0).

If from and totransform have the same number of transform functions, each transform function pair has either the same name, or is a derivative of the same primitive.
 Interpolate each transform function pair as described in Interpolation of transform functions. The computed value is the resulting transform function list.

In all other cases:
 The transform functions of each transform function list on the from and totransform get post multiplied and converted into 4x4 matrices. Each of the matrices gets interpolated following the instructions in Interpolation of matrices. The computed value is the transform function matrix if both initial matrices can be represented by a correlating 3x2 matrix and matrix3d otherwise.
In some cases, an animation might cause a transformation matrix to be singular or noninvertible. For example, an animation in which scale moves from 1 to 1. At the time when the matrix is in such a state, the transformed element is not rendered.
19. Transform function primitives and derivatives
Some transform functions can be represented by more generic transform functions. These transform functions are called derived transform functions, the generic transform functions primitives. Primitives for twodimensional and threedimensional transform functions are listed below.
Twodimensional primitives with derived transform functions are:
 translate()
 for translateX(), translateY() and translate().
 rotate() with three arguments
 for rotate() with one or three arguments if rotate with three arguments is supported.
 scale()
 for scaleX(), scaleY() and scale().
Threedimensional primitives with derived transform functions are:
 translate3d()
 for translateX(), translateY(), translateZ() and translate().
 scale3d()
 for scaleX(), scaleY(), scaleZ() and scale().
 rotate3d()
 for rotate(), rotateX(), rotateY() and rotateZ().
For derived transform functions that have a twodimensional primitive and a threedimensional primitive, the context decides about the used primitive. See Interpolation of primitives and derived transform functions.
20. Interpolation of primitives and derived transform functions
Two transform functions with the same name and the same number of arguments are interpolated numerically without a former conversion. The calculated value will be of the same transform function type with the same number of arguments. Special rules apply to rotate3d(), matrix(), matrix3d() and perspective().
The two transform functions translate(0) and translate(100px) are of the same type, have the same number of arguments and therefore can get interpolated numerically. translateX(100px) is not of the same type and translate(100px, 0) does not have the same number of arguments, therefore these transform functions can not get interpolated without a former conversion step.
Two different types of transform functions that share the same primitive, or transform functions of the same type with different number of arguments can be interpolated. Both transform functions need a former conversion to the common primitive first and get interpolated numerically afterwards. The computed value will be the primitive with the resulting interpolated arguments.
The following example describes a transition from translateX(100px) to translateY(100px) in 3 seconds on hovering over the div box. Both transform functions derive from the same primitive translate() and therefore can be interpolated.
div { transform: translateX(100px); } div:hover { transform: translateY(100px); transition: transform 3s; }
For the time of the transition both transform functions get transformed to the common primitive. translateX(100px) gets converted to translate(100px, 0) and translateY(100px) gets converted to translate(0, 100px). Both transform functions can then get interpolated numerically.
If both transform functions share a primitive in the twodimensional space, both transform functions get converted to the twodimensional primitive. If one or both transform functions are threedimensional transform functions, the common threedimensional primitive is used.
In this example a twodimensional transform function gets animated to a threedimensional transform function. The common primitive is translate3d().
div { transform: translateX(100px); } div:hover { transform: translateZ(100px); transition: transform 3s; }
First translateX(100px) gets converted to translate3d(100px, 0, 0) and translateZ(100px) to translate3d(0, 0, 100px) respectively. Then both converted transform functions get interpolated numerically.
The transform functions matrix(), matrix3d() and perspective() get converted into 4x4 matrices first and interpolated as defined in section Interpolation of Matrices afterwards.
For interpolations with the primitive rotate3d(), the direction vectors of the transform functions get normalized first. If the normalized vectors are equal, the rotation angle gets interpolated numerically. Otherwise the transform functions get converted into 4x4 matrices first and interpolated as defined in section Interpolation of Matrices afterwards.
21. Interpolation of Matrices
When interpolating between two matrices, each matrix is decomposed into the corresponding translation, rotation, scale, skew and (for a 3D matrix) perspective values. Each corresponding component of the decomposed matrices gets interpolated numerically and recomposed back to a matrix in a final step.
In the following example the element gets translated by 100 pixel in both the X and Y directions and rotated by 1170° on hovering. The initial transformation is 45°. With the usage of transition, an author might expect a animated, clockwise rotation by three and a quarter turns (1170°).
<style> div { transform: rotate(45deg); } div:hover { transform: translate(100px, 100px) rotate(1215deg); transition: transform 3s; } </style> <div></div>
The number of transform functions on the source transform rotate(45deg) differs from the number of transform functions on the destination transform translate(100px, 100px) rotate(1125deg). According to the last rule of Interpolation of Transforms, both transforms must be interpolated by matrix interpolation. With converting the transformation functions to matrices, the information about the three turns gets lost and the element gets rotated by just a quarter turn (90°).
To achieve the three and a quarter turns for the example above, source and destination transforms must fulfill the third rule of Interpolation of Transforms. Source transform could look like translate(0, 0) rotate(45deg) for a linear interpolation of the transform functions.
In the following we differ between the interpolation of two 2D matrices and the interpolation of two matrices where at least one matrix is not a 2D matrix.
If one of the matrices for interpolation is noninvertible, the used animation function must fallback to a discrete animation according to the rules of the respective animation specification.
21.1. Supporting functions
The pseudo code in the next subsections make use of the following supporting functions:
Supporting functions (point is a 3 component vector, matrix is a 4x4 matrix, vector is a 4 component vector): double determinant(matrix) returns the 4x4 determinant of the matrix matrix inverse(matrix) returns the inverse of the passed matrix matrix transpose(matrix) returns the transpose of the passed matrix point multVecMatrix(point, matrix) multiplies the passed point by the passed matrix and returns the transformed point double length(point) returns the length of the passed vector point normalize(point) normalizes the length of the passed point to 1 double dot(point, point) returns the dot product of the passed points double sqrt(double) returns the root square of passed value double max(double y, double x) returns the bigger value of the two passed values double dot(vector, vector) returns the dot product of the passed vectors vector multVector(vector, vector) multiplies the passed vectors double sqrt(double) returns the root square of passed value double max(double y, double x) returns the bigger value of the two passed values double min(double y, double x) returns the smaller value of the two passed values double cos(double) returns the cosines of passed value double sin(double) returns the sine of passed value double acos(double) returns the inverse cosine of passed value double abs(double) returns the absolute value of the passed value double rad2deg(double) transforms a value in radian to degree and returns it double deg2rad(double) transforms a value in degree to radian and returns it Decomposition also makes use of the following function: point combine(point a, point b, double ascl, double bscl) result[0] = (ascl * a[0]) + (bscl * b[0]) result[1] = (ascl * a[1]) + (bscl * b[1]) result[2] = (ascl * a[2]) + (bscl * b[2]) return result
21.2. Interpolation of 2D matrices
21.2.1. Decomposing a 2D matrix
The pseudo code below is based upon the "unmatrix" method in "Graphics Gems II, edited by Jim Arvo".
Input: matrix ; a 4x4 matrix Output: translation ; a 2 component vector scale ; a 2 component vector angle ; rotation m11 ; 1,1 coordinate of 2x2 matrix m12 ; 1,2 coordinate of 2x2 matrix m21 ; 2,1 coordinate of 2x2 matrix m22 ; 2,2 coordinate of 2x2 matrix Returns false if the matrix cannot be decomposed, true if it can double row0x = matrix[0][0] double row0y = matrix[0][1] double row1x = matrix[1][0] double row1y = matrix[1][1] translate[0] = matrix[3][0] translate[1] = matrix[3][1] scale[0] = sqrt(row0x * row0x + row0y * row0y) scale[1] = sqrt(row1x * row1x + row1y * row1y) // If determinant is negative, one axis was flipped. double determinant = row0x * row1y  row0y * row1x if (determinant < 0) // Flip axis with minimum unit vector dot product. if (row0x < row1y) scale[0] = scale[0] else scale[1] = scale[1] // Renormalize matrix to remove scale. if (scale[0]) row0x *= 1 / scale[0] row0y *= 1 / scale[0] if (scale[1]) row1x *= 1 / scale[1] row1y *= 1 / scale[1] // Compute rotation and renormalize matrix. angle = atan2(row0y, row0x); if (angle) // Rotate(angle) = [cos(angle), sin(angle), sin(angle), cos(angle)] // = [row0x, row0y, row0y, row0x] // Thanks to the normalization above. double sn = row0y double cs = row0x double m11 = row0x double m12 = row0y double m21 = row1x double m22 = row1y row0x = cs * m11 + sn * m21 row0y = cs * m12 + sn * m22 row1x = sn * m11 + cs * m21 row1y = sn * m12 + cs * m22 m11 = row0x m12 = row0y m21 = row1x m22 = row1y // Convert into degrees because our rotation functions expect it. angle = rad2deg(angle) return true
21.2.2. Interpolation of decomposed 2D matrix values
Before two decomposed 2D matrix values can be interpolated, the following
Input: translationA ; a 2 component vector scaleA ; a 2 component vector angleA ; rotation m11A ; 1,1 coordinate of 2x2 matrix m12A ; 1,2 coordinate of 2x2 matrix m21A ; 2,1 coordinate of 2x2 matrix m22A ; 2,2 coordinate of 2x2 matrix translationB ; a 2 component vector scaleB ; a 2 component vector angleB ; rotation m11B ; 1,1 coordinate of 2x2 matrix m12B ; 1,2 coordinate of 2x2 matrix m21B ; 2,1 coordinate of 2x2 matrix m22B ; 2,2 coordinate of 2x2 matrix // If xaxis of one is flipped, and yaxis of the other, // convert to an unflipped rotation. if ((scaleA[0] < 0 && scaleB[1] < 0)  (scaleA[1] < 0 && scaleB[0] < 0)) scaleA[0] = scaleA[0] scaleA[1] = scaleA[1] angleA += angleA < 0 ? 180 : 180 // Don’t rotate the long way around. if (!angleA) angleA = 360 if (!angleB) angleB = 360 if (abs(angleA  angleB) > 180) if (angleA > angleB) angleA = 360 else angleB = 360
Afterwards, each component of the decomposed values translation, scale, angle, m11 to m22 of the source matrix get linearly interpolated with each corresponding component of the destination matrix.
21.2.3. Recomposing to a 2D matrix
After interpolation, the resulting values are used to transform the elements user space. One way to use these values is to recompose them into a 4x4 matrix. This can be done following the pseudo code below:
Input: translation ; a 2 component vector scale ; a 2 component vector angle ; rotation m11 ; 1,1 coordinate of 2x2 matrix m12 ; 1,2 coordinate of 2x2 matrix m21 ; 2,1 coordinate of 2x2 matrix m22 ; 2,2 coordinate of 2x2 matrix Output: matrix ; a 4x4 matrix initialized to identity matrix matrix[0][0] = m11 matrix[0][1] = m12 matrix[1][0] = m21 matrix[1][1] = m22 // Translate matrix. matrix[3][0] = translate[0] * m11 + translate[1] * m21 matrix[3][1] = translate[0] * m12 + translate[1] * m22 // Rotate matrix. angle = deg2rad(angle); double cosAngle = cos(angle); double sinAngle = sin(angle); // New temporary, identity initialized, 4x4 matrix rotateMatrix rotateMatrix[0][0] = cosAngle rotateMatrix[0][1] = sinAngle rotateMatrix[1][0] = sinAngle rotateMatrix[1][1] = cosAngle matrix = multiply(matrix, rotateMatrix) // Scale matrix. matrix[0][0] *= scale[0] matrix[0][1] *= scale[0] matrix[1][0] *= scale[1] matrix[1][1] *= scale[1]
21.3. Interpolation of 3D matrices
21.3.1. Decomposing a 3D matrix
The pseudo code below is based upon the "unmatrix" method in "Graphics Gems II, edited by Jim Arvo", but modified to use Quaternions instead of Euler angles to avoid the problem of Gimbal Locks.
The following pseudocode works on a 4x4 homogeneous matrix:
Input: matrix ; a 4x4 matrix Output: translation ; a 3 component vector scale ; a 3 component vector skew ; skew factors XY,XZ,YZ represented as a 3 component vector perspective ; a 4 component vector quaternion ; a 4 component vector Returns false if the matrix cannot be decomposed, true if it can // Normalize the matrix. if (matrix[3][3] == 0) return false for (i = 0; i < 4; i++) for (j = 0; j < 4; j++) matrix[i][j] /= matrix[3][3] // perspectiveMatrix is used to solve for perspective, but it also provides // an easy way to test for singularity of the upper 3x3 component. perspectiveMatrix = matrix for (i = 0; i < 3; i++) perspectiveMatrix[i][3] = 0 perspectiveMatrix[3][3] = 1 if (determinant(perspectiveMatrix) == 0) return false // First, isolate perspective. if (matrix[0][3] != 0  matrix[1][3] != 0  matrix[2][3] != 0) // rightHandSide is the right hand side of the equation. rightHandSide[0] = matrix[0][3] rightHandSide[1] = matrix[1][3] rightHandSide[2] = matrix[2][3] rightHandSide[3] = matrix[3][3] // Solve the equation by inverting perspectiveMatrix and multiplying // rightHandSide by the inverse. inversePerspectiveMatrix = inverse(perspectiveMatrix) transposedInversePerspectiveMatrix = transposeMatrix4(inversePerspectiveMatrix) perspective = multVecMatrix(rightHandSide, transposedInversePerspectiveMatrix) else // No perspective. perspective[0] = perspective[1] = perspective[2] = 0 perspective[3] = 1 // Next take care of translation for (i = 0; i < 3; i++) translate[i] = matrix[3][i] // Now get scale and shear. 'row' is a 3 element array of 3 component vectors for (i = 0; i < 3; i++) row[i][0] = matrix[i][0] row[i][1] = matrix[i][1] row[i][2] = matrix[i][2] // Compute X scale factor and normalize first row. scale[0] = length(row[0]) row[0] = normalize(row[0]) // Compute XY shear factor and make 2nd row orthogonal to 1st. skew[0] = dot(row[0], row[1]) row[1] = combine(row[1], row[0], 1.0, skew[0]) // Now, compute Y scale and normalize 2nd row. scale[1] = length(row[1]) row[1] = normalize(row[1]) skew[0] /= scale[1]; // Compute XZ and YZ shears, orthogonalize 3rd row skew[1] = dot(row[0], row[2]) row[2] = combine(row[2], row[0], 1.0, skew[1]) skew[2] = dot(row[1], row[2]) row[2] = combine(row[2], row[1], 1.0, skew[2]) // Next, get Z scale and normalize 3rd row. scale[2] = length(row[2]) row[2] = normalize(row[2]) skew[1] /= scale[2] skew[2] /= scale[2] // At this point, the matrix (in rows) is orthonormal. // Check for a coordinate system flip. If the determinant // is 1, then negate the matrix and the scaling factors. pdum3 = cross(row[1], row[2]) if (dot(row[0], pdum3) < 0) for (i = 0; i < 3; i++) scale[i] *= 1; row[i][0] *= 1 row[i][1] *= 1 row[i][2] *= 1 // Now, get the rotations out quaternion[0] = 0.5 * sqrt(max(1 + row[0][0]  row[1][1]  row[2][2], 0)) quaternion[1] = 0.5 * sqrt(max(1  row[0][0] + row[1][1]  row[2][2], 0)) quaternion[2] = 0.5 * sqrt(max(1  row[0][0]  row[1][1] + row[2][2], 0)) quaternion[3] = 0.5 * sqrt(max(1 + row[0][0] + row[1][1] + row[2][2], 0)) if (row[2][1] > row[1][2]) quaternion[0] = quaternion[0] if (row[0][2] > row[2][0]) quaternion[1] = quaternion[1] if (row[1][0] > row[0][1]) quaternion[2] = quaternion[2] return true
21.3.2. Interpolation of decomposed 3D matrix values
Each component of the decomposed values translation, scale, skew and perspective of the source matrix get linearly interpolated with each corresponding component of the destination matrix.
Note: For instance, translate[0]
of the source matrix and translate[0]
of the destination matrix are interpolated numerically, and the result is used to set the translation of the animating element.
Quaternions of the decomposed source matrix are interpolated with quaternions of the decomposed destination matrix using the spherical linear interpolation (Slerp) as described by the pseudo code below:
Input: quaternionA ; a 4 component vector quaternionB ; a 4 component vector t ; interpolation parameter with 0 <= t <= 1 Output: quaternionDst ; a 4 component vector product = dot(quaternionA, quaternionB) // Clamp product to 1.0 <= product <= 1.0 product = max(product, 1.0) product = min(product, 1.0) if (product == 1.0) quaternionDst = quaternionA return theta = acos(dot) w = sin(t * theta) * 1 / sqrt(1  product * product) for (i = 0; i < 4; i++) quaternionA[i] *= cos(t * theta)  product * w quaternionB[i] *= w quaternionDst[i] = quaternionA[i] + quaternionB[i] return
21.3.3. Recomposing to a 3D matrix
After interpolation, the resulting values are used to transform the elements user space. One way to use these values is to recompose them into a 4x4 matrix. This can be done following the pseudo code below:
Input: translation ; a 3 component vector scale ; a 3 component vector skew ; skew factors XY,XZ,YZ represented as a 3 component vector perspective ; a 4 component vector quaternion ; a 4 component vector Output: matrix ; a 4x4 matrix Supporting functions (matrix is a 4x4 matrix): matrix multiply(matrix a, matrix b) returns the 4x4 matrix product of a * b // apply perspective for (i = 0; i < 4; i++) matrix[i][3] = perspective[i] // apply translation for (i = 0; i < 3; i++) for (j = 0; j < 3; j++) matrix[3][i] += translation[j] * matrix[j][i] // apply rotation x = quaternion[0] y = quaternion[1] z = quaternion[2] w = quaternion[3] // Construct a composite rotation matrix from the quaternion values // rotationMatrix is a identity 4x4 matrix initially rotationMatrix[0][0] = 1  2 * (y * y + z * z) rotationMatrix[0][1] = 2 * (x * y  z * w) rotationMatrix[0][2] = 2 * (x * z + y * w) rotationMatrix[1][0] = 2 * (x * y + z * w) rotationMatrix[1][1] = 1  2 * (x * x + z * z) rotationMatrix[1][2] = 2 * (y * z  x * w) rotationMatrix[2][0] = 2 * (x * z  y * w) rotationMatrix[2][1] = 2 * (y * z + x * w) rotationMatrix[2][2] = 1  2 * (x * x + y * y) matrix = multiply(matrix, rotationMatrix) // apply skew // temp is a identity 4x4 matrix initially if (skew[2]) temp[2][1] = skew[2] matrix = multiply(matrix, temp) if (skew[1]) temp[2][1] = 0 temp[2][0] = skew[1] matrix = multiply(matrix, temp) if (skew[0]) temp[2][0] = 0 temp[1][0] = skew[0] matrix = multiply(matrix, temp) // apply scale for (i = 0; i < 3; i++) for (j = 0; j < 3; j++) matrix[i][j] *= scale[i] return
22. Mathematical Description of Transform Functions
Mathematically, all transform functions can be represented as 4x4 transformation matrices of the following form:
One translation unit on a matrix is equivalent to 1 pixel in the local coordinate system of the element.

A 2D 3x2 matrix with six parameters a, b, c, d, e and f is equivalent to the matrix:

A 2D translation with the parameters tx and ty is equivalent to a 3D translation where tz has zero as a value.

A 2D scaling with the parameters sx and sy is equivalent to a 3D scale where sz has one as a value.

A 2D rotation with the parameter alpha is equivalent to a 3D rotation with vector [0,0,1] and parameter alpha.

A 2D skew like transformation with the parameters alpha and beta is equivalent to the matrix:

A 2D skew transformation along the X axis with the parameter alpha is equivalent to the matrix:

A 2D skew transformation along the Y axis with the parameter beta is equivalent to the matrix:

A 3D translation with the parameters tx, ty and tz is equivalent to the matrix:

A 3D scaling with the parameters sx, sy and sz is equivalent to the matrix:

A 3D rotation with the vector [x,y,z] and the parameter alpha is equivalent to the matrix:
where:

A perspective projection matrix with the parameter d is equivalent to the matrix:
Changes since last publication
Acknowledgments
The editors would like to thank Robert O’Callahan, Cameron McCormack, Tab Atkins, Gérard Talbot, L. David Baron, Rik Cabanier, Brian Birtles, Benoit Jacob, Ken Shoemake, Alan Gresley, Maciej Stochowiak, Sylvain Galineau, Rafal Pietrak, Shane Stephens, Matt Rakow, XiangHongAi, Fabio M. Costa, Nivesh Rajbhandari, Rebecca Hauck, Gregg Tavares, Graham Clift, Erik Dahlström, Alexander Zolotov and Boris Zbarsky for their careful reviews, comments, and corrections.