Publish to Play Store (Android)

How to publish your Thunkable project in the Google Play Store

Publishing your app to the Play Store is a relatively straightforward process and will help your app reach 2 billion active Android devices.

Success on Google Play starts with quality. The best apps and games have higher ratings, more installs, and more engagement. We recommend visiting the Play Store Developer Policy Center before you submit your app to the Play Store

Minimum requirements

  • Google Play Developer Account ($25 one-time fee). Don't have an account? Sign up here****

App info

To publish your app on Android, you'll need to add an app icon, a name, a package name and an app version. To find the App settings, click on the App Icon on the top left.

For recommendations on your app icon and name, please see this guide.

Each Android app that is published to the Play Store has a unique package name. Currently, you can enter this in the App (Bundle) ID field.

If you are only publishing to the Play Store, you do not need to enter a Team ID to publish to the Play Store (this is for iOS only)

Before you download your app, make sure you set the appropriate Build and Version Number. Google Play requires each new version of your app to have a unique and sequentially higher Build and Version Number. You can also let Thunkable auto-increment (or automatically increase) the build and version numbers for you.

Download your Android app

Select Download or Publish Android App and an .apk file will be generated on your desktop

Submit your app for review

Create a new app on the Google Play Developer Console

Next, create a new release. This is where you'll upload the latest version of your app (.apk)

Enable Google Play App signing. This is an optional program but we recommend it for most use cases.

Drag and drop your app (.apk) to the console

Update your Play store listing

To complete your Play Store listing, you will have to fill out a content rating questionnaire and set pricing and availability. In addition you will need to add a minimum of 4 design assets - two screenshots, a higher resolution icon (512 x 512 px) and a feature graphic (1024 x 500 px) that shows up on the Play Store app.

App screenshots
High resolution app icon (512 x 512 px)
Feature Graphic (1024 x 500 px)

Add a privacy policy

Apps that request access to sensitive permissions or data (as defined in the user data policies) are required by the Google Play Store to include a privacy policy. Currently all apps made on Thunkable request access to sensitive permissions or data, which means you will need to provide a privacy policy

Congrats! You are now ready to submit to the Play Store.

Updating an existing app on the Play Store

If you updating an existing app on the Google Play Store, your app will need to have the i) same package name, ii) a higher or incremented version number, and the iii) same keystore.

You can modify the first two in the App Settings page but you will need to follow the directions below to export / import a keystore if you are updating an app on the Google Play store that was originally created in Thunkable Classic or another platform.

Keystores in Android are storage mechanisms for security certificates to prevent others from updating your app on the Google Play store. Copied apps within an account (using the Make Copy) will keep the same keystore as the original app. Apps that are copied from a Share copy link will not have the same keystore.

Exporting / importing a keystore from Thunkable Classic

Thunkable Classic is retiring soon! We highly recommend you rebuild your apps in the Thunkable Cross-platform and import your keystore if your app is published to the Google Play Store

Export keystore from Thunkable Classic

Go to Thunkable Classic ( click Apps (in the upper left corner) and then Export keystore to save your Classic android.keystore file to your computer.

Import keystore to Thunkable X

On the Thunkable Cross Platform (, select the the app that you have previous published from Classic and are trying to update from X.

Click the name and icon of your app in upper left corner to bring up App Settings on right side.

Scroll all the way to the bottom of App Settings and click Import Keystore. Note this will replace the existing keystore for this app so be sure you havenโ€™t used it to publish to Google Play store before proceeding. You can always Export it first and save it to your computer just in case.

Enter โ€œandroidโ€ as the password

Enter โ€œandroidโ€ as the password and select the android.keystore file you previously saved to your computer from Classic.

Congrats! You should be able to successfully publish updates now. Note that youโ€™ll need to repeat the steps for each app you previously published with your Classic keystore as every app has their own keystore.

Export keystore from Thunkable X

If you make a copy of a Thunkable X app project, the copy will have a different keystore to the original project.

To export a keystore from a Thunkable X app project, Click the name and icon of your app in upper left corner to bring up App Settings on right side as seen in 'Import keystore to Thunkable X'. Scroll all the way to the bottom of the App Settings and click Export Keystore.

In the dialog that comes up, you will see the keystore's password and a button that says Export Keystore. You will need this password to import your keystore to other projects.

The keystore password and export button

Note: A Thunkable X app project will not have a keystore until either a keystore is imported or the project is downloaded as an Android app for the first time