> For the complete documentation index, see [llms.txt](https://docs.littlebaytech.com/templates/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.littlebaytech.com/templates/messaging-template/page-guides/pages/3.-logged-in/messages/built-in-functionality/9.-send-images-in-a-message.md).

# 9. Send Images in a Message

Bubble currently doesn't have its own multi-image uploader plugin. 

{% hint style="info" %}
Though Users can send multiple image files, they are stored as 'files' within the database, not images.  This is because the only way to upload multiple image files at a time (currently), is to use Bubble's Multifile Uploader's plugin. 
{% endhint %}

As a workaround, the template uses Bubble's Multifile Uploader plugin to allow the Current User to upload image files.  Once the filers are uploaded, the template displays those image files in the `Repeating Group Uploaded Files (Photos)` element, using the combination of elements below:

**`Popup Multifile Uploader (Images) Element`**

![](/files/-LXRdaSjhfhHaLF8ueRP)

The actual `Multifile Uploader (Images)` element is transparent, and placed on top of  the `IonicIcon Upload Image Files` element.  When the transparent `Multifile Uploader (Images)` element is clicked, the file selector will immediately open, so the Current User can select their photos. 

After the Current User selects their photos to upload, they are uploaded to your app's storage, and the transparent `Multifile Uploader (Images)` element becomes hidden. Then, the `Repeating Group Uploaded Files (Photos)` element becomes visible in order to display the images and a delete icon in the upper-right corner of each image cell:

![](/files/-LHyfs9FhAHPgyECgYJ_)

This custom setup makes sure that when the delete button is clicked next to an image, that image is completely removed from the app's storage (since the Current User has decided not send it, and we don't want unused images taking up space in the app's storage).  

{% hint style="info" %}
More specific information on these workflows can be found in the **D. Files/Images/GIPHYs** workflow folder and the **delete\_uploaded\_files** API workflow.

Note: A personal plan or higher is needed to run API workflows.
{% endhint %}


---

# 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.littlebaytech.com/templates/messaging-template/page-guides/pages/3.-logged-in/messages/built-in-functionality/9.-send-images-in-a-message.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.