> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/object-management/manage-object-images.md).

# Manage object images

Object images make equipment easier to recognize.

They are especially useful when similar objects exist at one location.

### Why images help

Images support:

* visual identification on site
* cleaner asset records
* faster checks during service work

{% stepper %}
{% step %}

### Open the object

Open the object in the BackOffice or app.
{% endstep %}

{% step %}

### Add or update the image

Choose the image field or camera option.

Then upload or capture a picture.
{% endstep %}

{% step %}

### Save the change

Save the object so the image is stored.
{% endstep %}

{% step %}

### Check the result

Open the object again and confirm that the image is visible.
{% endstep %}
{% endstepper %}

### Good image tips

* use a clear front view
* avoid dark or blurry pictures
* update the image when equipment changes visibly

### Frequently asked questions

<details>

<summary>Can technicians add images in the app?</summary>

Yes, if your app settings allow it.

</details>

<details>

<summary>Should every object have an image?</summary>

Not always.

Use images where visual recognition adds value.

</details>

<details>

<summary>Can I replace an old image later?</summary>

Yes.

You can update object images whenever needed.

</details>

### Related topics

* [**Create objects in the mobile app**](/marketplace-packages-and-power-ups/power-ups/object-management/create-objects-in-the-mobile-app.md)
* [**Object Management**](/marketplace-packages-and-power-ups/power-ups/object-management.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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/object-management/manage-object-images.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.