Apple's WebKit team on November 16, 2026 published a developer preview of spatial CSS, a proposed set of style rules and one JavaScript method that let a web page group 3D objects into a shared space, snap them together, light them, let people spin them around and, on Apple's headset, lift the whole arrangement out of the browser window and into the room. The preview runs only in Safari on visionOS 27.3, sits behind a feature flag called CSS Portals, and arrives alongside an early draft of the specification that would govern it.

In Short

Apple's browser engine team released a test version of "spatial CSS," a way for websites on Apple's headset to arrange 3D objects, light them and let people rotate them or place them in the room. It matters to publishers and creative teams because the controls are ordinary CSS and a single JavaScript call, the same tools already used to build web pages and HTML5 ads, while the 3D model element underneath already works in Safari 27 on every Apple platform. Nothing changes for live sites yet: the features are off by default, the specification is a first draft, and the post says nothing about ads, iframes or Apple devices other than the headset.

What the preview contains

The blog post, titled "Introducing spatial CSS: A developer preview" and written by Brandel Zachernuk, opens with its own summary. "Safari on visionOS 27.3 comes with an important update: a limited feature preview of the proposed spatial CSS API, with an initial focus on working with 3D objects through the element," according to the post. It describes the package modestly. "While it's a big conceptual jump, spatial CSS itself is made of a lot of small tweaks to existing syntax."

Six features make up the preview. Each borrows a name or a pattern from CSS that web developers already use for flat pages.

Feature Syntax as published What it does, according to WebKit Existing feature it extends
Portal spatial: portal Turns a container element such as <div> or <figure> into a shared 3D space for every child element inside it None named
Transform transform on models inside a portal Moves, rotates and scales each model independently, as a true 3D transform The DOMMatrix class behind 2D and pseudo-3D transforms
Anchoring anchor-name, position-anchor, position-context: anchor Snaps a model to a named reference point stored inside another model's 3D file CSS anchor positioning for 2D layouts
Environment map @environment-map rule with name, format and src, applied with environment-map Defines reusable lighting from 360º HDR images and shares it across elements An HTML attribute on the <model> element
Orbit portal-action: orbit Lets people rotate the scene in place to look around it The stagemode attribute on <model>
Volumetric scene requestVolumetricScene() (JavaScript) Moves the portal's contents out of the browser window into the viewer's space as a "Connected Volumetric Scene" that the page can keep updating None named

How the preview works, step by step

According to WebKit, access to the preview and the construction of its demonstration scene follow a fixed sequence. The post demonstrates each step with a case study built from "a simple set of children's blocks": a blue board with shaped holes, an octagon and a star.

  1. Switch on the flag. On the headset itself, or in the visionOS Simulator, the path is Settings > Apps > Safari > Advanced > Feature flags > CSS Portals.
  2. Get the simulator. The visionOS Simulator is installed through Xcode, which the post notes is distributed through the Mac App Store. Apple's developer documentation covers installing additional simulators.
  3. Declare a portal. A container element receives spatial:portal. In the sample, a <div class="world"> holds three <model> elements, each pointing at a USDZ file: board.usdz, octagon.usdz and star.usdz.
  4. Position the models. Each model is moved with an ordinary transform. The sample pushes the octagon to translateX(-50cm) and the star to translateX(50cm), setting the blocks either side of the board with centimetres as the unit.
  5. Anchor one model to another. The board receives anchor-name:--board. The octagon receives position-anchor:--board#octagon-position and position-context:anchor, which seats it in the matching hole. The star is hidden with display:none in this example.
  6. Light the scene. An @environment-map rule defines a lighting setup named "spooky" with format: equirectangular and src: url("night.hdr"). The class .world.spooky then applies it with environment-map: "spooky".
  7. Allow rotation. portal-action:orbit lets the viewer turn the scene in place.
  8. Launch into the room. A click handler finds the .world element and calls world.requestVolumetricScene(). The post specifies that the request must come from a user action.

The post links to a live version, the WebKids puzzle playground, hosted on webkit.org. One detail for anyone reproducing the first sample from the post: its style block closes with a misspelled </stye> tag.

Ordinary CSS for an extra dimension

Why route 3D through style sheets at all? WebKit's argument rests on what CSS already does for flat pages. "By routing functionality for spatial content through declarative CSS, a page can use media queries targeting aspect ratio, color theme and reduced motion to adapt spatially as well," according to the post. The same setting that dims a page for a viewer in dark mode, or calms animation for someone who has asked the system for reduced motion, can in principle reshape a 3D arrangement as well.

The second argument is about motion. "Even better, the numerical parameters can be animated and transitioned in the same way that any other value can be changed on the page." Positions, rotations and anchor points become values that CSS transitions can move between, rather than state that a script must track frame by frame.

The post also frames the work as larger than one headset. "And spatial content should not just be designed for spatial devices. The last few years have seen a dramatic rise in the number of websites showing 3D content - on phones, tablets and computers as well as headsets," it states. "Spatial web standards should support designing for browsers wherever they run." That ambition sits next to a plain limitation: the <model> element itself is, in the post's words, "now available in Safari 27 on all platforms," but the spatial CSS layer on top of it is confined to visionOS for now.

