Public vs SerializeField in Unity - Visual Side-by-Side Comparison

Concept Flow - Public vs SerializeField

Declare Variable

↓

Is it Public?

Yes→Visible in Inspector & Accessible Everywhere

No↓

Has SerializeField?

Yes→Visible in Inspector, Private Access

No↓

Not Visible in Inspector, Private Access

This flow shows how variable visibility and access depend on being public or marked with SerializeField in Unity.

Execution Sample

Unity

public class Player : MonoBehaviour
{
    public int health = 100;
    [SerializeField] private int mana = 50;
    private int stamina = 75;
}

Defines three variables with different access and inspector visibility in Unity.

Execution Table

Step	Variable	Declaration	Inspector Visible	Access Level	Notes
1	health	public int health = 100;	Yes	Public	Visible in Inspector and accessible anywhere
2	mana	[SerializeField] private int mana = 50;	Yes	Private	Visible in Inspector but not accessible outside class
3	stamina	private int stamina = 75;	No	Private	Not visible in Inspector and not accessible outside class
4	End	-	-	-	All variables declared with their visibility and access

💡 All variables processed with their visibility and access determined by public or SerializeField.

Variable Tracker

Variable	Declared	Inspector Visible	Access Level
health	Yes	Yes	Public
mana	Yes	Yes	Private
stamina	Yes	No	Private

Key Moments - 3 Insights

Why does a private variable with [SerializeField] show in the Inspector but is not accessible from other scripts?

Because [SerializeField] tells Unity to show the variable in the Inspector for editing, but the private keyword keeps it hidden from other scripts, as shown in execution_table rows 2 and 3.

If a variable is public, does it always show in the Inspector?

Yes, public variables are always visible in the Inspector by default, as seen in execution_table row 1.

What happens if a variable is private and not marked with [SerializeField]?

It will not show in the Inspector and cannot be accessed outside the class, as shown in execution_table row 3.

Visual Quiz - 3 Questions

Look at the execution_table, which variable is visible in the Inspector but not accessible outside its class?

A health

B mana

C stamina

D None

💡 Hint

Check the 'Inspector Visible' and 'Access Level' columns in rows 2 and 3.

At which step does the variable have public access and is visible in the Inspector?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Access Level' and 'Inspector Visible' columns in the execution_table.

If we remove [SerializeField] from mana, what changes in the variable_tracker?

A mana becomes accessible outside class

B mana becomes public

C mana is no longer visible in Inspector

D No change

💡 Hint

Refer to the 'Inspector Visible' column for mana in variable_tracker.

Concept Snapshot

Public vs SerializeField in Unity:
- public variables: visible in Inspector, accessible everywhere
- private variables: hidden in Inspector, accessible only inside class
- [SerializeField] private: visible in Inspector, but private access
Use [SerializeField] to keep variables private but editable in Inspector.

Full Transcript

In Unity, variables can be public or private. Public variables show in the Inspector and can be accessed by any script. Private variables are hidden in the Inspector and only accessible inside their class. Using [SerializeField] on a private variable makes it visible in the Inspector but keeps it private in code. This lets you edit values in the Unity Editor without exposing them to other scripts. The execution table shows three variables: health is public and visible everywhere; mana is private but serialized, so visible in Inspector but not accessible outside; stamina is private and not serialized, so hidden and private. This helps organize your code and control what other scripts can change.