Google Drive and Dropbox as a DAM: the limits, from their own documentation

Almost every comparison of digital asset management and cloud storage makes the same argument: folders do not scale, filenames are not metadata, and versions get lost. The argument is right. It is also, in nearly every version of it published by a DAM vendor, unsupported by a single number.

Google and Dropbox document their own limits in detail. This guide collects the ones that matter for a media library, quotes them, and links each to the page it came from. Where a limit is generous, it says so. The aim is not to argue that a shared drive is bad software. It is to let you check your own library against published figures and decide whether you are near any of them.

This is part 1 of a four-part series. Part 2 covers why file search cannot find an image, part 3 covers rights and the audit trail, and part 4 covers moving off the shared drive. Microsoft's side of the same question is in the SharePoint series, which quotes Microsoft's limits rather than repeating them here.

All figures were read on 6 September 2026. Google and Dropbox revise these pages, so check them again before you build a business case on any single line.

Where the numbers come from

Six pages carry almost everything a media library needs to know:

• Google's shared drive limits for capacity and membership.
• Google's storage and upload limits for storage per licence and daily upload.
• Google's file version history page for how long versions of an uploaded image survive.
• The Drive API limits page for quota and egress, which matters if you serve images from Drive.
• Dropbox's restrictions and limitations for team deployments for file counts, folder counts and sync.
• Dropbox's version history overview for retention by plan.

Capacity: how much fits

A Google shared drive holds a maximum of 500,000 items, and Google is specific about what counts: "files, folders, shortcuts, and items in trash". Two of those four are easy to forget. A team that has been organising by copying shortcuts into campaign folders is spending its item budget twice, and a team that never empties the trash is spending it on files nobody wants.

Half a million sounds far away until you count renditions. One product shoot of 200 frames, each kept as a raw file, a full-resolution TIFF, a web JPEG, a square crop and a thumbnail, is 1,000 items. Fifty shoots a year is 50,000. The limit is reachable within a decade of ordinary marketing work, and the failure is not graceful: you stop being able to add files to that shared drive and have to split the library across several, which is exactly the fragmentation the shared drive was meant to prevent.

Other published capacity figures:

Dropbox publishes its numbers as advice rather than as hard stops. Its team deployment page says users "shouldn't sync more than 300,000 files" and "shouldn't sync more than 1,000 shared folders or team folders". The hard limits it does state: 30,000 shared folders per account, 1,500 shared subfolders under any single folder, 1,000 members per shared folder or group or team folder (250 for restricted folders), and 1,000,000 write operations per namespace in a 24 hour period.

The 300,000 file figure is the one that reaches a design team first. Dropbox's desktop client syncs a local copy by default, and a creative department with a shared library of a few hundred thousand files will find that number on every machine in the department, along with the disk space, the indexing time and the battery cost. Selective sync and Smart Sync exist to manage it. Managing it is work, and it is work that has to be redone for every new laptop.

Storage: how much you get, and who else is using it

Google Workspace storage is pooled across the organisation, not allocated per person. The published allocation is a multiplier:

Pooling is generous and it has one consequence worth stating plainly: the marketing video archive draws from the same pool as everyone's Gmail attachments, everyone's Drive, and every other department's files. A 40-person company on Business Standard has 80 TB, which is a lot. A 40-person company on Business Starter has 1.2 TB, which a single year of video will consume.

Dropbox allocates per team rather than per user. Its team plans start at 3 TB for the whole team on Standard and 15 TB on Advanced, with more available on request.

Neither vendor charges for storage the way a DAM does, and for most libraries the storage line is not the problem. The lines below are.

File size and upload: the ceilings you meet during a shoot

Google's limits are high in one place and low in another. A single file can be up to 5 TB. But each user can upload and copy only 750 GB to Drive within 24 hours, and that is a per-user cap across My Drive and shared drives combined.

That number is the one that surfaces during a migration or after a large shoot. A video team delivering a day of 4K footage can pass 750 GB without trying. When they do, the upload does not fail loudly; it stops accepting new uploads from that account until the 24 hour window rolls. The workaround is to spread the upload across accounts or across days, both of which mean somebody is watching an upload instead of working.

Dropbox publishes three different maximum file sizes depending on how you upload:

The 50 GB browser limit matters because it is the route an outside contributor uses. A photographer who has been given a file request link, and who is uploading a large video package from a browser, gets a different ceiling from the staff member who has the desktop app installed.

Versions: the limit most teams discover late

This is the most consequential difference between what teams believe and what is documented, and it is the one no comparison page quotes.

Google's version history page states, for uploaded files: "A version might be permanently deleted after 30 days or if there are 100 newer versions." Retaining an older version past that requires someone to open the file, open Manage versions, and click Keep forever on that specific version.

Two things follow.

