A web component for displaying interactive 3D models on the web and in augmented reality (AR).
Model-viewer is a web component developed by Google that allows developers to easily embed and display interactive 3D models on websites and in augmented reality. It solves the problem of making complex 3D graphics accessible and performant within standard web workflows, supporting formats like glTF.
Web developers, designers, and product teams who need to integrate interactive 3D visualizations, product displays, or educational models into their websites or web applications.
Developers choose model-viewer because it provides a standardized, easy-to-use HTML element for 3D/AR content, is backed by Google, and integrates seamlessly with modern web development practices without requiring low-level WebGL programming.
Easily display interactive 3D models on the web and in AR!
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses a standard custom HTML element <model-viewer> for declarative, framework-agnostic embedding, making it as simple as adding an image tag, as highlighted in the README's web component focus.
Enables augmented reality experiences directly from the browser on supported devices, allowing users to view models in their real-world environment without native app development, per the key features.
Includes an online editor and fidelity testing tools, such as those in the render-fidelity-tools package, for easier debugging and quality assurance, as noted in the README.
Maintained by Google, ensuring ongoing updates, security patches, and alignment with web standards, which adds credibility and long-term support, as implied in the project description.
Setup and testing require WSL2 on Windows, with noted issues like GUI support for fidelity tests only on Windows 11 and troubleshooting steps for line endings, making local development cumbersome.
Primarily optimized for glTF models; other formats may need conversion or lack native support, potentially limiting flexibility for projects with diverse 3D assets.
AR functionality is restricted to supported devices and browsers, which can exclude users on older or incompatible platforms, reducing accessibility for some audiences.