> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/experience-editor/working-with-objects/replacing-an-object.md).

# Replacing an object

You can replace the object that a container references. For example, you can replace one IFX with another. If you replace an object, all position, scale, rotation, and keyframe information is retained. However, settings that are specific to an object, such as animation overrides, are not retained.

{% hint style="info" %}
This process is often used with the clone tool. For example, you could animate an IFX, clone it, and then change the IFX object.
{% endhint %}

To replace an object, complete the following steps:

1. Select the object.
2. Choose one of the following options:
   * Select the cog icon on the timeline container.
   * Select **IFX options** on the left-hand side of the editor panel.
3. In the **Current Effect Options** window, select Effect.
4. Choose the type of object that you want to use.
5. Select the replacement.
6. In the **Current Effect Options** window, select **SAVE EFFECT**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.engagevr.io/engage/experience-editor/working-with-objects/replacing-an-object.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.