# Custom Build Platforms

> Custom Build Platforms in Applivery extend App Distribution beyond mobile — distribute Builds for game consoles, web runtimes, and more.

Source: https://docs.applivery.com/en/app-distribution/platforms/custom-platforms/  •  Last updated: 2026-06-09

**Key topics:** Custom Platform Configuration, Build Upload Process, Metadata Requirements, API Integration, Supported Platforms, Applivery, Android, iOS, macOS, Windows, PlayStation, Xbox, Nintendo Switch, Steam, Upload API

---

**TL;DR:** Applivery's Custom Build Platforms allow you to distribute builds to any platform, including game consoles and web runtimes, using the same Applivery workflow.

By default, Applivery natively supports Android, iOS, macOS, and Windows Builds. **Custom Build Platforms** extends this to cover any platform your team distributes to — including game consoles, alternative storefronts, web runtimes, and archive formats — all managed through the same Applivery workflow.

This is particularly useful for game studios, cross-platform development teams, and organisations distributing to Devices or environments outside the four major mobile and desktop operating systems.

* * *

## Key capabilities

**Extended platform support** — upload and distribute Builds for platforms beyond iOS, Android, macOS, and Windows, including PlayStation, Xbox, Nintendo Switch, Steam, and more.

**Manual metadata configuration** — unlike native platforms, where Applivery extracts metadata automatically from the Build file, Custom Platforms require you to provide `packageName`, `packageVersion`, and optionally `packageIcon` manually at upload time.

**Unified management** — all Builds, regardless of platform, are managed in the same Applivery Workspace and accessible through the same [Upload API](https://docs.applivery.com/en/app-distribution/api/builds/upload-build/), keeping your distribution workflow consistent across every target.

**Raw file distribution** — Custom Platforms distribute build files in their original format without automated processing, giving you full control over what gets delivered.

* * *

## Supported platforms and file extensions

Every custom platform supports `.zip` and `.tar.gz` as universal container formats. Platform-specific supported extensions are listed below:

| Platform identifier | Supported extensions |
| --- | --- |
| `android` | `.apk`, `.aab` |
| `amazon` | `.apk`, `.aab` |
| `flexion` | `.apk`, `.aab` |
| `ios` | `.ipa` |
| `macos` | `.pkg`, `.dmg` |
| `macos-archive` | `.zip`, `.tar.gz` |
| `windows` | `.msi`, `.exe`, `.msix`, `.appx`, `.msixbundle`, `.appxbundle` |
| `windows-archive` | `.zip`, `.tar.gz` |
| `ps4` | `.pkg` |
| `ps5` | `.pkg` |
| `switch` | `.nsp` |
| `xbox-one` | `.zip`, `.tar.gz` |
| `xbox-series` | `.zip`, `.tar.gz` |
| `steam` | `.zip`, `.tar.gz` |
| `steam-mac` | `.zip`, `.tar.gz` |
| `epic` | `.zip`, `.tar.gz` |
| `epic-mac` | `.zip`, `.tar.gz` |
| `web` | `.unityweb`, `.wasm`, `.js`, `.html` |

:::info
All platforms also accept `.zip` and `.tar.gz` as generic archive formats, regardless of the extensions listed above.
:::

* * *

## How to upload a Build for a Custom Platform

**Upload your file**

Follow the standard build upload process described in [How to upload your first build](https://docs.applivery.com/en/app-distribution/getting-started/upload-first-build/). You can upload via the Dashboard or the [Upload API](https://docs.applivery.com/en/app-distribution/api/builds/upload-build/).

If you are uploading a `.zip` or `.tar.gz` file that does not correspond to a native platform, Applivery will prompt you to select the target Custom Platform in the next step.

**Select the Custom Platform**

After uploading, select the platform the Build is intended for from the Custom Platform selector. This tells Applivery how to categorise and display the Build within your Workspace.

![upload build for custom platform](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/a8a00bf3-bb23-4ec0-a6c6-c5e53272d447.png)

**Provide build metadata**

Because Custom Platforms do not undergo automated metadata extraction, you must supply the following information manually:

| Field | Required | Description |
| --- | --- | --- |
| `packageName` | Yes | The unique identifier for your App or build (e.g. `com.studio.mygame`). |
| `packageVersion` | Yes | The version string for this Build (e.g. `1.4.2`). |
| `packageIcon` | No | An icon image to represent the Build in the Applivery interface. |

![required fields custom platforms](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/11476b4f-43fb-4357-9a0b-236b5c36fa6d.png)

Once submitted, the Build will appear in your App's Builds section alongside any other Builds for that project.

* * *

## How to enable Custom Platforms

Custom Build Platforms are not enabled by default and must be activated at the Workspace level.

To view your currently enabled platforms, go to the [**Applivery Dashboard**](https://dashboard.applivery.io), navigate to the **Settings** 1 section, and select **Build Platforms** 2 from the left-hand menu.

![build platforms](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/eaa35661-27da-426a-9e59-7471833da260.png)

:::info
To enable Custom Platforms for your Workspace, contact the Applivery Support team at [support@applivery.com](mailto:support@applivery.com).  
We will enable the feature and help you configure the specific platforms you need.
:::

* * *

## Using the Upload API with Custom Platforms

Custom Platforms are fully supported through the Applivery Upload API, allowing you to integrate build uploads into your CI/CD pipeline just as you would for native platforms. The same endpoint is used — you simply specify the custom platform identifier in your request.

See the [Upload API documentation](https://docs.applivery.com/en/app-distribution/api/builds/upload-build/) for full details on request format, authentication, and required parameters, including `packageName` and `packageVersion` for custom platform Builds.