Skip to content

Godot 4.7 for mobile games: what changed and what to set up (2026)

Godot 4.7 is a tooling release for mobile, not a rendering one. The Gradle build is no longer marked experimental, a game can now be built and exported as an App Bundle on an Android device, splash screens are set in the export options, and a virtual joystick node is built in. Use 4.7.2, install JDK 17 and the Android SDK packages named in the engine's own build configuration, switch on the Gradle build, and export a signed AAB. For iOS you still need a Mac with Xcode.

By Futigo · Updated · 11 min read

Key points

  • Godot 4.7 was released on 18 June 2026. The current patch is 4.7.2, from 18 August 2026, and its release article lists no known incompatibilities with 4.7.1.
  • The Android build configuration in 4.7.2 sets target SDK 36, compile SDK 36, minimum SDK 24, Build-Tools 36.1.0, NDK 29.0.14206865 and Java 17. The 4.7 export page still lists the older SDK 35 packages.
  • New in 4.7: projects that use a Vulkan renderer (Mobile or Forward+) default to minimum SDK 29. Projects on the Compatibility renderer keep minimum SDK 24.
  • Google Play needs an Android App Bundle, and Godot only exports one through its Gradle build. Ads, billing and Play Games plugins need the Gradle build too.
  • Godot 4.8 is in beta (beta 3 on 9 November 2026) and adds automatic Android and Java SDK setup. It is not a stable release yet.

What 4.7 changed for mobile

The 4.7 release page leads with HDR output, area lights and a new Asset Store. The parts that matter on a phone are further down the page and in the changelog. None of them comes with a performance or file size figure for phones, so we give none.

Godot 4.7 changes that affect Android and iOS games, with the reason each matters and its source
Change in 4.7Why it matters on mobileSource
Godot Android Build Environment (GABE) declared stable on 2 June 2026The Android editor can run Gradle exports on the device, so AAB files and plugin builds no longer need a PCGABE stable release article
Experimental warning removed from the Use Gradle Build optionThe build path that Play Store releases depend on is now treated as a normal featureChangelog, GH-119172
Splash screen settings in the Android export optionsIcon, background colour and branding image no longer need hand-edited Android resource files. Godot's own boot splash can be switched offRelease page, GH-114671
Default minimum SDK is 29 for Vulkan renderers and 24 for CompatibilityA Mobile renderer game excludes devices below API 29 unless you change the settingGH-117355, GH-118942, export code at 4.7.2
Google Play OBB expansion file support removedOld projects that relied on OBB files must move to App Bundles or a separate pluginChangelog, GH-118283
Built-in VirtualJoystick node with Fixed, Dynamic and Following modesOn-screen sticks no longer need an add-on or your own codeRelease page, GH-110933
Multitouch support in BaseButtonButtons respond to screen touch events, so two can be held at onceChangelog, GH-110893
Workarounds for Adreno GPUs: ubershaders disabled on problematic compiler versions, and a fix for pipeline compilation errors on Adreno 660Fewer driver-specific failures with the Mobile renderer on Qualcomm phonesChangelog, GH-119639 and GH-120363
Picture-in-picture on AndroidA game can keep running in a small floating window. Android only for nowRelease page
Perfetto is the default tracing tool for Android buildsProfiling uses Android's standard tracing toolsRelease page, GH-118401
iOS: SDL3 for controllers, UIScene lifecycle events, one-click deploy fixed for Xcode 26Better default controller mappings and fewer export problems on current XcodeRelease page, changelog GH-116395 and GH-118559
Export templates can be downloaded per platform and architectureAn Android-only studio no longer downloads templates for every platformRelease page, GH-117072
New projects default to stretch mode canvas_items and aspect expandNew projects scale to different phone screens without extra setup. Existing projects are unchanged4.7 migration guide
2D: scene paint mode, one-way collision in any direction, DrawableTexture2D, offset transforms for Control nodesFaster level layout and simpler UI animation in 2D gamesRelease page

From godotengine.org/releases/4.7, the GABE article, the 4.7 migration guide and CHANGELOG.md at the 4.7.2-stable tag. GH numbers are pull requests in godotengine/godot. Checked on 15 November 2026.

