> For the complete documentation index, see [llms.txt](https://manual.platformbid.com/platform-bid-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.platformbid.com/platform-bid-user-guide/auction-management/managing-lots/image-upload.md).
# Image upload
Once you have added to the lots to the auction you will next want to add the images to help provide the buyers with an understanding of what the lots look like.
The more images you add, the better. The better the resolution of the images, the more helpful they will be to the buyers.
You can add as many images as you like for each lot.
Manging the bulk image upload for each lot.
You can upload images by lot. If you navigate to the 'Lot Image' highlighted in the screenshot above, you will see a list of lots already added to the auction. You filter by Draft, Published of Archived as required.
Press the 'Upload Images' button, browse for the photos you wish to add to the corresponding lot, and then upload them.
They will appear on the row you are working with as they are saved by the platform.
Repeat for each lots in turn down the page.
---
# 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://manual.platformbid.com/platform-bid-user-guide/auction-management/managing-lots/image-upload.md?ask=&goal=
```
`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.