First, this applies to images, video, PDFs and design files, and not to Google Docs, Sheets and Slides, which use a different system. A team that tests version history on a Doc will conclude that Drive keeps everything, because for a Doc it very nearly does. The same team's photography is on a 30 day clock. The test that would have told them is to open a JPEG uploaded two months ago and look for its earlier versions.

Second, "might be" is doing real work in that sentence. It is not a guarantee that a version survives 30 days. It is a statement that it will not survive indefinitely.

Dropbox is more predictable and publishes retention by plan:

Dropbox also states that version history does not count against the storage quota, which is a genuine advantage over systems that charge for every retained version.

The useful comparison is not "storage has no versioning". Both have versioning. It is that both treat a version as a recovery mechanism with an expiry, and a media library needs versioning as a permanent record: which crop was approved, which cut went to the client, which logo was correct in 2024 when the packaging was printed. Those questions get asked years later. A 30 day window and a 365 day window both answer them the same way.

Serving media from a drive

Some teams use Drive as the storage behind a website, an app or a partner integration. The Drive API limits apply:

Exceeding the per-minute quota returns 403: User rate limit exceeded or 429: Rate limit exceeded, and Google's recommended handling is exponential backoff. For a public-facing page, that means an image that fails to load rather than an error you can see.

One line on that page deserves attention from anyone budgeting: charges for exceeding quota limits are planned to begin in 2026, with at least 90 days' notice before any change takes effect. Free egress from a general-purpose drive has been an implicit subsidy for a lot of small integrations. It is documented as ending.

Drive is also not a CDN. There is no image transformation, no format negotiation, no responsive rendition, and no cache control you set. If a page needs a 400 pixel wide WebP, something has to make one and put it somewhere.

What it costs

A short version, since the DAM cost guide covers the DAM side properly.

For most companies the storage licence is already paid, and adding a media library to it has a marginal cost of zero. That is a real advantage and it is why the shared drive is where the media ends up.

Published list prices as of 6 September 2026, from Google and Dropbox, quoted in euro because that is the currency those pages served; both vary by region and contract:

The costs that do not appear on those pages are the ones that decide the question: the hours spent maintaining a folder convention, the assets recreated because nobody found the original, the time spent resizing files by hand because the storage does not generate renditions, and the exposure from an image used after its licence ended. Part 3 covers the last of those.

Where the shared drive is the right answer

Three cases, stated plainly, because a guide that concludes "always buy a DAM" is not useful.

A small library that is mostly documents. Contracts, decks, spreadsheets, a few hundred images. Drive and Dropbox handle this well, search works because documents contain text, and nothing in this guide applies.

A single team with a shared vocabulary. Five people who agreed on a folder structure and a filename convention, and who all still work there. Convention substitutes for metadata as long as everyone holds the same convention in their head.

Working files. Project directories, editable source files, scratch exports, the things a designer opens rather than the things a company publishes. These belong in a drive, and part 4 argues they should stay there even after a media library moves.

The case for a separate media library starts when a library is shared with people who did not agree to the convention: a new hire, a second office, an agency, a distributor. That is the point at which the folder structure stops being a shared memory and starts being a puzzle.

Frequently asked questions

Can Google Drive be used as a DAM?

For a small library, yes. Beyond that, three published limits set the boundary: a shared drive holds 500,000 items including trash and shortcuts, versions of uploaded images may be deleted after 30 days or 100 newer versions, and Drive's file metadata carries camera settings but no fields for captions, keywords or rights. Part 2 covers the search consequences of the last one.

What is the Google Drive file limit?

500,000 items per shared drive, counting files, folders, shortcuts and anything in the trash. There is no published per-folder file limit, and folders can nest up to 100 levels deep. My Drive has no equivalent published item cap, but shared drives are what a team library uses.

How long does Google Drive keep old versions of an image?

Google's documentation says a version "might be permanently deleted after 30 days or if there are 100 newer versions". This applies to uploaded files including images and video. Google Docs, Sheets and Slides use a different system with much longer retention, which is why teams who test versioning on a document reach the wrong conclusion. To keep a specific version, someone has to click Keep forever on it.

How many files can Dropbox sync?

Dropbox advises that users "shouldn't sync more than 300,000 files" and no more than 1,000 shared or team folders. These are recommendations rather than enforced caps, but they describe the point past which the desktop client's performance is no longer supported behaviour.

Is Dropbox or Google Drive better for a marketing team?

Neither is designed for one. Dropbox has longer and more predictable version retention on paid plans, and per-link expiry and passwords. Google has pooled storage that is generous on the mid and upper plans, and a shared drive model with clearer ownership. Both index filenames and document text rather than image content, and neither reads the caption, keyword and rights fields that photographers write into image files.

What happens when a Google shared drive hits 500,000 items?

You can no longer add items to that shared drive. The remedy is to move content out or split the library across several shared drives, which reintroduces the problem of assets living in more than one place.

Next in the series: Why you cannot find the image. If you want the side-by-side product comparison instead, see Freedam vs Google Drive and Freedam vs Dropbox.