One correction to a common assumption: target API 36 and NDK r29 are not new in 4.7. The build configuration at the 4.6-stable tag has SDK 35 and NDK r28b, and the one at 4.6.3-stable already has SDK 36 and NDK r29. 4.7 ships with those values from its first release. Support for 16 KB memory pages follows from the NDK: Google's page size guide says NDK r28 and higher build 16 KB aligned libraries by default.

The two patch releases are bug fixes. 4.7.1 fixed backspace on the Android soft keyboard and a drag and drop regression on touchscreens. 4.7.2 carries 57 fixes from 39 contributors.

The Android export setup, step by step

The official Android export page for 4.7 still names Build-Tools 35.0.1, SDK Platform 35 and NDK r28b. The engine's own build configuration at the 4.7.2 tag uses newer ones. We list the versions from the build configuration, because that file is what the Gradle build compiles against. The in-development docs for 4.8 already name the same newer versions.

Godot 4.7.2 Android and iOS export setup checklist: JDK, SDK packages, Gradle build, signing, icons and iOS requirements
StepWhat to install or setNotes
JavaOpenJDK 17The docs say higher versions also work but recommend 17. The build configuration sets Java 17
Android SDK packagesPlatform-Tools, Build-Tools 36.1.0, SDK Platform 36, Command-line Tools (latest), NDK 29.0.14206865, CMakeVersions from the 4.7.2 build configuration. The 4.7 docs page lists 35.0.1, Platform 35 and NDK r28b
Editor settingsJava SDK Path and Android SDK PathThe SDK folder must contain platform-tools/adb. On Linux, do not use your distribution's SDK package
Export templatesEditor, Manage Export TemplatesIn 4.7 you can install Android templates only
Gradle buildProject menu: install the Gradle Build template, then enable Gradle Build in the Android presetCreates res://android/build. Needed for AAB export and for Android plugins
Export formatSet the export format to AABGoogle Play has required App Bundles for new apps since August 2021
SDK levelsLeave target SDK at the default 36. Minimum SDK defaults to 24 on Compatibility and 29 on MobilePlay requires new apps and updates to target API 36 from 31 August 2026
Release keystoreCreate one with keytool, then fill in Release, Release User and Release PasswordThe keystore password and key password currently have to be the same. Untick Export With Debug
Play App SigningSet it up in Play Console before the first uploadGoogle holds the app signing key. Your keystore becomes the upload key
Package and versionUnique name in reverse-DNS form. Raise the version code for every releaseLowercase letters, digits, underscores and full stops only
PermissionsTick only what the game uses, for example Internet for network accessEach Android permission is a separate export option
IconsMain icon at least 192×192. Adaptive foreground and background at least 432×432. Optional monochrome iconKeep the important part inside the centred 66 dp safe zone, which is 264 pixels at this size
Splash screenIcon, background colour and optional branding image in the export optionsNew in 4.7. The background colour applies to Gradle builds only
iOSA Mac with Xcode, the iOS export templates, an App Store Team ID and a bundle identifierGodot exports an Xcode project. The default minimum iOS version in the 4.7.2 export code is 15.0

Versions from platform/android/java/app/config.gradle and the Android and iOS export code at the 4.7.2-stable tag. Steps from the Godot 4.7 export docs and class reference. Play rules from developer.android.com. Checked on 15 November 2026.

The Gradle build page notes that the native engine library stays precompiled, so you do not need a C++ toolchain. It also has one trap: assets inside a folder whose name starts with an underscore are left out of the build.

On signing, Google's app signing guide says App Bundles defer building and signing APKs to the Play Store, so Play App Signing must be configured before you upload a bundle. Keep the upload keystore and its password backed up. On target level, Google's target API page sets API 36 for new apps and updates from 31 August 2026, with an extension available to 1 November 2026.

For iOS, the export page says you must export from a computer running macOS with Xcode installed. It names no Xcode version. It also warns that the iOS simulator supports only the Compatibility renderer.

Mobile or Compatibility renderer

