Google Photos is not stored inside Google Drive, even though both live under the same Google account. Photos has its own library, Drive is a separate file store, and the two only overlap in storage usage for many personal accounts. In this article, I’m breaking down what that means in practice, how Google’s current storage rules work, why older guides still cause confusion, and how to move images without creating duplicates or losing track of them.
What you need to know before treating Google Photos and Drive as the same place
- Google Photos and Google Drive are separate services, not one shared folder tree.
- For a personal Google Account, the free 15 GB is shared across Drive, Gmail, and Photos.
- Deleting or editing a file in one service does not automatically change the other.
- If you copy a photo from Drive into Photos, you create a separate copy that uses storage.
- The old automatic sync between Drive and Photos is gone, so legacy folders can be misleading.
- Work and school accounts can behave differently, so transfer steps are not always identical.
Google Photos is its own library, not a Drive folder
The cleanest way to think about it is this: Drive stores files, while Photos stores a visual library. Drive is organised around folders, filenames, and manual file management; Photos is organised around dates, albums, search, sharing, and backups. That difference matters because a photo in Google Photos is not sitting inside a normal Drive folder structure that updates in real time.
For a standard personal Google Account in the UK, the free allowance is 15 GB shared across Google Drive, Gmail, and Google Photos. So the services are separate, but the storage pool often is not. That is why a full inbox or a large Drive archive can reduce the space available for new photo backups, even though Photos is not “stored in Drive”.
In practice, separate service, shared allowance is the rule to remember. That separation is the reason storage feels connected without being mirrored, which leads straight into how Google Photos actually uses space.
How Google Photos uses storage in practice
Google Photos backs up images and videos to your Google Account storage, and the backup quality determines how the files are handled. The current options are Storage saver, Original quality, and Express quality. Original quality keeps the same resolution you shot, while the other modes compress files to save space.
| Backup quality | What happens to the file | Storage impact | Best use case |
|---|---|---|---|
| Original quality | The file stays at the same resolution and quality. | Counts toward your Google Account storage. | Archiving masters, large prints, and footage you may edit later. |
| Storage saver | Photos above 16 MP are resized to 16 MP; videos above 1080p are resized to 1080p. | Counts toward your Google Account storage. | Everyday backup where file size matters more than preserving every pixel. |
| Express quality | Photos above 3 MP are resized to 3 MP; videos above 480p are resized to 480p. | Counts toward your Google Account storage. | Saving mobile data and keeping a lighter backup. |
There are two practical details people often miss. First, some older backups made under earlier rules may not count the same way as newer uploads. Second, if your storage fills up, new photos and videos stop backing up until you free space or buy more storage. That is why I always tell people to treat Photos as an active part of storage management, not as a passive vault.
The rules are simple once you know them, but the old Drive connection still trips people up, so I’ll separate history from current behaviour next.
Why Drive and Photos still feel connected
A lot of confusion comes from the older Google Photos and Google Drive integration. Google used to surface photos between the two services more automatically, and some legacy folders still exist in Drive. Those remnants make it easy to assume the systems are still linked in the same way, but they are not.
Today, new photos and videos in Drive do not automatically appear in Google Photos, and new items in Photos do not automatically populate a Drive folder. Deleting something in Drive does not remove it from Photos, and deleting it in Photos does not remove it from Drive. The two services may share storage on a personal account, but they do not act like a live mirror.
That is the part people usually get wrong: a copied file is not a synced file. If you see an old “Google Photos” folder in Drive, think of it as a static legacy copy, not an always-updated pipeline. Once you see that history, the transfer process makes much more sense.
How to move photos between them without duplication
If you want a photo to live in Google Photos, the cleanest path is to add it there deliberately rather than expecting Drive to handle it for you. On a computer, Google Photos lets you add items from Drive manually, which is useful when you want the image in both places for different reasons.
- To put a Drive image into Photos, open Google Photos and use the add-from-Drive option.
- To keep a file in Drive, upload it directly into the folder structure you want.
- To move rather than copy, download from the source service and upload to the destination service.
- If you use a work or school account, expect more manual steps, because Google flags that setup as different.
There is also a subtle but important rule: once you create a copy, the two versions are independent. Editing one does not edit the other. Deleting one does not delete the other. That is useful when you want a backup, but it becomes a problem if you forget which copy is the one you actually maintain.
For media creators, this distinction matters even more. If you are storing original camera files in Drive and also backing up phone photos into Photos, you need a clear purpose for each copy. Otherwise, you end up burning through the same allowance twice without getting a better workflow out of it. The real risk now is not moving a photo the wrong way; it is accidentally duplicating it and eating into shared space.
The mistakes that waste space fastest
The most expensive storage mistakes are usually simple ones, and they show up when people assume Google services behave like one big synced folder. I see the same patterns repeatedly:
- Assuming Drive and Photos are mirrors and deleting files in the wrong place.
- Uploading the same photo in both services without a clear reason.
- Ignoring Gmail, even though mail and attachments share the same allowance on personal accounts.
- Using Original quality for every upload when Storage saver would be enough for daily backup.
- Forgetting that videos usually consume space much faster than still images.
The last point is the one that catches people off guard. A photo library can look modest for months, then one burst of 4K video, screen recordings, or short clips suddenly shifts the storage picture. If you care about preserving original camera files, keep them in Original quality where it matters. If you mainly want safe, searchable backups of everyday shots, Storage saver is often the smarter compromise.
Once the main mistakes are clear, the best strategy is to decide in advance which service should own which kind of file.
The rule I use when organising cloud photos
I use a simple rule: Google Photos is for the searchable visual archive, and Google Drive is for structured file storage. That means Photos gets the memories, the timeline, and the family albums; Drive gets project folders, source files, deliverables, and anything that needs a filename-first workflow.
If I need both, I make that choice deliberately. I copy the file on purpose, label it mentally by function, and avoid assuming the two services will stay in step on their own. That habit saves more storage and confusion than any clever workaround.
If your allowance is tight, check the whole account, not just Photos. Gmail attachments and large Drive files can eat into the same pool and make it look as if Google Photos is the culprit when it is really only part of the problem. Keep the library in Photos, keep the archives in Drive, and treat every duplicate as an intentional decision rather than a hidden sync side effect.
