# image.manual render images in desired order

**URL:** <https://support.prodi.gy/t/image-manual-render-images-in-desired-order/3366>\
**Category:** Uncategorized\
**Tags:** usage, done, image, solved, streams\
**Created:** [September 3, 2020, 2:48pm UTC](https://support.prodi.gy/t/image-manual-render-images-in-desired-order/3366 "2020-09-03T14:48:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![yw2903](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/yw2903/32/1614_2.png) [@yw2903](https://support.prodi.gy/u/yw2903)\
**Post date:** [September 3, 2020, 2:48pm UTC](https://support.prodi.gy/t/image-manual-render-images-in-desired-order/3366/1 "2020-09-03T14:48:55Z")

</div>

Hello, I'm trying to do annotate a set of images with endings like "XXX-01.png", "XXX-02.png" etc. How can prodigy display the images in the desired order? The current session renders the images in random order.

---

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [September 3, 2020, 8:31pm UTC](https://support.prodi.gy/t/image-manual-render-images-in-desired-order/3366/2 "2020-09-03T20:31:51Z")

</div>

Hi! By default, the images are presented in the order produced by `Path("/your/source/directory").iterdir()` – I always thought this would be alphabetic, but maybe it's actually by edited date? 🤔

If you want to feed in your images in a custom order, the easiest way would be to load in a JSONL file with `{"image": "/some/path.jpg"}` etc. in your preferred order and then load it with `--loader jsonl`. Alternatively, if it'a not that many images, you could also consume the whole stream generator by calling `list()` around it in the recipe and then sort it in Python.

---

<div class="post-metadata">

**Author:** ![yw2903](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/yw2903/32/1614_2.png) [@yw2903](https://support.prodi.gy/u/yw2903)\
**Post date:** [September 8, 2020, 3:27pm UTC](https://support.prodi.gy/t/image-manual-render-images-in-desired-order/3366/3 "2020-09-08T15:27:48Z")

</div>

Great. Thanks. I have another issue regarding to image. manual. Suppose I don't add `--no-fetch` to my command, then the output of `db-out` would be really huge as it converts the image to 64 base. However, if I add `--no-fetch` to my command, the image would not be displayed.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/prodigy/original/2X/9/95f59c21f0a981fa35fe655c0c0d7396ade95e1c.png)

---

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [September 8, 2020, 8:02pm UTC](https://support.prodi.gy/t/image-manual-render-images-in-desired-order/3366/4 "2020-09-08T20:02:21Z")

</div>

The `--no-fetch` flag just decides whether local paths etc. in the data are loaded as base64, so you typically always want to set that if your input is a JSONL file with paths.

Whether the base64-encoded data is saved to the database can be toggled by setting `--remove-base64`. This will replace the image data with the path again. So if your input is a JSON file with file paths, you can set `--no-fetch` to load them and `--remove-base64` to not store the encoded data in the DB.

---

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [November 11, 2020, 9:51am UTC](https://support.prodi.gy/t/image-manual-render-images-in-desired-order/3366/5 "2020-11-11T09:51:05Z")

</div>

**Related update:** Just released v1.10.5, which now defaults to streaming files in alphabetic order 🙂