We released a first alpha build last week, and we want to keep a relatively short iteration cycle on future alpha and beta builds until the final 3.2 release. The new official buildsystem that our contributor HP van Braam (hpvb) set up for us is now quite efficient, so we can roll out builds fast and easily.

We thus publish Godot 3.2 alpha 2 as a second snapshot, fixing various issues from the last build. 152 commits have been merged since 3.2 alpha 1. This release is built from commit 3cc94b2.

As a reminder, the alpha stage corresponds for us to a feature freeze, as announced on GitHub a month ago, which means that we will no longer consider pull requests with new features for merge in the master branch, and that until Godot 3.2 is released. This way, we can focus on what we already have, finish and polish the major features which are still in progress, and fix many of the old and new bugs reported by the community.

Note: Illustration credits at the bottom of this page.


IMPORTANT: This is an alpha build, which means that it is not suitable for use in production, nor for press reviews of what Godot 3.2 would be on its release.

There will still be various fixes made before the final release, and we will need your detailed bug reports to debug issues and fix them.

There is also no guarantee that projects started with an alpha build will still work in later alpha builds, as we reserve the right to do necessary breaking adjustments up to the beta stage (albeit compatibility breaking changes at this stage should be very minimal, if any).

The features

Release notes are not written yet, but you can refer to the detailed changelog that our contributor Hugo Locurcio is working on.

Our past devblogs should also give you an idea of the main highlights of the upcoming release. Note that the Vulkan port outlined in Juan’s latest posts is developed in a separate branch for Godot 4.0, and is not included in this release.

Documentation writers are hard at work to catch up with the new features, and the latest branch should already include details on many of the new 3.2 features.

For changes since the previous alpha build, see the list of commits.


The download links are not featured on the Download page for now to avoid confusion for new users. Instead, browse one of our download repository and fetch the editor binary that matches your platform:

  • Classical build (GDScript, GDNative, VisualScript).
  • Mono build (C# support + all the above). You need to have MSbuild installed to use the Mono build. Relevant parts of Mono are included in this build.

IMPORTANT: Make backups of your Godot 3.1 projects before opening them in any 3.2 development build.


  • Due to some build issues alpha1 does not have export templates for the UWP platform. This will be fixed in later builds.
  • The alpha 1 issue with release exports of Mono projects should now be solved.
  • This build should also fix a regression for GLES2 rendering on some Windows and macOS devices.

Bug reports

There are still hundreds of open bug reports for the 3.2 milestone, which means that we are aware of many bugs already. Yet, many of those issues may not be critical for the 3.2 release and may end up be retargeted to a later release to allow releasing Godot 3.2 within a couple of months.

As a tester, you are encouraged to open bug reports if you experience issues with 3.2 alpha. Please check first the existing issues, using the search function with relevant keywords, to ensure that the bug you experience is not known already.

The illustration picture is from the gorgeous puzzle platformer Seedlings by Bardsley Creative. Follow its development on Twitter and play the recently updated demo on itch.io.