Feature by feature

Portals and transforms

The portal is the foundation. Any element that can contain others can become one, and its children then share a single 3D space. "This preview focuses on model elements, but the specification is written so that this approach should work for all content," according to WebKit. Text, images and other page elements are therefore within the stated scope of the design, though not of this preview.

Once models sit inside a portal, the familiar transform property gains a third dimension. "This takes the same DOMMatrix class that creates 2D and pseudo-3D transforms in other contexts, but can now act as a true 3D transform to objects inside the portal context," the post explains. Each block in the demonstration moves and rotates independently. WebKit sets this against what a single model file can already do on its own: "While a model's animation timeline could manage single sequence of action, this adds the degrees of freedom required for more sophisticated interaction or configuration."

Anchoring and the problem of void elements

Fitting objects together turned out to need a workaround. The <model> tag is a void element, which means one model cannot be nested inside another the way ordinary page elements nest. WebKit's answer reuses an existing CSS idea. "Instead, we're borrowing from the CSS concept of position-anchor and adding a way to align and orient objects according to their anchors. position-context: anchor is the way to make it work."

The anchors themselves live inside the 3D files. The board in the example was built in Blender and contains, besides its visible shape, reference positions that 3D editors often call "null objects" or "empties," marking where each block should slot in. A screenshot in the post shows the scene open in a beta of Blender 5.3.0. The CSS then refers to those embedded points by name rather than to coordinates copied out of the editor. "These anchor points can be animated, too, making it easier to compose elements even when they're moving around," according to WebKit.

For anyone who has assembled flat-pack furniture, the analogy in the post will be familiar: the holes are drilled at the factory, and the instructions simply say which peg goes where.

Environment maps

Lighting gets its own at-rule. "An environment map is the lighting that is reflected off of an object - think of it as the room that an object appears within," the post explains. WebKit first exposed environment maps as an HTML attribute on <model>, because that was the only element able to use one. With portals able to hold several elements, the setting moves into CSS, modelled on the @keyframes rule that animation already uses. "This preview provides support for 360º HDR images and adds the clarifying syntax to indicate what they are and how to work with them."

Orbit

Rotation is the interaction most people expect from a 3D object. "One of the main things that users want to do with 3D content is to look around it by rotating the scene in-place," according to the post. The new portal-action property supports only orbit in this preview. "It may be useful to add more modes in the future like pan-x or pan-y." WebKit notes that the setting mirrors the stagemode attribute already available on the <model> element, but that moving it into CSS makes it more flexible, since style rules can switch it on and off by context.

Connected Volumetric Scenes

The most headset-specific piece is the only one that is not CSS. "In addition to showing a spatial arrangement inside a portal, visionOS has the ability to show these scenes outside of the browser window in what we're calling a Connected Volumetric Scene," according to the post. A page calls requestVolumetricScene() on the portal element in response to a user action, and the content leaves the window. The viewer can then position the scene anywhere in the surrounding space, and the page keeps a live link to it, so objects can be added, removed or moved after launch.

The draft standard behind the preview

WebKit chose to publish the specification at the same time as the code. "While this feature preview is limited to visionOS, we thought it was important to release along with the full specification as an indication of how to approach bringing spatial concepts to the web," the post states. "There is a long journey ahead, and a lot more to get to in the proposed spatial CSS specification."

That specification is titled CSS Spatial Layout Module Level 1. It is hosted on the CSS Working Group's drafts server as an Editor's Draft dated November 16, 2026, the same day as the blog post, with two editors listed, Ada Rose Cannon and Elika J. Etemad, both affiliated with Apple. Like other editor's drafts, it carries the standard notice that it is offered for discussion and may change at any time.

The draft runs well beyond the six features in the preview. It lists properties the blog post does not discuss, among them portal-stage, portal-transform, front-limit, environment-intensity, environment-rotate, z-align-self and z-align-items, as well as a front-limit media query, a spatial-absolute value for the position property and inset properties for the front and back of a space. It also states that content which is not spatially positioned continues to be drawn and laid out in 2D as usual, and it records as an open issue what should happen when an element has no containing portal. No other browser maker is named in the post, and the draft lists no editors from outside Apple.

Why this matters for publishers and ad creative

PPC Land's coverage of Safari this year has mostly been about what Apple's browser takes away. Safari 27 blocks network access to identity resolution firms that turn email addresses into tracking IDs, a change WebKit announced on October 19, 2026. It also blocks The Trade Desk's ad domains through 11 lines of code WebKit merged in February, and an earlier beta blocked LinkedIn and Bing ad trackers by IP address. A year before that, Safari 26 made Advanced Fingerprinting Protection the default for all browsing.

The spatial CSS preview belongs to the other half of the WebKit release cycle: new capabilities for whoever builds the page. It also differs from the most recent rendering change PPC Land covered. With Adaptive Dark Mode, Safari 27.3 repaints light websites in dark colours without the sites knowing, a change applied by the browser at the viewer's request. Spatial CSS works the other way round. Nothing happens unless a page author declares a portal, places models in it and, for the volumetric step, waits for a viewer to ask.

