Godot 4.7 hits RC2 with stable now days away
Godot 4.7 reached its second release candidate today. The release has been baking since April 24, when beta 1 went out with 1,265 fixes from 309 contributors against 4.6-stable. RC1 landed on June 8 with just 16 fixes from 16 contributors, the kind of quiet snapshot that means the hard work is done. RC2 today mops up a few late regressions, and that's usually the last stop before a final build.
A hands-on overview of what's new in Godot 4.7
What RC2 actually fixed
RC2 is regression cleanup, not new features. The team caught a deadlock in WorkerThreadPool that could freeze multithreaded projects, and a related bug where the message queue stopped flushing before a MainLoop iteration finished. Both are the kind of intermittent hang that's miserable to reproduce and worse to ship. The rest of the list is editor polish: SceneTreeEditor drag operations that failed silently, AnimationTree crashes from a missing null check on root animation nodes, and a tilemap randomization bug that skipped the first tile.
None of these are glamorous. All of them are the reason you wait for a release candidate to settle before you move a production project over.
The features that ship with 4.7
We covered the headline features when beta 1 dropped, and nothing has changed since the feature freeze. The two worth repeating for anyone deciding whether to upgrade.
HDR output now works on every desktop platform. Godot has rendered internally in HDR for years, but the output stage tonemapped everything down to 8-bit SDR at the last step. 4.7 drives HDR monitors directly on Windows, macOS, Linux, and BSD, so bloom, emissive surfaces, and wide-luminance scenes finally land on the panel the way the renderer intended.
The new AreaLight3D node renders soft light from a rectangular surface. Before, you faked a ceiling panel or a window by scattering point lights and tuning attenuation until it looked passable. Now it's one node with a width and a height, with correct soft shadowing and distance falloff. Interior lighting setups that used to take an afternoon take a minute.
The release also brings C# hot-reload by default, an animation tree editor with proper undo/redo, and WebGPU web export behind a flag, which is the part we watch most closely.
What it means for web games
The WebGPU export flag is the line item that matters for browser games. Godot has shipped solid WebGL2 web export for years, but WebGPU is where compute shaders, better draw-call batching, and modern pipelines live. Having it in a stable Godot build, even behind a flag, means the engine's web target stops being a generation behind the native one. That gap closing is the whole reason WebGPU mattered in the first place, and we wrote about it in January.
For a platform like ours, where games run instantly in the browser with no install, an engine shipping a real WebGPU path is direct upside. More engines targeting WebGPU means more games that look good in a tab without a download, which is the bet Cinevva is built on.
Should you upgrade
If you're on 4.6 and your project is in active development, install RC2 in a branch and test now. The team's confidence in 4.7's compatibility is high, partly because the API stability promise tightened around 4.5 and has held. The migration path is the usual one: open in 4.7, clear the deprecated API warnings, run your test scenes.
If you ship on a fixed schedule, wait the few extra days for stable. RC2 being this quiet is the signal that the wait won't be long. The last beta-to-stable cycle for 4.6 went smoothly, and 4.7 looks set to repeat it.