Editor for Unitys
The Unity Editor is the application where you assemble a game. It has a Scene view for placing objects, a Hierarchy listing GameObjects, an Inspector for editing their components, and a Project window for assets. Scenes hold the objects of a level, and basic C# scripts attached as components make them behave.
Stage: Unity Essentials · Part of the Unity roadmap · Last reviewed 19 November 2026
What to learn in Editor
- Create a scene and arrange GameObjects using the Hierarchy and Scene view
- Edit component values in the Inspector and save the result as a prefab
- Write a MonoBehaviour script with Start and Update methods
- Organise project assets into folders and import files into the Project window
- Use Play mode to test a scene and explain which changes persist afterwards
Editor interview questions
What is the difference between a GameObject and a component in Unity?
A GameObject is an empty container that exists in a scene and carries a Transform. Components such as Rigidbody, Collider, AudioSource or your own scripts are attached to it and give it behaviour. Unity builds features by composing components, not by deep inheritance.
What is a prefab and why would you use one?
A prefab is a saved GameObject template with its components and children. You can spawn many instances in a scene or at runtime, and edits to the prefab update every instance. This avoids copy-pasting enemies, bullets or pickups and keeps changes consistent.
Where Editor fits in the Unity roadmap
Editor belongs to the Unity Essentials stage (beginner level), which takes about 33 hours. Start here.
Other units in this stage
Back to the full Unity roadmap