Ren'Py support devices running the Android operating system, such as smartphones and tablets. While these devices do not support 100% of Ren'Py's functionality, with minimal modification code can be packaged and ported to these devices.

RAPT - the Ren'Py Android Packaging Tool - is a program, downloaded separately from Ren'Py, that creates an Android package for testing or release purposes.

Required Language

Some of the libraries used by Ren'Py on iOS are licensed under the terms of the GNU Lesser/Library General Public License. You'll need to comply with the terms of that license to distribute Ren'Py. We believe including the following language in your app's description will suffice, but check with a lawyer to be sure.

This program contains free software licensed under a number of licenses, including the GNU Lesser General Public License. A complete list of software is available at

User Instructions

When a Ren'Py game has been launched on Android, the following keybindings work:

Returns to the Android home screen, suspending the Ren'Py game. As part of the suspend process, Ren'Py will automatically save the game. If necessary, the save will be automatically loaded when the user returns to the game.
Brings up the in-game menu, and returns to the game.
Rolls back.
Volume Up, Volume Down
Controls Android's media volume.

Platform Differences

There are many important differences between the touch-based Android platform and the mouse-based platforms that Ren'Py supports. Changes due to the Android software and hardware are:

  • The touchscreen is treated as if it was a mouse. However, it will only produce mouse events when the user is actively touching the screen.
  • Movie playback is only supported in fullscreen mode, and only with media formats that are supported by Android devices. See this page for a list of supported video formats.
  • Ren'Py cannot change the device volume. However, the android volume buttons work normally.
  • Ren'Py can't handle transparency in buttons and imagemaps. (This is due to performance problems on some devices with the display modes needed to support deciding which pixels are transparent.)

In addition, there are a few changes that may be necessary due to human factors:

  • Since Android smartphones can be smaller than a computer monitor, it may be necessary to increase text size.
  • Since touch input is less accurate than mouse input, touch-based buttons need to be larger than mouse-based ones.

To help you adapt to these differences, Ren'Py for Android automatically selects screen variants based on the device's screen size and capabilities. See Screen Variants for more information.

Testing and Emulation

For testing purposes, Ren'Py supports three Android emulation modes. These are accessed from the Android screen of the launcher.

This mode emulates an Android phone. Touch emulation is performed using the mouse, but only when the mouse button is held down. Escape is mapped to the menu button, and Page Up is mapped to the back button.
This mode emulates an Android tablet. Touch emulation is performed using the mouse, but only when the mouse button is held down. Escape is mapped to the menu button, and Page Up is mapped to the back button.
Television / OUYA

This mode emulates a television-based Android device, such as the OUYA console. The keyboard is mapped to remote or controller input, with the arrow keys providing navigation. Select is enter, Escape is menu, and page-up is back.

This mode also displays an overlay showing the Television-unsafe area. Content in the Television-unsafe area may not display on all Televisions.

While these emulators can be used to quickly test your project, it's best to also test on real hardware. The emulators do not deal with some human-factors issues, like the size of a user's fingers.


Building Android Applications

Ren'Py contains tools that help you take a packaging-centric approach to Android game development. In this approach, you will use a PC to build an Android package and upload it to your device. You can then run the game like any Android application. When it works correctly, you can upload the package you make to Google Play and other app stores.

Building an Android application consists of four steps:

  1. Download and install the Java Development Kit and Android USB Drivers (scroll down for links).
  2. Use the launcher to install the Android SDK and create keys.
  3. Use the launcher to configure the Android build.
  4. Use the launcher to build the Android application.

Once you've finished these steps, you'll have a runnable Android package. You'll only need to run step 3 when you decide to make changes to your game's configuration or when configuring a new game entirely; you'll run step 4 most often, whenever you need to make a new build of your game.

Step 1: Installing the Dependencies

There are three things you may need to manually download and install before you can build packages:

Java Development Kit. The Java Development Kit (JDK) contains several tools that are used by RAPT, including the tools used to generate keys and sign packages. It can be downloaded from:

Please note that the developer-focused JDK is different from the user-focused JRE, and you'll need the JDK to create Android packages.

