What Is a Prefab in Unity? How to Create and Use One

ASCENO / UNITY STUDY NOTES · 9

What Is a Prefab in Unity? How to Create and Use One

Prefab trong Unity là gì? Cách tạo và sử dụng Prefab

The lesson starts with a direct Unity screenshot so the practical action is visible. The nine following figures are language-neutral illustrations; the bilingual text below them carries the explanation. The main topic is prefab unity. Figure 1 is practical evidence; figures 2–10 use only shapes, symbols, and visual relationships so they can remain unchanged across languages.

Learning goals

• Explain the concept with a model or data flow.
• Know exactly which Unity window to open.
• Predict the result before pressing Play and find evidence.
• Rebuild a small experiment and debug it methodically.

1. Hands-on practice in Unity

Open the test Scene, select the relevant object, and perform the action described in the lesson. This is a native Unity screenshot that shows where to begin; the steps and meaning are explained in the text below.

2. System illustration

A Prefab is a reusable template for a GameObject or a group of GameObjects. It lets you update one source and propagate the change to many Scene instances, which is useful for enemies, items, bullets, and UI. The illustration below contains no language-specific text; read it together with this explanation and the concrete steps.

• prefab unity | the lesson concept | read the focus and hands-on example | do not infer it from object colours
• Input/setting | the input data or configuration | record the value before changing it | do not change several things at once
• Result/evidence | what must be observed in the Scene, Game, Inspector, or Console | capture the correct panel | a polished image is not evidence

3. Cause → result illustration

Read the arrow direction, relative position, and symbol changes as a causal relationship. The explanation below names each step in text rather than relying on words inside the image.

1. Prefab asset
2. Instance
3. Override
4. Apply / Revert
5. Variant
6. Spawn

4. Sequence illustration

Open Unity and identify the window that produces the lesson result; capture only after the object name, field, or output you need to teach is visible.

5. Object structure illustration

Read the object name in the Hierarchy first. If the name does not communicate its role, rename it in the test Scene; a screenshot is useful only when the reader knows what is selected.

6. Configuration illustration

Select the object representing prefab unity in the Hierarchy. Read Transform first, then find the relevant Component/field. Record the current value before changing it; Drag the GameObject from the Hierarchy into a Prefabs folder in the Project

7. Result observation illustration

The Console is not decoration: use it to verify Use Prefab Mode for shared changes and override an instance only when it truly needs to differ. If no log appears, check the active object, script compilation, and Console filters before adding more code.

8. Code → state illustration

Do not copy code away from the Scene. Before each line, identify the input object/reference; after each line, identify the state or output that should change.

using UnityEngine;

public class SpawnPrefab : MonoBehaviour
{
    [SerializeField] private GameObject prefab;
    [SerializeField] private Transform spawnPoint;

    public void Spawn()
    {
        Instantiate(prefab, spawnPoint.position, spawnPoint.rotation);
    }
}

9. Experiment illustration

You will create a Player Prefab, place it in a Scene, edit it in Prefab Mode, and inspect the instances. The article also separates intentional overrides from accidentally breaking the link.

1. Drag the GameObject from the Hierarchy into a Prefabs folder in the Project.
2. Name the asset clearly, for example PF_Player or PF_Enemy_Basic.
3. Use Prefab Mode for shared changes and override an instance only when it truly needs to differ.
4. Run again after reverting to check that the result is reproducible.
5. Record the input value, action, result, and reason for the change.

10. Failure → fix illustration

• Selecting the wrong object or asset means a correct edit appears to do nothing.
• Changing several fields at once hides the cause.
• Looking only at the Scene while ignoring the Inspector/Console.
• Skipping verification specific to prefab unity.

The ASCENO perspective: A good figure must help the reader answer one concrete question. If it does not show what to select, where to look, what to change, or where the result appears, it is not ready for documentation.