For creative teams, the relevant shift is the toolset. Interactive 3D advertising has existed for years, but in proprietary wrappers. In 2020, Google rolled out 3D Swirl creatives in Display & Video 360, interactive models confined to 300x250, 300x600 and 336x280 placements, served only on Google Ad Manager inventory and only on high-bandwidth traffic. WebKit's design places 3D positioning, lighting and interaction in standard markup and style sheets that any page or HTML5 creative can carry. Because the parameters are CSS values, they are also the kind of input that template-driven systems such as dynamic creative optimization already swap at serve time for 2D formats. That last point is PPC Land's reading; the post does not mention advertising at all.

The audience question is harder. The Vision Pro has no native ad format and Apple withholds eye-tracking data from apps, and WebKit's post gives no figures on headset ownership or Safari usage on visionOS. Rival hardware is arriving too: Snap priced its Specs glasses at $2,195 in September, pitching augmented reality to consumers outside Apple's ecosystem. WebKit's own argument, that spatial content should not be built only for spatial devices, points to the larger installed base. The <model> element that the preview builds on is already available in Safari 27 on all platforms, according to the post, which takes in iPhone, iPad and Mac. Whether portals, anchors and environment maps follow it to those screens is not addressed.

There is also a practical record here for anyone who follows WebKit's release rhythm. The 27.x cycle has already produced viewport changes for the folding iPhone Duo in Safari 27.1, a fix for a mistaken seven-day cookie cap in Safari 27.2 and, in Safari 27.3, Adaptive Dark Mode. Spatial CSS adds a visionOS-only entry to that list.

Where things stand

Item Status, according to the post
Spatial CSS features Limited feature preview in Safari on visionOS 27.3, off by default behind the CSS Portals flag
<model> element "now available in Safari 27 on all platforms"
iPhone, iPad, Mac support for spatial CSS Not part of the preview; "this feature preview is limited to visionOS"
Testing without a headset visionOS Simulator, installed through Xcode
Specification Proposed; CSS Spatial Layout Module Level 1, Editor's Draft dated November 16, 2026
portal-action values orbit only; pan-x and pan-y mentioned as possible future modes
Environment map formats 360º HDR images, declared as equirectangular
Feedback channels bugs.webkit.org; Mastodon and X accounts listed in the post

What the post does not say

The post gives no date for a general release, does not say whether visionOS 27.3 is still in beta (WebKit described Safari 27.3 as a beta on November 3), and does not say when or whether spatial CSS will reach Safari on other Apple devices. It does not mention advertising, iframes or cross-origin content, does not explain what a page learns when a viewer orbits a scene or places it in the room, and offers no file-size or performance figures for USDZ models. Other browser makers' positions are not mentioned.

Key facts

  • Source: WebKit blog, "Introducing spatial CSS: A developer preview," by Brandel Zachernuk, dated November 16, 2026, https://webkit.org/blog/18621/introducing-spatial-css-a-developer-preview/
  • Platform: Safari on visionOS 27.3, limited feature preview
  • Feature flag path: Settings > Apps > Safari > Advanced > Feature flags > CSS Portals
  • Features in the preview: spatial: portal; transform inside a portal; anchor-name, position-anchor and position-context: anchor; @environment-map (descriptors name, format, src) with the environment-map property; portal-action: orbit; requestVolumetricScene()
  • New term: Connected Volumetric Scene
  • Underlying element: <model>, available in Safari 27 on all platforms according to the post; sample files use the USDZ format, lighting uses an HDR file in equirectangular format
  • Specification: CSS Spatial Layout Module Level 1, Editor's Draft dated November 16, 2026, editors Ada Rose Cannon and Elika J. Etemad (Apple), https://drafts.csswg.org/css-spatial-1/
  • Demo: WebKids puzzle playground, https://webkit.org/demos/webkids-puzzle-playground/index.html
  • Testing: visionOS Simulator through Xcode
  • Feedback: bugs.webkit.org; Mastodon @jensimmons@front-end.social and @jondavis@mastodon.social; X @zachernuk and @webkit

Timeline

Summary

Who: Apple's WebKit team, through a blog post by Brandel Zachernuk, with a draft specification edited by Ada Rose Cannon and Elika J. Etemad of Apple. Web developers, publishers and creative teams building for Safari are the intended audience.

What: A limited developer preview of spatial CSS: portals that group 3D models into a shared space, 3D transforms, anchoring between models, reusable environment-map lighting, an orbit interaction and a JavaScript method that moves a scene out of the browser into the viewer's space as a Connected Volumetric Scene.

When: The post and the CSS Spatial Layout Module Level 1 Editor's Draft are both dated November 16, 2026. No general release date is given.

Where: Safari on visionOS 27.3, on Vision Pro or in the visionOS Simulator, behind the CSS Portals feature flag. The underlying <model> element is available in Safari 27 on all Apple platforms, according to the post.

Why: WebKit wants spatial content on the web to use the same declarative patterns as ordinary pages, so that media queries, transitions and animation can shape 3D scenes, and it is publishing the preview early to gather feedback on a specification it describes as the start of "a long journey."