Godot 4.7 beta brings real HDR output, AreaLight3D, and 1,265 fixes
Godot 4.7 beta 3 dropped today, focused on squashing regressions before stable. The release has been baking since April 24, when beta 1 went out with 1,265 fixes from 309 contributors against 4.6-stable. The headline features are HDR output across every desktop platform, a new AreaLight3D node, and a long list of editor and 3D pipeline improvements.
An overview of what changed in Godot 4.7 beta
HDR output, finally
Godot has rendered scenes internally in HDR for years. The piece that was missing was the output. 4.7 ships HDR output on every desktop platform: Windows, macOS, Linux, and BSD all now drive HDR monitors directly. The internal HDR pipeline can finally land its full dynamic range on the panel instead of getting tonemapped down to 8-bit SDR at the last step.
This is a much bigger deal than it sounds. Bloom, emissive surfaces, sun-disc highlights, and any scene with a wide luminance range now look the way the renderer always wanted them to. Combined with the existing tonemapper choices, it puts Godot's output in the same conversation as Unreal and Unity on consumer HDR hardware.
AreaLight3D
The new AreaLight3D node renders real-time light from a rectangular surface. Before 4.7, you'd scatter several point lights and tune attenuation to fake a soft area source. That's gone. You drop one node, set width and height, and get correct soft shadowing and proper distance falloff.
This is the kind of feature that makes interior lighting setups dramatically less painful. Studio softboxes, light panels, garage doors with daylight coming in: all of these were either ugly approximations or expensive light probe bakes. Now they're a single node.
Real HDR output in Godot 4.7
Ray-tracing polish and editor improvements
The ray-tracing pipeline introduced in 4.6 picks up meaningful fixes. Denoising quality is improved for static geometry. The probe placement tool got faster and more predictable. SDFGI's flicker on moving lights is reduced.
On the editor side, the 3D viewport got the usual round of quality-of-life: better gizmo precision, snapping improvements, and a new VirtualJoystick node that's useful for mobile and accessibility testing without leaving the desktop editor.
What else is in there
The release notes run long, but the items worth flagging for game devs:
- C# scripts now get hot-reload by default in the editor, which closes a long-standing gap with GDScript.
- The animation tree editor got an undo/redo overhaul that finally handles complex graph edits without breaking state.
- Web export now includes WebGPU support behind a flag, matching what the engine has done for native targets.
- Several Vulkan validation issues that caused intermittent crashes on Linux + Mesa were resolved.
Timing and stable release
Stable is expected late June. Beta 3 today is about regression cleanup, not new features, so this is the version to install if you want to test against your project before the final release lands.
For projects on 4.6, the upgrade path is the usual story: open in 4.7, hit the migration prompt, fix any deprecated API warnings, test. The team is unusually confident about 4.7's compatibility, in part because Godot's API stability promise tightened around 4.5 and has held.
This release follows the controversy in March about AI-generated pull requests overwhelming the maintainers. The fact that 309 human contributors landed 1,265 fixes since 4.6 suggests the project is still able to ship at pace despite the noise.
What we'd test first
For studios on 4.6, the HDR output is the single most visible upgrade. Open your most lit-up scene, switch to an HDR display target, and the answer to "should we ship 4.7" will be obvious within ninety seconds.
For new projects, AreaLight3D is the one to learn first. Build your standard lighting kit (sun, ambient, key, fill, kick) around area lights instead of points, and your scenes will look better than they did on 4.6 with zero extra effort.