Godot Engine Official

Dev snapshot: Godot 4.7 dev 5

Thaddeus Crews — Fri, 17 Apr 2026 12:00:00 +0000

As is tradition at this point: feature freeze arrived, and so too did countless last-minute pull requests from contributors. So despite the previous development snapshot releasing just one week ago, there’s no shortage of brand-new goodies ready to be experienced firsthand!

Please consider supporting the project financially, if you are able. Godot is maintained by the efforts of volunteers and a small team of paid contributors. Your donations go towards sponsoring their work and ensuring they can dedicate their undivided attention to the needs of the project.

Jump to the Downloads section, and give it a spin right now, or continue reading to learn more about improvements in this release. You can also try the Web editor, the XR editor, or the Android editor for this release. If you are interested in the latter, please request to join our testing group to get access to pre-release builds.

The cover illustration is from Lost Wiki: Kozlovka, a detective game where you explore a Wikipedia-esque database to solve a small-town mystery in 90s Eastern Europe. You can buy the game on Steam, and follow the developer on Bluesky, YouTube, or itch.io.

Highlights

Assetlib: Port asset store to new API

Did you know we have an overhaul to our asset store in the works? Well… Now you do! Michael Alexsander has been hard at work bringing our current system into this new paradigm, culminating in GH-112992 fully supporting the new API. While we hope to showcase details on this new system in the future, for now we’ll simply highlight the more obvious improvements that this PR delivers.

Starting with the main selection screen, the way we display our asset items has been polished. Not only will it be easier to parse the asset items themselves, but more metadata and the current rating will be readily visible.

When accessing an asset in isolation, you’ll have immediate access to the current description and all existing changelogs. What’s more, the ability to change an asset’s version is now just one click away.

Editor: Rework export template dialog to allow individual templates

A long-standing pain point for anyone that’s worked with export templates has been that they must be downloaded in bulk. This was in contrast to how our editor downloads were always isolated, causing the export templates to incur long download times for a range of platforms that aren’t necessarily relevant to a developer’s intended export targets.

This could be solved in two main ways: overhauling our existing distribution system to make the packages available in isolation, or somehow repurposing the existing bulk distribution to only distribute a subset of options.

Despite how absurd it sounded, Tomasz Chabora managed to implement the latter! GH-117072 managed the seemingly-impossible task of hijacking the bulk package and retrieving slices of the developer’s choosing. This is all achieved within the Godot editor itself, making the process as seamless and expedient as possible for users.

GUI: Enable scaling images relative to font size in `RichTextLabel`

Malcolm Anderson brings new life to [img] tags in RichTextLabel with GH-112617. Now width and height can specify em for their scaling. This would result in the following text…

Do you have any [img height=1em]coin.png[/img] coins?
...I said, [font_size=50]DO YOU HAVE ANY [img height=1em]coin.png[/img] COINS??[/font_size]

…displaying like this:

Shaders: Implement inline text shader previews

A long-awaited quality-of-life addition to the text shader editor comes courtesy of Yuri Rubinsky, with his PR GH-117726 bringing inline previews. This is a C++ implementation of Godot Shader Previewer, a popular addon written in GDScript by Cashew OldDew. Much like the addon before it, this aims to reduce the amount of guesswork when constucting text shaders, as now one can readily see the resulting effects within the text editor itself:

Rendering: Add rectangular area light source

Rendering has received a lot of love in these snapshots, and we’re ending things off strong with Emil Dobetsberger’s work in GH-108219 delivering rectangular area light sources. By leveraging the new AreaLight3D, it’s now possible to render real-time light from a rectangle in 3D space.

And more!

There are too many exciting changes to list them all here, but here’s a curated selection:

3D: Add vertex snap support for subgizmo points (GH-117922).
Audio: Revamp audio bus UI (GH-118266).
Editor: Allow moving and resizing the embedded game window on Android (GH-118417).
Editor: Improve Remote/Local SceneTreeDock buttons’ appearance (GH-118192).
Export: Android: Add export options to customize splash screen (GH-114671).
GDExtension: Add Variant::get_type_by_name to GDExtension Interface (GH-117160).
Input: Wayland: Implement touch support (GH-113886).
Platforms: Change embedded window options to use three stacked dots and add HDR info (GH-118079).
Rendering: Refactor raytracing pipelines (GH-118044).

Changelog

71 contributors submitted 135 fixes for this release. See our interactive changelog for the complete list of changes since 4.7-dev4. You can also review all changes included in 4.7 compared to the previous 4.6 feature release.

This release is built from commit a8643700c.

Downloads

Download Godot 4.7 dev5

Linux

macOS

Windows

Export templates and other downloads Make a Donation

Standard build includes support for GDScript and GDExtension.

.NET build (marked as mono) includes support for C#, as well as GDScript and GDExtension.

While engine maintainers try their best to ensure that each preview snapshot and release candidate is stable, this is by definition a pre-release piece of software. Be sure to make frequent backups, or use a version control system such as Git, to preserve your projects in case of corruption or data loss.

Known issues

With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of known bugs.

There are currently no known issues introduced by this release.

Bug reports

As a tester, we encourage you to open bug reports if you experience issues with this release. Please check the existing issues on GitHub first, using the search function with relevant keywords, to ensure that the bug you experience is not already known.

In particular, any change that would cause a regression in your projects is very important to report (e.g. if something that worked fine in previous 4.x releases, but no longer works in this snapshot).

Support

Godot is a non-profit, open-source game engine developed by hundreds of contributors in their free time, as well as a handful of part and full-time developers hired thanks to generous donations from the Godot community. A big thank you to everyone who has contributed their time or their financial support to the project!

If you’d like to support the project financially and help us secure our future hires, you can do so using the Godot Development Fund platform managed by the Godot Foundation. There are also several alternative ways to donate which you may find more suitable.

Donate now

Godot Mobile update — April 2026

Fredia Huya-Kouadio — Sat, 11 Apr 2026 21:00:00 +0000

Major improvements ahead!

Mobile games represent about half of global game revenue and are the largest market segment for games, ahead of consoles and PC. In terms of user base, that share is even higher. From the latest Godot community polls, about 49% of Godot developers target mobile platforms. Mobile is therefore a major outlet for Godot games and apps, and improvements as to how Godot can be used in this area are crucial.

A great deal of effort has recently been invested by the community and the Godot Foundation into improving Godot’s mobile capabilities, culminating in the Godot 4.6 and Godot 4.5.2 releases. Much of the recent “mobile export” work has focused on critical fundamentals: repeatable builds, fewer device-specific surprises, and smoother testing. Below is an overview of some of those efforts.

1. Android and iOS ecosystem plugins

The mobile game and app ecosystem relies on business models such as in-app purchases and advertising that differ significantly from the premium game model common on PC and consoles. Supporting these models requires the ability to connect apps to Apple’s and Google’s SDKs for store services and player engagement features, as well as to a wide range of third-party services dedicated to mobile gaming.

The Godot Foundation has decided to begin improving and maintaining the core plugins such as Godot Google Play Billing, Godot Google Play Games Services, and Godot StoreKit 2 to integrate with Apple’s and Google’s SDKs. These plugins are required to handle in-app purchases, achievements, leaderboards, and other features offered by the official stores and player engagement programs of the two main platforms.

While third-party plugins may still be needed for additional services, this initiative should enable Godot developers to meet the standard minimum requirements for publishing games and apps, and to reach billions of mobile users worldwide. Improved documentation on exporting and integrating plugins will hopefully improve developers’ experience in this field.

You can also find other community-maintained plugins under https://github.com/godot-sdk-integrations.

2. Mobile GPU and rendering compatibility

A major source of mobile stability issues lies in the wide diversity of GPU drivers in the wild, particularly on Android, which spans more than 12,000 different devices. Because crash and latency rates are closely monitored by Apple and Google, and directly affect user reviews and store visibility, keeping these metrics low is essential.

Thanks to detailed feedback from Kamaeru: A Frog Refuge from Humble Reeds, and Rift Riff from Adriaan de Jongh, two Godot games that reported crash data and issues following their launch on mobile stores in December 2025, Godot Foundation contractors were able to fix several problems related to rendering and GPU API usage. These changes included fixing our usage of the Vulkan API as well as identifying workarounds for certain broken GPU drivers. As a result of the fixes, both games saw their crash rates go from ~4% to less than 1%.

3. Mobile platforms stability

Additional work to improve the reliability and stability of the mobile platforms, and provide developers with the means to identify, address and / or report crashes were undertaken in the Godot 4.5 and 4.6 development timeline.

Godot 4.5 saw the addition of native debug symbols for Android. Native debug symbols for official templates are provided for every Godot release, while instructions are provided for generating equivalent native debug symbols for custom builds. In addition, the documentation was updated to provide detailed instructions for using them with the Google Play Console. This improvement was key to address the mobile GPU and rendering compatibility issues described in the previous section.

Support for Android instrumented tests was added in Godot 4.6. This is a valuable tool for engine developers as it provides the ability to continuously, automatically run a series of tests on physical Android devices through services like Google Firebase Test Lab in order to validate the stability of the platform and catch any regressions that may slip in. We are aiming to increase the test suite coverage to a significant extent, and run it on a wide range of Android devices in order to pre-emptively catch issues Godot developers may run into. At the moment though, we are running into the limitations of the Google Firebase Test Lab free tier regarding how many devices we can run the Godot engine test suite against. As such we welcome any and all community support and contributions toward addressing that blocker and reaching our goal to run on as many Android devices as possible.

Support for several tracing profilers, including Perfetto for Android and Instruments for Apple, were added to enable engine developers the ability to profile and trace the engine at a system level, opening the path for continuous and more granular improvements to the engine.

4. Mobile workflows improvements

Support for mirroring connected Android devices directly from the editor was added in Godot 4.6. This enables developers to interact with their project running on Android devices and allow them to test different screen sizes directly from their workstation, which improves iteration speed when developing and testing against Android devices.

iOS was not overlooked either, gaining logic that automatically enables export settings designed to reduce the risk of shipping builds that can technically be installed on certain devices but cannot run reliably.

What’s next?

The improvements made to Godot’s mobile platforms mark an important step toward making the engine a great choice for mobile games and apps.

