Reference Glossary
Hot storage
Hot storage is a cloud storage class built for frequent, low-latency access, priced higher per GB than cold tiers because the data has to be instantly readable at any time.
Why it matters in a DAM
Every asset a DAM shows in search results, renders a thumbnail for, or serves to an active campaign needs to sit in hot storage — that's what makes browsing feel instant rather than sluggish. Keeping the entire library on hot storage, including assets nobody has opened in years, is one of the most common and most avoidable cost drivers in a cloud-native or self-hosted DAM deployment.
A worked example
Common mistake
Treating hot storage as the default for the entire library rather than a working set — every asset ever uploaded stays in the most expensive tier because nobody configured lifecycle rules to move inactive files down.
Hot storage is the tier a DAM relies on for anything that needs to open the instant someone clicks it. Search results, grid thumbnails, active campaign files, and anything currently in a review or approval workflow all need to live here — the higher per-GB price buys guaranteed low latency, with no retrieval fee or waiting period.
The practical question for a DAM admin isn’t whether to use hot storage — every deployment does — but how big to let the hot working set grow. A library where 90% of assets haven’t been opened in over a year but still sit on hot storage is paying premium prices for files that behave, in every practical sense, like archive candidates.
This is why storage tiering exists as a companion concept: hot storage should shrink to roughly match what’s actually in active use, with lifecycle rules quietly moving the rest to cooler tiers. Skipping that step is the single most common reason a growing DAM’s cloud storage bill climbs faster than the actual size of the active library.
In practice, hot storage should be reserved for:
- Thumbnails and preview proxies shown in search results and grids
- Assets attached to an active campaign, project, or approval workflow
- Video proxies used for in-browser playback
- Anything a user would reasonably expect to open instantly, with zero wait
Frequently asked
Why is hot storage more expensive than other tiers?
The provider keeps the underlying disks always spinning and immediately addressable, with redundancy built for instant reads — that infrastructure costs more to run than the tape-like or spun-down systems behind cold and archive tiers, and the price reflects it.
Should a DAM's thumbnails also live in cold storage to save money?
No — thumbnails and preview proxies are small and accessed constantly during browsing, so they normally stay in hot storage even when the full-resolution master they represent has been moved to a colder tier.
How much of a DAM library should realistically sit in hot storage?
It varies by organization, but it's typically the working set from active and recent projects — often a small fraction of the total library size, with the rest eligible for tiering down once access frequency drops.
Does hot storage affect video streaming performance in a DAM?
Yes — video proxies used for in-browser playback benefit most from hot storage's low latency, since a cold-tier video would need to be restored before it could even be transcoded for preview.
What happens if an asset needed urgently was moved out of hot storage?
The DAM (or the storage layer behind it) has to initiate a restore from the colder tier first, which can take anywhere from minutes to hours depending on the tier, before the file is available again.
Is hot storage the same thing as "cloud storage" in general?
No — hot storage is one class within a provider's broader set of storage options; "cloud storage" is the general term, and most providers offer hot, cool/nearline, cold/coldline, and archive classes side by side.
Sources
- S3 Standard costs about $0.023/GB-month versus roughly $0.0036/GB-month for S3 Glacier Flexible Retrieval and $0.00099/GB-month for Deep Archive (US East list pricing). checked 2026-08-07 — CloudZero, Amazon S3 pricing guide