> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/convai-unreal-engine-plugin/compatibility-and-requirements/unreal-engine-platform-support-matrix.md).

# Unreal Engine platform support matrix

Use this reference to confirm which build targets the Convai Unreal Engine plugin supports, which engine plugin dependencies it enables, and what Android microphone access requires before packaging.

### Supported platforms

| Platform        | Runtime support | Editor support | Notes                                                                                |
| --------------- | --------------- | -------------- | ------------------------------------------------------------------------------------ |
| `Win64`         | Supported       | Yes            | Supported by the `Convai` and `ConvaiVisionBase` module allowlists.                  |
| `Android`       | Supported       | No             | Supported by the runtime module allowlists; requires microphone permission handling. |
| Other platforms | Not supported   | Not supported  | Not listed in the runtime module allowlists for this release.                        |

{% hint style="info" %}
macOS, Linux, and iOS are not supported in the current release.
{% endhint %}

### Engine plugin dependencies

The Convai plugin declares the following engine plugin dependencies. These are enabled automatically when the Convai plugin is active; you do not need to enable them manually.

| Dependency                 | Enabled by default | Required for                                                                      |
| -------------------------- | ------------------ | --------------------------------------------------------------------------------- |
| `AudioCapture`             | Yes                | Microphone input on Win64 and Android                                             |
| `AndroidPermission`        | Yes                | Requesting microphone permission at runtime on Android                            |
| `EditorScriptingUtilities` | Yes                | Editor tooling dependency; no user configuration required                         |
| `PropertyAccessEditor`     | Yes                | `FConvaiTrackedProperty.PropertyPath` Bind picker and property-binding details UI |

### Android microphone permission

Android builds require microphone access. The plugin declares `android.permission.RECORD_AUDIO` and uses the `AndroidPermission` dependency to request that permission at runtime, so the standard plugin flow does not require a separate Blueprint permission request.

Android toolchain setup is outside this plugin-specific reference. This page only describes the Convai plugin dependencies and microphone permission handling visible in the plugin source.

### Next steps

With platform dependencies confirmed, check which character rigs are compatible with the plugin.

{% content-ref url="/pages/9aF3O66XI2Xgu5NV461L" %}
[Character rig support](/api-docs/plugins-and-integrations/convai-unreal-engine-plugin/compatibility-and-requirements/character-rig-support.md)
{% endcontent-ref %}


---

# 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://docs.convai.com/api-docs/plugins-and-integrations/convai-unreal-engine-plugin/compatibility-and-requirements/unreal-engine-platform-support-matrix.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.