ARKit is the engine under Apple’s AR. It fuses the camera feed with motion sensors to understand where the floor is, how the room is lit and how the device moves, then anchors a 3D model to a real surface so it stays put as the user walks around it. On iPhones and iPads with a LiDAR scanner it adds precise depth, which powers features like RoomPlan, an API that scans a room into a tidy 3D floor plan. On visionOS it goes further still, with capabilities such as shared world anchors, fast hand tracking and environment occlusion that hides virtual content behind real objects.
For the web this matters indirectly. A website cannot talk to ARKit on its own, but it can hand a USDZ file to Apple Quick Look, which uses ARKit to do the placement. That is why iOS Web AR feels so solid.
On WordPress, PausAR Viewer takes care of the whole chain. Upload a USDZ (plus a GLB for ARCore on Android), and the Elementor widget triggers Quick Look on iOS, so you reach ARKit without writing a line of Swift.
| Property | ARKit | ARCore |
|---|---|---|
| Vendor | Apple | |
| Platforms | iOS, iPadOS, visionOS | Android |
| Web AR format | USDZ via Quick Look | GLB via Scene Viewer |
Not directly. A website hands a USDZ model to Apple Quick Look, which uses ARKit internally for tracking and placement.
ARCore from Google, which powers Google Scene Viewer for GLB files.
Use the PausAR Viewer Elementor widget. Upload a USDZ, drag the widget into a page, and the plugin launches Apple Quick Look on iOS, which runs on ARKit, with no coding.
You are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More Information