Godot has three renderers, and two are meant for phones. The renderer overview describes them this way:

  • Compatibility uses OpenGL. The docs call it the least advanced renderer, suited to low-end desktop and mobile hardware, and say it supports the widest range of devices. They suggest it for 2D games, for 3D games that do not need advanced features, and for web, where it is the only choice.
  • Mobile uses Vulkan or Metal. It is the default on mobile platforms, with fewer features than Forward+ but faster rendering of simple scenes. The docs suggest it for newer phones and for 3D games that want advanced features. It runs on old hardware, but slower than Compatibility.
  • Forward+ is supported on mobile but described as poorly optimised there. The docs say to use Mobile or Compatibility instead.

For 2D, the same page says Mobile works but Compatibility is usually good enough. Two export details follow from the choice. A Mobile renderer project gets minimum SDK 29 by default in 4.7, and the export check only accepts a lower value when the Fallback to OpenGL 3 project setting is on. The shader baker export option, which compiles shaders into the app, is supported only with Forward+ or Mobile.

The release page says the Mobile renderer now matches or beats Compatibility in a number of benchmarks. That sentence is about foveated rendering in XR headsets. It gives no figures and is not a claim about phones.

Plugins a mobile game usually needs

Godot ships no ads, billing or store services. All of these are Android plugins that need the Gradle build. None is maintained by the Godot Foundation: the godot-sdk-integrations organisation describes its SDKs as community-maintained and not endorsed by the Foundation, and godot-mobile-plugins calls itself a collection of community-maintained plugins.