With these efforts on reliability, stability, and real-world production needs, the improvements to the mobile workflow, and the focus toward providing and improving mobile ecosystem plugins, we hope that the experience of shipping games on mobile devices has been improved and we look forward to seeing the great creations to come.

Looking ahead, this work is far from finished. Mobile platforms continue to evolve, with new hardware, operating system constraints, and store requirements appearing every year. Future efforts will build on the progress made so far, with continued improvements to rendering, performance, testing infrastructure, plugin coverage, and development workflows with the aim of making Godot mobile support as polished as Godot desktop support.

The cover illustration is from Spin Hero, a roguelike deckbuilder where you spin the reels to decide your fate, collect powerful symbols for your inventory, adapt and evolve your strategy, and learn from defeats to unlock new possibilities and synergies. Spin Hero was created by Goblinz Studio, an indie game developer and co-producer from France. You can buy the game on Steam, GOG, Google Play, and the App Store, and follow the developers on YouTube or Bluesky.

Dev snapshot: Godot 4.7 dev 4

Thaddeus Crews — Thu, 09 Apr 2026 12:00:00 +0000

As we edge ever closer to feature freeze, many of our contributors have been hard at work to get their highly-anticipated features in hopes of Godot 4.7 integration. Fortunately for them, we’ve managed to accomodate several of these proposals, and are excited to showcase them today! Your testing will be crucial to ensure that everything listed stays in scope for a 4.7 release, so be sure to give this latest build a spin after the highlights

The cover illustration is from Poke ALL Toads, a puzzle game starring mischievous fairies on a queat to poke ALL toads. You can buy the game on Steam, and follow the developer on Bluesky, YouTube, or itch.io.

Highlights

Rendering: Add nearest-neighbor scaling

We’re starting things out with one of the most anticipated integrations for our rendering system: nearest-neighbor scaling for 3D viewports. Over the course of nearly three years, Hugo Locurcio has been refining GH-79731 to ensure that 3D titles with pixel-art aesthetics or lower resolution scaling will still look crisp without any compromise to performance:

Bilinear

Nearest (new behavior)

GUI: Add `custom_maximum_size` property to `Control`

Our previous development snapshot had a large focus on GUI improvements, and that QOL continues with the new custom_maximum_size property for Control. Enzo Novoselic in GH-116640 has at last brought us the maximal equivalent to the existing custom_minimum_size, enabling the fine-tuning of GUI element sizes to their full potential.

GUI: Improve drag and drop in `Tree`

vaner spear-headed GH-112993 in order to improve the overall usability and intuitiveness of Tree drag-and-drop functionality. Now when performing a drag-and-drop operation, there will be an always-present vertical indicator showing the potential parental chain, leveraging a standalone CanvasItem to prevent StyleBox occlusion.

Old	New

What’s more, this operation will now consider the x-position of the cursor while determining a to-be parent when in indent space (leftmost, empty space), whereas item space largely retains current behavior. This implementation mirrors what one would commonly find in vector design software.

Editor: Increase available space for array properties

Have you ever wondered why the inspector takes up so much negative space when working with arrays? Turns out it wasn’t done deliberately; it just so happened to be using the default offset of 0.5! Tomasz Chabora rightfully found this quite silly, and whipped up GH-118008 to rectify this oversight.

Old	New

And more!

There are too many exciting changes to list them all here, but here’s a curated selection:

2D: Rework TileSet editor proxy objects (GH-117574).
3D: Add vector components to 3D ruler tool (GH-106785).
Editor: Add folding to the Visual Profiler tree (GH-118120).
Editor: Add type filters to create dialog (GH-111518).
Editor: Hide renderer selector in main editor window and add editor setting (GH-117754).
Editor: Make right-clicking on unfocused scene tabs possible (GH-112919).
GDExtension: Allow viewing GDExtensions from inside project settings (GH-118063).
GDScript: LSP: Calculate simple string insertions on the server-side (GH-117710).
Particles: Fix angular velocity (GH-117861).
- NOTE: This is technically compatibility-breaking, but it’s bringing the functionality in-line with how its always been documented.
Particles: Fix particles moving when timescale is 0 (GH-109911).
Platforms: Android: Allow implementing java interfaces from GDScript (GH-115498).
Platforms: Windows: Implement OneCore TTS support using C++/WinRT (no deps) (GH-116349).
Platforms: Windows: Use OneCore/WinRT emoji picker when available (GH-116351).

Changelog

88 contributors submitted 188 fixes for this release. See our interactive changelog for the complete list of changes since 4.7-dev3. You can also review all changes included in 4.7 compared to the previous 4.6 feature release.

This release is built from commit 755fa449c.

Downloads

Download Godot 4.7 dev4

Linux

macOS

Windows

Export templates and other downloads Make a Donation

Standard build includes support for GDScript and GDExtension.

.NET build (marked as mono) includes support for C#, as well as GDScript and GDExtension.

Known issues

With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of known bugs.

There are currently no known issues introduced by this release.

Bug reports

Support

Donate now

Godot Showcase – Xogot: Godot for iPad & iPhone

Adam Scott — Sat, 04 Apr 2026 18:00:00 +0000

We’re happy to showcase a project that released last year, but was long in the making. The folks at Xibbon have been working hard to port the Godot Engine to the iOS platforms. Not only did they port the editor to make it run on iOS, they successfully interfaced the editor with a custom iOS interface in order to make the engine match Apple strict UI and UX guidelines. Using their app on the iPad and iPhone feels totally native, because it is!

Xibbon has been active in our community, in terms of code contributions and events. Xibbon has been our sponsor at events, such as the first GodotCon in the US!

Today, Miguel de Icaza, known for starting the GNOME, Mono, and Xamarin projects, is sharing with us his experience developing his iOS app.

Can you tell us a little bit about your project?

Xogot brings the Godot Editor to the iPad and the iPhone as a native iOS application.

Xogot uses the Godot Editor and the Godot Engine, but we provide an alternative user interface and shell that is built on top of Apple’s native user interface elements. We tuned the user experience to be both touch friendly and to work with the more limited screen space on these devices.

By being a new user interface on top of the existing Godot Editor, we remain compatible with the desktop Godot and users can move seamlessly between the platforms, but we also wanted to make a product that truly belonged on the iPad, not merely running the desktop experience on the iPad.

While I am an engineer, the joy that I derive from using creative apps on the iPad is unmatched.

Interacting with the world with our fingers is one of the earliest skills that we acquire as babies - and I find the physical feedback of using touch user interfaces to be very rewarding. Not only do I spend hours playing with my iPad, I also love watching creators use their iPads for sketching, drawing, modeling, composing, editing videos, and building games.

Why did you want to build Xogot?

Xogot is very much a labor of love, the result of a perfect storm of conditions and a way of expanding our own horizons and getting out of our comfort zone.

We have worked on the mobile world for almost fourteen years, and built developer tools for helping .NET developers target mobile platforms. Mostly building IDEs and tools and supporting others on their adventures to bring software to users (among those, funding the early effort to bring .NET to Godot).

We wanted to get out of our comfort zone, and build an end-user product that followed the ethos of iOS developers that obsess over highly polished apps. Products that obsess over the details of the user experience and strive to create delightful user interfaces.

For almost sixteen years we have helped folks in the game industry adopt .NET for game development, and we supported various games, engines, and hardware vendors with their efforts to bring our compilers and tools to their systems. Just like we were inspired by the iOS community, we are inspired by the game developer community - people pouring their hearts out exploring ways of entertaining and surprising us, and we wanted to get closer to this joyful world.

Lastly, we all witnessed a major turning point in the game-engine industry when Unity’s leadership made decisions that shook developer trust across the community. We watched as the industry rushed to find alternatives - and being emotionally invested already in Godot, we were very much in the camp “How can we give the Godot community an edge?”.

What was challenging about bringing the Godot Editor to the iPad and iPhone?

This is the poster child of a slippery slope, or an extreme case of Yak Shaving.

There are three buckets of challenges:

Multi-process
User experience
Embedding

At first, we figured “How hard could it be to get Godot on the iPad?” and it turned out that running Godot on iPad was quite simple, but comes with some strings attached. The first thing you have to deal with is that the Godot workflow uses three processes: the home screen that creates new fresh Godot Editors on demand, the Godot Editor itself, and every time you press “play”, a new and fresh instance of Godot.

The challenge is that iPadOS does not really support the above model where you get a fresh new process for each step, instead you get a single process and you get to live there. Without being able to launch a new project, Godot would have worked, but would not have been very interesting to people.

We first experimented with a proof of concept which was to reset the state of Godot to one of a fresh process. That worked, and it allowed us to edit one game, and then edit a second one. We called this the “reset state” effort. That was still not quite useful. The second stage was to make the editor run a child process, and for that what we did was to “virtualize” every single global variable in Godot, so we could run multiple instances simultaneously. That turned out to work great, but it relied on a very manual process of editing a very large chunk of Godot to remove every access to globals and static variables. We later invested in a clang-based rewriter that would take an existing Godot codebase and produce a virtualized Godot on demand. This is what we are based on now.

With the above system we could open multiple projects, but also start and stop the game under development over and over. So we were now cooking with gas. One last component was not just to launch separate instances of Godot, but having those run side-by-side, which was necessary to implement debugging over a “virtual” process that happened to be running on your same address space.

We took the limitations of the platform as a fun challenge to solve, and I am incredibly proud of the result.

That was a very satisfying technical problem to solve, but it did not lend itself to a great iPad experience. Godot is designed for a desktop computer where you have a lot of space, and you can easily aim your mouse at small user interface elements. On the iPad and iPhone, Apple recommends that elements are at least 44 points in size for users to be able to interact with them comfortably. In fact, every time I thought I could get away “just this time” with a smaller user interface, I found out the hard way that neither our users nor myself could tap it. We repeatedly learned that lesson.

44 points.

It is now hanging on a printed piece of paper next to my desk, so I do not forget.

But even if we resized the controls, the user interface did not feel good on the iPad. Godot was clearly intended to be used with a mouse and a keyboard, so we set out to solve the most problematic areas for our users. Some were mechanical, like “make this button larger” or “display this elsewhere”, but some were more philosophical. In my previous experience with the GNOME desktop, we pursued a path similar to Godot. That is, we tried to deliver a user interface, but whenever there were disagreements about the intended behavior, rather than making an editorial or design decision, we offered a choice. Or three. Or four. Or five, or as many choices as there were opinions.

