Godot Engine Official

Dev snapshot: Godot 4.8 dev 5

Thaddeus Crews — Thu, 10 Sep 2026 12:00:00 +0000

As we’re hoping to enter feature freeze later in the month, you can expect this to be one of the last development snapshot highlights of the 4.8 cycle. Relatedly, many of our contributors are currently hard at work to help get their features across the finish line in time, so the number of featured points this time might be slightly lighter than usual. That shouldn’t matter too much though, as quite a few of the new offerings are things that the community have been eagerly awaiting for years.

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 ScagJPT, a desktop simulation game, where your new ~~companion~~ best friend, Scag, is here for all your scagalicious needs. You can buy the game on Steam, and follow the developers on Bluesky and Discord.

Highlights

In case you missed them, see the 4.8 dev 1, 4.8 dev 2, 4.8 dev 3, and 4.8 dev 4 release notes for an overview of some key features which were already in those snapshots, and are therefore still available for testing in 4.8 dev 5.

Rendering: Mip-level texture streaming

In the context of an engine such as Godot, “texture streaming” refers to the ability to dynamically load and unload images based on a camera’s relative position. Such a system would allow games to handle significantly more visible textures at any given point in time, which is why such a feature was one of the community’s most desired. Unfortunately, like most highly-desired features, it’s much easier said than done, and the “best” implementation direction isn’t exactly set in stone.

The approach that Trevor Davenport took in GH-113429 was mip-level texture streaming. That is: Godot now only loads the necessary mipmap of a texture, representing smaller or less detailed versions of the base texture when far away or otherwise obfuscated. This results in a significant reduction of VRAM requirements for textures, particularly for 3D titles with large, open worlds.

In order to leverage this new functionality, streaming must first be enabled in the project settings, necessitating an editor restart. You can make runtime changes via the TextureStreaming singleton.

Once enabled, textures can be imported as streamed textures, utilizing the new texture import type: “Texture2D Streamed”. This new texture type comes equipped with overrides for minimum and maximum resolution for a given texture, so you can safely preserve crucial details on a case-by-case basis. The per-texture properties override the system settings; the default is to use the system settings.

Import: Allow preserving alpha test coverage

Speaking of mipmaps: an existing issue in the engine was actually caused by their use, albeit indirectly. Certain material shaders, such as alpha scissor, would look pretty rough at long distances; this was a direct result of mipmap levels causing them to overfilter and dissolve away. While technical workarounds do exist, such as using a texture format with built-in alpha coverage like .dds, it’s still too much of a technical hurdle for what should be straightforward.

Kasper Arnklit Frandsen shared the above sentiment, leading him to create GH-104289. This allows any given texture to preserve their alpha data, even when falling back to their scaled-down equivalents.

Jayden Sipe rounds out our highlights this time with GH-121080, bringing the editor’s 2D toolbar a well-earned makeover. Being the same mind behind the overhaul of our game view toolbar, these changes increase parity between the docks with a consistent vision and design philosophy. Once again, an emphasis on usability and clarity was absolutely crucial.

Before	After

And more!

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

2D: Add Information and Frame Time panels to the 2D editor (GH-122848).
Animation: Rename BoneSpreader3D to BoneSpaceAdjuster3D (GH-122888).
Buildsystem: Allow disabling RenderingDevice and/or its renderers while compiling (GH-103100).
Core: Add support for metadata in text scenes (GH-121920).
Core: Simplify GDType by storing all properties in a single unified map. Save ~12mb runtime RAM (GH-122751).
Editor: Make main screen dock colors more readable (GH-122903).
GUI: Add format property to SpinBox and deprecate prefix/suffix (GH-103998).
GUI: Add new default algorithm of automatic focus strategy for Control nodes (GH-120631).
Input: Add Input.get_device_orientation() returning hardware-fused quaternion (GH-119142).
Platforms: Implement Feral GameMode integration on Linux (GH-117938).

Changelog

78 contributors submitted 183 fixes for this release. See our interactive changelog for the complete list of changes since 4.8 dev 4. You can also review all changes included in 4.8 compared to the previous 4.7 feature release.

This release is built from commit 9552dfb68.

Downloads

Download Godot 4.8 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

Dev snapshot: Godot 4.8 dev 4

Thaddeus Crews — Wed, 26 Aug 2026 12:00:00 +0000

Those of you who follow our development blogposts closely might’ve noticed that the past few snapshots have been a little on the light side. This isn’t to say that there was a lack of features on display nor that we’re dissatisfied with what we’ve been able to share so far, but it was enough that some users were under the impression that Godot 4.8 was going to mainly be focused on stability and bugfixes compared to past releases. While that wouldn’t be inherently bad, it couldn’t be further from the truth. On the contrary, this development snapshot was easily the hardest to narrow down what features to highlight out of every blog post I’ve written since joining the foundation, because there’s so much to share. Buckle up, we’ve got a lot of ground to cover.

The cover illustration is from CICADAMATA”, a fast-paced first person platformer, where you shoot and speedrun your way through the CASCADE while unraveling what you have become. You can buy the game on Steam, and follow the developers on YouTube.

Highlights

In case you missed them, see the 4.8 dev 1, 4.8 dev 2, and 4.8 dev 3 release notes for an overview of some key features which were already in those snapshots, and are therefore still available for testing in 4.8 dev 4.

VFX: `Trail3D`

If you know anything about trails in 3D design, you know that they’re absurdly complicated to get right, requiring an innate understanding of linear algebra and geometry as an absolute minimum. This is why a 3D trail node remained one of our most highly-requested features for years; a means of bridging this knowledge gap for designers, allowing them to achieve the desired effects in an accessible manner. Some developers have taken a stab at their own implementations, such as Zi Ye as part of his Cozy Cube Godot Addons, but many desired a native solution that could be leveraged out-of-the-box.

Enter QbieShay. By building on top of the wonderful foundation provided by Zi, she managed an official integration of Trail3D with GH-117107. Those seeking stunning visual effects through trails will no longer need deep knowledge of how meshes are drawn, UVs are assigned, or anything of the sort; everything Just Works™.

Despite also introducing Line3D, that class is unimplemented at this time. Beyond enum declarations, direct use of Line3D cannot be achieved.

Shaders: VisualShader node groups

While we’re quite happy with the current state of our visual shader, some pain points have always remained. This is especially true for more complex implementations, as the scope of the graphs could become quite unweildy over time. It’s no surprise then, that one of the most common requests for the visual shader was a way to reduce or remove the bloat and redundancy that comes from these complex files.

Hendrik Brucker delivered a solution in GH-99404, gracing the visual shader with the versatility and ubiquity of node groups. By leveraging node groups, users can now efficiently encapsulate frequently-used sections of a shader and reuse them across the graph with zero friction. What was once a chaotic mess of boilerplate and difficult-to-parse information is now neatly bundled with dedicated node groups:

Editor: Convert main screen plugins into docks

Ever since the introduction of the EditorDock in Godot 4.6, Tomasz Chabora has been on a journey to migrate our existing editor plugins to this new system. The most ambitious migration yet occurred earlier this week with GH-113051, which converts the main screen itself into a dock. This is a very fundamental change to how the editor is handled, but the benefits that are immediately available are more than worth it.

As a result of these changes:

The main screen editors aren’t tied to specific plugins anymore, instead being regular EditorDocks.
Main screen docks have their own editor setting for tab style.
All main screens can be closed.
All main screens can float.
- The only exception is Game, as custom behavior is currently tightly integrated with WindowWrapper.

The old main screen plugin workflow is still supported, but deprecated. Compatibility might be broken in some edge cases, so exercise caution.

Editor: Script method outline to `Tree`

While most IDEs and other editor tools provide a method/section outline for their scripts/documentation in the form of a tree, our editor has presented them in the form of a list for the longest time. Starting with GH-121534, thanks to the work of Michael Alexsander, we were able to make the transition to a tree-like syntax thanks to… well, Tree.

Before	After

Also the current selection is no longer forgotten when saving your project. Whoops!

