# Where should images go?

**URL:** <https://discourse.gohugo.io/t/where-should-images-go/30199>\
**Category:** support\
**Created:** [December 25, 2020, 6:59am UTC](https://discourse.gohugo.io/t/where-should-images-go/30199 "2020-12-25T06:59:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![map](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@map](https://discourse.gohugo.io/u/map)\
**Post date:** [December 25, 2020, 6:59am UTC](https://discourse.gohugo.io/t/where-should-images-go/30199/1 "2020-12-25T06:59:29Z")

</div>

From reading about hugo it seems like images can either go in `/static/images` or in a page bundle with the content. Is that right? If so is there any guidance on which method is better? Pros/cons?

If I have an about page with some images, should I do:

```
/content/about/index.md
/content/about/image1.jpg

```

or

```
/content/about.md
/static/img/image1.jpg

```

If I have dozens of a specific type, say books, with a content page for each book and I want a picture of the cover of the book should that be:

```
/content/books/book-one/index.md
/content/books/book-one/cover.jpg
/content/books/book-two/index.md
/content/books/book-two/cover.jpg
etc.

```

or

```
/content/books/book-one.md
/content/books/book-two.md
/static/img/book-one-cover.jpg
/static/img/book-two-cover.jpg

```

Trying to understand the best practices

---

<div class="post-metadata">

**Author:** ![map](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@map](https://discourse.gohugo.io/u/map)\
**Post date:** [December 25, 2020, 8:01am UTC](https://discourse.gohugo.io/t/where-should-images-go/30199/2 "2020-12-25T08:01:21Z")

</div>

I did find this older thread [Discussion: Content Organization Best Practice](https://discourse.gohugo.io/t/discussion-content-organization-best-practice/6360) which weighs both options. It seemed like it was user preference with pro/cons on both sides, although in the very last post before the thread was closed, @alexandros, who seemed like he originally preferred having images in the static folder,  
said:

> Page Bundles and image processing is the way forward to proper content management.

So it sounds like grouping images and content together in page bundles is now the preferred method, am I understanding that correctly?

---

<div class="post-metadata">

**Author:** ![alexandros](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@alexandros](https://discourse.gohugo.io/u/alexandros)\
**Post date:** [December 25, 2020, 8:05am UTC](https://discourse.gohugo.io/t/where-should-images-go/30199/3 "2020-12-25T08:05:06Z")

</div>

> [@map](#):
>
> So it sounds like grouping images and content in page bundles is the preferred method, am I understanding that correctly?

It is the simplest way to manage images in a Hugo project.

If for some reason, you need to have them in a separate folder -like for example for Forestry or some other service- images will need to reside under the `assetDir` so that you can get them as resources on the fly with the method `resources.Get`

---

<div class="post-metadata">

**Author:** ![Grob](https://avatars.discourse-cdn.com/v4/letter/g/f14d63/32.png) [@Grob](https://discourse.gohugo.io/u/Grob)\
**Post date:** [December 25, 2020, 8:10am UTC](https://discourse.gohugo.io/t/where-should-images-go/30199/4 "2020-12-25T08:10:07Z")

</div>

> [@alexandros](#):
>
> It is the simplest way to manage images in a Hugo project.

I think so, too.

This is what I prefer:

```auto
/content/books/book-one.md
# or
/content/books/book-one/index.md

```

but

```auto
/content/books/book-two/index.md
/content/books/book-two/cover.jpg

```

When these files are in `/content/` you can use [Page Resources](https://gohugo.io/content-management/page-resources/) and [Image Precessing](https://gohugo.io/content-management/image-processing/) out of the box.

For blogging/time-critical contents I use

```auto
/content/blog/2020-12-25-my-post/index.md
/content/blog/2020-12-25-my-post/image.jpg
/content/blog/2020-12-25-my-post/pdf-file.pdf

```