---
title: Understand working with assets in Content hub
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

Every business works with different assets such as images, icons, infographics, videos or documents. Editors usually reuse and share these assets on websites, emails, and other digital marketing channels.

Previous Kentico versions used [media libraries](https://docs.kentico.com/documentation/business-users/media-libraries.md) where editors stored their data into a folder hierarchy. _Media libraries_ have become [obsolete](https://docs.kentico.com/documentation/business-users/media-libraries.md), and editors should store all assets into [Content hub](https://docs.kentico.com/documentation/business-users/content-hub.md).

Unlike _media libraries_, _Content hub_ doesn't use a hierarchical system. Instead, all reusable items exist in **a single flat list**.

Piling all assets into _Content hub_ without any structure may seem easy at first, but quickly becomes a problem, especially in larger editor teams. As the number of assets grows, editors will struggle to locate the correct file and waste time searching through _Content hub_. It can get even worse: if they don't immediately find the image they had in mind, they might upload duplicates. This could lead to inconsistencies across channels and become a content curation nightmare.

To manage large collections of assets, you can combine **workspaces** that separate content across the whole Xperience application and sort assets into **folders** within _Content hub_.

> **Note:** The following examples in this guide are recommendations and suggestions, not a prescription. You should discuss the kinds of assets you work with and how your teams collaborate during [content modeling sessions](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-guide/content-modeling-process.md) with the stakeholders and adapt the system to your project’s needs.

> **Info:** The exercises in this material were prepared in _Kbank_, our demo website environment. If you’d like to follow along, or if you simply want to know what it’s like working with [Xperience by Kentico](https://www.kentico.com/platform), you can request your demo site and ask for the [Xperience by Kentico – Business Tutorial Kbank](https://www.kentico.com/customers/educationcenter/training-website-requests) option.

## Understand how content folders work

_Content hub_ does not use a real folder hierarchy like a traditional file system. All assets represent [reusable content](https://docs.kentico.com/guides/digital-marketing/xperience-essentials/manage-content-hub-essentials.md) that exists alongside other content items within a [workspace](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/role-management/workspaces.md) in a single flat list.

[Content folders](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md) are a way to group and view content items inside _Content hub_. Adding an item, like an image to a _content folder_ doesn't move it anywhere or create duplicate copies. Instead, the folder creates a filter within _Content hub_ that helps editors find their content.

> **Key:** Key points to remember:
>
> - Content folders and smart folders are like filters over items in content hub; they don't remove the item form the _Content hub_.
> - Assets, like other content items, stay in the same _workspace_, even if you place them in a _folder_.
> - Each asset can belong to only one _folder_ at a time.
> - You can create a folder structure with parent folders and subfolders to match your needs.
> - The breadcrumb navigation at the top of the screen shows your location in the folder tree.
> - The _Location_ shows which content folder an item is assigned to.

![Content folder breadcrumbs](https://docs.kentico.com/docsassets/modules/understand-working-with-assets/content-folder-breadcrumbs.png "Content folder breadcrumbs")

This approach keeps navigation simple. Instead of scrolling through hundreds of assets, editors can open the correct folder and immediately see what they need.

🎬 [Video](https://docs.kentico.com/docsassets/modules/understand-working-with-assets/find-content-items-in-content-hub.mp4)

For example, an insurance company can create folders for each product type it provides: _Car insurance_, _Home insurance_, _Travel insurance_, and _Life insurance_. When a campaign team needs graphics to promote new travel insurance, they find the approved images in the _Travel insurance_ folder without digging through unrelated assets.