GUI: Resize font to fit option for `Label` and `RichTextLabel`

Every developer knows the struggle of text container constraints all too well. No matter how reasonable you think your font scale is, or what kind of variable text you believe can make it in, a translation string or player input will inevitably break those bounds. Even if you actively and thoroughly filter all input length at all times, that’s still a lot of code upkeep and boilerplating across different areas of your project to achieve the desired effect.

Ismail Ivanov is one of many who felt this struggle, and decided to do something about it. GH-116791 wakes Label and RichTextLabel from this nightmare in the form of three new properties: auto_font_size, min_font_size, and max_font_size.

Rendering: Multi-bounce ambient occlusion approximation

Rendering has already received quite a lot of love in the 4.8 development cycle, which is why it’s all the more impressive that there’s so much to showcase in this snapshot alone! KenzieMac130 starts out strong with an incredibly impressive first-time contribution in GH-115426, which introduces multi-bounce ambient occlusion approximation. Previously, ambient occlusion in Godot failed to account for interreflections, meaning scenes were over-darkened in practice. Moving forward, we’ll be able to leverage a low-cost approximation of these interreflections, providing a more vibrant and accurate representation of what a given surface “should” look like.

As cited in the PR, this implementation is based upon a method from this 2016 Siggraph presentation, the technique of which has been adoped as industry-standard across multiple other engines. Those seeking a more technical breakdown are strongly encouraged to view the presentation itself!

Disabled	Enabled

Rendering: Directional lightmap specular light

Much like the previous point, Juan Manuel builds upon an existing foundation—this time by longtime member Hugo Locurcio—in order to introduce directional lightmap specular light to the engine with GH-109737. This addresses an existing issue with the way baked directional light set as static interacted with the LightmapGI set to directional, as this combination failed to bake any specular information. Thanks to the aforementioned PR, any directional specular information can not only be baked into the LightmapGI, but will produce results comparable to realtime directional light!

Those who want more a more technical breakdown on the subject are encouraged to watch this 2018 GDC presentation. For practical examples, we welcome you to enjoy this small sample of comparisons pulled from the PR:

Disabled	Enabled

Rendering: Decal support for the compatibility renderer

While not a “new” rendering feature per-se, this might as well be for those stuck on the compatibility renderer. While several features are excluded from this renderer by design—the intent is maximal support and performance after all—that doesn’t mean that an effort isn’t being made to bring existing features over. The only caveat is that the features in question must be suited to the aforementioned scope, such that performance won’t be degraded to any significant degree, nor should the feature itself be compromised to a point that it might as well not have been brought over in the first place.

Bastiaan Olij is no stranger to this song-and-dance, so it’s no surprise that he’s behind GH-118070, which brings one such feature to the compatibility renderer: decals! Based upon the approach taken by our mobile renderer and further adjusted for OpenGL, decals are brought over largely unscathed for users of all renderer types to enjoy. The only caveats of note for the compatibility renderer are as follows:

The maximum number of decals for a given frame is dependant on the hardware’s buffer limits. This is soft-capped to 64 by default in the project settings, but can be further increased depending on the capabilities of your targeted platform.
A given surface can only have a maximum of 8 decals. This is a hard-coded limit.

Export: Automate Android & Java SDK setup

While Godot supports exporting projects to Android, we sympathize with those developers who’ve struggled with the busywork that comes with it. That is: handling the SDK setup for Android and Java beforehand. Nobody is more familiar with this workflow than Fredia Huya-Kouadio, which is why he took to streamlining the entire process in GH-121849. Starting now, users will be able to leverage the new AndroidSDKManager class, which automates the entirety of this process. Now, at the click of a button, the editor will take care of downloading, setting up, and managing the Android and Java SDKs automatically!

This can be achieved in one of two ways. The first is within the Export Presets windows when an Android preset is added. If the editor detects that the current Android/Java SDK is invalid or missing, you’re now prompted with the ability to set those up then and there.

The second method is a reworked Install Android Build Template... from the Project menu, now renamed to Setup Android Build.... The updated button triggers the prompt for installing the Android/Java SDK when it detects they are not properly set up.

And more!

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

2D: Improve editing of 2D polygons (GH-98417).
Animation: Add BoneSpreader3D & skin_scale property to Bone in Skeleton3D (GH-120609).
Animation: Add AnimationNodeObservers for signaling animation events (GH-118789).
Audio: Allow CoreAudio to sleep and avoid busy work when idling (GH-117162).
Buildsystem: Fix building Android Editor with separate arches (GH-122186).
Buildsystem: Update Emscripten to 6.0.1 (GH-122412).
Core: Move property maps from ClassDB to GDType. Accelerate Object property access 1.6x (GH-122596).
Editor: Add replace preview to Find in Files (GH-122659).
Editor: Add toggle button for texture preview metadata overlay (GH-117216).
Editor: Clean and simplify Inspector header (GH-117499).
Editor: List monitor resolutions and refresh rates in editor Copy System Info (GH-122809).
Export: Editor: Add visionOS templates to download manager (GH-122559).
GDScript: Disallow strings as comments (GH-121833).
Input: Add support for gamepad gyro auto-calibration (GH-121487).
Platforms: Android: Expand Portrait Mode support and fix related issues (GH-121892).
Platforms: Replace WinRT/C++ dependency with custom COM+ code (GH-121633).
Platforms: Windows: Implement support for desktop toast notifications (no WinRT/C++) (GH-121711).
XR: visionOS: Add support for hand tracking and PSVR2 controllers on Apple Vision Pro (GH-122567).

Changelog

86 contributors submitted 224 fixes for this release. See our interactive changelog for the complete list of changes since 4.8 dev 3. You can also review all changes included in 4.8 compared to the previous 4.7 feature release.

This release is built from commit b56a91878.

Downloads

Download Godot 4.8 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

Fixing high polling rate mice on Windows in Godot

Hugo Locurcio — Mon, 24 Aug 2026 14:00:00 +0000

At long last, a performance issue with high polling rate mice on Windows has been fixed in Godot, starting with the recently released Godot 4.7.2. This article describes how the fix works, and why it’s so important today.

Note: The definition of “high polling rate” here refers to any mouse that can be configured to having a polling rate of at least 2 kHz. Mice that poll at 1 kHz are not considered high polling rate here, as they generally did not exhibit performance issues except on CPUs with very slow single-core performance.

What are high polling rate mice, and what are they useful for?

To ensure games feel good to play, we want the delay between an action being performed and the result being visible on screen (input lag) to be as low as possible. We also want inputs to be spaced as consistently as possible, avoiding jitter.

Mice are polled at a fixed rate. Historically, this has been 125 Hz as dictated by the USB standard. This means that the mouse input is polled every 8 milliseconds. This poses several limitations:

The mouse position reported to the operating system only updates 125 times per second. If you have a high refresh rate monitor (144 Hz or more), the mouse position will not update every frame, which will make mouse movement look choppy. This affects not just the operating system, but also games that rely on mouse input, including captured mouse mode.
Even on monitors with a 120 Hz or lower refresh rate, the mouse position will not be as consistent across the displayed frames on screen as with higher polling rates. The reason for this is that the mouse updates don’t line up with display refreshes. With a higher polling rate, there will be a lower average deviation between the time the mouse was last updated and the display refresh.
On average, and on top of any latency incurred by the operating system and mouse hardware, there will be a delay of 4 milliseconds between the mouse being moved by the user and the updated position being available to the operating system. While this may sound negligible at first, it is possible for some people to notice differences in mouse latency down to a millisecond.

In the late 2000s, manufacturers started providing options with 250 Hz, 500 Hz and 1 kHz polling rates. For a long time, 1 kHz was the fastest polling rate available on the market.

However, since the early 2020s, manufacturers have pushed polling rates beyond 1 kHz, including for wireless models. We’ve seen 2 kHz, 4 kHz and even 8 kHz mice reach the market, with pricing becoming more affordable as time goes on. This high polling rate allows for slightly reduced input latency, but most importantly, it ensures mouse updates are more consistent over time. With modern displays being able to reach refresh rates of 480 Hz, 720 Hz or even more, it becomes increasingly important to push mouse polling rates beyond the 1 kHz barrier.

