Understanding the Unity Resources Folder

Understanding the Unity Resources Folder

When organizing a Unity project, developers often create folders like materials, prefabs, or scripts to manage their assets. However, most folders are only for convenience and not treated specially by Unity.

There is one exception: the Resources folder. This folder is recognized by Unity and is the only folder from which you can dynamically load assets at runtime using code.

Key Features of the Resources Folder

Load Assets Dynamically at Runtime

You can load any asset from the Resources folder during runtime like this:

GameObject prefab = Resources.Load<GameObject>("GameManager");
GameObject obj = Instantiate(prefab);

Included in Build Even if Not Used

Assets inside the Resources folder are always included in the build, even if they are not used in the game. This can bloat the file size if not managed carefully.

Folder Structure is Preserved

You can organize assets in subfolders and load them with path syntax:

Resources.Load("UI/PausePanel");

File Extensions Are Omitted

Do not include extensions like .prefab or .png when calling Load().

How to Create a Prefab and Use It with Resources

  1. Create an object in the Hierarchy window.
  2. Drag it into the Project window to make it a prefab.
  3. Move that prefab into the Resources folder.
  4. Then load and instantiate it via script:
GameObject obj = Instantiate(Resources.Load<GameObject>("Player"));

Note that this is separate from prefabs linked in the Inspector. When using Resources, you must load and instantiate manually.

Freeing Unused Assets from Memory

Assets loaded through Resources remain in memory. You should release them manually if they are no longer needed, such as:

  • When an asset is only used on a specific screen or scene
  • After switching scenes and the previous asset is no longer required
void OnSceneChanged()
{
    Resources.UnloadUnusedAssets();
}

This method is performance-intensive, so it’s best to use it only at the right time—like right after a scene change or during loading screens.

Important Notes

  • Assets in the Resources folder are always included in the build. Only include what’s necessary.
  • For large projects, Unity’s Addressables system is highly recommended.
  • Overusing Resources can make code harder to maintain and refactor, and lead to memory waste.

Summary

The Resources folder is the only location in Unity where you can load assets dynamically via code at runtime. It’s useful during the early stages of development, but as the project grows, using it strategically becomes more important.

Be selective with what you put in it, clean up memory when done, and if Resource management becomes overwhelming, consider transitioning to Addressables. It’s a more scalable and robust solution in the long run.

Popular posts from this blog

Understanding Arrays as Reference Types in C#

Image
Arrays as Reference Types In programming, it's important to understand the behavior of arrays. In most programming languages including C#, arrays are treated as reference types. This article will explore what that means and how to use that knowledge effectively. Value Types vs Reference Types In C#, data types are categorized into two main types: Value types : Store actual values directly. Examples : int , float , bool , struct Reference types : Store memory addresses instead of the actual values. Examples: class , string , array , delegate Arrays, like classes, are reference types. When you assign one array variable to another, you're copying the reference, not the actual data. Example: Arrays as Reference Types using System; class Program { static void Main() { int[] array1 = { 1, 2, 3 }; int[] array2 = array1; // Copy reference array2[0] = 100; Console.WriteLine(array1[0]); // Out...
Read more

Setting Up a Basic Follow Camera with Cinemachine 3.x

Image
Setting Up a Basic Follow Camera with Cinemachine 3.x Cinemachine has been significantly upgraded in version 3.x, introducing new concepts, improved terminology, and a refined workflow. In this post, we’ll go through how to set up a simple follow camera using the latest version. For more advanced examples, be sure to check out the sample scenes provided in the Cinemachine package—they’re very helpful for understanding the system. Install the Cinemachine Package Start by downloading and importing the Cinemachine package from the Unity Package Manager. Check the Main Camera After installation, you'll notice that the Main Camera now has a Cinemachine Brain component attached. Make sure the Live Camera field shows the name of your Cinemachine Camera. Create a Cinemachine Camera In the Hierarchy window, right-click and go to Cinemachine > Cinemachine Camera to create a new virtual camera. Set the Tracking Targe...
Read more

How to Initialize Struct – C# Struct Initialization Guide

Image
How to Initialize Struct – C# Struct Initialization Guide In C#, there are multiple ways to declare and initialize structs. While using just one method is often enough, it's common to encounter different initialization styles in real-world code. This guide summarizes the most common approaches, including how to handle struct arrays and lists. Struct Declaration struct Item { public string name; public int price; public string desc; } 1. Declare First, Assign Later This is the most straightforward method. Declare the struct first, then assign values to its fields one by one. Item item; item.name = "Fireball"; item.price = 100; item.desc = "Deals fire damage to the enemy."; Note: Structs are value types, so you can declare them without new . However, you must initialize all fields before use, or you'll get a compile-time error. 2. Use new and Assign Fields Item item = new Item(); item.name = "Fir...
Read more