"Can you sort out our assets?" usually arrives as a quick message, and it tends to land on whoever already knows where things are: the brand lead, or the designer who gets pinged every time someone needs the logo. Nobody means "rename the Drive folders." They mean "make it so I can find the right file without asking you."

The request rarely comes out of nowhere. Three versions of the same hero image are floating around, and a retail partner just posted last season's packaging shot. Meanwhile, the spring shoot is still on a photographer's hard drive, and a Slack thread that opened with "sorry, do you have the vertical crop?" has four replies and no file.

What you're being asked to build is a digital asset library: one shared, searchable home for your team's approved images, videos, logos, and design files, where anyone can find the current version and know it's okay to use without asking first.

This guide covers what a digital asset library is and what belongs in it, how it relates to a DAM and to cloud storage, where do-it-yourself setups tend to break, and five steps to build one that holds up as your content volume grows.

A digital asset library is the single place your team goes for finished, approved creative and the source files behind it. What makes it a library rather than a tidy folder is whether a colleague can use it without you in the room.

What goes in a digital asset library

Most libraries end up holding a mix like this:

• Product and lifestyle photography

• Video, from raw footage to finished cuts

• Logos, brand marks, fonts, and color references

• Campaign and ad creative, including social cuts and email graphics

• Packaging files and presentation templates

• UGC and influencer content

You keep the working files next to the exports, so changing one line of copy doesn't mean rebuilding a layout from a flattened JPEG. And you don't need the whole archive on day one, just the files people ask for most.

What separates a digital asset library from a folder

Put any setup through four questions:

1. Can someone who didn't make the asset find it?

2. Can they tell which version is current?

3. Can they tell whether it's approved?

4. Can they tell whether it's still cleared for this use?

A folder structure on its own passes none of them. It only answers "where did someone decide to put this?", and that depends entirely on who uploaded the file.

A digital asset library puts the context on the asset itself. Status, usage rights, campaign, and version history travel with the file instead of living in a spreadsheet or a Slack thread. That's what lets a library act as creative memory for the team: it remembers what each asset is and what's been approved, long after the people who made those calls have moved on.

Who uses a digital asset library day to day

A digital asset library serves two audiences at once. Creative teams need a system of record, while marketers, ecommerce teams, agencies, and partners need to pull approved files without routing every request through a designer.

Self-serve looks like this in practice:

• A social manager grabs approved vertical crops the morning of a launch

• An ecommerce coordinator pulls variant images for a new SKU

• A PR contact sends a press kit without waiting on anyone

• An agency collects brand files for a new campaign

If only one person knows where everything lives, you have a bottleneck with better thumbnails.

"Digital asset library" describes what your team is building, while DAM, cloud storage, brand portals, and project management tools describe the software around it.

So the digital asset library vs. DAM question has a simple answer: the DAM is the software, and the library is what you build inside it. A brand portal is one way to open that library to people outside the team. 

For the full side-by-side on storage, see digital asset management vs. cloud storage, and for the category itself, start with what is digital asset management.

Most growing teams need library behavior (search, current versions, approvals, and self-serve access) long before they need an enterprise rollout.

"I could just build a DAM myself" is a fair point to raise. With a shared drive, a clear folder plan, a naming convention, and maybe some home-built AI tagging, a disciplined team can keep things in order for months.

Then it starts to slip, usually in the same four places:

1. One file filed twice becomes two copies. Drive and Dropbox tie each file to one location, so filing the hero image under both "Spring campaign" and "Product" means two copies, and soon two "finals."

2. Search mostly knows filenames. Finding anything depends on what someone typed when they saved it, and "IMG_4872" won't come up when you search for "beach."

3. Nothing says whether it's approved or still licensed. That knowledge lives in someone's memory or in a thread nobody can find.

4. Upkeep has no owner. The structure holds until the person who built it gets busy or leaves.

Candid's team ran into all of this. Its customer story describes the previous state: "There was no comprehensive asset library, just a fragmented series of storage units." Assets were spread across Dropbox, Google Drive, servers, and hard drives. Just over a year after moving to Air, the team's workspace held 90,000 assets and 5.5 TB of content.

For a brand-conscious team, the stakes go beyond lost time: an outdated pack shot or an expired talent image can go live on a partner's site before anyone notices.

Signs you've outgrown the DIY version:

• "Can you send me the latest?" shows up every week

• People recreate assets because they couldn't find the original

• Partners are using files you don't recognize

• Nobody can answer "is this approved?" without digging

These five steps (gather, structure, describe, open it up, and keep it current) work in whatever tool you choose. We'll use Air as the worked example so you can see what each step looks like in practice.

Step 1: Gather what people actually ask for

Skip the full migration at first. List the 10 to 20 requests your team fields most often and collect those assets.

Pull from shared drives, laptops, old email threads, and shoot deliveries still sitting with photographers. In Air, the built-in importers bring content in from Google Drive, Dropbox, Box, and SharePoint. It's a one-time copy rather than a live sync, so the library becomes the source of truth instead of a mirror of the old folders.