Godot mobile plugins for ads, Play Billing, Play Games Services, in-app review and notifications: licence, latest release and maintainer
PluginPurposeLicenceLatest releaseMaintained by
[godot-admob-plugin](https://github.com/poingstudios/godot-admob-plugin)AdMob ads on Android and iOS, GDScript and C#MITv5.1.0, 13 September 2026Poing Studios (community). README states Godot 4.5.0 and above. Release notes say tested through 4.7.2
[godot-admob](https://github.com/godot-sdk-integrations/godot-admob)Google Mobile Ads on Android and iOS, GDScriptMITv7.0, 27 May 2026godot-sdk-integrations (community)
[godot-google-play-billing](https://github.com/godot-sdk-integrations/godot-google-play-billing)Google Play purchasesMIT3.3.0, 27 July 2026, on Billing Library 9.1.0godot-sdk-integrations (community). README states Godot 4.2 and above
[godot-play-game-services](https://github.com/godot-sdk-integrations/godot-play-game-services)Play Games sign-in, leaderboards, achievements, saved gamesMITv3.4.0, 20 July 2026godot-sdk-integrations (community). README states Godot 4.3 and above
[godot-inapp-review](https://github.com/godot-mobile-plugins/godot-inapp-review)Native review prompt for Google Play and the App StoreMITv5.3, 25 May 2026godot-mobile-plugins (community). Release notes say tested against Godot 4.7
[godot-notification-scheduler](https://github.com/godot-mobile-plugins/godot-notification-scheduler)Local notifications on Android and iOSMITv6.0, 13 June 2026godot-mobile-plugins (community). Release notes say tested against Godot 4.7
[godot-storekit2](https://github.com/godot-sdk-integrations/godot-storekit2)In-app purchases and subscriptions on iOSMITv0.2, 18 September 2025godot-sdk-integrations (community). Last push April 2026

Licence, latest release and release date from the GitHub API for each repository. Supported Godot versions as stated in each README or latest release notes. All six Android-capable repositories had commits between July and November 2026. Checked on 15 November 2026.

Check each plugin's native libraries as well as the engine. The AdMob plugin's v5.1.0 notes say its Android side compiles against SDK 35, which is one level behind the engine. That is not an error by itself, but it shows that plugins move on their own schedule. For how this compares with first-party SDKs elsewhere, see Godot vs Unity and Flutter vs Godot.

Keeping the APK or AAB small

Godot's documentation gives no typical size for an Android export, so we quote none. It does document these ways to reduce it:

  • Upload an AAB. Google's signing guide says the App Bundle format makes an app smaller, because Play builds the APKs for each device.
  • Choose architectures on purpose. The Android preset has a tick box each for arm64-v8a, armeabi-v7a, x86 and x86_64, and each one adds that architecture's binaries.
  • Leave native library compression off for Play. The export option reference says compression can shrink the binary but slow startup, and recommends keeping it off when distributing through the Play Store.
  • Export only what the game uses. The export preset's resource options can export only selected scenes or resources with their dependencies, and have filters to exclude files.
  • Compile a custom export template. The size guide says disabling 3D reduces the binary by about 15%. It also covers size-optimised builds, a build profile that detects unused engine features, and a lighter fallback text server.

Be careful with the last item. The docs say the fallback text server is enough only for Latin, Greek and Cyrillic based languages, so a game with Hindi or Tamil text should keep the default one. Custom templates also mean compiling the engine from source. Feature tags such as mobile and android can override project settings per platform, which is useful for options you want only on phones.

Upgrading a project from 4.6

The migration guide says most 4.6 projects should be relatively safe to move. These are the items most likely to touch a 2D mobile game:

  • Line drawing. CanvasItem no longer adds an antialiasing feather when drawing lines. Lines look thinner than in 4.6, so art drawn in code may need wider line widths.
  • Input device IDs. Mouse and keyboard events no longer use device ID 0. Check the event type, or compare with InputEvent.DEVICE_ID_MOUSE and InputEvent.DEVICE_ID_KEYBOARD.
  • GDScript return types. A method that overrides one with a typed return now inherits that type and needs an explicit return statement.
  • Audio bus overrides. The default area mask of AudioStreamPlayer changed from 1 to 0, which stops Area2D bus overrides until you set the mask again.
  • Removed and renamed. AudioEffectSpectrumAnalyzer.tap_back_pos is removed, and a RichTextLabel image enum value is renamed.
  • OBB files. Play Store OBB support is gone from the engine, as listed in the changelog.

The new stretch defaults apply only to newly created projects. Back up or commit first: the 4.7.1 and 4.7.2 articles both recommend a backup or version control before upgrading. On a Mac, Godot now needs macOS 11 or later.

What is coming in 4.8

Godot 4.8 is in development and not stable. Beta 1 came out on 15 October 2026 and beta 3 on 9 November 2026. The beta 1 notes describe automatic download and setup of the Android and Java SDKs from the editor, native touch support for more GUI controls, and decals in the Compatibility renderer. Do not ship a game on a beta.

What we do at Futigo

We build most of our games in Godot 4.7. Some use the Compatibility renderer, for example Ants Flood Escape, Power Cut and Mithai Match-3. Others use the Mobile renderer, for example Claywheel, 10-Minute Rider and Night Auto.

For ads we use a community AdMob plugin, which means every release goes through the Gradle build described above. For a wider view of engine choices, see our open-source engine comparison.

Questions

What is new in Godot 4.7 for Android games?
The Gradle build is no longer marked experimental, the Godot Android Build Environment lets the Android editor export AAB files on the device, splash screens are set in the export options, and a VirtualJoystick node is built in. Projects on a Vulkan renderer now default to minimum SDK 29.
Which JDK and Android SDK versions does Godot 4.7 need?
OpenJDK 17 is the recommended JDK. The Android build configuration in Godot 4.7.2 uses SDK Platform 36, Build-Tools 36.1.0 and NDK 29.0.14206865, although the 4.7 export docs page still lists the older SDK 35 packages.
Does Godot 4.7 meet Google Play's API level 36 requirement?
Yes. Godot 4.7.2 targets API level 36 by default, which Google Play requires for new apps and updates from 31 August 2026. It builds with NDK r29, and Google says NDK r28 and higher produce 16 KB aligned libraries by default.
How do I export an AAB from Godot 4.7?
Install the Gradle Build template from the Project menu, enable Gradle Build in the Android export preset, set the export format to AAB, and sign with a release keystore. Google Play requires Play App Signing to be set up before you upload the bundle.
Should I use the Mobile or Compatibility renderer for a 2D mobile game?
Godot's docs say Compatibility is usually good enough for 2D and supports the widest range of hardware. Mobile is the default on mobile platforms and is aimed at newer phones and games that need more advanced rendering features.
Can I export a Godot 4.7 game to iOS from Windows or Linux?
No. The Godot docs say you must export for iOS from a computer running macOS with Xcode installed. Godot produces an Xcode project that you then build and submit from Xcode.