Storage tiering keeps an asset's searchable preview and metadata on fast online storage, while the large original file lives somewhere cheaper — tape, or a Glacier-class cloud archive — and is restored only when someone actually needs it.
In plain English
Most DAM tools quietly assume every file is sitting on fast, always-available disk. That assumption is affordable when a library is photographs. It stops being affordable when a library is footage: an archive measured in hundreds of terabytes, of which perhaps two percent gets touched in any given month, is paying premium storage prices for bytes nobody is reading.
Storage tiering separates the two things a DAM actually needs to keep online. The lightweight proxy and the metadata record stay on fast storage, so the asset remains fully searchable, browsable and reviewable. The heavyweight original master moves down to a cold tier, where storage costs a fraction as much, and comes back up on demand when someone needs the real file for a final export.
This is one of the sharpest lines between a general-purpose DAM and a dedicated media asset management (MAM) tool. In our testing, MAM platforms like iconik and CatDV keep searchable proxies and metadata online while the originals stay on tape or Glacier-class storage, restoring on demand. Standard DAMs assume disk-resident files — which is exactly the assumption that becomes expensive at footage scale.
One caution about the words themselves: "storage tiering" and a "storage tier" on a vendor's pricing page are unrelated. The first is an architecture describing where files physically live. The second is just a billing step — how many gigabytes your plan includes before you pay for more. A tool can have priced storage tiers and no tiering architecture whatsoever.
Why it matters in a DAM
For photo libraries, storage tiering rarely matters — the whole archive fits on disk without straining a budget. For any team whose library is dominated by video, it can be the difference between an archive that is economically viable to keep and one that quietly forces deletion decisions. The trade it introduces is latency: a cold-tier restore is not instant, and a workflow that assumes any master is a click away will feel the difference.
Buyer’s test: if you're evaluating a tool for a large video archive, ask what happens when a user requests a master that has been tiered down — does the tool queue a restore automatically and notify them, or does it simply show an error? And ask what the restore actually costs, since Glacier-class retrieval is billed per request as well as per gigabyte.
Related terms
See it in action
Our best media asset management software ranking tests which tools genuinely index and search assets whose originals live on tape or Glacier-class storage, rather than assuming every file is disk-resident.
FAQ
What is storage tiering in a DAM?
Storage tiering keeps an asset's searchable preview and metadata on fast online storage while the large original file lives in cheaper cold storage - tape or Glacier-class archives - and is restored only when someone actually needs it. The library stays fully browsable even though most of its bytes are offline: you can search, filter and preview normally, and the wait only appears at the moment someone asks for the master. It is how an archive that outgrew its fast disk stays usable instead of being deleted or forgotten.
Is a 'storage tier' on a pricing page the same thing?
No - the same words mean two different things. Storage tiering is an architecture for where files physically live, hot versus cold. A 'storage tier' on a vendor's pricing page is a billing step: how many gigabytes or terabytes your plan includes before you pay for more. A tool can have priced storage tiers and no tiering architecture at all. If the feature matters to you, ask specifically whether originals can be moved to cold storage while previews stay online.
How long does it take to get a file back from cold storage?
Not instantly, and how long depends on the archive class the DAM is using - some return a file in minutes, deep archive tiers can take hours, and the vendor should be able to tell you which they use. That delay is the whole trade: you accept a wait on the rare request in exchange for not paying fast-disk prices on assets nobody has opened in years. It is why tiering suits finished archives and back catalogue, and not the material a team is working on this week.
What stays online when a file is tiered to cold storage?
The parts that make the asset findable: its metadata, its thumbnails and preview renditions, and its place in collections and search results. What goes cold is the heavy original - the layered master, the RAW, the video source. In practice that means the library looks and behaves normally to everyone browsing it, and most people never notice that the bytes are elsewhere, because most requests are answered by a preview rather than by the master.
Who actually needs storage tiering?
Teams whose library is dominated by large files they rarely open again: video and RAW archives, campaign back catalogue, anything kept for legal or historical reasons rather than daily use. If your library is mostly modest-sized files, or everything gets used regularly, tiering adds complexity and a retrieval wait for savings you will not notice. The signal to look for is a big gap between how many bytes you store and how many bytes you actually touch in a year.