> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c160/c166/q548.md).

# What is the maximum number of photos I can add to a single report and can that limit be increased?

We don't have a maximum number of images for reports. However, large reports (usually around 100 images) will be split into multiple documents when exported. The app will warn you if the generated report needs to be split.

In the offline version, you can disable this with some impact to functionality: 

* the final file size may be too large to send via email 
* the app may become unstable if too many images are added to a single file

## Related

* [FAQ: How do I share reports that are too large to send via email?](/manual/faq/c160/c164/q540.md)
* [FAQ: Where are photos, PDFs, and other media files stored in the offline version of the app?](/manual/faq/c142/c147/q417.md)
* [FAQ: What is the maximum number of characters that can be added to a description in a report?](/manual/faq/c160/c166/q549.md)
* [FAQ: How do I add multiple images to a single comment?](/manual/faq/c150/c153/q455.md)
* [FAQ: Why am I unable to add images from the gallery?](/manual/faq/c160/c161/q522.md)
* [FAQ: How do I contact support?](/manual/faq/c169/q575.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 by asking a question.

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

```
GET https://docs.reportandrun.com/manual/faq/c160/c166/q548.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.