> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/documentation/api-and-sdk-en/unity/manual-integration.md).

# Manual integration

{% hint style="info" %}
**We recommend using the Appintos Unity SDK**

The direct integration method requires manually implementing everything, including the JS Bridge, WebGL build settings, and packaging. Unless there is a special reason, [Appintos Unity SDK](/documentation/api-and-sdk-en/unity/integration.md)we recommend using it.
{% endhint %}

To deploy a Unity game to Appintos, build the Unity project to **WebGL**WebGL. This guide explains the basic steps for creating a WebGL build in Unity.

### 1. Install the WebGL module

The WebGL platform must be installed in Unity Hub.

1. Run Unity Hub
2. Select the Installs tab
3. Click the three dots (···) next to the Unity version you're using → Add Modules
4. Check WebGL Build Support → Install
5. Once installation is complete, when you go to File > Build Settings in Unity, it appears in the platform list **WebGL**appears.

### 2. Switch platforms

1. Open the Unity project
2. Go to File > Build Settings
3. Select WebGL → Click Switch Platform

### 3. Adjust Player settings

In the Edit > Project Settings > Player menu, configure the following items.

* Publishing Settings
  * Compression Format: `Brotli` set to

### 4. Build

1. Go to File > Build Settings
2. With WebGL selected → Click Build
3. Specify the output folder (e.g., Build/)

### 5. Check the output

When the build is complete, usually `index.html`, `Build`, `TemplateData` folders are created. Depending on the Unity project settings or version, the folders that are created may vary slightly. You can include these folders in a Vite project and display them as a web page.

For how to wrap Unity WebGL with Vite, please refer to Wrapping Unity WebGL with Vite.

{% hint style="info" %}
**Note**

In versions earlier than Unity 6000.1.8, when using the 2D physics engine (Rigidbody2D), in WebGL builds **there was a GC memory leak issue**For details, see [the Unity Discussions forum](https://discussions.unity.com/t/memory-leak-when-using-rigidbody2d-physics-in-webgl/1649803)here.
{% 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 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://developers-apps-in-toss.toss.im/documentation/api-and-sdk-en/unity/manual-integration.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.