The Godot project has published the second beta snapshot of engine version 4.8, roughly two weeks after the first beta. According to the official release post, the team addressed the detection and resolution of close to 150 regressions in that window, and the release is described as feature-complete at this stage. The build is compiled from commit cafc17a19.
The post frames this snapshot as lighter than earlier development snapshots, and directs readers to the beta 1 highlights for the overall picture of what is new in 4.8. The beta 2 notes therefore cover only changes made between the two beta snapshots, which the project says are largely regression fixes — cases where something that worked in a previous release stopped working.
Scale is spelled out in the post: 59 contributors submitted 144 fixes for this release. An interactive changelog lists the complete set of changes since 4.8-beta1, and a separate comparison covers everything in 4.8 against the previous 4.7 feature release.
The listed fixes span most of the engine's subsystems. In animation, collapsing the time of a bezier track with box scaling produced incorrect undo data (GH-124433). The Asset Store's default sorting was returned to most relevant (GH-124749). The build system's CI minimum Python version moved from 3.9 to 3.10 (GH-122597), and Optimize was enabled for GodotSharp debug builds in the C# area (GH-124391).
Editor and scripting fixes include disabling CanvasItem manipulation for native debug builds (GH-124549), correcting an evaluator that did not run inside static functions (GH-107791), and applying COMPLETION_DECLARATION to for-loop variables in GDScript (GH-124885). In GUI, BaseButton now checks the visible viewport rect when handling touch events (GH-123008).
Rendering and content-pipeline items are also in the list: a fix for multiply blending being too dark in Compatibility (GH-124838), a bug in insertion of lightmap caches into unwrap_cache (GH-122494), and a change to the default curve range for particle angles to [-1, 1] (GH-123959). Various Unicode-related files were updated to version 18.0.0 (GH-123567), and the error message when using a Camera3D on an XR viewport was improved (GH-124680).
One change has a direct tooling consequence for C# developers: the .NET build, marked as mono, now requires .NET 10.0 or newer, moving the minimum supported version up from .NET 8 to 10. The standard build continues to include support for GDScript and GDExtension, while the .NET build adds C# on top of those.
The project also points testers at alternative targets: a Web editor, an XR editor, and an Android editor for this release. Access to the Android editor's pre-release builds requires requesting to join a testing group.
The post is explicit that this is pre-release software. Maintainers advise frequent backups or a version control system such as Git to protect projects against corruption or data loss. During beta, the stated focus is on solving both regressions and significant new bugs introduced by new features, with a dynamic list of regressions and significant issues maintained and updated as more users test the snapshots.
The project also acknowledges that each release ships with issues already reported but not yet fixed, pointing to the GitHub issue tracker for the full list of known bugs. Testers are asked to search existing issues before filing new reports, and regressions in their own projects — things that worked in earlier 4.x releases but fail in this snapshot — are called out as especially important to report.
For working developers, the practical read is that 4.8 is in stabilization rather than feature development. Teams evaluating an upgrade can use the beta period to test their projects against the snapshot and file regressions while maintainers are still prioritizing them, rather than discovering breakage after the stable release. The .NET 10 requirement is the item most likely to force action before adoption, since it changes the toolchain baseline for C# projects.
That last point is editorial interpretation, not a project recommendation: the post does not state a stable release date, does not describe migration steps for projects on older .NET versions, and does not quantify how many of the 144 fixes affect any particular workflow. The regression count of nearly 150 is the project's own characterization of work done between betas, not an independent audit.
The post also does not detail what the beta 1 highlights contained, so readers assessing the full 4.8 feature set need that separate document. And because the notes cover only the delta between beta 1 and beta 2, anyone jumping straight to beta 2 should review both sets of notes.
Godot is described as a non-profit, open-source engine developed by hundreds of contributors in their free time alongside a small number of part- and full-time developers funded by donations through the Godot Development Fund, managed by the Godot Foundation. The release post includes a funding appeal alongside the technical notes.
The concrete takeaway: beta 2 is a maintenance-focused snapshot with a documented fix list, a raised .NET floor, and an open invitation to report regressions. Whether it is stable enough for production depends on testing specific to each project, which the project itself leaves to its users during the beta stage.