> For the complete documentation index, see [llms.txt](https://gamelauncher.cloud/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gamelauncher.cloud/help/applications/upload-builds/upload-builds-dashboard.md).

# Upload from the Dashboard

The fastest way to publish an update: drag your ZIP into the dashboard, wait for processing, set it as active.

{% hint style="info" %}
**Maximum file size: 5 GB.** For bigger builds use the [CLI Tool](/help/applications/upload-builds/upload-builds-cli.md).
{% endhint %}

***

## Before You Start

Your build must be a **.zip** file with all game files **in the root** of the ZIP (not inside a single folder). See [Prepare Your Build](/help/applications/upload-builds.md#prepare-your-build) if you are not sure.

***

## Step 1: Open the App Builds Tab

{% stepper %}
{% step %}
**Access the dashboard**

Log in to your [Game Launcher Cloud](https://app.gamelauncher.cloud/dashboard) account.
{% endstep %}

{% step %}
**Select your app**

In the sidebar, click on your app.

<div align="left"><figure><img src="/files/qlxYZy4OumTO5kpq9SgX" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Open the App Builds tab**

Click the **App Builds** tab in your application page.

<div align="left"><figure><img src="/files/xHAhimFGO3You3gfqZN8" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

***

## Step 2: Upload Your ZIP

1. **Drag and drop or browse:** select your .zip file
2. **Add build notes** (optional): describe changes, bug fixes, new features
3. **Click "Upload Your Build":** the upload starts immediately
4. Keep the tab open until the upload finishes

<figure><img src="/files/gofaWqaxIgV7x2sFn2SA" alt=""><figcaption></figcaption></figure>

***

## Step 3: Wait for Processing

After the upload, the build goes through the queue. You can follow it in the Jobs Monitor.

<figure><img src="/files/2boHHWD97QanFdSNnR6W" alt=""><figcaption><p>Jobs Monitor - Processing App Build</p></figcaption></figure>

1. **⬆️ Uploading:** file upload to cloud storage
2. **⬇️ Downloading:** server retrieves the file
3. **📦 Unzipping:** extracting build contents
4. **🔧 Creating Patch:** generating delta patches
5. **✅ Completed:** build is ready for distribution

{% hint style="info" %}
**Processing time** (depends on build size and file count)

* Small builds (under 1 GB with about 500 files): 5 to 30 seconds
* Medium builds (1 to 5 GB with about 1,000 files): 3 to 5 minutes
  {% endhint %}

***

## Step 4: Set the Build as Active

A processed build is not live yet. Activate it so players can download it:

{% stepper %}
{% step %}
**Find your build**

In the **App Builds** tab, your new build appears in the list with status **Completed**.

<figure><img src="/files/c8QwTqOHTvnLpw4Ok9JZ" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Open Change Active Build**

Switch to the **Environments** tab and click **"Change Active Build"**.

<figure><img src="/files/jkrJTaGwKKYgkF9X47Ww" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Confirm**

Select the build and click **Set Build**.

<figure><img src="/files/M62sk9jlMRbNRFEBiJbA" alt=""><figcaption><p>Change active build dialog</p></figcaption></figure>
{% endstep %}
{% endstepper %}

That is it. Open your launcher and click refresh to fetch the new update.

{% hint style="info" %}
**Active build:** only ONE build per platform and environment can be active at a time. Setting a new one replaces the previous one.
{% endhint %}

{% hint style="success" %}
**Players update automatically:** once a build is active, players receive it the next time they open the launcher.
{% endhint %}

***

## Troubleshooting

<table data-full-width="false"><thead><tr><th width="200">Issue</th><th width="150">Cause</th><th>Solution</th></tr></thead><tbody><tr><td><strong>Stuck at "Enqueued"</strong></td><td>Build waiting in the processing queue</td><td>It should start after a few minutes. If it stays stuck, contact support with the Build ID.</td></tr><tr><td><strong>Stuck at "Processing"</strong></td><td>Large file being processed</td><td>Wait and check the status regularly. Large builds take longer.</td></tr><tr><td><strong>Build shows "Failed"</strong></td><td>Corrupt ZIP or invalid structure</td><td>Re-compress the file and make sure no file inside is corrupted.</td></tr><tr><td><strong>Upload very slow</strong></td><td>Network connection</td><td>Check your internet speed, or use the <a href="/pages/Pu8gtIiAg3DRg8KNEz9X">CLI</a> for better upload performance.</td></tr><tr><td><strong>Can't find the build after upload</strong></td><td>Wrong environment selected</td><td>Check the other environments (Staging, Production, custom).</td></tr><tr><td><strong>File is over 5 GB</strong></td><td>Dashboard limit</td><td>Use the <a href="/pages/Pu8gtIiAg3DRg8KNEz9X">CLI Tool</a>.</td></tr></tbody></table>

{% hint style="success" %}
**Need help?** Join [Discord](https://discord.com/invite/FpWvUQ2CJP) or email <support@gamelauncher.cloud>
{% endhint %}

***

## Next Steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>⚡ CLI Upload</strong></td><td>For builds over 5 GB and automated releases</td><td><a href="/pages/Pu8gtIiAg3DRg8KNEz9X">/pages/Pu8gtIiAg3DRg8KNEz9X</a></td></tr><tr><td><strong>🧩 How Patching Works</strong></td><td>Why players only download what changed</td><td><a href="/pages/G7EDuuyO4kDn9NxT7p7M">/pages/G7EDuuyO4kDn9NxT7p7M</a></td></tr><tr><td><strong>🌍 Environments</strong></td><td>Test in Staging before going to Production</td><td><a href="/pages/Bzo5c15XEsyTL0bEaWsM">/pages/Bzo5c15XEsyTL0bEaWsM</a></td></tr><tr><td><strong>📰 News &#x26; Updates</strong></td><td>Announce the update to your players</td><td><a href="/pages/uquAxcCnbM4zORBOKUyW">/pages/uquAxcCnbM4zORBOKUyW</a></td></tr></tbody></table>


---

# 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://gamelauncher.cloud/help/applications/upload-builds/upload-builds-dashboard.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.