How to organize a brand asset folder so your team can find anything in seconds

A brand asset folder is the quiet workhorse behind every consistent logo placement, every on-brand social post, and every quick yes/no decision about whether something is approved. The moment it turns into a dumping ground named “Brand Stuff FINAL v3 use this one (2).zip,” your team starts losing hours to searching, second-guessing, and re-creating files that already exist. A solid structure turns that chaos into a single source of truth, and it does not require expensive software or a brand-platform migration to get there.

This guide walks through how to organize a brand asset folder in a way that survives real team use. It covers the structure, naming, governance, and small habits that keep a folder clean six months after launch, not just on day one.

How to organize a brand asset folder that scales

Most folder problems start long before anyone opens Finder or Explorer. They begin with unclear ownership and the assumption that “everyone will be careful.” A scalable system has three layers: a clear top-level structure, a predictable naming pattern, and a small set of governance rules that anyone on the team can apply in under a minute.

Before you touch the file tree, agree on three things with the people who will actually use it:

• Who owns the folder. One person, usually a brand or design lead, with final say on structure and naming. This is not gatekeeping; it is the difference between a folder and a landfill.
• What “approved” means. Approved assets live in the main folder. WIP and drafts live in a separate space, clearly named, and never get sent to clients or partners.
• Where the canonical copy lives. Logos, fonts, and templates can drift if multiple copies float around. Pick one folder as the source and link to it everywhere.

With those three answers, the file structure stops being a personal preference and becomes a shared tool.

The core folder structure

There is no single correct folder shape, but the pattern below is the one that holds up across small studios, in-house teams, and agency handoffs. It separates the what (assets) from the why (guidelines and source files) and from the who (external versions).

Top-level folder	What goes inside	Who edits it
00 – Brand Foundations	Logo files, wordmark, submarks, favicon, official color tokens, typography files, icon system, brand guidelines PDF	Brand lead only
01 – Logos and Marks	Master logos in all colorways, lockups, cleared-space specs, and export presets	Brand lead, with review by design lead
02 – Color and Typography	Color palette files (ASE, ACO, CSS variables), font files, type ramp documents, web-safe fallbacks	Brand lead, web lead for code exports
03 – Photography and Imagery	Approved hero imagery, product shots, lifestyle photos, on-brand illustration, AI-generated assets cleared for use	Marketing lead, with brand sign-off
04 – Templates	Social post templates, slide decks, document templates, email templates, presentation masters	Any designer, with templates locked where possible
05 – In-Use Collateral	Pieces currently in market: campaign visuals, packaging artwork, landing page modules, partner co-brand kits	Project owners
06 – Partner and Co-Brand Kits	Logos and assets from partner brands with usage rules, co-branded lockups, sponsor toolkits	Partnership or marketing lead
07 – Source and Working Files	Editable Figma, Sketch, AI, PSD, AE, and 3D files, plus font sources and licensed asset receipts	Designers, with read-only access for others
08 – Archive	Old logos, retired palettes, past campaign files, anything kept for legal or historical reasons	Brand lead only
09 – Inbox	New uploads and drafts waiting to be reviewed, named with date and contributor	Anyone; emptied weekly

The numbered prefixes matter. They keep the folders in a stable order regardless of the operating system, and they make the table of contents obvious to a new team member on their first day. The two-digit gap (00, 01, 02) leaves room to insert a new section in the future without reshuffling the whole tree.

Subfolders: how deep is too deep

A common mistake is to over-nest. Once a user clicks through four or five levels, they start saving files in the wrong place because the right place is too far away. A workable rule of thumb:

• Two levels deep for almost everything. For example, 03 - Photography and Imagery / Hero Shots / Product 2026.
• Three levels deep is acceptable for large asset families like photography, where year, shoot, and retoucher may all be meaningful.
• Four levels is a signal that you should restructure, not add another folder.

If you find yourself creating 2026/Q2/March/Approved/V2/, the categories have collided. Split by shoot, project, or product line instead of by month.

Naming conventions that actually get used

The best naming scheme is the one a tired person can apply correctly at 6 p.m. on a Friday. That means short, predictable, and forgiving of small mistakes. A reliable pattern is:

[Brand]_[AssetType]_[Variant]_[Context]_[Version].[ext]

Read that as: who, what, which, where, when. Each segment answers one of those questions, separated by underscores, with hyphens allowed inside a segment for readability.