Android Device Drivers. On Windows, you may want to install a device driver to access your device, although this is not necessary. Links to android device drivers can be found at:

On Linux or OS X, you won't need a device driver. If you can't access your device, you may need to read:

However, modern versions of Linux and OS X should just work.

Step 2: Set up the Android SDK and Development Environment

The next step is to set up the Android SDK and the rest of your development environment. This step will:

  • Check that the JDK is installed properly.
  • Install Apache Ant.
  • Install the Android SDK.
  • Use the Android SDK to install the appropriate development packages.
  • Create a signing key that will be used to sign packages that are placed on the market (android.keystore: this will be generated in the RAPT directory).

This step requires Internet access.

To perform this step, choose "Install SDK & Create Keys" from the Android screen in the Ren'Py Launcher.

RAPT will report on what it's doing. It will also prompt you with warnings about licenses, and ask if you want it to generate a key.


The key generated by RAPT is created with a standard passphrase. You should really use keytool to generate your own signing keys.

At the very least, you should keep the android.keystore file in a safe place. You should also back it up, because without the key, you won't be able to upload the generated applications.

Step 3: Configure Your Game

Before building a package, you must give Ren'Py some information about the Android build of your game. To do this, choose "Configure" from the Android screen of the Ren'Py launcher.

If you need to change the information - for example, if you release a new version of your game - you can re-run the configure command. Your previous choices will be remembered.

Step 4: Build and Install the Package

Finally, you can build and install the package. This is done with a by connecting your Android device to your computer, and choosing "Build & Install" from the Android screen of the Ren'Py launcher. (The first time you install, your Android device may ask you to authorize your computer to install applications.)

If you'd rather copy the game's apk file to your Android device manually, choose "Build Package" from the Android screen of the Ren'Py launcher. Then navigate to the 'bin' directory underneath the RAPT directory and copy the file mygame-release.apk into your Android Device. You will then need to find the .apk file in your Android device using a file manager application and open it to install the game.

Viewing Debug Output

Debug output can be found by running the adb command manually from the terminal. After installing the SDK, the adb command can be found as rapt-dir/android-sdk/platform-tools/adb. (On Windows, use adb.exe.)

To view output from Ren'Py, consider a command line like:

adb logcat -s python:*

Icon and Presplash Images

There are several special files that are used to set the icon and presplash images used by the package. These files should be placed in the base directory.

The icon that's used for the app in the Android launcher. This icon is automatically scaled down to the appropriate size, and should be larger that 144x144.

If present, these are used in preference to android-icon.png for screens of the given densities. This allows for pixel-perfect icons. Available screen densities and the corresponding icon sizes are:

  • ldpi (36x36)
  • mdpi (48x48)
  • hdpi (72x72)
  • xhdpi (96x96)
  • xxhdpi (144x144)
The image that's used when the app is loading. This should be surrounded by a monocolored border. That border is expanded to fill the screen.
A 732x412 icon that's used on the OUYA console.

Google Play Expansion APKs

Ren'Py optionally supports the use of expansion APKs when used on a device supporting Google Play. Expansion APKs allow Google Play to host games larger than 50MB in size. Please see:

For information about expansion APKs work. Right now, only the main expansion APK is supported, giving a 2GB limit. When an Expansion APK is created, all game files will be placed in the expansion APK. Ren'Py will transparently use these files.

To configure your game to use Expansion APKs, you'll need to set two variables:

build.google_play_key = "..."

This is the Google Play license key associated with your application, which can be found on the "Services & APIs" tab associated with your application in the Google Play developer console. (Be sure to remove all spaces and newlines from the key.)

build.google_play_salt = ( ... )

This should be a tuple of 20 bytes, where each byte is represented as an integer between -128 and 127. This is used to encrypt license information returned from Google Play.

A valid (if insecure) value for this variable is:

(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19)

RAPT will place the expansion APK on the device when installing the APK package on the device. The expansion APK will be an .obb file found inside the bin subdirectory of the RAPT directory.

In normal operation, Google Play will place the expansion APK on the device automatically when the user installs the application.