> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/mobile/add-and-name-photos.md).

# Add and name photos in the mobile app

Technicians can add one photo or select several photos from a visit. The batch **Review photos** screen appears only when more than one photo is selected and shows every photo and its name together before saving.

> **Where to find it:** Mobile app > Visits > open a visit > Files > Add

## Before you start

An admin can choose whether technicians must enter a name for every photo:

1. In the web app, go to **Settings > Technician App**.
2. Under **Photo uploads**, turn **Require photo names** on or off.
3. Select **Save**.

When the setting is on, a technician must enter a name before a photo can be saved. When it is off, Essential starts with the image's original filename. The technician can keep that filename, replace it, or clear the field and let Essential use the original filename when saving.

This setting applies to job, property, and asset group photos. File names for documents are still required.

## Add one photo

1. Open the visit and find the **Files** section.
2. Select the **Job Files** or **Property Files** tab, then tap **Add**.
3. Tap **Take Photo** to use the camera, or **Select Photos** to choose from the photo library.
4. Enter or edit the **Photo Name** when needed. Use the **X** in the field to clear the current name.
5. Choose whether to save the photo as a job file or property file, then tap **Save**.

## Add several photos at once

1. In the attachment screen, tap **Select Photos**.
2. Select the photos in the device's photo library and confirm the selection.
3. On **Review photos**, check each preview and edit its name as needed.
4. To remove a photo from the upload, tap the **X** on its preview.
5. Tap **Save *****\[number]***** photo** or **Save *****\[number]***** photos**. The button uses the singular or plural label that matches how many photos will be saved.

If photo names are required, the save button becomes available after every selected photo has a name. If names are optional, no editing is required.

If only part of a batch succeeds, **Review photos** keeps the remaining photos so you can retry without duplicating the completed uploads.

## Rename an uploaded photo

1. Reconnect, then open an editable uploaded photo from the visit's files.
2. Tap **Edit filename**.
3. Enter the new name and tap **Save**.

Edit filename is not available in read-only historical job or visit views, or for a property photo uploaded by another user. Renaming changes the display filename; it does not replace the photo.

## Related guides

* [Add files, notes, and access info on mobile](/field-operations/mobile/add-files-notes-and-access-info.md)
* [Open a visit in the mobile app](/field-operations/mobile/open-a-visit.md)
* [Work offline and sync mobile changes](/field-operations/mobile/work-offline-and-sync.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://learn.withessential.com/field-operations/mobile/add-and-name-photos.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.