Segment	Meaning	Example
Brand	Short brand code, usually 2 to 4 letters	MV_ for the studio, AC_ for a client project
AssetType	What the file is: logo, palette, hero, deck, template	Logo, Palette, Hero, Deck
Variant	Which version: primary, mono, dark, light, square, horizontal	Primary, Mono, Dark, Horizontal
Context	Optional. Where it is used: web, social, print, partner	Web, Instagram, Print, Partner
Version	Date or v-number. Dates are easier to sort than v1, v2, v3.	2026-08-04 or v03

Putting the brand code first means the assets for one project sit together when the folder is sorted alphabetically. Using a date in ISO format (YYYY-MM-DD) means the newest version sorts to the bottom or top depending on your sort order, with no ambiguity between US and European date styles.

A real example for a logo set might look like:

• MV_Logo_Primary_Horizontal_Web_2026-08-04.svg
• MV_Logo_Primary_Horizontal_Print_2026-08-04.eps
• MV_Logo_Mono_Dark_Square_2026-08-04.png
• MV_Logo_Submark_Social_2026-08-04.png

For photography, drop the Variant segment and add a descriptive tag:

• MV_Hero_ProductOnWhite_2026-Q2-Retouch_v02.jpg
• MV_Lifestyle_StudioWorkspace_2026-Q2-Retouch_v01.jpg

Two more naming rules save a lot of pain:

1. Spaces become hyphens, never underscores between words. Underscores separate segments; hyphens join words inside a segment. This lets you split a filename with one keystroke in most tools.
2. No final-final, no FINAL-v2-real. If you need a new version, save it as a new file with a new version stamp. The old file moves to 07 - Source and Working Files or 08 - Archive.

File formats: pick the right export for the job

Format choices are part of organization, because the wrong export silently corrupts a brand. A logo saved as a 72-dpi JPEG looks fine on screen and falls apart in print. A vector saved without outlined text breaks on a partner’s machine. The table below maps the most common needs to formats that travel well.

Asset type	Primary format	Secondary format	When to use which
Logo, vector	SVG	PDF, EPS	SVG for web; PDF or EPS for print, embroidery, large-format, and partners who request them
Logo, raster	PNG with transparency	JPG on white	PNG for overlays and dark backgrounds; JPG only when transparency is not needed and file size matters
Photography	High-res JPG or TIFF	Web-optimized JPG or AVIF/WebP	Master files in 00 to 03; web exports in a clearly named _web subfolder
Color palettes	ASE (Adobe), Figma variables	CSS variables, SCSS map, JSON	Design tools use ASE or native tokens; web uses CSS or JSON exports
Typography	WOFF2 for web, OTF or TTF for desktop	License receipt as PDF	Keep web fonts in a separate web-fonts folder, never inside the brand folder the client receives
Templates	Figma, Keynote, PowerPoint	PDF preview	Editable source plus a read-only PDF preview for stakeholders who do not need the editor
Iconography	SVG sprite or individual SVGs	PNG at 1x, 2x, 3x	SVG for the web, PNG fallbacks for email and older tools

A common question is whether to keep both .ai and .svg versions of the same logo. Yes, with a clear rule: the .ai or .fig file is the source of truth and lives in 07 - Source and Working Files. The .svg and .png exports live in 01 - Logos and Marks for everyday use. Anyone who needs to edit the logo pulls from source; everyone else pulls from exports.

Versioning without losing your mind

Versioning is where most folders quietly turn into graveyards of “FINAL,” “FINAL (1),” and “FINAL use this one.” Two lightweight habits fix that:

• Version the export, not the source. The editable .fig or .ai is a living document. Numbered versions apply to the exports: 2026-08-04, 2026-09-12, and so on.
• Keep three versions, not thirty. Current, previous, and archive. Anything older than the previous version goes to 08 - Archive with a year prefix.

If your team uses a design tool with native history, like Figma or Sketch, the file itself tracks changes. The folder only needs to show the current approved export. This is the single biggest reason brand folders stay small: do not store every draft in the main folder.

Permissions and access: who sees what

Structure alone is not enough. The folder also needs the right access model, especially in cloud drives. A reasonable baseline:

• Brand lead: full read and write access to everything, including archive.
• Designers: read access to all approved folders, write access to 04 - Templates and 09 - Inbox, write access to their project in 05 - In-Use Collateral.
• Marketing and content: read access to all approved folders, write access to 09 - Inbox, no write access to 00 - Brand Foundations or 07 - Source and Working Files.
• External partners: read-only access to a curated subset, usually a shared “External Kit” mirror, not the master folder.