This led to the rapid adoption of mice with such high polling rates, which poses a problem for software developers.

What’s the issue with high polling rate mice?

As the operating system receives mouse events much more frequently, it must handle them in a timely manner to avoid dropped events, or events being handled too late (which results in additional latency). In other words, with great polling rate comes great responsibility.

Unfortunately, operating systems originally didn’t account for the fact that mice could one day send thousands of updates per second. While modern CPUs’ processing power makes it possible to bruteforce through this problem on some platforms, this was particularly brutal on Windows.

In practice, this manifests as significant framerate drops as soon as a certain threshold of mouse updates per second is exceeded. How fast this threshold is reached depends on the mouse movement speed (as tiny mouse movements will not send an update on every poll), as well as CPU single-core performance. As of 2026 and on recent Windows 11 versions, on most CPUs, this limit is generally somewhere between 1 kHz and 2 kHz. If your mouse sends much more updates than this limit, the framerate can drop to the single digits, leading to an unplayable experience:

This issue is particularly difficult to troubleshoot for less tech-savvy users, as some mice can even default to polling rates above 1 kHz. This leads to a performance loss that appears to be related to the use of a specific mouse model, when it is in fact related to its polling rate.

Godot is not the only engine that runs into this issue on Windows. Thousands of games suffer from this issue too, from the earliest days of Windows gaming to today’s popular releases. Games that use non-captured mouse modes (i.e. with the mouse cursor visible) are more prone to this issue, as extra care must be taken to avoid performance pitfalls in this situation.

Linux (on both Wayland and X11) is generally not affected by this issue, regardless of the game.

Why does this issue happen on Windows specifically?

Windows has a long story of backward compatibility, dating back 30+ years. While this is a blessing in many cases, it ends up being a problem in this situation.

Windows has several types of mouse motion events:

Legacy input (known as WM_MOUSEMOVE). This is the usual kind of mouse motion event, designed for applications rather than games.
Raw input (known as WM_INPUT). Raw input was introduced in Windows XP as a way to allow games to read mouse input in a way that ignores OS processing (such as mouse acceleration, also known as the “Enhanced pointer precision” option). This is particularly desirable for first-person games, where mouse acceleration is usually not wanted by players (or is better configured in-game when desired).

However, when requesting raw input in a Windows application, it will still receive legacy input events at the same time. This is the case even when the application is currently in captured mouse mode (such as a first-person game, where the mouse cursor is not visible).

While it is possible to request only raw input and no legacy input, doing so breaks several parts of the application that are expected by users, such as moving the window by dragging its title bar. Therefore, we had to implement a different solution inspired by PH3’s blog post about high polling rate mice on Windows.

Solution

The solution is to treat mouse motion inputs separately from other input types, and handle them in a way that prevents congesting the input system. To achieve this:

Buffered reads are performed in the DisplayServerWindows::process_raw_input() function.
Additionally, in DisplayServerWindows::process_events(), the Windows API PeekMessageW() function is called in a way that prevents raw input (WM_INPUT) from being dispatched right away (which is what normally causes performance drops in captured mouse mode). Instead, it stays in queue for the next buffered read in process_raw_input().
Legacy inputs (WM_MOUSEMOVE and WM_NCMOUSEMOVE) are handled separately, but are only dispatched once per frame at most each. This avoids performance issues at high polling rate when in non-captured mouse modes.

Other inputs (keys, mouse buttons, mouse wheel) are treated as before, as they are not sent frequently enough to be a problem under the old approach. While keyboards with a polling rate greater than 1 kHz exist, it’s humanly impossible to (de)press keys in a way that could saturate the current input system.

Gamepad input remains treated by a separate system on Windows, and is not impacted by this fix. In any case, there are very few gamepads that can poll above 1 kHz as of writing.

Note that projects should still be careful to optimize their _input() and _unhandled_input() functions, particularly the code paths that are called for InputEventMouseMotion. These methods may be called once per rendered frame when input accumulation is enabled (the default). For example, on a 480 Hz monitor with V-Sync enabled, these methods may be called 480 times per second during fast mouse movements, assuming the system is fast enough to render at least 480 FPS. When input accumulation is disabled, these methods may be called on every mouse update, which can potentially mean 8,000 calls per second when using a mouse with 8 kHz polling rate.

Benchmark

For testing, we use the InputRepro2 testing project which is available in the pull request description.

PC specifications:

CPU: AMD Ryzen 9 9950X3D
GPU: NVIDIA GeForce RTX 5090
RAM: 64 GB (2×32 GB DDR5-6000 CL30)
OS: Windows 11 24H2
Monitor: ASUS ROG PG32UCDP (1080p @ 480 Hz mode)

Note: 4.7.1.stable does not include the fix described in this article, while 4.8.dev3 is the first development snapshot to include it. The recently released 4.7.2.stable also includes the fix.

Average framerate when moving the mouse in circles quickly:

No V-Sync (unlimited maximum framerate)

Benchmark	4.7.1.stable	4.8.dev3
No movement	4097 FPS (0.24 mspf)	4061 FPS (0.25 mspf)
With movement, visible mouse @ 1 kHz	2641 FPS (0.38 mspf)	2560 FPS (0.39 mspf)
With movement, visible mouse @ 2 kHz	1751 FPS (0.57 mspf)	1848 FPS (0.54 mspf)
With movement, visible mouse @ 4 kHz	973 FPS (1.03 mspf)*	1546 FPS (0.65 mspf)
With movement, visible mouse @ 8 kHz	173 FPS (5.78 mspf)*	1103 FPS (0.91 mspf)
With movement, captured mouse @ 1 kHz	2583 FPS (0.39 mspf)	2669 FPS (0.37 mspf)
With movement, captured mouse @ 2 kHz	1979 FPS (0.51 mspf)	2110 FPS (0.47 mspf)
With movement, captured mouse @ 4 kHz	1778 FPS (0.56 mspf)*	1962 FPS (0.51 mspf)
With movement, captured mouse @ 8 kHz	< 1 FPS (>1000.00 mspf)**	1703 FPS (0.59 mspf)

Prior to the fix, performance dropped to unplayable levels when moving the mouse with 8 kHz polling rate. Even with a 4 kHz polling rate, there were significant frametime deviations that resulted in movement being visibly jagged:

Compare the above graph with this frametime graph recorded under the same conditions, but with the fix in effect:

The 1% low FPS figure has been increased by a factor of 45.8 here! This is just one example of how significant the improvement can be thanks to this fix.

On slower CPUs, you will get more benefit from the fix described in this article, as the CPU used for this test has very high single-core performance (which is what determines how many input messages can be read per second). While this fix was not a huge change at 2 kHz polling rate on this particular CPU, it will definitely come in handy on slower processors or laptop CPUs, which have lower single-core performance compared to desktop CPUs.

How does this translate to a scenario where we aim to reach a high framerate consistently? With this fix, it’s a lot more feasible at 8 kHz now:

V-Sync 480 Hz

Benchmark	4.7.1.stable	4.8.dev3
No movement	480 FPS (2.08 mspf)	480 FPS (2.08 mspf)
With movement, visible mouse @ 1 kHz	478 FPS (2.09 mspf)	478 FPS (2.09 mspf)
With movement, visible mouse @ 2 kHz	473 FPS (2.11 mspf)	477 FPS (2.10 mspf)
With movement, visible mouse @ 4 kHz	472 FPS (2.12 mspf)*	477 FPS (2.10 mspf)**
With movement, visible mouse @ 8 kHz	151 FPS (6.62 mspf)*	477 FPS (2.10 mspf)
With movement, captured mouse @ 1 kHz	477 FPS (2.10 mspf)	478 FPS (2.09 mspf)
With movement, captured mouse @ 2 kHz	477 FPS (2.10 mspf)	478 FPS (2.09 mspf)
With movement, captured mouse @ 4 kHz	469 FPS (2.13 mspf)*	478 FPS (2.09 mspf)
With movement, captured mouse @ 8 kHz	< 1 FPS (>1000.00 mspf)**	477 FPS (2.10 mspf)