Offering choices sounds great on paper, but is terrible in practice. Options can paralyze users, but each option forces you to test two codepaths - and that is if you are lucky, if you have options that interact with other options. Now you have to test combinations of those features, and so on. And then you get to document all these combinations.

We wanted an application that lived up to the ethos of great iOS applications. We felt that we had to act as editors and make design choices that surfaced the right defaults, and we opted to only surface what we felt was necessary.

Overall, I think that we did a pretty good job, but every once in a while, our users would complain and make a case for why they really needed an option. So, in those cases, we have brought back a level of configuration or re-surfaced elements that were previously not shown.

Our design process was documented in our blog, and you can see our process and some of the iterations on the concepts over time.

We initially thought we would only touch on a couple of pieces, the scene pad, the file pad - and over time we found ourselves rewriting almost all of the user interface in Godot, both because it felt so much better, but also as users struggled with different parts of the UI. This is a process that has been both extensive, but also quite enjoyable - as SwiftUI has made this a delightful exercise.

At first, we just layered a new UI on top of the Godot Editor, and we customized Godot to show fewer UI elements when running. This served us well for a while, but at some point we found ourselves needing to “host” parts of the Godot UI in SwiftUI views that we controlled, like the bottom bar panels, the plugins that render inside the inspector, as well as having a fallback for custom Godot user interface code - and for that we used a system that allows us to “rehost” parts of the Godot UI - but having this was important to fully take control of the user experience, while ensuring that everything you need to work with Godot was still there.

Adapting Godot from a desktop application into a pleasant, touch-first, iPad application was a lot of work, and we were convinced there was no more shrinking or adjusting in our future. But even during the beta period before we launched the iPad version, our testers kept asking us for an iPhone version. We were not convinced that this was necessary, but our users kept telling us all the reasons why they would want this - tuning their apps, experimenting on the go, testing an idea during small breaks, adjusting some properties of their game during their bus or train ride or during their lunch breaks.

But there is a big gap between what people tell you they want and what they are actually going to do, so we remained skeptical for a long time. The first time we reconsidered this was when we heard a presentation from Chad Stewart on using Godot on Android where he shared his real-life experiences doing his work on the go. Then the Godot foundation shared information about usage of Godot on Android, on phones and tablets - and it was then that we grasped that for some folks their phone is their sole computing device. So not only was this possible, for some folks it was a necessity.

So, delivering the full Godot Editor on iPad and iPhone has meant more than just porting a desktop app. To meet App Store requirements and match Apple users’ expectations, we rebuilt the interface to be truly native and touch-first - something that feels at home on touch devices rather than adapted for it. Xogot has been a multi-year effort and a significant engineering investment. It’s a commercial product created by a small team deeply passionate about both Godot and Apple platforms. Xogot includes a free tier open to everyone, with the complete version provided at no cost to students and contributors to the Godot open-source project.

What are the biggest differences between the Xogot and the Godot Editor?

Xogot has two major limitations. First, it can not run third-party plugins authored in native code, or run .NET code. The reason for the former is that Apple’s security system does not allow for third-party dynamic code to be loaded into a process, so all of these plugins fail.

And the ability to run .NET code is not something we have worked on.

Considering the improvements made to adapt to the new form factor, are there any plans on bringing Xogot to other platforms?

We want to bring Xogot to the Apple Vision Pro. Anecdotally, just before we decided to embark on bringing Godot to the iPad, we were working on building frameworks and games for the Vision Pro. We were going to our first Boston Unity meeting to learn more about Unity and Vision when the Boston Unity group disbanded in response to Unity’s license changes. It was in this turmoil that we were inspired to jump headlong into the Godot world.

The idea of building and testing immersive experiences directly inside the headset feels like a natural extension of what we have done so far - creating something with your hands, right in front of you, makes the process feel immediate and physical. But like the iPad effort, there are a number of very interesting problems to solve there before we can ship a product that would meet the expectations of users, so we are going to have to work through those.

We don’t currently have plans to bring Xogot to non-Apple platforms. Our focus right now is on delivering the best possible experience on iPhone and iPad, and continuing to refine what it means to build games natively on Apple’s devices. So you will see us iterating on the experience and incorporating user feedback until we can score ourselves one of those Apple Design Awards.

That said, Godot already runs on many platforms, and we see Xogot as part of that larger ecosystem. For now, our aim is to deliver a great experience to game developers on the Apple platforms, and to maintain a high level of compatibility with Godot so that both environments can complement each other.

Were there some improvements made in Xogot that made it upstream?

Our biggest contribution so far has been the LibGodot effort, which is a major investment we’ve been funding with the development work led by Migeran. LibGodot makes it possible to embed Godot inside modern applications, and Migeran is now in the process of getting it upstreamed so it can benefit the broader community.

We’ve also contributed a number of smaller patches and fixes, and we’re continuing to learn what it takes to shepherd contributions through the review and merge process. Looking ahead, we expect to contribute larger components as well. We already have a few ideas in mind. But as we’re still relatively new to the game development community, we want those contributions to be shaped by what we learn as Xogot and its user base continue to grow.

I would love to participate more directly in Godot’s workgroups and community discussions. Balancing that with running a company and raising three kids can be challenging, but I have enormous respect for the dedication and care of the Godot team. My hope is that over time we can contribute not just code, but also ideas and processes that help strengthen the community.

What’s next for Xogot?

We’re especially excited about Xogot Connect, our new open-source Godot add-on that lets developers on Windows, Linux, or macOS easily run and debug their projects on iPhone or iPad without the usual complexity of exporting to iOS, building in Xcode, or managing provisioning profiles.

Our goal is to keep expanding that bridge between desktop and mobile development. Xogot Connect already makes it simple to configure on-screen controls in your game by enabling the iOS Virtual Controller in Project Settings, and we have a few more ideas like this in the works that bring the mobile-specific affordances we’ve developed for Xogot directly to Godot developers on the desktop and make targeting mobile smoother and more approachable.

I would like to thank Miguel de Icaza for sharing with us the experience of his ride of adapting the Godot Editor specifically for a new platform.

You can easily find Xogot in the App Store or at its homepage.

Also, don’t forget to check out Xogot Connect in the Godot Asset Library. (Expect it to be also in the upcoming Asset Store!)

Maintenance release: Godot 4.6.2

Thaddeus Crews — Wed, 01 Apr 2026 12:00:00 +0000

While the majority of our team continues to focus on development snapshots for Godot 4.7, we still have a commitment to maintenance releases for the latest stable version. Specifically, our release support policy promises active support until the successor’s first patch release, so there’s still room for yet more maintenance releases in the future. As for now, we’d like to thank everyone who took the time to evaluate and ratify our release candidates for Godot 4.6.2.

Maintenance releases are expected to be safe for an upgrade, but we recommend to always make backups, or use a version control system such as Git, to preserve your projects in case of corruption or data loss.

Download Godot 4.6.2 now or try the online version of the Godot editor.

Download Godot 4.6.2 stable

Linux

macOS

Windows

Export templates and other downloads Make a Donation

The cover illustration is from Bombun, a wholesome 3D platformer where you guide Bombun, a bomb-throwing bunny, on a mission to defend her floating fortress from a friend-turned-foe. You can buy the game on Steam, and follow the developer on Bluesky or itch.io.

Changes

61 contributors submitted 122 fixes for this release. See our interactive changelog for the complete list of changes since the 4.6.1-stable release.

3D: Fix 3D focus selection for subgizmos (GH-116972).
3D: Fix DirectionalLight3D property list (GH-117189).
Animation: Check playback_queue existance after emit animation_finished signal (GH-116676).
Animation: Deselect bezier keyframes when switching animations (GH-116953).
Animation: Fix timeline cursor following mouse during marker selection (GH-117634).
Animation: Fix visual shift of animation editor keys during selection (GH-117290).
Core: Fix String::split_ crash on empty string (GH-117353).
Core: Fix editable children state when duplicating instantiated nodes (GH-117041).
Core: RingBuffer: Fix T read() method reading empty buffer (GH-117388).
Core: RingBuffer: Fix overreading on methods that take an offset as an argument (GH-117151).
Editor: Fix build profile generator creating bogus profiles (GH-115410).
Editor: Fix mute button after pausing and stopping (GH-116537).
Editor: Fix theme item inspector tooltips for Window subclasses (GH-115245).
Editor: Set accessibility name on Tree inline cell editor when editing (GH-117135).
Editor: Stop autocomplete from eating words by default (GH-117464).
Export: Android Editor: Copy keystore to temp file during export (GH-116161).
GDExtension: Add missing GDVIRTUAL_BIND(_get_supported_extensions) on MovieWriter (GH-117479).
GUI: Fix “Custom” anchor preset being ignored if the parent isn’t a Control (GH-117488).
GUI: Fix RichTextLabel drag selection not working after double-click (GH-117201).
GUI: TextEdit: Fix clipping of last character due to right margin rounding (GH-116850).
GUI: TextServer: Ignore language of embedded object replacement spans when updating line breaks (GH-116197).
Import: Blender attempts should be incremented to avoid endless loop (GH-116589).
Physics: Jolt Physics: Make MoveKinematic more accurate when rotating a body by a very small angle (GH-115327).
Physics: Jolt Physics: Rework how gravity is applied to dynamic bodies to prevent energy increase on elastic collisions (GH-115305).
Physics: Jolt Physics: Swapping vertices of triangle if it is scaled inside out (GH-115089).
Platforms: Android: Fix FileAccess crash when using treeUri in Gradle-built apps (GH-117131).
Platforms: Fix macOS Steam time tracking lost when opening a project (GH-117335).
Platforms: iOS: Add UIScene lifecycle events (GH-116395).
Platforms: iOS: Propagate VC UI preferences to SwiftUI hosting controller (GH-116633).
Platforms: macOS: Enable wake for events if Magnet is running (GH-116524).
Platforms: Wayland: Improve mapping robustness and synchronization (GH-117385).
Platforms: Windows: Set current driver when ANGLE init fails (GH-117253).
Rendering: Apply fixed size properly for mono/stereo rendering (GH-115147).
Rendering: Fix accidental write-combined memory reads in canvas renderer (GH-115757).
Rendering: Fix Tangent decoding detection when computing vertex skinning (GH-117401).
Rendering: Fix viewport debanding not working with spatial scalers (GH-114890).
Rendering: macOS: Force ANGLE (GL over Metal) when running in VM (GH-117371).

