Unity Splash Screen Not Showing - Build Branding Fix (How to Fix)

Your Unity game build runs but the splash screen never appears: the screen goes straight to your first scene or shows a blank or default Unity logo instead of your custom branding. This can be frustrating when you have a Plus or Pro license and expect a personalized splash, or when the default Unity splash fails to show at all.

This guide walks you through why the Unity splash screen does not show in builds and how to fix it. By the end, you will know how to verify your settings and get your branding to appear correctly.

The Problem

Common symptoms:

Splash screen never appears – build launches directly into the game
Default Unity logo shows instead of custom splash – your image or settings are ignored
Black or white screen where the splash should be
Splash shows in Editor but not in build – behavior differs between Play mode and built player
"Unity Personal" or wrong logo – licensing or branding settings not applied

These usually point to Player Settings, licensing, or platform-specific splash configuration.

Why This Happens

Player Settings and Splash Screen Section:

Splash screen disabled in Edit > Project Settings > Player > Splash Screen
Show Splash Screen unchecked
Custom splash image not assigned or not meeting size/format requirements
Draw Mode or Animation set in a way that skips or hides the splash

License and Branding:

Unity Personal (free) license limits or removes custom splash options
Project not linked to a Plus/Pro license that allows custom splash
License changed or deactivated after configuring splash

Platform-Specific Behavior:

Mobile (iOS/Android) or console platforms use different splash pipelines
Application Display Mode (fullscreen, windowed) affecting when splash is shown
Platform-specific overrides (e.g. Android splash screen) overriding Unity splash

Build and Script Order:

Scripts that load the first scene too quickly (e.g. in Awake or very early Start) before splash has time to display
Splash Screen duration set to zero or very low

Assets and Quality:

Splash image missing from build, wrong path, or stripped by build process
Addressables or asset bundles affecting when splash assets are available

Solution 1: Enable and Configure Splash Screen in Player Settings

This is the main place to fix the splash screen not showing.

Step 1: Open Player Settings

In Unity, go to Edit > Project Settings.
Select Player in the left sidebar.
Under Player, open the Splash Screen section (under Resolution and Presentation on some versions).

Step 2: Enable Splash Screen

Find Show Splash Screen (or Splash Image / Display Splash Screen).
Ensure the checkbox is checked.
If you use Splash Style, set it to Light or Dark as needed so the logo is visible.

Step 3: Set Splash Image and Duration

In Splash Image, assign your logo or image (recommended: 1024x1024 or 2048x2048 PNG with alpha if needed).
Set Animation to Static if you want a simple image; use Dolly or Custom only if you have tested them in builds.
Set Duration to at least 2–3 seconds so the splash is visible (avoid 0 or near-zero).
Click Apply or ensure changes are saved.

Step 4: Rebuild and Test

File > Build Settings – choose your platform and build.
Run the built executable and watch the startup sequence.
Confirm the splash screen appears for the set duration before the first scene loads.

Verification: The built game shows your splash image for the configured duration, then transitions to the first scene. If it still does not show, continue with the steps below.

Solution 2: Check Unity License and Custom Splash Eligibility

Custom splash screen options depend on your Unity license.

Step 1: Confirm License Type

Go to Edit > Project Settings > Player > Splash Screen.
If you see a message that custom splash is only available with Plus/Pro (or similar), your license does not allow custom branding.
In Unity Hub, click your account icon and check Manage License to see Personal, Plus, or Pro.

Step 2: Link or Activate the Correct License

In Unity Hub, open Manage License.
Activate or link a Plus or Pro license if you need custom splash.
Restart Unity and reopen the project.
Recheck Edit > Project Settings > Player > Splash Screen – custom options should be available if your license supports them.

Verification: With a Plus/Pro license, you can set a custom splash image and it is not grayed out. With Personal, you may only be able to show the default Unity splash or a limited variant.

Solution 3: Prevent the First Scene from Loading Too Early

If a script loads or switches the scene immediately, the splash can be skipped.

Step 1: Find What Loads First

In File > Build Settings, check Scenes In Build – the first scene (index 0) runs at startup after the splash.
Open that scene and look for scripts that run in Awake or Start and call SceneManager.LoadScene or change state in a way that might bypass the splash.

Step 2: Delay Scene Logic If Needed

Do not load another scene or show main menu in the first frame of the first scene.
If you must do something immediately, use a short delay so the splash can display:

void Start()
{
    StartCoroutine(AllowSplashThenProceed());
}

System.Collections.IEnumerator AllowSplashThenProceed()
{
    // Give splash screen time to display (match duration in Player Settings)
    yield return new WaitForSecondsRealtime(2.5f);
    // Your normal startup logic here
}

Rebuild and test.

Verification: With the delay in place, the splash screen appears for the expected time before your game logic takes over.

Solution 4: Platform-Specific Checks (Mobile and Console)

On mobile and console, splash behavior can differ from PC.

Android

Edit > Project Settings > Player > Android > Splash Screen (or Resolution and Presentation).
Ensure Override for Android is configured if you use it, and that Show Splash Screen is enabled.
Check Publishing Settings and Minimum API Level – very old or restricted APIs can affect startup.
Build a development or release APK and test on a real device; emulators sometimes skip or shorten splash.

iOS

Edit > Project Settings > Player > iOS > Splash Screen (or Resolution and Presentation).
Enable Show Splash Screen and set image and duration.
Be aware that iOS may show a system launch screen before Unity’s splash; both can appear in sequence.
Build and run on device to verify.

Console and Other Platforms

For PlayStation, Xbox, Nintendo Switch, etc., use the Platform-specific tab under Player and open the Splash Screen (or equivalent) section.
Enable splash and set duration and image per platform documentation.
Rebuild for that platform and test on dev kit or target hardware.

Verification: The built game on the target platform shows the Unity splash (and your custom one if supported) for the set duration.

Alternative Fixes

Reset Splash to Default Then Reapply: In Player Settings > Splash Screen, set Splash Image to None, apply, then set it back to your image and set duration again. Rebuild.

Clean Build: Close Unity, delete the project’s Library folder (and Builds output if you prefer a fully clean build), reopen the project, reconfigure splash, and build again.

Check Unity Version: If you recently upgraded, check the Splash Screen section name and options in the manual for your exact version (e.g. 2026.x); menus can move between versions.

Disable Splash-Skipping Code: Search the project for SplashScreen API usage (e.g. UnityEngine.Rendering.SplashScreen) and ensure you are not stopping or bypassing the splash programmatically unless intended.

Prevention Tips

Set splash once and leave it: After enabling and configuring splash in Player Settings, avoid turning Show Splash Screen off unless you intend to hide it.
Use a supported image format and size: PNG or JPEG, 1024x1024 or 2048x2048, to avoid stripping or format issues in builds.
Match duration to design: Use at least 2–3 seconds so players and store reviewers see your branding; avoid zero or near-zero duration.
Test builds regularly: Run a build after changing Player Settings or license so you catch "splash not showing" early.
Document your license: If working in a team, note whether the project uses Personal, Plus, or Pro so everyone expects the correct splash behavior.