Prior to the fix, we saw a similar issue to the test case where V-Sync is disabled. The framerate didn’t quite reach the 480 FPS target we set here. In fact, it was lower when V-Sync is enabled at 8 kHz with the visible mouse mode (151 FPS instead of 173 FPS). On the frametime graph, there were frametime spikes that were easily noticeable to the naked eye:

The framerate is much more stable now, and is almost a locked 480 FPS:

Slight deviations at framerates this high are expected, as each frame only has ~2.1 milliseconds to render. It may be possible to find further improvements, but we are getting into the realm of diminishing returns here.

*: Large deviations in frametime occur, with some frames going past ~16.7 ms (slower than 1 frame at 60 FPS). Still playable, but not smooth (which is what we’d want from those high polling rates).
**: Huge deviations in frametime occur (some frames taking over 500 ms), making it unplayable.

References

Pull request
PH3 blog post about high polling rate mice on Windows
Blur Busters mouse guide
Fixing jitter, stutter and input lag in the Godot documentation

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 or 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.

Maintenance release: Godot 3.6.3

lawnjelly — Sat, 22 Aug 2026 12:00:00 +0000

Godot 3.6.2 has been our recommended stable LTS version of 3.x for a while now, but the time has come to make a new build, primarily due to changes in requirements for Android and iOS.

Google Play now requires new apps and updates to target Android 16 (API level 36). As a result we have updated Godot Android APIs and made compatibility changes to ensure users can update their Godot 3 games on Play Store with 3.6.3.

On iOS, the minimum version is bumped to 15.0 (the minimum supported by XCode 27), a minimum target export option is added, and 32-bit export is removed as it is not supported since iOS 11.

This is a safe and recommended update for all Godot 3.6.x users. It should have no major impact on your projects, even complex ones in production, if you’re already using 3.6.2-stable.

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

Download Godot 3.6.3 stable

Linux

macOS

Windows

Export templates and other downloads Make a Donation

The cover illustration is from Soul’s Remnant, a 2D platformmer MMORPG, where you’ll socialize and conquer your way through this mysterious world. You can play the game for free on Steam, and check out the developers on Bluesky and YouTube!

Changed

Export: iOS: Bump min. version to 15.0, remove 32-bit code, add min. target export option (GH-122324).
Network: mbedTLS: Always use Godot’s OS as entropy source (GH-121894).
Network: mbedTLS: Update to 3.6.7 (GH-121110).
Platforms: Android: Bump default target SDK to 36 (GH-120883).
Thirdparty: libpng: Update to 1.6.58 (GH-122506).

Fixed

Audio: Fix audio crackling issues due to incorrect WASAPI buffer size (GH-89283).
Audio: Suppress error when device is invalidated after IAudioClient::GetBufferSize (GH-122467).
Buildsystem: Add proper flags when using external recast (GH-112029).
Buildsystem: Ping master cache after saving cache (GH-122267).
Core: Minor BVH correctness fixes (GH-121501).
Export: Preserve the output from the gradle build command (GH-120612).
GDScript: Fix missing function signature hint (GH-68449).
Input: Fix new CI compiler warnings (GH-120627).
Platforms: iOS: Fix x86_64 simulator build. (GH-122639).
Platforms: LinuxBSD: Process TTS callback on the main thread to avoid speech-dispatcher deadlock (GH-110481).
Rendering: FTI - Optimize non-interpolated 2D items (GH-111195).
Rendering: Make physics interpolation compatible with separate-thread rendering (GH-114211).
Web: Add internal get_entropy() javascript function for web build (GH-122647).

Changelog

16 contributors submitted 20 fixes for this release. See our interactive changelog for the complete list of changes since the 3.6.2 release.

This release is built from commit a3378686f.

Bug reports

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

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 3.6.2 or earlier 3.x releases no longer works in 3.6.3).

Support

Donate now

Maintenance release: Godot 4.7.2

Thaddeus Crews — Tue, 18 Aug 2026 12:00:00 +0000

Has it already been a whole month since the last 4.7 maintenance release? How time flies… Well, no time to dwell on the past; let’s instead dwell on the present with yet another maintenance release: Godot 4.7.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.7.2 now or try the online version of the Godot editor.

Download Godot 4.7.2 stable

Linux

macOS

Windows

Export templates and other downloads Make a Donation

The cover illustration is from Horse Magnifier: The Full Horse, a horse-magnifier game about magnifying horses. You can buy the game on Steam, and follow the developer on Bluesky.

Changes

39 contributors submitted 57 fixes for this release. See our interactive changelog for the complete list of changes since the 4.7.1 maintenance release.

This release is built from commit ed1daf0bf.

3D: Fix 3D ruler tool tooltip (GH-120890).
Assetlib: Asset Store: Fix image width on different Editor Scales (GH-121470).
Core: Fix crash when failing to open log file for writing (GH-121926).
Core: Forbid negative weights in RandomPCG::rand_weighted (GH-120004).
Core: Make it impossible to have more than one main thread, and don’t release unnecessarily (GH-121161).
Core: Update DirAccess::create_temp to not fail on empty prefix parameter (GH-121315).
Editor: Don’t auto-translate favorite nodes (GH-122260).
Editor: Fix Visual Profiler cursor not appearing when graph is partially filled (GH-118294).
GDExtension: Fix register_extension_class never iterating parents for exposed checks (GH-120985).
GUI: Fix BaseButton input when enable_long_press_as_right_click is true (GH-120962).
Input: Fix performance issues when moving the mouse with high polling rate on Windows (GH-109639).
Input: Fix simultaneous shift release (GH-120327).
Input: Wayland: Fix IME popup position under fractional scaling on KDE Plasma (GH-121571).
Multiplayer: Fix peers stopping replication on deleting node they spawned with MultiplayerSpawner (GH-109864).
Navigation: Fix debug NavigationRegion3D colors not updating until project re-start (GH-120939).
Network: mbedTLS: Always use Godot’s OS as entropy source (GH-121759).
Platforms: Windows: Add exception handling to DispatcherQueueOptions init (GH-122261).
Rendering: Fix PCSS shadows using shadow range begin in the wrong space (GH-120774).
Thirdparty: Update AccessKit to 0.22.3 (GH-121393).

Known incompatibilities

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

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

Bug reports

Support

Donate now

Submissions open for Godot 2026 showreel

Emi — Sat, 15 Aug 2026 13:00:00 +0000

Showcase your Godot Engine 2026 creations! We invite you to submit videos featuring your published or in-progress games or tools so we can make the Godot 2026 Showreel.

Our annual showreels are informative and celebratory showcases, to highlight the wide array of projects developed using the Godot Engine. If you want to participate this year and share your Godot-made game, app, or tool, submit your entry starting today.

Help us to decide!

Like last year, we want to invite more people to participate in the voting phase. So, if you are a member of the Development Fund, you will be able to cast your votes alongside the Godot maintainers! To be eligible to vote, you need to have a recurrent donation active.

How to submit

You can submit your entry in our Godot Showreel website. Before submitting, please read the submission guidelines.

📅 Submissions close on October 1st 2026
📅 Voting from October 2nd until October 16th 2026

Need inspiration?

Check out our showreel playlist for some creative sparks and see what makes a great submission! Here is last year’s showreel:

Good luck! We can’t wait to see your creations!

GodotFest 2026 returns to Munich this November

GodotFest Team — Wed, 12 Aug 2026 00:00:00 +0000

Last November, close to 500 people joined us in Munich for the first GodotFest. We had 34 speakers, two stages, a workshop room, and two busy days of Godot. For a first edition, it was quite a turnout.

GodotFest is an annual conference for people who build with Godot. We are the small Munich team behind GodotCon 23, and we run the event independently, in close cooperation with the Godot Foundation. We started it because we wanted a place where developers could share what they had learned, show their games, and meet others working with the engine.

