> 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/getting-started/system-requirements.md).

# System requirements

A powerful machine is not required to create in Vectary

Projects created in Vectary run seamlessly across all devices and operating systems through [WebGL 2.0](https://www.khronos.org/webgl/) in the browser.

Minimum Hardware Requirements for Vectary Studio:

* 2.0 GHz multi-core processor
* 8 GB of RAM or higher
* Graphics card with at least 1 GB of dedicated or shared video memory

{% hint style="warning" %}
Please note that on low-performance devices, scene quality may be automatically reduced to maintain optimal performance.
{% endhint %}

\
We highly recommend using the **Google Chrome** browser for the best possible experience, due to the limitations on key technologies used by Vectary in other browsers.<br>

{% hint style="info" %}
On desktop and laptop computers equipped with multiple graphics cards, ensure that Vectary Studio is running in the browser using the dedicated, high-performance graphics card for optimal results.
{% endhint %}

Vectary Studio is not optimized or intended for use on **mobile devices**. However, certain actions can still be performed from mobile devices if the browser is set to desktop mode. Please note that the experience will be significantly limited. It is recommended to use a computer for the best results.


---

# 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/getting-started/system-requirements.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.