/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Google confirms putting a 5M-file limit per Drive account, even for paid Google One plans, in February 2023 without telling users, who thought the cap was a bug

The new file limit means you can't actually use the storage you buy from Google.  —  “Please delete 2 million files to continue using your Google Drive account.”

Ars Technica Ron Amadeo

Context & Ripple Effects

Google One’s consumer storage tiers were built around capacity pricing, including a 2018 plan overhaul that added a 200GB tier and cut the 2TB price. The newly disclosed file-count ceiling exposes a separate constraint: paid capacity does not necessarily equal usable storage for accounts with many small files.

The policy was not durable in its original form: Google later backed away from applying the 5M-file cap to all Drive users and said it would explore alternatives. That reversal makes notice, product terms, and how platforms meter storage as important as the limit itself.

First-order effects

  • Drive accounts with large numbers of small files can be blocked from adding content despite having unused paid storage, forcing deletion or account restructuring.
  • Google One’s storage promise becomes harder to interpret for affected subscribers, while Google must address a policy users encountered as an apparent product failure.

Second-order effects

  • Heavy archival and backup users gain an incentive to consolidate files, split data across accounts, or evaluate storage providers whose limits are framed differently.
  • The rapid retreat from the universal cap raises the cost to Google of introducing operational controls without clear disclosure, likely increasing scrutiny of future storage-policy changes.

Third-order effects

  • Consumer cloud storage is increasingly defined by multiple quotas—not only advertised gigabytes—so product comparison will hinge on the practical limits attached to paid plans.
  • If providers keep tightening non-capacity constraints, portability and digital-library migration become more consequential for customers whose archives are costly to reorganize.

The trend: This is one instance of cloud platforms translating the operational cost of managing vast user libraries into finer-grained limits beyond headline storage capacity.