> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/day-to-day-operations/products/product-images.md).

# Product images

Add images to products, which format to use, and where they show up.

Add images to any product. Flow Retail supports an unlimited number of images per product, with one of them marked as the featured image.

Good product images pay for themselves several times over:

* Staff can see at a glance that they picked the right product.
* You can show the customer in front of you what they are buying.
* Images sync to your webshop, so they are maintained in one place.
* They appear on offers sent to customers and on A4 PDF receipts.

{% hint style="warning" %}
We **strongly recommend JPG/JPEG**. More modern formats such as WEBP are supported, but JPEG still gives the best combination of compatibility and compression.

**Not recommended:** GIF (256 colours, unusable) · PNG (poor compression, and transparency rarely helps here) · SVG (vector, useless for photos) · HEIF/HEIC (great compression, but only really works in the Apple ecosystem).
{% endhint %}

## Recommended format and size

**Aspect ratio**

* Clothing — jackets, jeans and similar — looks best at **3:4**, for example 900 × 1200 px.
* More generic products suit something wider, around **4:5**, for example 800 × 1000 px.

**File size**

Unless you are going to print large physical posters from them, a JPEG at 900 × 1200 should land between **300 kB and 800 kB**. Keep JPEG quality around **94–98, ideally 96** — that is where the compression earns its keep without visible loss.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FQgExNyxT4D1DabPFICVJ%2Faf7848b9eadde21529a79935cb7d80924957a134ffb00d2b7392b1c903c8f4fd.jpg?alt=media&#x26;token=33d6ef55-7d37-4a6a-aa3f-d848d6af506a" alt=""><figcaption></figcaption></figure>

## Adding images to a product

1. Go to **Backoffice > Products**, open the product, and choose the **Media** tab.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FsRoKyuWncnmiZVC0VHZ5%2FSCR-20250110-mqcf.png?alt=media&#x26;token=a007fc59-5918-4ba0-8f5f-7af0d097588a" alt=""><figcaption></figcaption></figure>

2. Choose **Upload image** (NO: *Last opp bilde*) or **Add from URL** (NO: *Legg til bilde fra URL*).

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FIaaF14nHnvWAqNqgqaZS%2FSCR-20250110-mssv.png?alt=media&#x26;token=ac1e4c20-9693-4cee-afdf-33d9837ccdce" alt=""><figcaption></figcaption></figure>

3. Mark it as the featured image, or leave it as one of the others.

### Upload or URL?

|                  | What happens                                                        |
| ---------------- | ------------------------------------------------------------------- |
| **Upload image** | The file is stored in Flow Retail. Use JPEG.                        |
| **Add from URL** | Flow Retail keeps the **URL**, not the file. Nothing is downloaded. |

The difference matters. A product image added from a URL breaks the moment the source is deleted, renamed or moved. If the images live in a PIM or DAM you control, that is fine. If they live somewhere you do not control, upload them.

## Where the images appear

Images show up nearly everywhere products are listed.

### In the sales view

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FAf7iqgZQIa0TvTMsTjI0%2FSCR-20250110-mtky.png?alt=media&#x26;token=33fbe452-e035-4977-b916-6659ec396118" alt=""><figcaption></figcaption></figure>

With several images on a product, select it and choose **Media** in the left menu — the left and right arrow keys scroll through them.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FMDCccbFeOnSszfYNPIc2%2FSCR-20250110-muez.png?alt=media&#x26;token=9e950efd-89ec-4366-a880-0eee1ab7d061" alt=""><figcaption></figcaption></figure>

### On offers

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FW6aJwvBoabJWtcb7pcls%2FSCR-20250110-mxsx.png?alt=media&#x26;token=b95d2d2f-bc88-4d2a-90d6-e05e1022f1fa" alt=""><figcaption></figcaption></figure>


---

# 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.flowretail.com/docs/day-to-day-operations/products/product-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.