The UnityEngine.Object
class acts as a base class for all objects that Unity can reference in the Unity Editor. You can drag and drop classes that inherit from UnityEngine.Object
into fields in the InspectorA Unity window that displays information about the currently selected GameObject, asset or project settings, allowing you to inspect and edit the values. More info
See in Glossary, or pick them using the Object Picker next to an Object field.
Rather than inheriting directly from Object
for your own custom classes, it’s often better to inherit from a class designed to be more specific to your goal. For example:
MonoBehaviour
if you want to write a custom component which you can add to a GameObject
, to control what the GameObject
does or provide some functionality relating to it.ScriptableObject
if you want to create custom assets which can store serialized data.Both of these inherit from UnityEngine.Object
but provide extra functionality to suit those purposes.
Note: UnityEngine.Object
is different from .NET’s base System.Object
, which is not included in the default script template so that the names don’t clash. You can still inherit from .NET’s System.Object
if you want to create classes which you don’t need to assign in the Inspector.
The Object
class provides methods for instantiating and destroying Objects and for finding references to Objects of a specific type. For more information on the API for the Object class, refer to the script reference page for Object.
UnityEngine.Object
is a special type of C# object in Unity, because it’s linked to an unmanaged (C++) counterpart object. For example, when you use a CameraA component which creates an image of a particular viewpoint in your scene. The output is either drawn to the screen or captured as a texture. More info
See in Glossary component, Unity stores the state of the Object on the Object’s C++ counterpart, not on the C# Object itself.
Unity doesn’t currently support the use of the C# WeakReference
class with instances of UnityEngine.Object
. For this reason, you shouldn’t use a WeakReference
to reference a loaded asset. Refer to Microsoft’s WeakReference documentation for more information on the WeakReference
class.
When you use a method such as Object.Destroy or Object.DestroyImmediate to destroy an object derived from UnityEngine.Object
, Unity destroys (unloads) the C++ counterpart object. You can’t destroy the C# object with an explicit call, because the garbage collector manages the memory. Once there are no longer any references to the managed object, the garbage collector collects and destroys it.
If your application tries to access a destroyed UnityEngine.Object
again, Unity recreates the native counterpart object for most types. Two exceptions to this recreation behavior are MonoBehaviours and ScriptableObjects: Unity never reloads them once they have been destroyed.
MonoBehaviour
and ScriptableObject
override the equality (==) and inequality (!=) operators. If you compare a destroyed MonoBehaviour
or ScriptableObject
against null
, the operators return true when the managed object still exists and hasn’t yet been garbage collected.
Because you can’t overload the ?? and ?. operators, they aren’t compatible with objects that derive from UnityEngine.Object
. The operators don’t return the same results as the equality and inequality operators when you use them on a destroyed MonoBehaviour
or ScriptableObject
while the managed object still exists.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising. Some 3rd party video providers do not allow video views without targeting cookies. If you are experiencing difficulty viewing a video, you will need to set your cookie preferences for targeting to yes if you wish to view videos from these providers. Unity does not control this.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.