> For the complete documentation index, see [llms.txt](https://studio-docs.sandbox.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio-docs.sandbox.game/the-editor/preview-a-game-on-mobile.md).

# Preview a Game on Mobile

Use Mobile Preview to check the game's layout, orientation, touch controls, and gameplay within a simulated phone view.

{% embed url="<https://youtu.be/tMOU4eQmcAY?si=PTCErdJHBfcMmXQn>" %}

{% stepper %}
{% step %}

## Open the Play menu

Select the small arrow beside the Play button to open the available play options.
{% endstep %}

{% step %}

## Select Mobile Preview

Choose Play Mobile Preview from the menu. This changes the editor's Play view to a mobile-style presentation.
{% endstep %}

{% step %}

## Open the mobile settings

Select the Play Mobile settings to configure the device, orientation, and input options used by the preview.
{% endstep %}

{% step %}

## Choose a device

Select the phone model or screen profile you want to test. Use more than one profile when the game must support different screen shapes or sizes.
{% endstep %}

{% step %}

## Choose the orientation

Select Portrait or Landscape to match the intended way players will hold the device.
{% endstep %}

{% step %}

## Enable touch emulation

Turn on touch emulation when you need to test taps, touch input, or on-screen movement controls with desktop input.
{% endstep %}

{% step %}

## Start the mobile preview

Press Play. The game opens inside a mobile-style frame using the selected device and orientation.

{% hint style="info" %}
*NOTE: On-screen thumbsticks may appear when the project includes compatible movement controls. Confirm that they respond correctly; projects with custom controls may require additional setup. How to enable and tune sticks, and how to add jump or interact buttons, is on* [*Mobile development*](/the-editor/mobile-development.md)*.*
{% endhint %}
{% endstep %}

{% step %}

## Check the interface and controls

Test the user interface, movement, buttons, touch areas, text size, and important gameplay information. Look for content that is clipped, too small, covered by controls, or difficult to reach.
{% endstep %}

{% step %}

## Repeat the test in other layouts

Return to the mobile settings and test another device or orientation when the game supports multiple layouts. Fix interface or control issues, then preview the game again.

{% hint style="info" %}
*TIP: Mobile Preview is an editor simulation. Complete a final check on supported physical devices when accurate touch behaviour and device performance matter.*
{% endhint %}
{% endstep %}
{% endstepper %}

## What You've Done

The game now runs in a configurable mobile-style preview where its interface, orientation, and touch controls can be reviewed before device testing. For sticks, buttons, and asset rules, see [Mobile development](/the-editor/mobile-development.md).


---

# 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://studio-docs.sandbox.game/the-editor/preview-a-game-on-mobile.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.