<model-viewer> is a customizable and easy-to-use web component that enables developers to seamlessly integrate 3D models into websites and applications. It simplifies the process of rendering, animating, and manipulating 3D objects in real-time, providing an immersive user experience. By leveraging modern web technologies like WebGL and WebXR, <model-viewer> ensures cross-platform compatibility, accessibility, and responsiveness. Its extendable and open-source nature allows for creative customizations, making it perfect for product visualizations, interactive content, and augmented reality experiences. With <model-viewer>, building engaging 3D web experiences is just a few lines of code away.
1,507
websites using <model-viewer>
Create a technology report →Export the list of all websites using <model-viewer> with their listed metadata
Websites using <model-viewer> by countrymarket share · top 8 countries
🇺🇸United States
🇩🇪Germany
🇬🇧United Kingdom
🇮🇹Italy
🇮🇳India
🇯🇵Japan
🇪🇸Spain
🇳🇱Netherlands
0%2%4%6%8%
Websites using <model-viewer> by industrydetected industries
Technology & Computing25%
Shopping20%
Software Development18%
Manufacturing & Industrial15%
Marketing & Advertising12%
Design & Creative11%
Websites using <model-viewer>
showing 25 of 1,507| Website | Country | Industry | Size | Founded | |
|---|---|---|---|---|---|
| 🇺🇸US | SaaS & Cloud | 1-10 | - | ||
| 🇭🇷HR | Shopping | 1001-5000 | 1990 | ||
| 🇺🇸US | Software Development | 11-50 | 2021 | ||
| 🇺🇸US | Business & Finance | 201-500 | 2016 | ||
| 🇨🇳CN | Technology & Computing | 201-500 | 2008 | ||
| 🇪🇸ES | Fashion & Beauty | 1001-5000 | 1984 | ||
| 🇨🇦CA | Technology & Computing | 1-10 | 2015 | ||
| 🇩🇪DE | Software Development | 201-500 | 1987 | ||
| 🇧🇩BD | Hardware & Electronics | 10001+ | 1977 | ||
| 🇩🇪DE | Hardware & Electronics | 1001-5000 | 1905 | ||
| 🇧🇪BE | Gaming | 51-200 | - | ||
| 🇺🇸US | Shopping | 1001-5000 | 1987 | ||
| 🇳🇴NO | Sports | 51-200 | 2011 | ||
| 🇦🇺AU | Technology & Computing | 11-50 | 2013 | ||
| 🇨🇦CA | Mining & Metals | 11-50 | 2011 | ||
| 🇺🇸US | Software Development | 51-200 | 2001 | ||
| 🇩🇪DE | Shopping | 11-50 | 2004 | ||
| 🇮🇹IT | Medical & Healthcare | 5001-10000 | 1973 | ||
| 🇪🇸ES | Environment & Sustainability | 51-200 | 2016 | ||
| 🇩🇪DE | Manufacturing & Industrial | 201-500 | 1924 | ||
| 🇧🇩BD | Shopping | 1-10 | - | ||
| 🇨🇦CA | Manufacturing & Industrial | 51-200 | 2007 | ||
| 🇵🇱PL | Construction | 501-1000 | 1987 | ||
| 🇺🇸US | Software Development | 1-10 | - | ||
| 🇺🇸US | Sports | 11-50 | 2012 |
Showing 25 of 1,507 websitesGet the full list →
Frequently asked
What is the purpose of the <model-viewer> component?›
The <model-viewer> component is a custom HTML element that allows you to easily display interactive 3D models on your website. It supports various 3D file formats and has built-in support for responsive design, lazy loading, and accessibility features.
Which 3D file formats are supported by the <model-viewer> component?›
The <model-viewer> component primarily supports the glTF format (.gltf or .glb files). Additionally, it has some support for USDZ files, which can be used for AR experiences on iOS devices.
Can I control the appearance of the 3D model in the <model-viewer>?›
Yes, you can control the appearance of the 3D model using various attributes and CSS custom properties. You can adjust the lighting, shadow, background, rotation, and more in the <model-viewer> component to create the desired look for your 3D model.
Is it possible to use AR (Augmented Reality) with the <model-viewer> component?›
Yes, the <model-viewer> component supports AR capabilities on compatible devices. By adding the "ar" attribute to the component, you can enable AR features for your 3D model, allowing users to experience the model in their physical surroundings on devices that support WebXR or Quick Look on iOS.
Is the <model-viewer> component compatible with all web browsers?›
The <model-viewer> component is compatible with most modern web browsers that support Web Components and WebGL. However, browser compatibility may vary slightly due to differences in browser implementations, and some older browsers may not fully support the component. It is always recommended to test your implementation on multiple browsers to ensure a consistent user experience.