It worked, so GodotFest is coming back to smartvillage in Munich on the 3rd and 4th of November 2026.

This year’s theme is “Godot Means Business”. There will still be plenty of technical talks, panels and community time, but we are making more room for studios, publishers and service providers building businesses around Godot. MeetToMatch, powered by Photon, is included with every ticket, so attendees can arrange meetings before the event.

There will also be a game showcase, with space to bring your own hardware and let people play your game. The talks from 2025 are online if you would like an idea of what to expect from the programme.

And yes, the food is included again. Every ticket covers premium catering on both days: breakfast, lunch and afternoon snacks, plus coffee, soft drinks and water throughout the event. Vegan and gluten-free options will be available.

Call for speakers

Did you ship a game with Godot, build a useful tool, or learn something the hard way? We would like to hear about it. We are looking for talks and panels from developers, artists, educators, tool makers and community organizers. First-time speakers are welcome, too.

Submit a proposal, deadline: August 31st, 2026 at 13:00 UTC

The deadline was already extended once, so this one is final.

Tickets

Early Bird tickets have sold out. Regular tickets cost 249€ until September 30th and Late Bird tickets cost 349€ after that. VIP tickets are 799€ and include the VIP dinner and a custom shirt.

Tickets are on sale here.

We will share programme announcements on Bluesky, Mastodon and the newsletter. You can also join the Discord.

See you in Munich!

Overview

🌐 Website	GodotFest.com
📅 Dates	3rd, 4th of November 2026
🌍 Location	Munich, Germany
📍 Venue	smartvillage Bogenhausen Rosenkavalierplatz 13, 81925 Munich
🎤 Call for talks	talks.godotfest.com, until August 31st
🎟️ Tickets	tickets.godotfest.com
💬 Discord	https://discord.com/invite/vA4pNu4TTd

Dev snapshot: Godot 4.8 dev 3

Thaddeus Crews — Fri, 07 Aug 2026 12:00:00 +0000

With GodotCon Boston now behind us, our contributors have had nothing but time and energy to get their most-wanted features over the finish line. While feature freeze still isn’t for at least another month, that hasn’t stopped our community from making rapid progress in their work and reviews, meaning that we have quite a lot to go over today, so buckle up!

The cover illustration is from Sovereign Tower, a story-rich manangement RPG, where you play as the Sovereign of a magical tower and recruit eccentric Knights to your Round Table. You can buy the game on Steam, and follow the developers on Bluesky and their website.

Highlights

In case you missed them, see the 4.8 dev 1 and 4.8 dev 2 release notes for an overview of some key features which were already in those snapshots, and are therefore still available for testing in 4.8 dev 3.

Documentation: Support for admonitions

We rarely have the opportunity to showcase improvements in our documentation as proper highlights, much less as the opening item in a snapshot’s blog post! So when something like Cyril Bissey’s work in GH-111375—salvaged from Hugo Locurcio’s original PR—delivers something that’s just begging for a spotlight, we’ll welcome the opportunity with open arms.

In particular, our documentation—both in-editor and online—now offer native support for admonitions; That being: the built-in systems many documentation tools provide to highlight crucial information. As time of writing, our documentation tools use simple prefixes like “Note:” or “Warning:” to convey a similar effect, but this method causes critical details to blend in with the rest of the text. So starting now, we’ll begin slowly rolling out admonition replacements for these legacy systems, which will end up looking something like what you see below:

Dark Mode	Light Mode

GDScript: Underline warnings and errors in editor

Another improvement to visual feedback of critical details, and one which you will be able to experience right away, comes in the form of in-editor underlines for GDScript warnings and errors. Courtesy of Malcolm Anderson in GH-119588, the debugging process for GDScript will become much more streamlined thanks to the direct and immediate information provided by these underlines.

Now hang on, you might be thinking: “doesn’t GDScript already have this support?” Well, yes and no. Yes, because you would previously have a line with a warning/error be highlighted if a problem existed. No, because it highlighted the entire line, which both obfuscated the problem and risked multiple issues being hidden if they existed on the same line. With these changes, only the relevant portions of a given line will be underlined. For instance, the following codeblock would’ve previously been highlighted in its entirety:

Editor: `FileSystem` quality-of-life

Jayden Sipe is cheating a bit with this next point, as they managed to squeeze in two features worthy of a highlight in GH-119103. Not that we’re complaining; the more the merrier! Both highlights have to do with improvements to FileSystem and the way users interact with it.

The first of these features is the ability to zoom in/out of the window with a mouse’s scrollwheel. By simply holding Ctrl while hovering over a FileSystem window, the contents will either growing or shrinking upon scrolling the mouse up or down respectively.

Next up is glob-based searching. Sometimes you want to find a type of file or something with a specific prefix, without necessarily narrowing it down to a specific file. By utilizing glob-based search, now your results can explicitly capture whatever use-case you desire.

Plugin: Expose the property clipboard

Between this and FuzzySearch, we’ve been on a bit of a roll with granting developers access to previously-internal API. Jamis Gelvin took the helm this time around with GH-87087, granting access to the property clipboard directly. Previously, the only way a property’s contents could be copied/pasted is by the engine itself, meaning that users couldn’t directly modify or access this data. Moving foward, one can leverage get_property_clipboard() and set_property_clipboard() via EditorInspector, granting all developers direct access to this information.

XR: visionOS module

Remember Ricardo Sanchez-Saez, the contributor responsible for native visionOS support? Well, their work hasn’t concluded just yet, as they—along with co-authors Stuart Carnie and huiedenanhai—bring visionOS to new life as a module in GH-109975! With these changes, not only has our build server’s logic dramatically simplified, but this lays the groundwork for tvOS support in the near-future! This is all because… Um…

Alright, I’ll give it to you straight: I have no idea what any of this is about. These are people way smarter than me that’ve been tirelessly at work over the course of a year to fundamentally change systems I can’t even begin to understand to entirely new systems I only marginally understand. So for the time being, we’ll have to leave it at that, with the promise of more information coming soon™.

Hopefully the next highlight won’t be as technically involved to a point that it’d necessitate a dedicated blog post as well!

Input: Fix performance issues when moving the mouse with high polling rate on Windows

Ah.

To make a long story short: some mice are too fast for Windows; they were simply built different. Fortunately, Godot is also built different, and can now handle those mice like a champ. Hugo, the brain behind GH-109639 which implemented this fix, is preparing a dedicated blog post to give this fix the deep-dive it deserves. In the meantime, enjoy this comically oversimplified comparison:

Before	After

Update: The dedicated blog post is now up: Fixing high polling rate mice on Windows in Godot

And more!

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

Editor: Add Clear Project Cache option (GH-120093).
Editor: Android: Enable screen orientation change on large screens and in Project Manager (GH-121387).
Editor: Automatically create default resources in the editor for many objects (GH-88647).
Editor: Fix metadata formatting in inspector (GH-108878).
GDScript: Fix shutdown crash when ScriptInstance references its owner (GH-121762).
GUI: TabBar: Add options for tab sizing strategy (GH-113385).
GUI: Use OS taskbar progress when ProgressDialog is shown (GH-121505).
Physics: Add get_velocity_at_(local)_position() to RigidBody2D (GH-121142) and RigidBody3D (GH-121122).
Rendering: Fix directional shadow culling for orthogonal cameras (GH-121775).
Rendering: Improve SPIR-V reflection performance (GH-121835).

Changelog

91 contributors submitted 176 fixes for this release. See our interactive changelog for the complete list of changes since 4.8 dev 2. You can also review all changes included in 4.8 compared to the previous 4.7 feature release.

This release is built from commit 51105ccbe.

Downloads

Download Godot 4.8 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

Donate now

Release candidate: Godot 4.7.2 RC 1

Thaddeus Crews — Mon, 03 Aug 2026 12:00:00 +0000

