> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/2024.1/objects-and-types/prefabs/creatingandusingprefabs.md).

# Creating and Using Prefabs

## Introduction

A **Prefab** is composed of a collection of **Objects** that can be instantiated several times. Each of these **Instances** acts like a single **Object** and can retain unique properties via overrides. The characteristics that are shared through all **Instances** of a **Prefab** are managed from the **Prefab Asset** which is generated whenever a **Prefab** is created. Changes made in the **Prefab Asset** are enacted across all **Instances**.

**Prefabs** are available in both **Scenes** and **Scene2Ds**. They are treated virtually the same within **Projects**, just having dominion over different **Object** types.

**Prefabs** in **Scene2Ds** are treated as [**Frames**](/incari-studio/2024.1/objects-and-types/scene2d-objects/frame.md), but with the properties of a **Prefab**. However, on the surface, they essentially work the same as **Prefabs** in **Scenes**.

This section shows how to get started with **Prefabs**. It first describes how **Prefabs** can be created and how to edit them thus modifying all **Instances** of the **Prefab**. This is followed by a description of how to edit one single **Prefab Instance**. Finally, how to unpack **Prefabs** is explained. See how this works in both **Scenes** and **Scene2Ds**:

* [**Prefabs in Scenes**](/incari-studio/2024.1/objects-and-types/prefabs/creatingandusingprefabs/3d.md)
* [**Prefabs in Scene2Ds**](/incari-studio/2024.1/objects-and-types/prefabs/creatingandusingprefabs/2d.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.incari.com/incari-studio/2024.1/objects-and-types/prefabs/creatingandusingprefabs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.