Godot 4.8 dev 6: contact shadows, and what to test carefully

Source check: 28 September 2026. A rendering feature can make a development release worth investigating without making it the right version for an existing game project. Godot 4.8 dev 6 is a useful example: its September announcement contains concrete changes, but its release channel remains part of the story.

Start with the version label

At this source check, the official release archive lists 4.8 dev 6, dated 15 September 2026, as a development build. The latest stable entry is 4.7.2, dated 18 August 2026. These are different tracks, not interchangeable labels for the same release.

That distinction answers an important question before any feature comparison: are you looking at a development snapshot to evaluate, or the project’s stable maintenance release? Check the archive again when acting on this article, because these entries will change.

What the September snapshot announces

The 4.8 dev 6 announcement introduces screen-space contact shadows for directional lights. The controls involve both the Environment resource and the directional light node, and the feature blends with existing shadow maps. The release also reorganizes the 3D toolbar.

The same announcement says it fixes a macOS startup crash and a Google Play upload failure found in dev 5. Those are the project’s reported fixes, not a guarantee that every development-build issue is resolved.

We have not benchmarked or run this build. A feature announcement establishes what its developers report changing; it does not establish the visual result or frame time in your game. Our cover image is a tabletop illustration, not evidence of the new feature in action.

Turn the news into a bounded test

Even the stable 4.7.2 maintenance announcement recommends preserving projects with backups or version control. Its statement that there were no known incompatibilities refers specifically to the previous 4.7.1 release. It should not be stretched into a promise about moving a project to 4.8.

For someone who chooses to evaluate the development build, our suggested checklist is:

1. Keep a recoverable baseline. Preserve the working project and its current engine version before experimenting.
2. Choose a specific question. For example, does a particular directional-light scene benefit from the new contact-shadow option?
3. Compare deliberately. Record the settings, camera view, hardware and build used. Judge appearance separately from frame time.
4. Check the project workflow. A pleasing test scene does not, by itself, establish that importing, editing and exporting your game all behave as expected.

This is an evaluation plan, not a report of tests we performed. The useful result is a documented decision about your project, rather than a general claim that a newer development version must be faster or better.

Release labels also matter outside game engines. Our Minecraft Java rendering update explains why a setting called “Default” can change meaning between versions.

References

• Godot Engine. (n.d.). Godot release archive. Retrieved September 28, 2026, from https://godotengine.org/download/archive/
• Thaddeus Crews. (2026, August 18). Maintenance release: Godot 4.7.2. Godot Engine. https://godotengine.org/article/maintenance-release-godot-4-7-2/
• Thaddeus Crews. (2026, September 15). Dev snapshot: Godot 4.8 dev 6. Godot Engine. https://godotengine.org/article/dev-snapshot-godot-4-8-dev-6/

Reading notes and scope

Primary sources checked on 28 September 2026, using current-year announcements within the preceding 365 days. All three sources belong to the Godot project and are not independent performance evidence. No hands-on testing, popularity ranking or benchmark is claimed. Archive retrieval date is shown because its contents change.