This release is built from commit 001aa128b.

Known incompatibilities

As of now, there are no known incompatibilities with the previous Godot 4.6.1 release. We encourage all users to upgrade to 4.6.2.

If you experience any unexpected behavior change in your projects after upgrading to 4.6.2, please file an issue on GitHub.

Bug reports

Support

Godot is a non-profit, open-source game engine developed by hundreds of contributors on their free time, as well as a handful of part and full-time developers hired thanks to generous donations from the Godot community. A big thank you to everyone who has contributed their time or their financial support to the project!

If you’d like to support the project financially and help us secure our future hires, you can do so using the Godot Development Fund.

Donate now

Dev snapshot: Godot 4.7 dev 3

Hugo Locurcio — Thu, 26 Mar 2026 17:00:00 +0000

Following hot on the heels of the last snapshot, the third development snapshot for what will become Godot 4.7 is now out! This snapshot comes packed with some long-awaited features, some of which may transform the way you design GUIs in Godot. As always, we need as much testing as possible to ensure everything can be stabilized.

The cover illustration is from Lucid Blocks, a game where you explore, build, and survive in a cryptic expanse oozing with dreamlike oddities and esoteric critters. You can buy the game on Steam, and follow the developers on Bluesky, YouTube, or Discord.

Highlights

GUI: Add transform offset to Control nodes

One of the most long-awaited features in Godot’s GUI system is to be able to translate, rotate, or scale a Control node without it affecting the rest of the container. This is most notably used for animation purposes, so that buttons can smoothly slide in view or fade away with a scale change.

However, Godot’s various Container nodes apply the position, rotation, and scale to their children, which means any changes made to the children’s transform is lost when the container is sorted again (which occurs when children are added, removed, or moved in the scene tree). The new transform offset properties implemented by Timo Schwarzer in GH-87081 aim to address this limitation in a self-contained manner, similar to the transform property in CSS.

You can choose whether the transform offset affects mouse input. By default, transform offset is purely visual, which means there is no risk of buttons losing their hover status after being transformed. Controls with a transform offset applied show their original bounding box with a gray dotted rectangle:

GUI: Implement search bar for PopupMenu

As a tool that can be used to create complex projects, Godot is no stranger to popups with dozens of options to choose from (if not more). While incremental search can be used to focus the first item that starts with a given letter (by pressing the letter in question), this can be difficult to use as incremental search lacks visible feedback once you perform it.

To resolve this longstanding usability quirk, Alexander Streng added search bars to PopupMenu in GH-114236. This is particularly useful for long lists such as animations, skeleton bones, inspector dropdowns for Resource properties, and more. A visible search bar also makes searching more discoverable, which is a win for usability.

This feature is available in any PopupMenu node, which means it can also be used in projects such as non-game applications.

Editor: Add vertex snapping to the 3D editor

One of the most keenly awaited features to improve 3D editor usability is finally here! Robert Yevdokimov implemented vertex snapping in the 3D editor in GH-117235. This allows you to snap the selection to nearby nodes’ vertices, which is useful for level design and ensuring everything is visually connected to neighboring nodes.

To use vertex snapping, hold B and move the mouse near the selection’s vertices. Once you see a yellow circle, hold the mouse button and move the mouse to the desired location (you can release B at this point). The circle becomes green once a vertex to snap to is detected near the mouse cursor. For better depth perception, the yellow/green circle appears with reduced opacity if it’s occluded by another surface.

Vertex snapping works differently depending on whether the selected node has a mesh-based representation or not. For example, MeshInstance3D and CSG nodes have a mesh-based representation, while other nodes such as Label3D and Marker3D do not. Nodes without a mesh-based representation will teleport to the highlighted vertex when holding B and clicking on another node’s vertex. Thanks to the follow-up contribution GH-117380, you can opt into this behavior for nodes that have a mesh-based representation too.

Editor: Use class name instead of Object ID in remote scene view

The remote scene tree is very useful to diagnose what’s going on in a running project. However, until now, everything was shown as a bunch of anonymous-looking Object IDs. Jayden Sipe has improved this view by adding class names in GH-115738, making this tool significantly more useful.

Before

After

Editor: Create a proper editor for `MeshLibrary`

GridMap users rejoice! The MeshLibrary resource (which stores tiles that can be used in a GridMap node) can now be edited much more easily, thanks to the work of Michael Alexsander in GH-117376.

This new bottom editor comes with the following features:

Presentation of items in a grid, with search and zooming.
Editing of individual items in a separate inspector.
Full undo/redo for all actions.
Fallback preview to an item’s mesh in case none was specifically set.

Here’s an example of what it looks like:

Android: Add support for picture-in-picture

Thanks to the work of Fredia Huya-Kouadio in GH-114505, Godot now has the ability to run a project and move it to a small window pinned to one of the screen corners. This relies on Android’s native support for picture-in-picture (PiP) display. For example, YouTube on Android uses this functionality to show the currently played video in a corner of the screen.

Note that picture-in-picture does not permit interacting with the application while it is in this mode, so this feature is most useful for applications and games that have sections that don’t require real-time input (idle games, autobattlers, etc.).

Picture-in-picture functionality can be enabled in two ways:

Explicitly by calling DisplayServer.pip_mode_enter().
Configured to happen automatically by calling DisplayServer.pip_mode_set_auto_enter_on_background(). In this case, the app will automatically go into picture-in-picture mode when the user presses the home button or uses the home gesture on their device.

As an example, since this ability can be toggled at runtime, you can allow picture-in-picture mode to engage when a cutscene starts and disable it when returning to interactive contents.

Here’s an example of it in action on the game Rift Riff, where PiP mode is only enabled during one of the game’s waves:

Android: Enable orientation change in Script Editor

The improvements for Android don’t stop there. Thanks to the work of Anish Kumar in GH-117109, you can now switch to portrait mode while in the script editor on Android devices. This makes it easier to view code while you’re typing on a virtual keyboard. Note that distraction-free mode must be enabled for this to be possible (it can be toggled). This restriction has to be in place, since the side docks take a lot of horizontal space and the script editor in portrait mode wouldn’t be practical with the side docks visible.

