> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/web/bim/bim.md).
# WebViewer BIM
Discover the power of WebViewer BIM for viewing, annotating, and collaborating on BIM models. Easily navigate, annotate, and toggle object visibility in complex models. Explore rich metadata and desig
{% hint style="info" %}
New licenses for WebViewer BIM are no longer offered.
{% endhint %}
WebViewer BIM allows you to view, annotate and collaborate on BIM models.
* Load models from your own servers without relying on the cloud.
* Navigate complex BIM models with the look and feel of the familiar Webviewer UI.
* Traverse the model tree and toggle visibility of objects.
* View model properties and rich metadata such as material and dimensional information.
* Annotate BIM models to track design issues.
This sample uses the [BIM addon](https://www.npmjs.com/package/@pdftron/webviewer-bim-client/) for WebViewer.
Download WebViewer BIM
## Supported File Types
| Format | Type |
| ------ | --------------------------- |
| IFC | Industry Foundation Classes |
| RVT | Revit (Autodesk) |
| OBJ | Object ASCII |
| STL | Stereolithography CAD |
| DWG | Drawing (Autodesk) |
## Architecture
There are two components to WebViewer BIM:
1. [Server-side](/web/bim/setup-server.md) file conversion that supports 3D streaming to the client.
2. [Client-side](/web/bim/setup-client.md) 3D viewer that renders BIM models and allows navigation entirely encapsulated in our familiar WebViewer UI.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.apryse.com/web/bim/bim.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.