If you use a tool like Figma, Notion, or Frontify as the brand source, treat the folder as a sync target rather than the editing surface. Figma is a good place to learn how design teams manage shared systems; a practical look at collaborative design workflows and how ideas become shipped work shows how this plays out in real teams.

The “External Kit” pattern for partners and clients

Most folder chaos comes from people sending the wrong logo to a partner, or sending the right logo in the wrong color. The fix is a separate, pre-approved kit that you can hand to anyone outside the team. A good external kit contains only the assets a partner is allowed to use, in the formats they are most likely to need:

• Logo in primary, mono dark, and mono light, in SVG, PNG, and PDF
• Clear-space and minimum-size rules in a one-page PDF
• Approved color codes in RGB, CMYK, and HEX
• One example of correct usage and one of incorrect usage
• A short “do not” list: do not stretch, recolor, add effects, or place on busy backgrounds

Keep the external kit in its own folder under 06 - Partner and Co-Brand Kits, with a clear name like MV_Partner-Kit_2026.zip. When someone asks for assets, you send the kit. When the kit changes, you update the kit, not the master folder.

Documentation that does not rot

A folder is only as good as the one-pager that explains it. Without a short guide, every new teammate reinvents the structure, slowly pulling it apart. A useful brand folder README answers, in plain language:

1. What this folder is and what it is not.
2. The folder map, with one sentence per section.
3. The naming pattern, with two or three real examples.
4. Who owns the folder and how to request changes.
5. Where to put new files when you do not know where they belong (usually 09 - Inbox).
6. The single rule: if you are about to save FINAL-v2, stop and version the file instead.

Keep the README as a README.md at the top of the folder, or as a pinned page in the team’s workspace. A short guide tied to a broader visual identity system is more durable than a long style guide nobody reads.

Maintenance: the 30-minute monthly check

Folder structures do not collapse dramatically. They drift. A new template gets saved in the wrong place, then duplicated, then renamed, then sent out by accident. A small, scheduled check stops drift before it becomes a problem.

A 30-minute monthly pass can include:

• Empty 09 - Inbox and move anything approved into its proper home.
• Check that no file in approved folders has FINAL, copy, or a stray number in its name.
• Confirm the three most recent versions of each major asset are present and earlier versions are archived.
• Update the external kit if anything in 00 - Brand Foundations changed.
• Review access permissions after any team change.

Do this with a calendar reminder. The whole point of a brand asset folder is that it stays boring.

Common mistakes and how to avoid them

Even with a good plan, a few patterns reliably break brand folders. Knowing them in advance saves a cleanup later.

Mistake	Why it hurts	What to do instead
One folder named “Brand Stuff”	No top-level structure means everything ends up at the same level, and nothing is findable	Use the 00 to 09 top-level layout from this guide, even if some sections are empty at first
Mixing source and exports in the same folder	Partners grab the editable .ai by mistake and break layouts downstream	Keep source files in 07, exports in their functional folders
Saving every draft in the main folder	The folder becomes huge, search becomes useless, and old drafts get reused by accident	Drafts live in 09 - Inbox and move to archive when the campaign ends
Letting anyone rename files	External links break, partners end up with inconsistent names, and the naming pattern erodes	Restrict rename rights on 00 - Brand Foundations to the brand lead
Storing fonts inside the brand folder	Font licensing is per-seat, and distributing the font file often breaks the license	Keep font files in a separate, access-controlled folder and link to them; share only web-font subsets when needed
Using a single color code style	HEX is great for web, CMYK for print, and mixing them silently shifts brand colors	Store one master palette with HEX, RGB, and CMYK side by side, and export to the format the team needs

If you are auditing an existing folder rather than building one from scratch, this table doubles as a checklist. Walk through each row and fix what you find.

Adapting the structure to different tools

The folder layout above works in Dropbox, Google Drive, OneDrive, Box, SharePoint, and on a local drive. A few tool-specific notes help it land well in each.

• Google Drive: turn on color coding for the top-level folders so 00 - Brand Foundations and 08 - Archive are visually distinct. Use the “Shortcuts” feature to surface the external kit in shared drives without duplicating it.
• Dropbox: use the “Brand Kit” or “Showcase” feature for client-facing assets, and keep the working folder internal. Pin the README to the top of the folder list.
• OneDrive and SharePoint: rely on the metadata columns. Add columns for Asset Type, Status, Owner, and Expiry Date so the team can sort and filter without opening folders.
• Local drives and NAS: mirror the same structure on each designer’s machine under a known path, and use symlinks for shared network folders so file paths stay stable.

