Start Building

Unity Console Window Not Showing Errors - Debug Console Fix

You hit Play, something obviously breaks, but the Unity Console stays completely empty. No red errors, no warnings, no Debug.Log messages. This makes it almost impossible to understand what is happening in your project.

This article explains why the Console may appear “silent” and walks you through step-by-step fixes to restore your debug output.

1. Check Console Filters and Collapse Settings

The most common reason for a “silent” Console is simply filters hiding messages.

Step-by-step

  1. Open the Console window: Window → General → Console.
  2. In the Console toolbar, make sure Error, Warning, and Log icons are all enabled (they should be highlighted).
  3. Disable Clear on Play and Collapse temporarily so you can see each message as it appears.
  4. Press Play again and trigger the issue.

Why this helps

If any of the filters are off, Unity will hide those message types entirely. Collapse can also make it look like nothing is happening if only one message repeats.

Verification: You should now see new messages appear when you press Play or hit breakpoints in your code.

2. Confirm Scripts Are Compiling and Attached

If your scripts are not compiling correctly or not attached to any GameObject, the code containing Debug.Log or throwing errors may never run.

Step-by-step

  1. Look in the Console after a script change (outside Play mode) for compile errors.
  2. Fix any red compile errors first; Unity will not enter Play mode properly until scripts compile.
  3. Select the GameObject you expect to log messages from and check the Inspector:
    • Is the script component attached?
    • Does the script file name match the class name?
  4. Add a simple test log to Start or Awake:
using UnityEngine;

public class ConsoleTest : MonoBehaviour
{
    void Awake()
    {
        Debug.Log("ConsoleTest Awake called");
    }
}
  1. Attach this component to a GameObject in your starting scene and press Play.

Why this helps

If the script is not compiled or not attached, Unity has nothing to execute, so the Console remains empty even though you expect output.

Verification: If the test script logs successfully, you know the Console itself is working and the issue is with your original scripts not running as expected.

3. Reset Layout and Reopen the Console Window

Sometimes Unity’s editor layout becomes corrupted and a docked Console panel stops refreshing.

Step-by-step

  1. Go to Window → Layouts → Default (or another known-good layout).
  2. If the Console disappears, reopen it via Window → General → Console.
  3. Undock the Console into its own window, then dock it again where you want it.
  4. Press Play and reproduce the issue.

Why this helps

Corrupted layout files can prevent certain editor windows from repainting or updating properly. Resetting the layout forces Unity to rebuild the UI configuration.

Verification: Logs and errors should now appear in the refreshed Console window when they are generated.

4. Make Sure You’re in the Right Mode (Editor vs Player Logs)

If you are testing a built player (Standalone, mobile, WebGL), some errors appear only in the player log, not directly in the Editor Console.

Step-by-step

  1. When testing inside the Editor, rely on the normal Console window.
  2. For built players:
    • On desktop builds, find the Player log (e.g., Player.log on Windows/macOS).
    • On mobile, use platform tools (Xcode, Android Logcat) to see runtime logs.
  3. Add Debug.Log messages specifically around the failing area and rebuild.

Why this helps

If you only look at the Editor Console while testing a player build, you might miss errors that only occur in the built environment.

Verification: Confirm that logs appear either in the Editor Console (for in-Editor tests) or in the appropriate player logs for builds.

5. Check Scripting Define Symbols and Conditional Logging

Conditional compilation can silence logs in certain build configurations.

Step-by-step

  1. Open Edit → Project Settings → Player → Other Settings and look at Scripting Define Symbols.
  2. Search your codebase for #if, #endif, and attributes like [Conditional("DEBUG_LOGS")].
  3. If logs are wrapped in conditions that are not defined in your current build target, they will never run.
  4. Temporarily remove or simplify conditions to confirm whether they are hiding logs.

Why this helps

Teams sometimes use conditional symbols to control noisy logging. If you switch platforms or configurations, these symbols may no longer be defined, silently disabling logs.

Verification: After adjusting or removing the conditions, you should see your previously missing logs appear again.

6. Verify Editor Log Settings and Stack Trace Options

Unity allows you to control how much detail appears in the Console.

Step-by-step

  1. Open the Console window and click the gear icon in the top-right.
  2. Review Stack Trace Logging settings for Error, Assert, Warning, Log, and Exception.
  3. Ensure they are not set to “None” for the message types you care about.
  4. Click Open Editor Log to confirm that errors are being written there even if the Console looks empty.

Why this helps

If stack traces or certain message types are disabled, you might miss critical information that is still being logged under the hood.

Verification: With appropriate stack trace and logging options set, new errors or logs should show up with useful details.

7. When the Console Still Shows Nothing - Deep Checks

If you have tried everything above and the Console is still silent, consider:

  • Editor extensions that may intercept or suppress logs. Temporarily disable custom logging tools or console plugins.
  • Scriptable Render Pipeline or custom bootstrap scenes that skip the scene you think is loading. Your test objects might never be instantiated.
  • Multiple projects or layouts open where you are looking at the Console of a different project than the one actually running.

For a final sanity check:

  1. Create a new empty Unity project.
  2. Add a single script with Debug.Log("Test log"); in Start.
  3. Press Play and confirm you see output there.

If logs work in a new project but not in your main one, the issue is likely project-specific (extensions, layout, corrupted Library folder, etc.).

Verification Checklist

After applying the fixes above, confirm:

  • [ ] Error, Warning, and Log filters in the Console are all enabled.
  • [ ] Scripts compile without red errors and are attached to active GameObjects.
  • [ ] The Console window layout has been reset and is visible.
  • [ ] You are checking the correct logs (Editor vs player).
  • [ ] No conditional compilation or extensions are silently blocking logs.

If all of these are true and the Console still shows absolutely nothing, consider backing up your project and trying:

  • Deleting the Library folder and letting Unity regenerate it.
  • Reinstalling or repairing your Unity Editor version.

Prevention Tips

To avoid losing Console output in the future:

  • Keep filters enabled by default and only narrow them temporarily when needed.
  • Avoid overusing custom conditional logging that depends on obscure define symbols.
  • Be cautious when installing Console-related editor extensions; test them in a copy of your project first.
  • Periodically reset your Editor layout if windows start behaving strangely.

Related Help Articles

If you are still troubleshooting Unity issues, these guides may help:

  • Unity C# Compilation Errors - How to Fix Common Issues
  • Unity Console Errors Not Showing - Debug Console Fix
  • Unity 2026 Editor Slow or Laggy - How to Fix (Performance)
  • Unity Build Fails with "Missing Assembly References" Error - Compilation Fix

Bookmark this page so you can quickly restore your Console if it stops showing errors again, and share it with your team if they run into the same issue.