Unity Manual and Scripting API

What it is

The Unity documentation has two halves. The Manual explains features and workflows: the editor, GameObjects and components, prefabs, 2D and 3D physics, the Input System, animation, UI, audio, graphics, profiling and building for each platform. The Scripting API is the reference for C#: every class, such as MonoBehaviour, Rigidbody2D or Transform, with its properties, methods and short examples.

Both are versioned. The URL and version picker let you read the docs for the exact Unity version you use, which matters because features and names change between releases.

Is it worth using over tutorials?

Yes, alongside them. Tutorials show one way to build one thing. The Manual tells you what a system can do and its rules, such as the order of event functions or when trigger callbacks fire. Many "why does this not work?" questions are answered by one Manual page.

Pages worth knowing early:

• Order of execution for event functions, which explains Awake, Start, Update and FixedUpdate.
• Prefabs, including variants and nested prefabs.
• The Input System package documentation.
• Physics 2D or 3D overview, colliders and layers.
• The Profiler and the build settings for each platform.

Time and prerequisites

There is nothing to finish. Look things up as you need them. Basic C# helps you read the Scripting API.

Free vs paid

The documentation is free. The editor is free under Unity Personal for individuals and companies below US$200,000 a year in revenue and funding, as of 2026-09 per Unity's pricing page; Unity Pro is required above that.

Tips for using it well

• Search the Scripting API for the class name first, then read its methods.
• Check the version selector before you trust a page, especially for input, rendering and UI, which changed a lot in recent versions.
• When a forum answer disagrees with the Manual for your version, trust the Manual and test it.

Common questions

Is there a separate reference for packages? Yes. Packages such as the Input System, Cinemachine and the Universal Render Pipeline have their own documentation linked from the Manual and the Package Manager.

Where do I find examples? Many Scripting API pages include short examples; Unity Learn and sample projects show bigger ones.