Google has somewhat hidden file limitations for its Google Drive online cloud storage service and it is catching some users by surprise. For years, this has been a popular solution along with similar options like Apple’s iCloud service. All of these have offered free use up to a certain capacity limit (15GB for Google Drive), but users aren’t just limited by space and other restrictions aren’t so easy to learn about.
The company now has over a billion users worldwide making use of this service and this would tax the resources of any company when it comes to the cost ratio. Especially, when you consider the fact that many of these users make use of the free account tier.
Users can pay to expand their storage from 15GB (free) to as high as 10TB ($200/month) with a few options in between that are much more reasonable to the average person. This is known as a “Google One” subscription. Many of us here have 100GB to 200GB accounts for various personal uses and it works out to be a really good tool to have.
In order to help balance the load on the company’s server, it makes use of a number of other restrictions. The restriction that seems to be catching some by surprise has to do with how many files a user is storing on Google Drive.
Google has been enforcing these file limits lately, causing some users to lose access to the upload of further content until current data is deleted to make room. Essentially freezing these accounts until the user takes action.
Some documents on Google claim that the file limit is around 400K, although current data going around states that there is a new limit of 5 million files, which is actually more than reasonable (quite more). In fact, most web hosts enforce the same restriction. This is also known as “inode” limits, where inodes are the number of files/folders being stored on a system.
File systems are limited when it comes to inodes, just like they are when it comes to overall capacity. Too many files and the system is unable to store anything else regardless of any free space left over. So to prevent a small number of users from taking potential inode counts from others on a server, these numbers are limited on a per-user basis.
Almost every host that offers shared hosting space or VPS services has inode limitations. So it is no surprise that Google is doing the same for its cloud storage solutions. Some web hosts even go as far as using these as a bait trick to force users into upgrading to pricey accounts–by setting the inode limit so low that the user hits it way before they hit their storage capacity limits. Or they will offer “unlimited space” (which is never true as you’ll always be limited in other ways).
Companies like Bluehost are well known for this. Bluehost, setting its inode limit to just 50K files (which isn’t much at all). Especially, when you take into account that a brand new WordPress/blog installation is around 2-3K inodes. If someone posts daily, that limit is going to be hit pretty fast even though the user would likely have plenty of space left over. Kind of cruel when other hosts over similar accounts for the same price but with 4-6x the inode limitations. For example, Namecheap has 300K-1.5 million inode limits for its accounts (VPS solutions typically fall around 1 million inodes or more).
So when you consider a 5 million file (inode) limit for Google Drive, this isn’t bad at all. Especially, if this limit also includes its 15GB free tier account as it would be incredibly difficult to hit this limit unless you were storing nothing but small text files. Heck, the 400K file limit isn’t bad either for those free accounts. I mean, the account is free and it would have better inode limits than many of the paid web hosts out there.
Google also implements additional limitations, like the amount of data a user can move in a day. Also not so much a sales tactic as this can severely limit access for others if one person is moving overly-massive amounts of data everyday, taxing the server(s) related. It appears this limitation is “up to 750GB per day”, which is yet another fair restriction. Another restriction is that text files cannot exceed 50MB (they rarely due unless you have massive error or debug logs you are trying to archive).
I am happy to see that Google isn’t gouging the public with unfair limits as a way of trying to bully people into paid (or more expensive) subscriptions.
What are your thoughts on these limitations? Feel free to share them below in the comments!



