> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/creator/build-for-mobile/develop/optimize-performance.md).

# Performance

Mobile scene limits and performance targets for Decentraland scenes, and how to preview and measure them from the Creator Hub.

Mobile devices have tighter resource constraints than desktop or web. Understanding the mobile scene limits and how to preview them helps you ship a scene that runs smoothly for the widest audience.

## Mobile Scene Limits

The table below shows the limits enforced when running on mobile. Reaching a **soft limit** triggers a warning in the performance panel; reaching a **hard limit** blocks the scene from loading.

| Metric                         | Soft Limit | Hard Limit |
| ------------------------------ | ---------- | ---------- |
| Triangles                      | 1,000,000  | 1,200,000  |
| Entities                       | 4,800      | 6,000      |
| Meshes (bodies)                | 2,400      | 3,000      |
| Geometries                     | 1,000      | 2,000      |
| Materials                      | 400        | 500        |
| Textures                       | 400        | 500        |
| Colliders                      | 1,200      | 1,500      |
| VFX emitters                   | 8          | 10         |
| Live particles                 | 25,000     | 50,000     |
| Light sources                  | 8          | 16         |
| Shadow lights                  | 2          | 4          |
| Content size                   | 120 MB     | 150 MB     |
| External content               | 40 MB      | 50 MB      |
| Memory (process RSS)           | 1,638 MB   | 2,048 MB   |
| Draw calls                     | 1,000      | 2,000      |
| Performance (higher is better) | 90%        | 85%        |

## Lights and particles

The light rows count **authored** scene content, not what the engine ends up running. Each graphic profile activates only a budget of the nearest light sources (0 on Very Low up to 8 on High) and may disable shadows entirely — so a scene that authors 20 lights still pays their scene cost even though at most 8 emit light at once. Author to the limit, don't rely on the runtime budget.

Particles are additionally capped at runtime: 5,000 particles per emitter and 50,000 per scene. Anything authored above those caps is silently clamped, so exceeding them only wastes scene budget.

## Preview Mobile Performance

You can check your scene’s mobile performance directly from **Creator Hub** without deploying to a physical device.

1. Open your scene in **Creator Hub**.
2. Select Preview > Show QR Code for Mobile
3. Open the **Scene Limits Preview** from the top right icon in your phone (monitor with statistics in red).

![Mobile scene limits panel in Creator Hub](https://45449780-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoPnXBby9S6MrsW83Y9qZ%2Fuploads%2Fgit-blob-65a2ca6fbdd8873f352431b5433817c0f944121d%2Fmobile_scene_limits.png?alt=media\&token=ed32dc52-362d-4af1-9a40-56e683774e94)

{% hint style="warning" %}
**Keep Performance above 90% on High Graphics**

The **Performance** value is a percentage of the FPS budget set by the active graphic profile. A score of **100%** means the scene is hitting the full FPS target.

Always test on a mid-spec device like the **Samsung Galaxy A54** and aim for a **Performance score above 90% on the High graphic profile**. This ensures a smooth experience for the majority of mobile players. See [Hardware Requirements](/creator/build-for-mobile/mobile-client/hardware-requirements.md) for reference devices.

You can change the graphic profile from **In-Game Menu → Settings → Graphics → set Dynamic Graphics to Off → switch Profiles**.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.decentraland.org/creator/build-for-mobile/develop/optimize-performance.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.