Short answer: a spreadsheet — Excel or Google Sheets — can list your assets: a row per file with a name, a link and a status. But a list is not the assets. There are no previews, no embedded metadata, no rights, no search-by-image, and the links rot. It is the manual “before” almost every team starts with. A DAM is the actual managed library that replaces it — and if you have already upgraded to Airtable, that is a better tracker but still not a DAM.
Spreadsheet vs DAM, side by side
| Spreadsheet | Digital asset management | |
|---|---|---|
| Holds | A list that points at files | The files themselves, managed |
| Preview | None (maybe a pasted thumbnail) | Every asset, visual browse |
| Metadata | Manual columns, unlinked to files | Embedded IPTC/XMP + taxonomy + AI tags |
| Search | Text filters on your rows | Metadata, keyword & visual search |
| Links | Break when files move | Assets and links stay valid |
| Rights & versions | Whatever you remember to type | Tracked rights, expiry & versions |
Why the asset tracker always breaks
A spreadsheet can describe your assets, but it can never be them — and that gap is where every tracker eventually fails. The row says hero_spring.jpg lives at a certain path, was shot by a certain photographer, and is cleared until a certain date. But the sheet holds none of the actual pixels, reads none of the file's own embedded metadata, and shows no preview. It is a hand-typed index sitting next to the files, and it drifts out of sync the moment someone moves, renames or deletes a file without updating the row. Links rot silently; nobody notices until the asset is needed. For the tools that replace a tracker properly on the stills side, see our photo library management ranking.
It also enforces nothing. Rights and expiry are free text in a cell, not rules — nothing stops a colleague from grabbing a shot whose licence lapsed last quarter, because the spreadsheet can't see the file, let alone gate access to it. There is no version history of the asset, no thumbnail wall to browse, and no way to search by what is actually in an image. You can search only what somebody remembered to type.
The hard limits arrive too. A single Excel worksheet stops at 1,048,576 rows; a Google Sheet stops at 10 million cells — and because that ceiling is cells rather than rows, a tracker with twenty metadata columns fills up around 500,000 rows. Google also silently drops any cell longer than 50,000 characters when it imports an Excel file. Long before those numbers, though, a shared sheet with several people editing has already become slow, fragile and quietly wrong.
The moment the sheet lies to you
A small brand team keeps a “master asset list” in Google Sheets: filename, Drive link, photographer, usage rights, expiry. It works for a year. Then someone reorganises the Drive folders, a batch of links breaks, and two people add the same shoot under slightly different names. A month later a manager filters the sheet for “approved, in-licence product photography,” pulls a hero image and ships it — not knowing the licence expired six weeks earlier, because the expiry column was last touched by hand in March. Nothing in the spreadsheet was capable of catching that.
This is an illustrative composite, not a measured incident, but every failure point — broken links, duplicates, a stale rights column nobody re-checked — comes straight from the fact that the sheet is a detached description, not the managed asset itself.
What a DAM replaces — and keeps
A DAM is, in one sense, the spreadsheet done properly: the columns you maintained by hand — creator, date, keywords, rights, expiry — become indexed, validated fields bound to the actual file and its renditions, not a detached list that drifts. The difference is that the DAM reads much of that metadata straight out of the file (embedded IPTC and XMP keywords, capture date, camera), shows a thumbnail wall instead of a wall of filenames, and can actually enforce the rules the spreadsheet could only note. If your team likes the structured, columnar way of thinking, a database-style tool such as Airtable is a step up from a flat sheet — but it still isn't bound to the assets the way a DAM is.
When a spreadsheet is fine — and when to stop
A spreadsheet is fine as a temporary, small-scale index — a few hundred files, one or two maintainers, a short-lived project where nobody tracks enforceable rights. Stop using it the moment the library grows into the thousands, more than a couple of people edit it, links start breaking, or a wrong-rights mistake would actually cost you. That is the point a real managed library pays for itself. Start with the best DAM software ranking, or read how to organise a photo library for the structure a DAM gives you.
Sources & references
- IPTC Photo Metadata Standard — the embedded metadata that keeps data attached to the asset, unlike a spreadsheet, accessed July 2026.
- Daminion — DAM that replaces a fragile spreadsheet tracker, vendor site, accessed July 2026.
- Microsoft — Excel specifications and limits — the 1,048,576-row worksheet limit, accessed July 2026.
- Google — Files you can store in Google Drive — the Google Sheets 10-million-cell limit, accessed July 2026.
- PhotoLib methodology — how we research and test DAM tools. See our methodology.
Keep reading
FAQ
Can I use a spreadsheet as a DAM?
For a tiny, stable set of files one person maintains, a spreadsheet list works. But it tracks assets rather than holding them: no previews, no embedded metadata, no search-by-image, and links break when files move. It reliably collapses as the library grows past a few hundred assets.
Why do spreadsheets fail as asset trackers?
Because the list and the files drift apart. Move a folder and links rot; hand-typed metadata lives nowhere near the asset; there are no previews; versions multiply with no source of truth; and rights are a column nobody maintains. A DAM keeps metadata inside the asset and the library is the files themselves.
Is Airtable better than a spreadsheet for assets?
Airtable is a stronger tracker - relational, with attachments and views - but it is still a database that points at assets, not an asset manager. It hits the same ceiling on large binaries, renditions, embedded metadata and rights. See our DAM vs Airtable guide for where it stops.
When should we move from a spreadsheet to a DAM?
As soon as more than one person maintains the library, links or versions start breaking, or you cross a few hundred assets. A DAM replaces the fragile list with a managed library where search, previews, rights and versions stay attached to the files.
How many assets can a spreadsheet really hold?
The hard ceilings are high - an Excel worksheet allows 1,048,576 rows, and a Google Sheet allows 10 million cells, which with twenty columns of metadata is roughly 500,000 rows. But those numbers are not the real limit. A shared sheet becomes slow, error-prone and full of broken links and duplicates long before then, because it is a manual list detached from the files it describes. Teams outgrow the spreadsheet on reliability, not on row count.