> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/sharing-exporting-embedding/optimizing-a-shared-project/textures.md).

# Textures

Textures are often the main reason for large project sizes and slow loading times. Using high-resolution textures or too many of them can also lead to memory issues, especially on mobile devices or low-performance hardware.

Some textures may offer little to no visual benefit while significantly increasing project size. These should either be removed or their resolution reduced to the lowest acceptable level.

All active textures can be reviewed and adjusted in [**Preview mode**](/documentation/sharing-exporting-embedding/performance-analyzer.md), where resolution changes can be applied globally. Textures can also be edited individually in the material or environment settings where they're used.

#### Tips & recommendations

* **Use textures only when necessary.** In some cases, adjusting the geometry may be more efficient than simulating detail through textures.\ <br>
* **Reduce resolution wherever possible.** For example, lowering a texture from `2048×2048` to `512×512` often makes little visual difference but improves performance and loading time significantly.\ <br>
* **Choose efficient formats.** Use **JPG** or **SVG** instead of **PNG**, unless transparency is required. PNG files are typically heavier and less optimized for web.\ <br>
* **Avoid GIFs.** For animations, use **Lottie** or **MP4** formats — both are far better optimized for performance and file size.\ <br>
* **Test on mobile devices.** Preview the scene on a phone or low-spec device to check if textures cause memory or rendering issues.


---

# 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://help.vectary.com/documentation/sharing-exporting-embedding/optimizing-a-shared-project/textures.md?ask=<question>&goal=<user_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.