Code inspection: There is no scene with the same name in the build settings

This inspection reports scene names passed to SceneManager.LoadScene(...) and related APIs when the scene exists in the project but is missing from Unity build settings.

This is different from an entirely missing scene file. The inspection warns when the string points to a real scene asset, but that scene is not included in EditorBuildSettings, so it cannot be loaded by name at runtime.

Example

In this example, the "Gameplay" scene is loaded, but it is not added to the Build Settings. The quick-fix adds the scene to the Build Settings.

                using UnityEngine.SceneManagement;

                public class Example
                {
                    public void Load()
                    {
                        // Reported: scene 'Gameplay' is not in build settings
                        SceneManager.LoadScene("Gameplay");
                    }
                }
            

                using UnityEngine.SceneManagement;

                public class Example
                {
                    public void Load()
                    {
                        // Scene 'Gameplay' is added to build settings
                        SceneManager.LoadScene("Scenes/Gameplay");
                    }
                }
            

Quick-fix

The quick-fix can add the matching scene to Unity build settings. If several scenes share the same short name, it can also replace the argument with the exact scene path representation.

In projects with multiple matching scenes, choose the intended scene entry so the call can also be updated to the correct path-based name.

26 March 2026