Safari 27 and the model element: what it adds to web 3D

What Safari 27 adds

On 17 September 2026, WebKit announced the HTML model element for Safari on iOS, iPadOS and macOS, following its introduction on visionOS.

It embeds 3D content and allows alternative sources. WebKit’s example includes USDZ, GLB and a fallback image, with options for lighting and interaction.

This provides a native route for displaying objects. It does not automatically supply a complete product configurator.

What a configurator still needs

Changing finishes, enforcing valid combinations, displaying dimensions and connecting selections to orders require application logic and product data.

Before replacing an existing viewer, list the functions it must preserve. Rotating an object may be enough for a simple listing; configurable purchases require more checks.

Plan a fallback from the start

Do not infer universal compatibility from a Safari release. Check the versions and devices your audience uses, including browsers embedded in other applications.

The page should still explain the product if the feature is unavailable or the model fails to load. An image and essential specifications can provide a useful fallback; broader interaction may require a tested alternative viewer.

Detecting an API is only part of the assessment. Test the actual file and the specific functions you intend to use.

Check the product across destinations

Export from an editable master and review each format. Differences in materials, transparency and lighting can affect appearance across viewers.

Avoid unnecessarily loading two complete versions of the object. Measure the initial download and what happens when the visitor activates 3D.

Use our guide to mobile 3D viewer performance and limits to plan those tests. For catalogue distribution, see preparing a model for multiple channels.

To plan those tests with your catalogue, tell us which devices your product page is opened on today.