Linux/*BSD: Support HDR output

Continuing from the previous development snapshots which added support for HDR output on Windows and Apple platforms, we have added support for HDR output on Linux when using the Wayland display server (GH-102987). Kudos to ArchercatNEO for their dedication to developing and maintaining the Wayland support alongside the Windows and Apple PRs for more than a year!

Also of note is that documentation on HDR output is now available. Check it out! A demo project for testing HDR output will follow soon.

And more!

There are too many exciting changes to list them all here, but here’s a curated selection:

3D: Add automatic smoothing for CSG nodes (GH-116749).
Animation: Optimize Animation Resource, Library, Mixer, and Player (GH-116394).
Animation: Optimize AnimationTree, Improve internals & Editor & Node::process_thread_group safety (GH-117277).
Core: Improve thread-safety of Object signals (GH-117511).
Core: Use TRACY_ON_DEMAND by default for Tracy integration (GH-117583).
Editor: Add View3DController for editor 3D view manipulation (GH-115957).
Editor: Add 3D vertex snap base setting (Vertex/Origin) (GH-117380).
Editor: Depict version discrepancies in Project Manager (GH-111528).
Editor: Generate and display documentation for the properties generated by PropertyListHelper (GH-115253).
Editor: Reorganize Output dock (GH-112690).
Editor: Revamp autoload creation (GH-91124).
Editor: Stop autocomplete from eating words by default (GH-117464).
Editor: Support folding, groups, and subgroups in remote scene inspector (GH-117357).
GUI: Add triple-click paragraph selection to RichTextLabel (GH-116868).
Input: Add project setting to ignore joypad events if the app is unfocused (GH-115119).
Platforms: Add haptic feedback on long-press right-click in the editor (GH-117198).
Platforms: Enable wake for events if Magnet is running (GH-116524).
Rendering: Add fast path to Polygon2D (GH-117334).
Rendering: Add scale 3D and rotation 3D in particle process (GH-112447).

Changelog

113 contributors submitted 297 fixes for this release. See our interactive changelog for the complete list of changes since 4.7-dev2. You can also review all changes included in 4.7 compared to the previous 4.6 feature release.

This release is built from commit 60fff00a6.

Downloads

Download Godot 4.7 dev3

Linux

macOS

Windows

Export templates and other downloads Make a Donation

Standard build includes support for GDScript and GDExtension.

.NET build (marked as mono) includes support for C#, as well as GDScript and GDExtension.

Known issues

With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of known bugs.

There are currently no known issues introduced by this release.

Bug reports

Support

Godot is a non-profit, open source game engine developed by hundreds of contributors on their free time, as well as a handful of part and full-time developers hired thanks to generous donations from the Godot community. A big thank you to everyone who has contributed their time or their financial support to the project!

If you’d like to support the project financially and help us secure our future hires, you can do so using the Godot Development Fund platform managed by Godot Foundation. There are also several alternative ways to donate which you may find more suitable.

Donate now

Release candidate: Godot 4.6.2 RC 2

Thaddeus Crews — Fri, 20 Mar 2026 12:00:00 +0000

Last week, we released our first Release Candidate snapshot for 4.6.2, and have since backported even more critical bugfixes. While we normally only need a single pass for maintenance releases, sometimes enough changes are integrated to warrant a second pass. So, once more for good measure: Godot 4.6.2 RC 2 is ready for general testing!

The illustration picture for this article comes from Funi Raccoon Game, a 3D platformer collectathon, where you play as a raccoon on a quest to fill their newly acquired home with an incalculable quantity of knick-knacks. You can buy the recently-released game or try the demo for free on Steam, and follow the developers, Crayon and Kit, on Bluesky.

What’s new

25 contributors submitted 29 improvements for this release. See our interactive changelog for the complete list of changes since 4.6.2-rc1. You can also review all changes included in 4.6.2 compared to the previous 4.6.1 maintenance release.

This section covers all changes made since 4.6.2-rc1, which are largely regression fixes:

3D: Fix 3D focus selection for subgizmos (GH-116972).
3D: Fix DirectionalLight3D property list (GH-117189).
Animation: Deselect bezier keyframes when switching animations (GH-116953).
Animation: Fix visual shift of animation editor keys during selection (GH-117290).
Buildsystem: Add UTF-8 encoding to SVG file open in platform_builders.py (GH-117454).
Buildsystem: CI: Bump JavaScript actions to Node 24 (GH-117428).
Buildsystem: ScrollBar: Fix compilation with precision=double (GH-117224).
Buildsystem: Update CODEOWNERS (GH-117674).
Core: Fix String::split_ crash on empty string (GH-117353).
Core: Fix editable children state when duplicating instantiated nodes (GH-117041).
Core: RingBuffer: Fix T read() method reading empty buffer (GH-117388).
Core: RingBuffer: Fix overreading on methods that take an offset as an argument (GH-117151).
Editor: Set accessibility name on Tree inline cell editor when editing (GH-117135).
GDExtension: Add missing GDVIRTUAL_BIND(_get_supported_extensions) on MovieWriter (GH-117479).
GUI: Fix “Custom” anchor preset being ignored if the parent isn’t a Control (GH-117488).
GUI: Fix RichTextLabel drag selection not working after double-click (GH-117201).
GUI: TextEdit: Fix clipping of last character due to right margin rounding (GH-116850).
Import: Blender attempts should be incremented to avoid endless loop (GH-116589).
Platforms: Apple Embedded: Fix static .a/.xcframework library loading in open_dynamic_library (GH-117469).
Platforms: Fix macOS Steam time tracking lost when opening a project (GH-117335).
Platforms: iOS: Propagate VC UI preferences to SwiftUI hosting controller (GH-116633).
Platforms: macOS: Enable wake for events if Magnet is running (GH-116524).
Platforms: Windows: Set current driver when ANGLE init fails (GH-117253).
Plugin: Android: Fix java.util.HashMap handling (GH-114941).
Plugin: Fix EditorDock not reopening (GH-117340).
Rendering: Fix Tangent decoding detection when computing vertex skinning (GH-117401).
Rendering: macOS: Force ANGLE (GL over Metal) when running in VM (GH-117371).
Thirdparty: libpng: Update to 1.6.55 (GH-117564).
Thirdparty: Update access-kit to 0.21.2 (GH-117433).

This release is built from commit 638b2f1e9.

Downloads

Download Godot 4.6.2 rc2

Linux

macOS

Windows

Export templates and other downloads Make a Donation

Standard build includes support for GDScript and GDExtension.

.NET build (marked as mono) includes support for C#, as well as GDScript and GDExtension.

Known issues

During the Release Candidate stage, we focus exclusively on solving showstopping regressions (i.e. something that worked in a previous release is now broken, without workaround). You can have a look at our current list of regressions and significant issues which we aim to address before releasing 4.6.2. This list is dynamic and will be updated if we discover new showstopping issues after more users start testing the RC snapshots.

With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of known bugs.

Bug reports

Support

If you’d like to support the project financially and help us secure our future hires, you can do so using the Godot Development Fund.

Donate now

Maintenance release: Godot 4.5.2

Rémi Verschelde — Thu, 19 Mar 2026 12:00:00 +0000

While most users have upgraded their projects to Godot 4.6 by now, some have to stay on the previous 4.5 branch for various reasons, so we do our best to provide them with important fixes.

Our release support policy is that we support a given stable branch actively until its successor has had its first patch release, which happened a month ago with 4.6.1. But 4.5.2 was already in the pipeline with RC1, I just never got to finalizing it… so it’s time to wrap it up with a stable release!

Note: Following this maintenance release, the 4.5 branch switches to partial support, and the 4.4 branch is end of life and won’t get new patch releases.

Download Godot 4.5.2 now or try the online version of the Godot editor.

Download Godot 4.5.2 stable

Linux

macOS

Windows

Export templates and other downloads Make a Donation

The cover illustration is from Spooky Express, a 3D puzzle game which has you in charge of the only rail service willing to transport both humans and undeads in turns, or in other words, the goat, cabbage, and wolf problem in spookyland! Spooky Express was created by the award-winning designers at Draknek & Friends, who recently started using Godot for their new titles. You can buy the game on Steam, itch.io, App Store, and Google Play, and follow the developers on Bluesky or Mastodon.

Highlights

This release backports important fixes on the rendering and platform porting areas, notably:

Thanks to work done by the Android maintainers in Godot 4.5, we’ve been providing debug symbols for the Android export templates, which users can upload to Google Play to symbolicate their crash logs. This has enabled developers of games such as Rift Riff, Kamaeru, and Spooky Express to share detailed stack traces about crashes that some players run into on their games. These developers also assisted the rendering maintainers in debugging the issues, and so Skyth could write fixes for most issues found, which are available in this release.
- If you have a game published on Google Play using Vulkan Mobile, we strongly recommend upgrading to 4.5.2 or later, as this should resolve a lot of crash reports that your game might have. If using Compatibility, there are also significant crash fixes worth getting.
Still on the rendering side, we’ve backported a number of Direct3D 12 bug fixes and performance improvements, notably to reduce initial shader compilation time and get it closer to what we have with Vulkan. While Godot 4.6 has even more fixes and new features, enabling it to make Direct3D 12 the default driver on Windows, for 4.5.2 it remains opt-in, but these fixes should improve the experience for developers who choose to target this API.
And finally, again on rendering, iOS exports using Metal (Forward+ or Mobile rendering methods) will now default to restrict support to A12 devices or newer. This means excluding some older iPads which technically support Metal but struggle to run Godot games properly. You can toggle this option in the export preset, as this is just a change of its default state based on your rendering method.

Changes

107 contributors submitted 218 fixes for this release. See our interactive changelog for the complete list of changes since the 4.5.1-stable release.

2D: Check for tiles outside texture on TileSet atlas settings changes (GH-112271).
3D: Don’t redraw Sprite3D/AnimatedSprite3D outside the tree (GH-112593).
Animation: Separate branching ping-pong time and delta (GH-112047).
Audio: Fix AudioStreamPolyphonic to honor AudioStreamPlayer.pitch_scale (GH-110525).
Audio: Check if on tree before calling can_process() (GH-114966).
C#: Fix dotnet class lookup returning modified names instead of engine names (GH-112023).
C#: Ensure .NET editor supports Visual Studio 2026 (GH-112961).
Core: Fix load_threaded_get returning null when used with CACHE_MODE_IGNORE (GH-111387).
Core: Improve determinism of UIDs (GH-111858).
Core: Fix duplicating node references of custom node type properties (GH-112076).
Editor: Visual Shader: Fix nodes’ relative positions changed in a different display scale (GH-97620).
Editor: Fix editing resources in the inspector when inside an array or dictionary (GH-106099).
Editor: Fix switch to GameView when closing game window (GH-111811).
Editor: EditorRun: Load override.cfg to get window configuration for embedded mode (GH-111847).
Editor: Add donate button to project manager (GH-111969).
Editor: Fix file duplication making random UID (GH-112015).
Export: Disable shader baker when exporting as dedicated server (GH-112361).
Export: iOS: Automatically enable iphone-ipad-minimum-performance-a12 if project is using Forward+/Mobile renderer (GH-114098).
Export: Fix Android export with multiple architectures failing when GDExtension includes native dependencies (GH-114483).
GDExtension: iOS: Fix loading of xcframework dynamic libraries (GH-112784).
GDScript: LSP: Fix goto native declaration (GH-111478).
GUI: Fix update order for exclusive child window (GH-94488).
GUI: FoldableContainer: Override has_point to use title rect when folded (GH-110847).
GUI: Fix IME input in multiple windows at once (GH-111865).
Network: Normalize IP parsing, fix IPv6, tests (GH-114827).
Particles: Fix CPUParticle3D not randomizing (GH-112514).
Physics: Fix transform updates sometimes being discarded when using Jolt (GH-115364).
Platforms: Android: Add support for Android XR devices to the Godot XR Editor (GH-112776).
Platforms: Android: Fix ANRs when shutting down the engine due to the render thread (GH-114207).
Platforms: Android: Trigger save of the RD pipeline cache on application pause (GH-114463).
Platforms: Apple Embedded: Fix static .a/.xcframework library loading in open_dynamic_library (GH-117469).
Platforms: macOS: Fix ~500ms hang on transparent OpenGL window creation on macOS 26 (GH-111657).
Platforms: macOS: Fix microphone issue (GH-111691).
Platforms: macOS: Disable window embedding code in export templates (GH-113966).
Platforms: Linux: Add SSE4.2 support runtime check (GH-112279).
Platforms: Linux/X11: Fix input delay regression (GH-113537).
Platforms: Windows: Fix EnumDevices stall using IAT hooks (GH-113013).
Platforms: Windows: Set current driver when ANGLE init fails (GH-117253).
Rendering: Round values after renormalization when generating mipmaps (GH-111841).
Rendering: Use AABB center instead of origin for visibility fade (GH-113486).
Rendering: D3D12: Fix not checking for fullscreen clear region correctly (GH-111321).
Rendering: D3D12: Fix specialization constant patching (GH-111356).
Rendering: D3D12: Greatly reduce shader conversion time & fix spec constant bitmasking (GH-111762).
Rendering: OpenGL: Add all PowerVR devices to the transform feedback shader cache ban list (GH-111329).
Rendering: OpenGL: Use GL_FRAMEBUFFER instead of GL_DRAW_FRAMEBUFFER when doing final blit to the screen framebuffer to work around OBS bug (GH-111834).
Rendering: Vulkan: Create new pools when they become fragmented (GH-114313).
Rendering: Vulkan: Implement workaround for GPU driver crash on Adreno 5XX (GH-114416).
Rendering: Vulkan: Create separate graphics queue instead of reusing the main queue when transfer queue family is unsupported (GH-114476).
Shaders: Fix VisualShader conversion failing with subresources (GH-109375).
Thirdparty: libpng: Update to 1.6.55 (GH-117564).
Thirdparty: mbedTLS: Update to version 3.6.5 (GH-111845).
Thirdparty: pcre2: Update to 10.46 (GH-114766).

Known incompatibilities

As of now, there are no known incompatibilities with the previous Godot 4.5.x releases. We encourage all 4.5 users to upgrade to 4.5.2 (or newer stable releases).

If you experience any unexpected behavior change in your projects after upgrading to 4.5.2, please file an issue on GitHub.

Bug reports

Support

If you’d like to support the project financially and help us secure our future hires, you can do so using the Godot Development Fund.

Donate now

Godot XR update — March 2026

Bastiaan Olij — Mon, 16 Mar 2026 12:00:00 +0000

Godot XR Game Jam V

We’re having another XR-focused game jam starting March 15/16th (depending on your timezone). The jam runs for a full week, after which voting will remain open for the week after.

This is always a good chance to get introduced to using XR in Godot, whether you are new to Godot or new to XR.

We’ll primarily be helping people along on our XR channel on the official Godot Discord.

Check out the details on the jam’s itch.io page.

OpenXR 1.1. support

The OpenXR 1.1 specification was released some time ago and adoption of this is now such that most headsets support it.

OpenXR is the industry standard interface making it possible for Godot to interact with many of the leading XR devices.

OpenXR 1.1 has promoted various extensions to core such as:

Palm pose is now Grip surface pose and guaranteed to be supported.
Local floor reference space is guaranteed to be supported.
Various controller interaction profiles are now part of the core.
New Meta interaction profiles identifying specific controllers.

Godot now has logic to initialise OpenXR 1.1 when supported by the headset and fall back to OpenXR 1.0 if not.

Some of these promotions have resulted in renames of various entries in the action map. For developers, we’ve made this as transparent as possible: you set up your action map for OpenXR 1.1 and Godot will translate it to an OpenXR 1.0 action map.

Note that this will result in your existing action map being upgraded to OpenXR 1.1 standards, and thus will be incompatible with earlier versions of Godot.

This work was made possible thanks to funding through the Khronos Godot Integration Project.

Vulkan multithreading

Godot has the ability to run rendering in a separate thread allowing for parallel processing of the next frame while the current frame is being produced.

While we did an initial pass for thread safety in the core logic around OpenXR, the vendor plugin has now undergone the same treatment, as well as improving threading support for a number of new features in the core.

This potentially provides a decent performance upgrade when running your game on standalone VR hardware.

This work was made possible thanks to contributions by W4Games.

Setup wizard

The Godot OpenXR vendor plugin now includes a Project Setup Wizard! This tool is meant to guide users through the configuration of new XR projects, getting them export-ready for standalone headsets faster than ever. With the vendor plugin installed, you can find the XR Project Setup Wizard under the tools section of the project menu. Simply select your target headset vendor and project type, and the wizard will present you with a list of required and recommended settings tailored to your choices, most of which can be applied instantly with the click of a button.

Without a main scene set for your project, the wizard also provides access to template XR scenes and scripts that handle all the needed logic for starting XR. Be sure to give this tool a try on your next Godot XR project!

Khronos loader

In Godot 4.6, Godot now embeds the Khronos OpenXR loader into any Android OpenXR game. Godot already did this for other platforms but previously relied on the vendor plugin to embed the loader.

This change in theory allows you to create a single Android OpenXR APK and deploy it to multiple headsets. This is great news for people participating in game jams or wanting to distribute through stores like itch.io.

This works for many of the mainstream headsets. However, a number of runtimes do require additional manifest entries to unlock functionality. Or they can require various vendor extensions for features to be unlocked. We do recommend users keep using the vendor plugin to have access to these things.

DirectX default on Windows

Godot recently made DirectX the default back-end on Windows for new projects. It is important to note here that for XR developers, there are things to consider.

Godot fully supports DirectX as a backend for OpenXR. However, as all of the standalone headsets only support OpenGL and Vulkan, there are potential differences between using DirectX and the other backends. We are also further along with certain optimizations on the other backends.

Nothing much changes for developers who are using the Compatibility renderer. If you’re using the Mobile or Forward+ renderers for your XR projects, we recommend using Vulkan also on Windows for the foreseeable future.

New platforms

Godot 4.6 welcomed two new XR platforms into the mix.

Godot now has official support for AndroidXR. The necessary changes were added to both Godot and the vendor plugin late last year. Together with W4Games, we are hard at work bringing additional AndroidXR functionality to Godot. As part of this work, we’re also contributing to a few open-source Godot game projects and bringing them to the AndroidXR platform.

We are also proud to report that Godot runs on the Steam Frame. We have tested all three deployment modes: PCVR over Steam Link, running natively as an Android APK, and running a native Linux ARM64 version. With thanks to GP Garcia, we can also confirm that the popular GodotSteam library is working as expected on the platform including a native Linux ARM64 build that is now available.

The illustration picture for this article comes from Augmental Puzzles, an XR game by Flammable Penguins Games, a puzzle game currently focussing on Sudoku with daily challenges. Other puzzle types are in the pipeline. It’s currently available on the Meta Store and Steam.

Release candidate: Godot 4.6.2 RC 1

Thaddeus Crews — Mon, 09 Mar 2026 12:00:00 +0000

It’s been nearly two months since the initial release of Godot 4.6, and three weeks since the 4.6.1 maintenance release. In that time, we’ve had a steady chain of development snapshots for 4.7—the latest of which came out last week—and the number of resolved issues from bugs/regressions have only increased since then. In fact, we’ve received so many fixes that we’re preparing for yet another maintenance release: Godot 4.6.2!

The illustration picture for this article comes from MR FARMBOY, a colony/farming simulation game, where you build your dream farm and community by leveraging the power of automation (hired labor). You can buy the recently-released game for sale on Steam, and follow the developer on Twitch and Discord.

What’s new

43 contributors submitted 86 improvements for this release. See our interactive changelog for the complete list of changes since the 4.6.1-stable release.

This section covers the most relevant changes made since the 4.6.1 maintenance release, which are largely regression fixes:

Animation: Check playback_queue existance after emit animation_finished signal (GH-116676).
Editor: Fix build profile generator creating bogus profiles (GH-115410).
Editor: Fix mute button after pausing and stopping (GH-116537).
Export: Android Editor: Copy keystore to temp file during export (GH-116161).
GUI: TextServer: Ignore language of embedded object replacement spans when updating line breaks (GH-116197).
Physics: Jolt Physics: Make MoveKinematic more accurate when rotating a body by a very small angle (GH-115327).
Physics: Jolt Physics: Rework how gravity is applied to dynamic bodies to prevent energy increase on elastic collisions (GH-115305).
Physics: Jolt Physics: Swapping vertices of triangle if it is scaled inside out (GH-115089).
Platforms: Android: Fix FileAccess crash when using treeUri in Gradle-built apps (GH-117131).
Platforms: iOS: Add UIScene lifecycle events (GH-116395).
Rendering: Apply fixed size properly for mono/stereo rendering (GH-115147).
Rendering: Fix accidental write-combined memory reads in canvas renderer (GH-115757).
Rendering: Fix viewport debanding not working with spatial scalers (GH-114890).

This release is built from commit 257ac3532.

Downloads

Download Godot 4.6.2 rc1

Linux

macOS

Windows

Export templates and other downloads Make a Donation

Standard build includes support for GDScript and GDExtension.

.NET build (marked as mono) includes support for C#, as well as GDScript and GDExtension.

Known issues

With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of known bugs.

macOS builds are not signed this release; this will be resolved by the time 4.6.2-stable comes out.

Bug reports

Support

If you’d like to support the project financially and help us secure our future hires, you can do so using the Godot Development Fund.

Donate now

Dev snapshot: Godot 4.7 dev 2

Thaddeus Crews — Tue, 03 Mar 2026 12:00:00 +0000

As the development cycle leaves the early stages, so too does the comparatively constrained scope of changes. Some changes are so big in fact, that they’re being distributed in small increments, rather than all at once. This is admittedly a bit awkward from a blog post perspective, as not everything is in a position to be showcased just yet, but rapid integration for the sake of early testing will always be a top priority. Besides, there’s still plenty of goodies ready to be shown off in the meantime!

The cover illustration is from Horripilant, an incremental dungeon crawler, where you meet God and subsequently kill God. You can buy the game on Steam, and follow the developers on Bluesky, YouTube, or Discord.

Highlights

Editor: Add support for copy/paste of section/category properties

Raphaël Daubelcour is starting this off with a bang, as their work in GH-111469 brought a highly-requested feature for the editor to light: the ability to copy and paste data from entire sections and categories! Now instead of copying the data from individual segments of a given property and pasting them piece-by-piece, this process is now handled in a singular action.

Editor: Use monospaced font for code names in UI

The editor got quite a lot of QOL love this snapshot, as Malcolm Anderson delivered yet another highly-requested feature in the form of monospaced code names (GH-112219). You’d be surprised by just how much the readability of the UI improves when code-like data (methods, signals, properties, etc.) is represented in a font representing their context, especially when coupled with a standard font for all other information.

Animation: Collapse groups in animation track editor

Malcolm isn’t done yet, as the animation track editor got some love in GH-113479, enabling users to collapse groups. This simple change should immediately resonate with users dealing with the absurd sizes animation trees can reach, though the benefits can be felt at all sizes.

Apple: Support HDR output

As you might recall from the previous development snapshot, our intention during the 4.7 cycle is to roll out HDR support across all supported platforms. Windows already got their initial implementation; now, it’s Apple’s turn. Stuart Carnie delivered full support for EDR display to all Apple platforms (GH-106814). Documentation is still in the works for HDR, as there’s quite a lot of ground to cover, but you can expect a proper deep-dive into the concept in the coming weeks!

Input: Add device IDs to keyboard and mouse input events

If you’ve used InputEvents in your projects and their device property directly, you may have noticed that the engine sets the device ID for keyboard and mouse devices to 0. This conflicts with joypads that may also use this ID. Therefore, the only valid way to check if an InputEvent was sent by a keyboard, is to check its type by using if event is InputEventKey: (your code here).

A proposal was made to resolve this issue, and Nintorch made a PR for it here: GH-116274. With this change, users can finally differentiate between joypad, keyboard and mouse events just by checking the device property. However, this also means that if your project depends on the previous behavior of keyboard and mouse having an ID of 0, you will have to modify your project. If you’re not happy with this change, please let us know by making a GitHub issue. If enough people are not happy with this change, it will have to be reverted.

And more!

There are too many exciting changes to list them all here, but here’s a curated selection:

2D: Add a scene painter tool (GH-109360).
3D: Add “Follow Selection” in the 3D editor by using Center Selection twice (GH-99499).
Buildsystem: SCons: Enable wasm64 support on web builds (GH-102378).
Editor: Show custom class name in the remote inspector (GH-108208).
GUI: Add script editor join_lines keybind (GH-111547).
GUI: Improve the table in RichTextLabel (GH-116277).
GUI: Support tiling AtlasTexture in TextureRect (GH-113808).
Input: Add support for SDL3 joystick input driver for iOS (GH-114316).
Plugin: Android: Add support for plugins gradle platform dependencies (GH-115888).
Rendering: Editor additions for MipMaps and rd_textures (GH-109004).

Changelog

105 contributors submitted 248 fixes for this release. See our interactive changelog for the complete list of changes since 4.7-dev1. You can also review all changes included in 4.7 compared to the previous 4.6 feature release.

This release is built from commit 778cf54da.

Downloads

Download Godot 4.7 dev2

Linux

macOS

Windows

Export templates and other downloads Make a Donation

Standard build includes support for GDScript and GDExtension.

.NET build (marked as mono) includes support for C#, as well as GDScript and GDExtension.

Known issues

With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of known bugs.

There are currently no known issues introduced by this release.

Bug reports

Support

Donate now

Godot Showcase - Buckshot Roulette

Hugo Locurcio — Fri, 27 Feb 2026 18:00:00 +0000

Mike Klubnika tells us about his experience developing the 2024 indie hit Buckshot Roulette, as well as his newer project, s.p.l.i.t.

We are extremely grateful to Mike, our latest Corporate Platinum sponsor of the Godot Development Fund. Thanks to his donation, we’ll be able to keep working on the engine for all of you. Like him, if you’d like to support the project financially you can do so using the Development Fund platform managed by Godot Foundation.

How did you get your start in game development? And how did it grow into a full-time position?

I started out by learning to do 3D artwork around 2018, so around 3 years before I got into solo game development. Eventually I started getting more and more interested in game development, and decided to work on a small game for 2 months. Once that was released, it basically snowballed from there, and I couldn’t stop thinking about making games.

By the end of 2023 I had released 16 small games, and had a decent following of both players and content creators. These were all developed between studying or full-time jobs — my biggest inspirations were obscure games with weird visuals, mechanics, and narratives, and there was a lot of freedom working on stuff when I wasn’t relying on them to turn a profit or anything like that. I was already super grateful for my small community. So after selling Buckshot Roulette for a dollar in late 2023, I was absolutely floored when it hit mainstream. Since then I’ve been able to make games full time.

Some people may be familiar with your game Buckshot Roulette, but could you tell us a bit about your newer project s.p.l.i.t.?

s.p.l.i.t is a game I still don’t fully know how to describe. Basically it’s a hacking simulator with “Typing of The Dead” elements, and a bunch of existential horror. After Buckshot Roulette I had a really strong desire to do something more narrative heavy, and so s.p.l.i.t ended up being the perfect project for that.

For the gameplay side I tried to have somewhat “realistic” hacking, so the terminal is very barebones with no flashy visuals, and the game uses commands that players would hopefully already be familiar with.

What were some of the biggest challenges you faced during the development process, and how did you overcome them?

I decided early on that the game would run on a keyboard only, which had some challenges in figuring out a control scheme for navigating different screens, and interacting with the environment. That “Typing of The Dead” type of mechanic ended up working well for that, where the player would have their action thoughts visible in certain parts of the environment, and type them out to go through with the interaction. It also just looked cool — it was fun to frame different thoughts in a cinematic way through the different cutscenes.

The biggest challenge was having the game be at least somewhat accessible to people who haven’t touched a command line before. Originally the terminal puzzles in the game were designed so that the end goal was clear, but the path there wasn’t. Players ended up being left in the dark, so making the steps to the goal clearer helped a lot. The puzzles ended up in a place where the player would have a pretty clear outline of a goal, and have to translate the steps to fulfill that into terminal commands.

How did you discover Godot? What made you pick it for your project?

I originally discovered Godot somewhere around 2022, but opened it up for the first time in late 2023. Before then I had used Unity for around 3 years, but once they announced the runtime fee, I decided to try switching engines. I really liked the fact that Godot was open source, and found it was pretty easy to get into since it shares a lot of similarities to the workflow I had in Unity.

What do you like about Godot?

It’s very fast, even in bigger projects. My favourite feature has to be the AnimationPlayer, which is very powerful and quick to set up. Coming from C#, I also liked GDscript once I got used to it. I think it’s a very nice programming language. Generally though I feel like it’s super quick to iterate on features — there’s not a lot of friction in experimenting or tweaking small things.

While making your game, were there any features that you would have liked to see in Godot?

It’d be great to be able to see a real-time visualization of the remote scene tree in the editor. Similar to Unity where if you run the game, you can see it running in the editor, navigate around, and tweak variables of objects in real-time.

What advice would you give to aspiring game developers who are just starting out in the field?

I would highly recommend making a bunch of small games — something you can finish in a couple of weeks. The first game is always the trickiest, since you’re doing everything for the first time, but once you go through the process multiple times everything starts to make a lot more sense.

For solo game development, there are quite a few different hats to wear. What really helped me get into game development were those years learning 3D software before I got into a game engine. Because of that I was comfortable with quite a few things in a game engine already, and the only thing that I had to learn from scratch was programming.

But generally it all just takes time, best to keep on trucking. For me personally, I only started noticing my progress when I looked back at my earliest games, after just a couple months of making stuff.

Thank you very much Mike for taking the time to answer our questions!

Mike Klubnika’s games including Buckshot Roulette and s.p.l.i.t are available on Steam. You can also join his Discord server.

GodotCon Amsterdam - Save the date!

Emi — Wed, 18 Feb 2026 13:00:00 +0000

The official GodotCon returns to Europe and this time, it will be the first GodotCon in the city where the Godot Foundation calls home. For this edition of the event, we teamed up with the Dutch Games Association to help us organize it and make sure that everything runs smoothly.

Information

📅 Dates	23rd, 24th of April
🕑 Time	10:00 - 18:00
🇳🇱 Location	Amsterdam, The Netherlands
📍 Venue	Pathé Amsterdam Noord. Buikslotermeerplein 2003, 1025 XL Amsterdam, Netherlands
🌐 Website	https://conference.godotengine.org

Buy tickets 🎟️

Call for speakers and sponsors

If you would like to be a part of the conference by giving a talk or a workshop, please submit your proposals through the link below. We are looking for a diverse range of topics, from beginner to advanced, so don’t hesitate to submit your ideas.

➡️ Call for submissions, Deadline: 30th of March

We are also actively looking for sponsors to support the GodotCon Amsterdam. If you or your company would be interested in learning more about sponsorship opportunities, feel free to reach out to godotcon@godotengine.org.

Call for volunteers

An event like this only happens thanks to passionate people like you who are willing to help behind the scenes. If you want to contribute to making GodotCon 2026 a welcoming and smooth experience for everyone, we are currently looking for volunteers to help us manage different aspects of the conference, from stage managers to photographers.

If you would like to participate, please fill out this form.

Tickets and more

Get your tickets here and stay tuned for more information by joining the GodotCon Discord or the mailing list.

Will there still be a Godot event in the US in 2026?

Absolutely! The same team behind the GodotCon Boston will be announcing more details about the event for 2026 in the US. It will come back with a different name, but everything else should be the same.

See you soon!

Maintenance release: Godot 4.6.1

Thaddeus Crews — Mon, 16 Feb 2026 12:00:00 +0000

It’s been three weeks since the release of Godot 4.6, and we’re blown away by everything the community has already showcased in such a short time. And while Godot 4.7 is already well underway, a maintenance release for 4.6 was always set to release soon after. This release, Godot 4.6.1, addresses all the known show-stopping regressions and issues new to the Godot 4.6 release. We’d like to thank everyone who took the time to identify and squash these bugs, allowing for the expedient release of 4.6.1-stable!

Download Godot 4.6.1 now or try the online version of the Godot editor.

Download Godot 4.6.1 stable

Linux

macOS

Windows

Export templates and other downloads Make a Donation

Edit 2026-02-16 @ 22:30 UTC: The first macOS editor binaries for 4.6.1 had a signing issue (missing entitlements) which broke .NET and GDExtension support. They have been reuploaded with a fixed signature. Please redownload the macOS version if you downloaded it before the time of this edit.

The cover illustration is from Tearscape, a 2D top-down action-adventure game, where you must blend fast-paced combat and keen exploration to successfully navigate this Gothic, dreary world. You can buy the game or try out the demo on Steam, and follow the developers on Bluesky, YouTube, or Discord.

Changes

25 contributors submitted 38 fixes for this release. See our interactive changelog for the complete list of changes since the 4.6-stable release.

3D: Change orbit snap shortcut with navigation scheme (GH-115298).
3D: Fix Skeleton3D Edit Mode bone buttons have priority over transform gizmo (GH-115608).
3D: Fix viewport orbit snap defaulting to always snapping when shortcut(s) are set to none (GH-115002).
3D: Increase float precision in the editor inspector for Quaternions (GH-106352).
3D: Register zoom shortcuts to match preset Godot navigation scheme (GH-115290).
Animation: Fix double memdelete of dummy_player (GH-115968).
Animation: Fix LookAtModifier3D / AimModifier3D forward vector (GH-115689).
Animation: Fix use-after-free in Animation Blend Tree (GH-115919).
Animation: Fix use-after-free in AnimationTree (AHashMap realloc) (GH-115931).
Buildsystem: Fix missing lib with builtin_glslang=false (GH-93478).
C#: Revert “Improve performance of CSharpLanguage::reload_assemblies” (GH-115759).
Core: Fix ClassDB class list sorting regression (GH-115923).
Core: Fix the NodePath hash function to not yield the same value for similar paths (GH-115473).
Editor: Fix NodePath EditorProperty using the wrong scene root (GH-115422).
Editor: Fix create dialog recents (GH-115314).
Editor: Fix Rename option for instance roots (GH-115575).
Editor: Fix Unique Resources from Inherited Scenes (GH-115862).
Editor: Fix wrong base type when creating script (GH-115778).
Export: Load translation files to check locale for ICU data export (GH-115827).
GDScript: LSP: Add godot to known language ids (GH-115671).
GDScript: LSP: Handle clients that do not support CompletionContext (GH-115672).
GUI: Fix current line highlight not extending into gutter (GH-115729).
Input: Update editor shortcuts when changing 3D navigation scheme (GH-115289).
Particles: Revert “Change curve range for particle multipliers” (GH-116140).
Physics: Allow SoftBody3D to have a total_mass of 0 again (GH-116111).
Physics: Fix transform updates sometimes being discarded when using Jolt (GH-115364).
Platforms: Android: Fix Bad file descriptor in SAF/MediaStore in long term access (GH-115751).
Platforms: Fix crash in StorageScope.kt on Android (GH-115515).
Platforms: Wayland Embedder: Fix FD leak with inert objects (GH-115823).
Platforms: Windows: Disable MSVC control flow check on IAT hooks (GH-115430).
Plugin: Android: Fix plugin type mismatch regression (GH-115685).
Rendering: Avoid reading from sky pointer when rendering background without sky (GH-115874).
Rendering: Ensure that uv border size is passed in to sky rendering functions (GH-115606).
Rendering: Pick the sample closer to the camera when resolving 2x MSAA (GH-115124).
Rendering: Update re-spirv with more derivative operations (GH-115921).
Rendering: Use sky’s corrected camera projection for combined_reprojection (GH-115292).
Rendering: Use transmittance instead of opacity in the early-out branch when calculating volumetric fog (GH-116107).
Thirdparty: libpng: Update to 1.6.54 (GH-115714).

Known incompatibilities

As of now, there are no known incompatibilities with the previous Godot 4.6 release. We encourage all users to upgrade to 4.6.1.

If you experience any unexpected behavior change in your projects after upgrading to 4.6.1, please file an issue on GitHub.

Bug reports

Support

If you’d like to support the project financially and help us secure our future hires, you can do so using the Godot Development Fund.

Donate now

Dev snapshot: Godot 4.7 dev 1

Thaddeus Crews — Fri, 13 Feb 2026 12:00:00 +0000

The first development snapshot for 4.7 has arrived! With it, several quality PRs are free from the backlog at last, be it because they were locked out from the 4.6 feature freeze or were simply deemed too risky for the stable release. The majority of the latter cases were already highlighted earlier this week in our 4.6.1 RC 1 snapshot, so this article will be focused on the former: new features and quality-of-life goodies.

As usual, safety precautions should be taken with any pre-release environment. While we prepare these snapshots with the intent to be suitable for general testing, there will always be a non-zero risk of data loss/corruption. Creating backups before hand and/or utilizing version control are strongly recommended!

The cover illustration is from TR-49, a story-rich puzzle game set in an alternate history, where you’re tasked solving a mystery by navigating the archives of a long-abandoned World War II computer. You can buy the game on Steam or the iOS App Store, and follow the developers on Bluesky or Discord.

Highlights

Input: `VirtualJoystick`

Joypad controls for mobile games have been historically awkward to integrate. While community-based tools do exist to mitigate this problem, this still involves developers jumping through significantly more hoops than other input devices. Kazox61 has come to the rescue with GH-110933, offering a built-in solution for handling joysticks inputs virtually with VirtualJoystick.

JOYSTICK_FIXED: The joystick doesn’t move.

JOYSTICK_DYNAMIC: The joystick is moved to the initial touch position as long as it’s within the joystick’s bounds. It moves back to its original position when released.

JOYSTICK_FOLLOWING: The joystick is moved to the initial touch position as long as it’s within the joystick’s bounds. It will follow the touch input if it goes outside the joystick’s range. It moves back to its original position when released.

Rendering: `DrawableTexture`

One very widely-requested feature across Godot’s entire lifetime has been the ability to easily draw on a texture. While this can be somewhat achieved by using Viewport, it remained quite limited and wasn’t suited for more complex tasks. Conversely, RenderingDevice is an answer for those not afraid to get their hands dirty with the guts of the engine, but that leaves the average user in the dust and is hardly a convenient solution even for those that know what they’re doing. Colin O’Rourke delivered a solution in the form of DrawableTexture: a simple API layer to abstract away all the technical noise and give users of all skill levels a convenient way to “do the thing”. (GH-105701).

The above clip is taken from a dedicated demo project by Bastiaan Olij. If you’re interested in experiencing the changes firsthand, you can try it for yourself here.

3D: Enable `Path3D` collider snapping

Gustavo Jaruga Cruz has given the 3D editor some love in the form of Path3D collider snapping (GH-102085). Now when creating and editing paths, you have the option of snapping those paths to whatever collider the mouse is hovering over, rather than simply dropping a point in space arbitrarily. As demonstrated in the below clip, this behavior is toggleable on the Path3D options menu.

GDScript: Improve display non-exported members in Remote Tree Inspector

If you’ve ever tried to wrangle with non-exported enums in a remote play session, you’re already aware of how annoying it to have those values revert to simple integers. Danil Alexeev has brought us a solution via GH-115705, ensuring that metadata is retained for variables regardless of their export status.

Before	After

Rendering: Vulkan raytracing plumbing

While Vulkan has had an API available for a few years now to support raytracing, actually implementing that API is much easier said than done. Rendering is already one of the most complex parts of the engine, and adding raytracing on top of that increases that complexity exponentially. With that in mind, it cannot be overstated just how impressive it is that Antonio Caggiano has provided us with the groundwork necessary to make that a reality (GH-99119). He’s graciously provided a demo project to showcase this new functionality via GDScript.

Windows: Support HDR output

Those that followed our 4.6 blog posts might remember a section that touched on the future implementation of HDR to the engine. The future is now, as one of our goals for 4.7 is making HDR output possible on all supported platforms. Documentation and implementation is still in the early stages, so we won’t have much to touch on this blog post. However, we can offer a small preview, as Josh Jones, Alvin Wong, and Allen Pestaluky have begun this long-term goal with an implementation on Windows (GH-94496).

And more!

There are too many exciting changes to list them all here, but here’s a curated selection:

Core: PCKPacker: Add method to add files from buffer (GH-108830).
Editor: Add a script editor keyboard shortcut to show the documentation tooltip for the word the caret is on (GH-115767).
Editor: Improve appearance of built-in help (GH-107597).
Editor: Optimize tree size computation and the scene tree dock filter (GH-110759).
Editor: Support navigating to the script in list (GH-112796).
Editor: Take custom type of parent scripts into account when dropping onready variables (GH-115158).
GUI: Add accessibility region role for landmark navigation (GH-114449).
GUI: Add conic gradient to GradientTexture2D (GH-115394).
Input: Add support for joypad motion sensors (GH-111679).
Physics: Add one-way collision direction for CollisionShape2Ds (GH-104736).
Platforms: Add device orientation change signal to DisplayServer (GH-115434).
Platforms: Android: Enable native file picker support on all devices (GH-115257).
Rendering: Clearcoat improvements and fixes (GH-111464).
Rendering: Give every pass its own unique environment uniform buffer (GH-115177).
Rendering: Metal: Refactor; fix dynamic uniforms; acyclic render graph support (GH-114484).
Rendering: Vulkan: Update all components to Vulkan SDK 1.4.335.0 (GH-114075).

Changelog

127 contributors submitted 311 fixes for this release. See our interactive changelog for the complete list of changes since the 4.6 feature release.

This release is built from commit bf95b6258.

Downloads

Download Godot 4.7 dev1

Linux

macOS

Windows

Export templates and other downloads Make a Donation

Standard build includes support for GDScript and GDExtension.

.NET build (marked as mono) includes support for C#, as well as GDScript and GDExtension.

Known issues

There are currently no known issues introduced by this release.

With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of known bugs.

macOS builds are not signed this release; this will be resolved by the time 4.7-dev2 comes out. Edit 2026-02-17 @ 23:00 UTC: Signed builds have been uploaded for macOS, replacing the previous binaries.

Bug reports

Support

Donate now

Godot Engine Official

Dev snapshot: Godot 4.7 dev 5

Highlights

Assetlib: Port asset store to new API

Editor: Rework export template dialog to allow individual templates

GUI: Enable scaling images relative to font size in RichTextLabel

Shaders: Implement inline text shader previews

Rendering: Add rectangular area light source

And more!

Changelog

Downloads

Godot is downloading...

Known issues

Bug reports

Support

Godot Mobile update — April 2026

Major improvements ahead!

1. Android and iOS ecosystem plugins

2. Mobile GPU and rendering compatibility

3. Mobile platforms stability

4. Mobile workflows improvements

What’s next?

Dev snapshot: Godot 4.7 dev 4

Highlights

Rendering: Add nearest-neighbor scaling

Bilinear

Nearest (new behavior)

GUI: Add custom_maximum_size property to Control

GUI: Improve drag and drop in Tree

Editor: Increase available space for array properties

And more!

Changelog

Downloads

Godot is downloading...

Known issues

Bug reports

Support

Godot Showcase – Xogot: Godot for iPad & iPhone

Can you tell us a little bit about your project?

Why did you want to build Xogot?

What was challenging about bringing the Godot Editor to the iPad and iPhone?

What are the biggest differences between the Xogot and the Godot Editor?

Considering the improvements made to adapt to the new form factor, are there any plans on bringing Xogot to other platforms?

Were there some improvements made in Xogot that made it upstream?

What’s next for Xogot?

Maintenance release: Godot 4.6.2

Godot is downloading...

Changes

Known incompatibilities

Bug reports

Support

Dev snapshot: Godot 4.7 dev 3

Highlights

GUI: Add transform offset to Control nodes

GUI: Implement search bar for PopupMenu

Editor: Add vertex snapping to the 3D editor

Editor: Use class name instead of Object ID in remote scene view

Before

After

Editor: Create a proper editor for MeshLibrary

Android: Add support for picture-in-picture

Android: Enable orientation change in Script Editor

Linux/*BSD: Support HDR output

And more!

Changelog

Downloads

Godot is downloading...

Known issues

Bug reports

Support

Release candidate: Godot 4.6.2 RC 2

What’s new

Downloads

Godot is downloading...

Known issues

Bug reports

Support

Maintenance release: Godot 4.5.2

Godot is downloading...

Highlights

GUI: Enable scaling images relative to font size in `RichTextLabel`

GUI: Add `custom_maximum_size` property to `Control`

GUI: Improve drag and drop in `Tree`

Editor: Create a proper editor for `MeshLibrary`

Input: `VirtualJoystick`

Rendering: `DrawableTexture`

3D: Enable `Path3D` collider snapping