Folder Structure

Common ways to structure folders

Top level by	Example path	Works well for	Breaks down when
Date	2026 / 03 / Trade show	Photo archives, events	People search by product or campaign, not date
Campaign or project	Campaigns / Spring launch / Social	Agencies, campaign teams	An asset is reused in a later campaign
Client or brand	Clients / Acme / Brochures	Agencies, multi-brand groups	Assets are shared across brands
Asset type	Photos / Videos / Logos / Documents	Small libraries	Volumes grow and every type folder needs its own subfolders
Product	Products / Pumps / P-200 / Packshots	Manufacturers, retailers	Products are renamed or move between ranges
Department	Sales / Marketing / HR	Internal documents	Departments reorganise, or share the same files

Folder structure best practices

• Keep it shallow. Three or four levels are enough for most libraries. Every extra level is a click, and a deeper tree leads people to file the same kind of asset in different places.
• Agree the top level first. It is the hardest level to change later. Choose the dimension most people browse by.
• Name folders consistently. Same language, same date format, same case. The rules of a file naming convention apply to folders too.
• Watch path length. Microsoft documents a limit of 400 characters for the full path, folder names included, in SharePoint and OneDrive, and many Windows tools still stop at 260. Deep trees with long names reach these limits during migrations and syncs.
• Separate work in progress from approved files. A folder of final, approved assets is easier to share than one where drafts sit beside them.
• Avoid personal folders in shared spaces. "Anna's stuff" stays after Anna leaves.
• Archive rather than delete. Move finished projects to an archive branch so the current tree stays short.

Folders, metadata and collections

The weakness of any folder structure is that each file has one location. A product photo used in the spring campaign, the French catalogue and the partner kit has to be copied into three folders, or left in one where two of the three teams will not look. Copies then drift apart when one is retouched or replaced.

	Folders	Metadata	Collections
How many places per file	One	Any number of values	Any number of collections
How you find files	Browse the path	Search and filter	Browse a curated group
Good for	A single, stable classification	Every attribute people search by: product, market, rights, type	Campaigns, kits, shortlists, projects
Weak at	Assets that belong to several categories	Browsing without knowing what to filter	Classification across the whole library

A DAM usually combines the last two: metadata drawn from a taxonomy for classification, and collections for the groups people put together for a purpose. Folder-like browsing remains, but the file no longer depends on it to be found.

Moving a folder structure into a DAM

1. Inventory the tree. List the top two or three levels and what each one means.
2. Map folder names to fields. A 2026 / France / Packshots path holds three facts: year, market and asset type. Each becomes a metadata field.
3. Decide which folders become collections. Campaign and project folders usually do; date and type folders usually become filters.
4. Remove duplicates. Copies of the same file in several folders become one asset in several collections. See duplicate detection.
5. Freeze the old tree. Make the shared drive read-only once the import is checked, so that two libraries do not grow side by side.

The guide on migrating from cloud storage to a DAM covers the process in more detail.

Folder structure in Freedam

• Collections are nested. An administrator defines collection types that set how many levels a type has, what each level is called (for example Campaign, Channel, Deliverable), whether assets can sit at each level, and which metadata fields each level shows.
• One asset can belong to several collections at once, so the spring campaign and the partner kit can share the same file.
• Collection rules file new assets automatically by a path built from their metadata, such as Campaigns / {year:created_at} / {campaign}, and create the collections that do not exist yet.
• My Collections gives each user a private set of nested collections for shortlists and work in progress.
• Data sources import from WebDAV servers, S3 buckets and Google Drive, and can place the files of each scanned folder in a collection.
• Saved searches keep a combination of keywords and filters, which works like a folder whose contents update themselves. See the asset library and the collections documentation.

Frequently asked questions

What is the best folder structure for marketing assets?

There is no single best one. For most marketing teams, a top level by campaign or product, a second level by channel or asset type, and a separate archive work better than a structure by date or department. Keep it to three or four levels and record the rest as metadata.

How deep should a folder structure be?

Three or four levels. Beyond that, people stop browsing and start searching, and different people file the same kind of asset in different branches.

Do DAM systems use folders?

Most offer folder-like browsing, often called collections, but do not rely on it. Files are found by metadata and search, and one file can appear in several collections without being copied.