> For the complete documentation index, see [llms.txt](https://docs.viverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.viverse.com/polygon-streaming/introduction-and-benefits.md).

# Introduction & Benefits

This page introduces you to the goals and technology that make up VIVERSE Polygon Streaming.

***

VIVERSE Polygon Streaming is an intelligent visualization core technology that overcomes modern-day 3D visualization challenges. It unleashes the potential to stream spatial content from the cloud and seamlessly shares high-fidelity models and worlds on any device.

Polygon Streaming aims to provide creators, developers, designers, and enterprises with tools to build immersive, high-quality 3D content that is widely compatible with the most popular game engines and can be experienced across different platforms.

VIVERSE Polygon Streaming focuses on the next shift in computing and the future of the internet. It breaks down barriers and enables accessibility from any device (mobile, tablet, PC, and even XR headsets), allowing people to create, share experiences, and collaborate like never before.

Allow end-users to consume big 3D models rapidly by only downloading the geometry that has relevant visual impact for them at their specific position and bandwidth. With Polygon Streaming, you can stream large 3D models into your platform or projects without taking up local storage space, leveraging the number of polygons that can be shown in a cross-platform and multi-device way.

### Start Here

1. Check [Supported Formats & Standards](/polygon-streaming/supported-formats-and-standards.md) and [Asset Preparation & Best Practices](/polygon-streaming/asset-preparation-and-best-practices.md).
2. [Upload and convert your asset](/polygon-streaming/upload-and-convert-a-3d-asset.md), then obtain its streaming model URL.
3. Choose an integration below and follow its setup instructions.
4. Test the model in the running application. An editor or console preview alone does not verify runtime streaming behavior; see [Preview Mode vs. Play Mode](/polygon-streaming/avoiding-common-mistakes-preview-mode-vs.-play-mode.md).

### Choose an Integration

| Your project                                                      | Start with                                                                                                |
| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| Embed a model viewer in an existing webpage                       | [iFrame Integration](/polygon-streaming/integrations-and-plugins/polygon-streaming-iframe-integration.md) |
| Work in the PlayCanvas Editor or VIVERSE extension workflow       | [PlayCanvas SDK](/polygon-streaming/integrations-and-plugins/polygon-streaming-playcanvas-sdk.md)         |
| Add streaming to a Unity project                                  | [Unity SDK](/polygon-streaming/integrations-and-plugins/polygon-streaming-unity-sdk.md)                   |
| Add streaming to an Unreal Engine project                         | [Unreal Engine SDK](/polygon-streaming/integrations-and-plugins/polygon-streaming-unreal-engine-sdk.md)   |
| Build a JavaScript application with PlayCanvas Engine or Three.js | [JavaScript SDK](/polygon-streaming/polygon-streaming-javascript-sdk.md)                                  |

Review the requirements and limitations of your chosen integration before installation. Features and platform support can differ between SDKs.

### AI-Assisted Development

Use the integration table above to select the documentation for your engine before asking an AI coding assistant to implement streaming.

#### Skill Resources

Explore the [VIVERSE SDK Skills repository](https://github.com/viverseofficial/viverse-sdk-skills/tree/main/skills) for relevant Skill resources. Inspect the selected `SKILL.md` to confirm that it covers Polygon Streaming and your target environment before using it. The repository entry is a discovery link; a specific Polygon Streaming Skill path and installation procedure have not yet been verified for this guide.

Give your assistant:

* Your engine and project setup, along with the matching SDK guide linked above.
* The task you want to complete, such as loading a converted model in Three.js or adding streaming to an existing Unity scene.
* A usable streaming model URL, or the [upload and conversion guide](/polygon-streaming/upload-and-convert-a-3d-asset.md) if conversion is still needed.

Ask the assistant to read the selected SDK guide and any applicable Skill before proposing changes. Use the SDK's download and installation page for dependency information, then validate the result in the running application.

If a VIVERSE documentation connector is available in your assistant, use it to search for the relevant guide and retrieve the full page. Otherwise, provide the public documentation links directly. Documentation access alone does not provide model upload or conversion operations.

### Benefits

* Only transfer geometry is needed in the user’s current position and field of view in the scene over time. 
* Automatic LOD generation and texture compression. Texture compression method optimized for lightweight decompression.
* Minimal back-end server requirements, only requiring HTTP requests. 
* Utilize the end-user's GPU for full rendering. No Cloud GPU is necessary at any step.

{% hint style="info" %}
For license & agreement, please click on this [link](/polygon-streaming/viverse-sdk-license-agreement.md).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.viverse.com/polygon-streaming/introduction-and-benefits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.