To keep new work flowing in, Content Collection links let outside contributors like photographers and agencies upload straight into a board without an Air account, and you can require fields like usage rights before they submit.

As you gather, keep one copy of each asset. If an import surfaces duplicates, a filename search shows every instance so you can keep the best one and delete the rest.

Step 2: Structure it the way people ask for things

Create a few top-level groupings named the way colleagues actually talk: "Spring campaign," "Product photography," "Logos and brand," "Social," and "Events." Skip department codes and keep nesting shallow, because a file five levels deep is only findable by the person who put it there.

In Air, Boards act as visual smart folders, and one asset can sit in several boards at once without being copied. A single hero image can live in the Spring campaign, Product photography, Paid social, and Retail partners boards with only one file to update, which ends the "campaign or product?" debate. 

Custom fields work the same way, so changing an asset's status once updates it everywhere it appears. Scrubbable previews help too, since hovering over a video beats opening ten tabs to find the right cut.

Step 3: Describe assets with a starter set of fields

Hold off on a full taxonomy. Start with a handful of custom fields that answer the questions people actually ask:

Air workspaces come with status, rating, usage rights, and assignee fields by default, and you can add a date field for expiry. Once approval status lives on the asset, nobody has to reconstruct a decision from a Slack thread. 

Let the software handle the descriptive tagging your team won't keep up with. Air's Smart Tags label images on upload based on the objects, themes, and concepts they contain, and OCR picks up text inside images and PDFs. Conversational search then lets someone type a description instead of guessing a filename.

Candid saw the difference here. Before Air, the team's lead brand designer spent up to 20% of the week finding assets for other people, and with search across the library, that dropped to around 2%.

Deeper schemas can come later, once you use starter fields consistently.

Step 4: Open it up to the people who need it

Access is the step DIY setups most often skip, and it's the one that decides whether the library actually becomes useful.

Every Air plan includes unlimited seats, so adding the whole marketing team, ecommerce, sales, and the ops lead doesn't change the bill. For people outside the workspace, share links can carry passcodes and expiration dates for one-off sends. When partners, retailers, press, or clients need a curated view, a Showcase packages selected boards and assets into a single curated page without moving anything in your workspace.

Self-serve doesn't mean uncontrolled though. Roles and link settings decide who can view, comment, download, and edit, so work in progress stays internal.

To get adoption going, run one short walkthrough with the marketing team using a real request they made last week, which lands better than a training doc.

Step 5: Keep it current

Version stacking in Air puts new iterations on top of the original, keeping earlier versions in the stack for comparison. Annotations pin feedback to a spot on an image, time-based comments attach it to a moment in a video, and a Kanban view grouped by status lets you move assets from "In Progress" to "Approved" by dragging them. 

For public-facing images, CDN links keep published assets current, so updating an asset in Air updates every website or email using that link.

It’s worth noting that automated content expiration is an Enterprise feature in Air. On other plans (or with whichever software you choose), schedule a monthly or quarterly sweep against your expiry field to retire lapsed licenses, expired talent images, superseded packaging, and retired logos.

Here’s a maintenance checklist you can copy:

• New work goes into the library first, not onto a desktop

• The owner reviews new uploads every week

• Expired assets get archived on a set schedule

• Status fields never stay blank

Organizing your assets is the starting point, and the return comes when approved work gets reused instead of rebuilt. Once a marketer can find an approved design and see its status, they can adapt it for a new channel without opening a fresh creative request.

In Air, that happens in Canvas, the built-in editing layer:

• Smart Resize generates a version for each channel while keeping layout and text intact

• Background and object removal cleans up product shots

• Image-to-video turns a still into a short clip or GIF

• Edit text swaps copy on an image without the source file

• Batch edits apply the same change across many assets at once

Context stores your brand details (colors, fonts, logos, and instructions for how to use them), so Canvas edits reflect your brand without anyone re-entering it each time. Using AI this way can only multiply work that's approved and well described, which is exactly what steps one through five build.

Ready to start? Create a free Air workspace and build the first version of your library around the assets your team asks for most.

What is a digital asset library?

It's one shared, searchable home for a team's approved images, videos, logos, and design files, where anyone can find the current version and see whether it's cleared to use.

Is a digital asset library the same as a DAM?

Not exactly. The library is the collection your team builds, while a DAM is the software that runs it at scale. Air is a DAM, and more, with approvals on the asset and built-in AI editing for reusing approved work.

What should go into a digital asset library first?

Start with the 10 to 20 assets people request most, such as logos, current campaign creative, top product photography, and core templates. The archive can follow.

How do you organize a digital asset library so non-designers can find things?

Use a few shallow top-level groups named in your colleagues' own words, then let AI tagging and plain-language search surface assets by what's in them.

Can I build a digital asset library in Google Drive or Dropbox?

You can start one there, but it gets harder as volume grows. Files tied to one folder get duplicated across folders, and there's no built-in way to show whether an asset is approved or still licensed.

How long does it take to set up a digital asset library?

Starting with your most-requested assets instead of the full archive, a working first version is realistic within a week. Air's Free plan has no time limit and needs no credit card, so you can test the structure on real files first.