A month and a half has passed since our initial release of Godot 4.7, which was then followed up with the Godot 4.7.1 maintenance release nearly three weeks ago. While we stand by the stable foundation of our maintenance releases, that doesn’t mean we’re ready to stop giving support to our most recently released version. In fact, thanks to the amount of work put into the in-progress 4.8 builds, the amount of resolved issues and regression fixes has only gone up! As such, we’re eager to deliver yet another maintenance release in the near future, starting with this initial release candidate: Godot 4.7.2 RC 1!

The cover illustration is from MOLDRISE, a psychological horror game where you must go up, go up, Go Up, Go Up, GO UP, GO UP, GO—. You can buy the game on Steam, and follow the developer on Bluesky, YouTube, and itch.io.

Highlights

This section covers the most relevant changes made since the 4.7.1 maintenance release, which are largely regression fixes (critical changes highlighted in bold):

3D: Fix 3D ruler tool tooltip (GH-120890).
Assetlib: Asset Store: Fix image width on different Editor Scales (GH-121470).
Core: Fix crash when failing to open log file for writing (GH-121926).
Core: Forbid negative weights in RandomPCG::rand_weighted (GH-120004).
Core: Make it impossible to have more than one main thread, and don’t release unnecessarily (GH-121161).
Core: Update DirAccess::create_temp to not fail on empty prefix parameter (GH-121315).
Editor: Fix Visual Profiler cursor not appearing when graph is partially filled (GH-118294).
GUI: Fix BaseButton input when enable_long_press_as_right_click is true (GH-120962).
Input: Fix performance issues when moving the mouse with high polling rate on Windows (GH-109639).
Input: Fix simultaneous shift release (GH-120327).
Input: Wayland: Fix IME popup position under fractional scaling on KDE Plasma (GH-121571).
Multiplayer: Fix peers stopping replication on deleting node they spawned with MultiplayerSpawner (GH-109864).
Navigation: Fix debug NavigationRegion3D colors not updating until project re-start (GH-120939).
Network: mbedTLS: Always use Godot’s OS as entropy source (GH-121759).
Rendering: Fix PCSS shadows using shadow range begin in the wrong space (GH-120774).
Thirdparty: Update AccessKit to 0.22.3 (GH-121393).

Changelog

37 contributors submitted 43 improvements for this release. See our interactive changelog for the complete list of changes since the 4.7.1 maintenance release.

This release is built from commit 36a04fe52.

Downloads

Download Godot 4.7.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

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.7.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

Dev snapshot: Godot 4.8 dev 2

Thaddeus Crews — Tue, 21 Jul 2026 12:00:00 +0000

Happy GodotCon Boston for those who celebrate! While many key contributors are already at this event as we speak, that doesn’t mean that development snapshots are slowing down anytime soon. We hope anyone that couldn’t make it to the event this year looks forward to further coverage and highlights in the near future, as you enjoy Godot 4.8 dev 2 in the meantime!

The cover illustration is from The Incident at Galley House, a detective game where you wield a strange contraption to reveal the truth behind the 1936 tragedy at Galley House. You can buy the game on Steam, and follow the developers—William Rous and Evil Trout—on their socials.

Highlights

In case you missed them, see the 4.8 dev 1 release notes for an overview of some key features which were already in that snapshot, and are therefore still available for testing in 4.8 dev 2.

Editor: Automatically expand created resources in inspector

Hugo Locurcio starts our roundup with GH-99725, bringing a long-desired QOL addition to the inspector: auto-expansion of resources. While most of our inspector items automatically revealed themselves when initialized, resources always existed as an unfortunate blindspot. As demonstrated below, this will no longer be the case!

While the process of playing a scene is already relatively streamlined, there’s always potential for further improvement, if you know where to look. Case-in-point: why not make it possible to play a scene from the file system directly? DexterFstone had this exact same thought, and decided to do something about it in GH-111941. Now any scene can be played from the file system’s context menu alone; no extra steps required!

Core: Write Object variants with `\n` between properties

While version control is a system we wholeheartedly stand by for production environments, there are undoubtably annoyances that come from it. There’s a reason that most developers will opt for storing settings as text instead of binary data, as the former allows for seamless integration of diff and merge functionality.

…In theory, anyway.

Yeah, this advantage kind of breaks apart when everything is batched together on a single line, as is the case with any Object data. This makes parsing differences between file versions nearly impossible at a glance, and effectively makes any merge tool have to treat the file as if it were binary to begin with. Robert Wallis recognized these concerns, and spearheaded GH-92102 to give Object some breathing room.

And more!

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

2D: Add proper instructions for using scene paint 2D (GH-121227)
3D: Re-enable freelook inertia by default in the 3D editor (GH-121478).
Assetlib: Set the Asset Store’s default sorting to highest scored (GH-121112).
Core: Make it impossible to have more than one main thread, and don’t release unnecessarily (GH-121161).
Core: Speed up removing many child nodes (GH-120942).
Editor: Show doc tooltips in quick settings (GH-121278).
Editor: Show inspector warning on deprecated properties (GH-121364).
Export: Make shader compiler float constant formatting deterministic (GH-120968).
GDScript: Make language shutdown more crash resilient (GH-120976).
Input: Ignore joypads on unfocused window by default for new projects (GH-120399).
Rendering: Use non-volumetric fog in WorldEnvironment sky reflections (GH-107958).
Thirdparty: Update to Jolt Physics 5.6.0 (GH-121260).

Changelog

93 contributors submitted 197 fixes for this release. See our interactive changelog for the complete list of changes since 4.8 dev 1. You can also review all changes included in 4.8 compared to the previous 4.7 feature release.

This release is built from commit 7220d456d.

Downloads

Download Godot 4.8 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 Community Poll 2026

Emi — Thu, 16 Jul 2026 17:00:00 +0000

Update: This poll is now over. You can view the results here or download the csv with all the responses.

We want to learn more about the Godot community, understand who the users of the engine are, and find out how we can better support you. To achieve that, we have a short set of questions and hope you will take a few minutes to fill them out. The results will also help us guide our current and future items in the priority list.

The poll is anonymous, and we will share the results publicly once submissions are closed. It will remain open for a month and should take only 5-10 minutes to complete.

👉 Click here to complete the 2026 community poll!

If you are interested in results from previous years, you can find them at the following links: 2025, 2024, 2023, 2022, 2021, 2020.

Godot Team Updates @ GodotCon Boston 2026

Chad Stewart — Tue, 14 Jul 2026 15:00:00 +0000

Our second annual GodotCon in North America is right around the corner and it is full steam ahead for the Godot community in Boston. The schedule has been announced so we thought it would be worth highlighting some of the official updates and fun talks from the Godot Foundation that will take place during the conference.

Godot Rendering Team Update

🗣️ Clay John

An update on what major changes have happened within the renderer over the last two years with a focus on technical hurdles that we have overcome and the major limitations that we are now seeing.

Also, a brief look at the future of Godot’s renderer including what to expect in terms of new high-end features and the long-term vision for the renderer.

What’s New in Android

🗣️ Fredia L Huya-Kouadio

Discover what’s new in Android in 2026 for Godot developers!

This talk will provide updates, new development, and new features to the Godot Android Platform since 2025.

The talk will also cover the growth of the Godot Android editor since 2025, and will provide a quick look at its 2026 development roadmap.

How to make a VR game entirely in VR! (No PC required)

🗣️ David Snopek, Logan Lang

Did you know that the Godot editor can run on standalone VR headsets like the Meta Quest 2/3, Pico 4, or Samsung Galaxy XR?

This can allow you to build a game entirely in VR, without using a desktop or laptop computer at all!

In this talk, David Snopek and Logan Lang of Godot’s XR team, will:

Tell the story of “Expedition to Blobotopia”, a VR game which they built in one week for the Godot Wild Jam #81, working entirely on Meta Quest 3 headsets
Explain the advantages of doing game dev in the headset
Share tips and tricks for how you can do it too
Demonstrate the newly released GABE, which allows running full Android Gradle builds on the headset
Explain the basics of publishing your VR game on the Meta Horizon Store and Google Play Store
Give a live demo of the editor running on a headset!