Whatever tool you use, the principle is the same: a clear folder map, a single naming pattern, and a small set of governance rules. The rest is just file storage.

How this connects to the wider brand system

A brand asset folder is one piece of a larger system. It feeds the website, the social channels, the pitch deck, and the partner kit. When it is in good shape, the rest of the system is faster because nobody is hunting for the right file or wondering whether a logo is up to date. The same logic that keeps a folder clean also keeps a website performant, a deck on-brand, and a launch on schedule. A practical look at how a planned site actually performs shows how that discipline carries over from file management to the web.

None of this requires a brand portal, a DAM platform, or a six-week migration. It requires a structure, a pattern, and someone willing to spend 30 minutes a month keeping it honest. That is the difference between a folder and a brand asset folder.

Frequently asked questions

What is the best folder structure for brand assets?

A two-level structure works for most teams: numbered top-level folders (00 to 09) for asset families, then one or two levels of subfolders for context like variant, campaign, or year. Avoid nesting deeper than three levels, and put drafts, archive, and external kits in their own clearly named sections so the working folder stays focused on approved assets.

How do I name brand asset files consistently?

Use a short, predictable pattern such as [Brand]_[AssetType]_[Variant]_[Context]_[Version].[ext]. Separate segments with underscores, join words inside a segment with hyphens, and use ISO dates like 2026-08-04 for version stamps so files sort correctly. Avoid words like “final” or “copy” in filenames; instead, create a new file with a new version stamp.

Where should editable source files live in a brand folder?

Keep editable source files such as .ai, .fig, .psd, and .sketch in a dedicated source folder, often labeled 07 - Source and Working Files, with write access limited to designers and the brand lead. The main brand folders should contain only approved exports, so partners and other team members cannot accidentally grab a working draft.

How often should a brand asset folder be cleaned up?

A 30-minute monthly review is enough for most teams. Empty the inbox folder, move approved items into their proper homes, archive anything older than the previous version, and check that the external kit still reflects the current brand. Larger organizations may add a quarterly review focused on permissions, licensing, and storage size.

Should fonts be stored inside the brand asset folder?

It is usually better to keep font files in a separate, access-controlled folder. Many font licenses are per-seat and do not permit redistribution, so embedding fonts in a folder shared with external partners can violate the license. Use web-font subsets in the website and keep desktop fonts on the machines of the people who need them.

What is the difference between a brand asset folder and a digital asset management system?

A brand asset folder is a structured directory in a cloud drive or local file system, governed by a small set of naming and permission rules. A digital asset management system, or DAM, is dedicated software for storing, tagging, searching, and distributing assets at scale, often with metadata, usage analytics, and approval workflows. A well-organized folder can serve small and mid-size teams for years before a DAM becomes worthwhile.

How do I share brand assets with external partners safely?

Create a separate “External Kit” or “Partner Kit” folder that contains only the assets and formats partners are allowed to use, plus a short usage guide. Share it as a zip file or a read-only shared link rather than giving partners access to the master folder. Update the external kit whenever the brand foundations change, and keep the master folder internal.

How do I keep a brand asset folder from getting messy again?

Restrict rename and delete rights on the core folders to the brand lead, keep an inbox folder for new uploads, and agree on a short README that explains the structure and naming pattern. A monthly 30-minute cleanup keeps drift under control, and a single rule, “no FINAL in filenames, version the file instead,” prevents the most common source of clutter.

What file formats should I keep for logos?

For everyday use, keep SVG for web, PNG with transparency for digital overlays, and PDF or EPS for print and large-format production. Master source files such as .ai or .fig belong in the source folder, not in the public-facing logo folder. Avoid JPG for logos, because JPG does not support transparency and introduces compression artifacts on sharp edges.

How do I migrate an existing messy brand folder into the new structure?

Start by creating the new folder skeleton alongside the old one, then move assets in batches by category: logos first, then color and typography, then photography, then templates. Rename files as you move them so the new naming pattern is in place from day one. Archive the old folder rather than deleting it, so you have a fallback while the team adjusts.

Related reading

• Graphic design jobs: a practical guide to roles, skills, and pay
• Design within reach: a working guide to the brand and what it offers