In this lesson, you will learn how Unity uses invisible meta files to track your assets and keep your project from breaking.
When you import an asset into your project—like a 3D model, a texture, or an audio clip—you might see it appear in your Project window. However, behind the scenes, Unity is doing much more than just copying the file into your folder. For every file you add, Unity automatically creates a hidden companion file with a .meta extension.
What is inside a .meta file?
If you were to open one of these .meta files in a text editor like Notepad, you would see a unique string of characters called a GUID (Globally Unique Identifier).
Think of the GUID as a social security number for your asset. Unity uses this ID to keep track of your files, regardless of what you name them or where you move them inside your Assets folder.
Why does this matter?
Imagine you have a Player Prefab that uses a specific character texture. If you were to rename the texture file in your computer’s folder or move it to a different subfolder, a normal computer program might lose track of it, resulting in a "missing texture" error.
Because Unity relies on the GUID inside the .meta file rather than the file path, it can maintain the link:
fileFormatVersion: 2
guid: a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6
DefaultImporter:
...
As long as the .meta file stays with the original asset, Unity knows exactly which object in your Scene or Prefab is linked to that specific file. This is what allows your project to stay "stitched together" even as your game grows and your folder structure becomes more complex.
If you ever delete a .meta file, Unity will generate a new one the next time it opens, but the original GUID will be gone. This breaks the link to any Prefabs or Scripts that were looking for that specific ID, turning your assets into "missing" references.
Key Takeaway: Unity uses GUIDs stored in .meta files to track assets independently of their names or folder locations, ensuring that your project references remain stable and unbroken.