Discover a new way to add VR directly into your game development workflow!

Where Every Millisecond Counts: Optimizing Godot for Low-Spec Devices

🗣️ Clay John, Pablo Selener, David Snopek

Low-spec targets like mobile and standalone VR leave little room for waste. This session covers two things: the engine-level optimizations W4 Games contributed upstream that make all Godot games faster, and the techniques developers can apply in their own projects without modifying Godot’s source. Much of this work was originally funded by commercial engagements and is now upstream for everyone.

Getting started with cross-platform XR development

🗣️ Fredia L Huya-Kouadio, David Snopek

This talk will walk attendees through the process of creating an XR game that can run on all modern XR platforms (Android XR, Meta Horizon OS, Pico OS, visionOS) and leverage capabilities unique to each platform.

Attendees will also be walked through the process of porting an existing ‘flat’ 3D game to an immersive or volumetric game running on an XR device.

GodotCon Boston 2026 takes place from July 20th - July 22nd with a day of workshops on the 20th and the main conference on the 21st and 22nd. There are 20 other talks to see along with the Godot games showcase, nightly social events, and catered breakfast and lunch. Tickets are on-sale now. Room in workshops is still available!

Buy tickets 🎟️

Maintenance release: Godot 4.7.1

Thaddeus Crews — Tue, 14 Jul 2026 12:00:00 +0000

It’s been nearly four weeks since we saw the release of Godot 4.7, which has given our team ample time to prepare for its first maintenance release. This progress was made in tandem with Godot 4.8, whose first development snapshot released last week, and will hopefully see its second snapshot later this week. But for those sticking with the rock-solid foundation Godot 4.7 provided, only iterating on critical regressions/crashes reported by the community in that time, you need look no further than today’s maintenance release: 4.7.1-stable!

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

Download Godot 4.7.1 stable

Linux

macOS

Windows

Export templates and other downloads Make a Donation

The cover illustration is from Stackflow, a strategy rougelike game, where you clear rows of blocks to unlock abilities to more proficently and satisfyingly clear yet more rows of blocks. You can buy the game or try the demo on Steam, and follow the developer on itch.io and GitHub.

Changes

42 contributors submitted 78 fixes for this release. See our interactive changelog for the complete list of changes since the 4.7-stable release.

This release is built from commit a13da4feb.

2D: Improve 2D editor dropping code (GH-119418).
3D: Fix closed Curve3D first/last point missing in/out control point (GH-120684).
Animation: Make animation folding access cfg only at save/load project time (GH-120403).
Assetlib: Set the Asset Store’s default sorting to highest scored (GH-121112).
Editor: Guard against non-main-thread emission of EditorFileSystem changed signal (GH-115083).
Editor: Wrap long project title (GH-119580).
GUI: Don’t automatically open virtual keyboard when popup menu shows (GH-120768).
GUI: Fix crash in Tree::_get_item_focus_rect (GH-120538).
GUI: Fix scene tree drag-n-drop regression on touchscreens (GH-120456).
GUI: Fix visual glitch with connections lines in GraphEdit (GH-120488).
Input: Android: Fix EditorSettings not instantiated error when running game (GH-120723).
Input: Fix backspace being unable to delete pre-existing text in any input field when using a soft keyboard on Android (GH-119798).
Navigation: Fix navigation agents unconditionally getting added to avoidance simulation after pause resume (GH-120249).
Network: Set inited=false on CookieContextMbedTLS::clear to avoid accidental double destruction (GH-120371).
Rendering: Fix flickering lighting on mesh-instances with non-uniform scale (GH-119784).
Rendering: Fix orthographic camera directional shadow culling (GH-120711).
Rendering: Fix previous transform getting remembered for 2 frames after the instance stops moving (GH-119941).
Rendering: Seek past skipped shader variant payloads to avoid reading incorrect data (GH-119792).

Known incompatibilities

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

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

Bug reports

Support

Donate now

Release candidate: Godot 4.7.1 RC 2

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

As distance from the Godot 4.7 stable release grows, so too does the amount of spotted regressions and subsequent regression fixes. We don’t have quite as many fixes to share compared to 4.7.1 RC 1, but there’s still enough to go around to warrant a second release candidate for this maintenance cycle.

The cover illustration is from Interdimensional Vending Machine, a psychological horror game where you play as a homeless girl in a distorted city, surviving off a vending machine whose contents reshape your fate. You can buy the game on Steam or try an older version for free on itch.io, and follow the developer on itch.io and YouTube.

Highlights

This section covers all changes made since 4.7.1 RC 1, which are largely regression fixes:

2D: Improve 2D editor dropping code (GH-119418).
3D: Fix GridMap editor cursor starting at the wrong position (GH-120595).
Animation: Fix Abort on Reset functionality in AnimationNodeOneShot (GH-120478).
Core: Cherry-picks for the 4.7 branch (future 4.7.1) - 3rd batch (GH-120917).
Editor: Clean Up x position calcuation of the AudioStream filename in the Inspector (GH-119995).
Editor: Fix .godot file icon saturation in editor file dialogs (GH-120376).
Editor: Fix crash in Project Settings when an autoload has been freed (GH-120874).
Editor: Fix debugger call stack not selecting nodes in remote scene tree (GH-94096).
Editor: Fix incorrect non-unique resource indicator (GH-120886).
Editor: Fix ownership issues when pasting as replacement (GH-119790).
Editor: Fix possible freeze when running project with floating script editor (GH-119614).
Editor: Fix scene not requesting save for Load as Placeholder (GH-120823).
Editor: Fix scene tab titles not updating on language change (GH-120554).
Editor: Guard against non-main-thread emission of EditorFileSystem changed signal (GH-115083).
Editor: Make Instant Preview work for first selection after being enabled (GH-116651).
Export: Fix incorrect per-instance shader parameters when exporting in headless mode (GH-120794).
GUI: Add empty icons for file dialog menu to the default theme (GH-120449).
GUI: Don’t automatically open virtual keyboard when popup menu shows (GH-120768).
GUI: Range: Don’t use min for snap offset when it’s too big (GH-113380).
GUI: Set SpinBox’s internal node’s use_parent_material to true (GH-120714).
Import: Fix extracting materials without a per-material override (GH-120870).
Import: GLTF: Use p_state parameter directly (GH-119071).
Network: mbedtls: Update to 3.6.7 (GH-121055).
Physics: Fix crash when assigning more than 2047 MiB to Jolt temp buffer (GH-120895).
Physics: Fix crash when clicking via the Game view API created collisions (GH-120826).
Rendering: Fix hint_default_transparent used with sampler2DArray (GH-120433).
Rendering: Fix orthographic camera directional shadow culling (GH-120711).
Tests: Crypto: Add sign/verify and encrypt/decrypt tests (GH-120903).
Tests: Crypto: Add tests for AESContext (GH-120847).

Changelog

24 contributors submitted 29 improvements for this release. See our interactive changelog for the complete list of changes since 4.7.1 RC 1. You can also review all changes included in 4.7.1 compared to the previous 4.7 feature release.

This release is built from commit d6096250e.

Downloads

Download Godot 4.7.1 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.7.1. 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

Dev snapshot: Godot 4.8 dev 1

Thaddeus Crews — Mon, 06 Jul 2026 12:00:00 +0000

It’s been just over two weeks since we saw the stable release of Godot 4.7. In that time, we’ve been hard at working preparing for an upcoming maintenance release with our first 4.7.1 release candidate, and laying a strong foundation for what will become Godot 4.8. Last week already highlighted the former, so we’re opening the week strong with the latter: our first Godot 4.8 development snapshot. Unlike last week, which was entirely focused on regressions and critical bugfixes, we’ll be spotlighting several new features and functionality you can get your hands on right now.

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 Feed The Pit, a story-driven, investigative horror game where you hunt down the wealthy in order to Feed The Pit. You can buy the game on Steam or the iOS App Store, and follow the developers on YouTube and itch.io.

Highlights

