The practical answer to the google drive shared with me storage question is simpler than most people expect: files in Shared with me usually do not take space from your own quota. The confusion starts when you copy a file, upload your own version into a shared folder, or move work into a shared drive, because each of those actions changes who actually owns the data. This guide breaks down the storage rules in plain English, with the details that matter for everyday use, especially if you handle client files, video assets, or collaborative project folders.
What actually counts against your Drive quota
- Shared with me files normally use the owner’s storage, not yours.
- Copies of shared files do count against your storage.
- Your own uploads to a shared folder count against your storage, even if the folder belongs to someone else.
- Shared drives work differently and are usually team-owned, not tied to one person’s personal quota.
- Your Google storage is shared across Drive, Gmail, and Photos, so a Drive problem can be caused by something outside Drive.
- If storage looks wrong, check Trash, duplicate files, and files you personally created or uploaded.
How Google Drive allocates storage for shared files
I treat Drive storage as an ownership problem, not a location problem. A file does not use your quota just because you can see it in your account; it uses your quota when you own it, create it, copy it, or upload it as your own data. That is why a file in Shared with me can sit in front of you without touching your own storage at all.
| Situation | Who owns the file | Does it use your storage? | What that means in practice |
|---|---|---|---|
| A file in Shared with me | Someone else | No | You can access it, preview it, or work with it without paying storage for the original file. |
| A copy you make from a shared file | You | Yes | The copy becomes your file, so it starts counting against your quota immediately. |
| Your own upload inside a shared folder | You | Yes | The folder is shared, but the upload is still yours, so the storage charge follows the uploader. |
| A file in a shared drive | The team or organisation | Usually not your personal quota | This is a different model built for collaboration, not a personal hand-off of ownership. |
The important takeaway is that Drive storage follows ownership. Once you understand that, most “why is my storage full?” moments become much easier to explain, which leads straight into the actions that actually trigger a charge.
When a shared file starts counting against your quota
A shared item becomes your storage problem the moment it turns into your content. In practice, that usually happens in four situations:
- You make a copy. This is the clearest trigger. If you want your own editable version, a copy is the right move, but it will count against your quota.
- You upload files into a folder someone shared with you. The folder may belong to another person, but your upload is still your file. This is one of the most common misunderstandings.
- You create new collaborative files in that space. Google Docs, Sheets, Slides, Drawings, Forms, Recorder files, and similar content can count depending on when they were created or last edited. For modern workflows, I would assume newly created work is part of your storage footprint unless you are working inside a shared drive.
- You duplicate assets for your own workflow. If you build a new version for grading, colour work, captions, or delivery, the duplicate is yours and storage follows that duplicate.
For video teams, this is the difference between a review link and an archive copy. A shared preview file can stay light and cheap; a downloaded master, re-export, or personal backup copy can quickly become the thing that pushes an account over quota. If that distinction matters to your workflow, the next question is whether you are using a shared folder or a shared drive.
Shared folders and shared drives are different storage models
A shared folder inside My Drive and a shared drive are not interchangeable. They both let multiple people access files, but they do not handle ownership the same way. In a shared folder, people can add files, and those uploads are still owned by the uploader. In a shared drive, files are team-owned, and they remain with the drive even if a member leaves.
| Model | Ownership | Storage impact | Best for |
|---|---|---|---|
| Shared folder in My Drive | Mixed; each file keeps its own owner | Your uploads and copies usually count against your quota | Small collaborations, quick exchanges, one-off reviews |
| Shared drive | Team-owned | Usually tied to the shared drive or organisation, not one person’s personal storage | Ongoing team projects, asset libraries, client work, media production |
For creators and agencies, the shared drive model is usually cleaner. It reduces the “who owns this file?” mess, and that matters once you start passing around large exports, project files, or source footage. If your workspace supports shared drives, I would strongly favour them for anything that needs more than a quick hand-off.
How to check what is really filling up your account
When storage feels inconsistent, I always check the full picture instead of staring only at Drive. Google storage is shared across Drive, Gmail, and Photos, so a file problem may actually be a mail problem or an old media backup. That matters because people often blame a shared folder when the real culprit is a huge attachment, a copy sitting in their own Drive, or content still in Trash.
- Check your storage breakdown. Look at Drive, Gmail, and Photos separately so you can see where the pressure is coming from.
- Empty Trash and Spam. Deleted items still count until they are permanently removed.
- Allow time for updates. After a large clean-up, storage can take 48 to 72 hours to refresh.
- Look for copies first. If you copied a shared file, the copy is now part of your storage.
- Review uploads to shared folders. If you added your own files there, they count as yours even though the folder is shared.
- Double-check Drive for desktop. Local placeholder files on your computer do not always match what you use in the cloud.
That last point catches a lot of people. The number on a laptop or desktop sync client can look different from the number in the browser, and the browser view is the one that actually reflects cloud quota. Once you know where the space is really going, the fix becomes a lot more deliberate.
The rule I use when a shared project file starts feeling expensive
My practical rule is simple: if I only need access, I keep the file shared; if I need ownership, I copy it intentionally; if several people need to add, revise, and store assets over time, I move the project into a shared drive. That approach avoids accidental storage use and keeps the file history easier to manage.
- Review-only work should stay shared, so you do not create extra files you do not need.
- Working copies should be made on purpose, because they are the point where storage starts to count.
- Active team projects belong in a shared drive, especially if the files are large or the team changes often.
- Finished exports and backups should be kept only where they are actually needed, not duplicated across multiple accounts.
If you remember just one thing, make it this: in Google Drive, visibility does not equal ownership. Shared files are usually storage-free for the recipient, but your own copies and uploads are not. That one distinction explains most quota surprises, and it is the fastest way to keep a collaborative Drive setup under control.
