Fix: Unity SerializedField Not Showing in Inspector

Here is how to fix Unity serializedfield not showing inspector. You add [SerializeField] to a private field, but it does not appear in the Inspector. No errors, no warnings — just a missing field. The attribute is correct and the code compiles, but Unity's serialization system has strict rules about what it will display.

The Symptom

A private field with [SerializeField] on a MonoBehaviour or ScriptableObject is invisible in the Inspector. The component is there, other fields show up, but the new one is missing. Sometimes a field was visible before and disappeared after a code change.

What Causes This

1. Non-serializable field type. Unity serializes: primitives, strings, enums, arrays and Lists of serializable types, UnityEngine.Object subclasses, and custom classes marked [System.Serializable]. Interfaces, dictionaries, multidimensional arrays, and unmarked classes are invisible.

2. Compilation error elsewhere. Any compile error in any script prevents recompilation. The Inspector shows the last compiled version, which does not include your new field.

3. [HideInInspector] attribute. If both [SerializeField] and [HideInInspector] are present, the field is serialized but hidden. This sometimes happens when attributes are applied to a block of fields.

4. Custom property drawer hiding the field. A custom Editor or PropertyDrawer for the component can override what the Inspector displays. Your new field may not be included in its layout.

5. Wrong script attached. If the script reference is broken or you have two scripts with similar names, the Inspector will not show the expected fields. Check for "Missing Script" warnings.

The Fix

Step 1: Use only serializable types.

using UnityEngine;

public class PlayerConfig : MonoBehaviour
{
    // These WILL show in the Inspector
    [SerializeField] private int _health = 100;
    [SerializeField] private string _name;
    [SerializeField] private GameObject _prefab;
    [SerializeField] private AttackData _attack;

    // Will NOT show - Dictionary not serializable
    // [SerializeField] private Dictionary<string, int> _inv;

    // Will NOT show - interface not serializable
    // [SerializeField] private IDamageable _target;
}

// Custom classes MUST have this attribute
[System.Serializable]
public class AttackData
{
    public float damage = 10f;
    public float cooldown = 0.5f;
}

Step 2: Check for conflicting attributes.

// Visible: SerializeField alone
[SerializeField] private float _speed = 5f;

// HIDDEN: HideInInspector wins over SerializeField
[SerializeField, HideInInspector]
private float _hidden;

// For polymorphic fields, use SerializeReference
[SerializeReference] private IAbility _ability;

Step 3: Validate serialized fields via editor script.

#if UNITY_EDITOR
[ContextMenu("List Serialized Fields")]
void ListFields()
{
    var so = new UnityEditor.SerializedObject(this);
    var prop = so.GetIterator();
    while (prop.NextVisible(true))
        Debug.Log($"{prop.name} ({prop.propertyType})");
}
#endif

Related Issues

If fields show up but lose values when loading via Addressables, see Addressables failed to load asset. If shadows render incorrectly on objects with serialized material references, check shadow flickering and z-fighting.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

No [System.Serializable] on the class? Unity pretends the field does not exist.