One of the most exciting additions of the past few release cycles was undoubtably the ability to embed the game view within the editor. However, this feature might come as a surprise to many of you, as the default behavior since its inception has been a floating window. This was initially because not all desktop platforms had full support for this functionality, but we’ve since reached the point that all of our supported platforms can utilize it. As such, Michael Alexsander officially kickstarted this new default view in GH-120736 for all projects moving forward.

Pairing nicely with this new default setting is a new layout for the game view itself. Specifically: a toolbar overhaul. Because even if you were aware of the docked view before, actually finding the embed options was a bit tricky, as quite a lot of the important information was obfuscated or otherwise obstructed. Jayden Sipe spearheaded a brand new look for the toolbar in GH-118664, emphasizing usability and clarity compared to the prior implementation.

Old	New

Docked game view is only enabled by default for new projects; existing projects will have to manually enable this by toggling this option on the updated game view:

Editor: Support drag-toggle visibility in scene tree

There’s a lot of editor goodies to cover today, and Mikael Hermansson keeps the ball rolling with GH-118634, adding the ability to drag-toggle visibility in the scene tree editor. Now when toggling the visibility of a given node, the newly toggled state can be applied to any subsequent nodes when dragging the mouse across them.

Editor: Allow 3D viewports to override `Gridmap` axis

Michael delivered some QOL to 3D viewports with GH-117569, enabling them to dynamically override the GridMap editor axis. Through the new editor option “Allow Viewport Override” (enabled by default), hovering the mouse over a viewport set to a specific side will cause the currently edited axis to match that side.

Editor: Pseudolocalization preview

We’ve talked about the importance of accessibility a lot in these blog posts, so it should be emphasized that internationalization goes hand-in-hand with those efforts. To that end: making a title more accessible to users across multiple languages can be streamlined significantly through the use of pseudolocalization. This simple toggle simulates changes that might take place during localization, allowing any issues that would come from that process to be recognized as early as possible in development.

It then should come as no surprise that Tomasz Chabora, the same user responsible for hot-swapping languages in the editor, would seek to further expand the utility and awareness of this crucial functionality. Thanks to GH-119443, users are now able to access this functionality from within the editor itself. The hope is that this will not only make developers able to find these issues even earlier than before, but that it will also shine a spotlight on the feature as a whole.

GUI: Sticky tree items

One of the most common requests we’ve seen for improving Tree functionality is the ability to support “sticky items”. That is: the ability for a given line to stick to the top if it represents a foldable region. Koliur Rahman is no stranger to integrating popular editor requests, so it was only a matter of time before they delivered the desired functionality in GH-115697.

Certain trees that have above-average nesting might have a net-negative experience with sticky headers. This will be given hard-coded exceptions in the meantime (see GH-121000 for Skeleton3D), as we investigate configurable minimums.

GUI: `TextEdit` and `CodeEdit` touch support

We’ve given the standard desktop experience a lot of love this blogpost, so let’s pivot to something a bit more niche (for desktops): touch support. Given mobile devices represent some of our most prominent platforms, we seek to make the tactile experience of Godot first-rate wherever possible. To that end: Anish Kumar expanded the red-carpet treatment even further with GH-119706, bringing touch support to both TextEdit and CodeEdit. The new functionality is as follows:

Tap (press → release): Positions the cursor and opens the virtual keyboard.
Drag (press → drag → release): scrolls the text content, including inertial scrolling support.
- This extends to the code completion popup, which previously could not be scrolled via touch input.
Text selection:
- Double-tap selects a word.
- Double-tap, hold, and drag selects the portion you’re hovering over.

Core: `FuzzySearch` and `FuzzySearchMatch`

“Fuzzy searching” is the practice of a search result returning matches similar to the passed query, rather than only returning an exact match. This functionality has actually been part of the core engine for nearly two years at this point, courtesy of first-time contributor Adam Johnston in GH-98278, in service of our quick open search. However, that’s where the functionality remained ever since, never actually being exposed to our binding API. But now, courtesy of now regular contributor Adam in GH-107126, this functionality is finally ready to roll for all users.

var items := ["Potion of Healing", "Greater Health Potion", "Poison Vial"]
var fuzzy := FuzzySearch.new()
for result in fuzzy.search_all("health potion", items):
# Prints "Greater Health Potion", "Potion of Healing".
print(result.target)

And more!

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

3D: Add octant visualization to GridMap (GH-118583).
Audio: Fix AudioStreamPlayer.get_playback_position() with AudioStreamPlaylist returns 0 regardless of start time (GH-114867).
Editor: Add an option to run the project upgrade tool when updating to a new Godot version (GH-119466).
Editor: Android: Update game menu bar to match desktop editor (GH-119156).
Editor: Show enum integer values in inspector tooltips (GH-102734).
Editor: Use VHS Circle as the default editor color picker shape (GH-110615).
Export: Add Filter to Project Export → Options tab (GH-118898).
Export: Add SPM support for Apple Embedded plugins (.gdip) (GH-116939).
Input: Add support for joypad touchpads (GH-111714).
Network: mbedTLS: Update to 4.1.0, PSA Crypto (GH-120725).
Platforms: Implement OS::get_processor_name() for Android (GH-120896).
Rendering: Add support for ASTC 6x6 and high quality compression profiles (GH-115003).
Shaders: GDShader: Add implicit conversion of bool constants to float, int, and uint (GH-120715).

Changelog

135 contributors submitted 314 fixes for this release. See our interactive changelog for the complete list of changes since the 4.7 feature release.

This release is built from commit ebbf577a0.

Downloads

Download Godot 4.8 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

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 Engine Official

Dev snapshot: Godot 4.8 dev 5

Highlights

Rendering: Mip-level texture streaming

Import: Allow preserving alpha test coverage

Editor: Clean and simplify 2D toolbar

And more!

Changelog

Downloads

Godot is downloading...

Known issues

Bug reports

Support

Dev snapshot: Godot 4.8 dev 4

Highlights

VFX: Trail3D

Shaders: VisualShader node groups

Editor: Convert main screen plugins into docks

Editor: Script method outline to Tree

GUI: Resize font to fit option for Label and RichTextLabel

Rendering: Multi-bounce ambient occlusion approximation

Rendering: Directional lightmap specular light

Rendering: Decal support for the compatibility renderer

Export: Automate Android & Java SDK setup

And more!

Changelog

Downloads

Godot is downloading...

Known issues

Bug reports

Support

Fixing high polling rate mice on Windows in Godot

What are high polling rate mice, and what are they useful for?

What’s the issue with high polling rate mice?

Why does this issue happen on Windows specifically?

Solution

Benchmark

No V-Sync (unlimited maximum framerate)

V-Sync 480 Hz

References

Support

Maintenance release: Godot 3.6.3

Godot is downloading...

Changed

Fixed

Changelog

Bug reports

Support

Maintenance release: Godot 4.7.2

Godot is downloading...

Changes

Known incompatibilities

Bug reports

Support

Submissions open for Godot 2026 showreel

Help us to decide!

How to submit

Need inspiration?

GodotFest 2026 returns to Munich this November

Call for speakers

Sponsors

Tickets

Overview

Dev snapshot: Godot 4.8 dev 3

Highlights

Documentation: Support for admonitions

GDScript: Underline warnings and errors in editor

Editor: FileSystem quality-of-life

Plugin: Expose the property clipboard

XR: visionOS module

Input: Fix performance issues when moving the mouse with high polling rate on Windows

And more!

Changelog

Downloads

Godot is downloading...

Known issues

Bug reports

Support

Release candidate: Godot 4.7.2 RC 1

Highlights

VFX: `Trail3D`

Editor: Script method outline to `Tree`

GUI: Resize font to fit option for `Label` and `RichTextLabel`

Editor: `FileSystem` quality-of-life

Core: Write Object variants with `\n` between properties

Editor: Allow 3D viewports to override `Gridmap` axis

GUI: `TextEdit` and `CodeEdit` touch support

Core: `FuzzySearch` and `FuzzySearchMatch`