Can you duplicate a folder in Google Drive?
The direct answer, why Drive has no folder copy button, and exactly what gets left behind when you duplicate: permissions, comments, version history, and shortcuts.
Aymeric Zhuo10 min read
On this page
Not directly, and not from the right-click menu. Google Drive gives you Make a copy on a file, and the option simply does not appear when you right-click a folder. You can duplicate a folder's contents, and there are several reliable ways to do it, but every one of them is a workaround rather than a built-in feature.
That much takes ten seconds to discover for yourself. The more useful question, and the one this page is about, is what actually happens to your data when you duplicate a folder by any of these methods, because the answer involves a surprising number of things that quietly do not come along. If you already know you want to do it and just need the steps, the methods that work compares the four approaches.
What we'll cover
Why there is no folder copy button
The absence looks like an oversight, and it comes up often enough in Google's own product forums that it clearly is not one. The most plausible explanation sits in how Drive models storage.
Copying a file is a contained operation with a predictable cost: one file in, one file out, storage doubled for that item. Copying a folder is an operation with no upper bound. The folder you right-clicked might hold four documents or it might hold a hundred thousand files across nine levels of subfolders, including items shared with you by other people, shortcuts pointing to things you cannot access, and files owned by accounts outside your organization.
A single menu click that might take a second or might take nine hours, and might quietly multiply your storage usage, is an unpleasant thing to ship. The other methods all exist because they make that cost visible: you either wait while your desktop client syncs, or you run a script that reports progress, or you build an automation that handles failures deliberately.
What a folder actually is in Drive
This is worth understanding, because it explains most of the surprises that follow.
A Drive folder is not a container in the way a folder on your hard disk is. It is a label, and files record which folders they belong to. This is why a file could historically live in two folders at once, why moving a file between folders is instant regardless of size, and why "the folder" has no meaningful content of its own to copy.
So duplicating a folder is really an instruction to create a new set of labels and then create a copy of every file carrying the old label, reattaching each copy to the new one. Every method below does exactly that, whatever interface it wears. Understanding this makes it obvious why the operation is recursive, why it can be slow, and why the copies are new files with their own identities rather than the same files in a second place.
What survives a duplication and what does not
This is the part worth reading carefully, because the losses are silent. Nothing warns you.
File contents survive. The document, spreadsheet, image, or PDF arrives intact. This is the part everyone assumes and it does hold.
Folder structure survives, if your method is recursive. Nested subfolders are recreated when you use a desktop client, a script, or an automation. Selecting files in the browser and copying them does not recreate structure, which is the single most common way people end up with a flat pile of files.
Sharing permissions do not survive. The copy is a new file, owned by whoever made the copy, shared with nobody. If the original folder was shared with twelve colleagues, the duplicate is shared with none of them until you set that up again. For a team folder, this is usually the thing that causes the phone call.
Ownership changes. You own the copies, even of files someone else owned. On a personal account this affects your storage quota: duplicating a 40GB folder consumes another 40GB against your allowance.
Comments and suggestions do not survive by default. Copying a Google Doc through the interface offers a checkbox to bring comments and suggestions across. Scripted and bulk copies generally do not, so a document full of review discussion arrives clean.
Version history never survives. The copy begins its life with a single version. Every previous revision, and the record of who changed what and when, stays with the original. Where a folder is being duplicated for audit or compliance reasons, this is the detail that matters most and it is rarely noticed until someone goes looking for a revision that no longer exists.
Shortcuts survive as shortcuts. A shortcut in the original folder is copied as a shortcut, still pointing at the same original target rather than at any copy of it. Duplicate a folder full of shortcuts and you have duplicated the signposts while leaving the destinations exactly where they were.
Timestamps change. Every copy is created now. If you sort by modified date, or if anything downstream depends on when a file was last touched, that information is gone.
The files Drive will refuse to copy
Some items will not duplicate at all, and a copy operation that encounters them either skips them silently or stops, depending on the method.
View-only files where the owner disabled copying. When someone shares a file with "viewers and commenters cannot download, print, or copy" enabled, that restriction is enforced. The file cannot be duplicated by you, by a script running as you, or by any tool acting with your credentials.
Files you can see but do not own, in some configurations. Organizational sharing policies can prevent copying content outside a domain, which typically surfaces as a permission error partway through a large copy.
Google Forms with response destinations. A copied form is a new form. Its link to the original response spreadsheet does not come with it, so a form that looked duplicated may be collecting nothing.
Files above the size limit for their type. Google's own formats have conversion limits, and a spreadsheet near the cell ceiling can fail to copy cleanly.
The practical consequence is that a folder copy which reports success is not proof that everything arrived. On anything important, comparing file counts between source and destination is a worthwhile ten seconds.
Shared drives behave differently
If your folder lives in a shared drive rather than My Drive, several of the rules above change.
Files in a shared drive are owned by the drive itself rather than by a person, so copying within the same shared drive keeps that ownership and does not touch your personal quota. Copying from a shared drive into My Drive makes you the owner and does consume your allowance.
Permissions in a shared drive are inherited from the drive, which means a copy placed in the same shared drive is immediately visible to everyone with access, without you configuring anything. This is the opposite of the My Drive behaviour above, and it catches people out in both directions: duplicating a folder in a shared drive can expose a draft you assumed was private.
Shared drives also enforce their own limits on item counts and nesting depth, and a bulk duplication is exactly the kind of operation that finds those ceilings.
So what can you actually do
Four approaches work, and they suit different situations.
Google Drive for desktop lets you copy and paste a folder in Finder or File Explorer, and the sync client recreates everything in the cloud. It handles nesting properly and needs no technical knowledge. It is slow for large folders and requires the files to download locally first.
Selecting files in the browser and using Make a copy works for a single folder with no subfolders. It is quick and it flattens anything nested, so it suits a simple case and misleads in a complicated one.
Google Apps Script can walk a folder recursively and copy as it goes, giving you control over naming, which file types to include, and what to do about failures. It needs someone comfortable writing a little JavaScript, and it runs against execution time limits on large jobs.
An automation handles it on a trigger, which is what you want when the duplication is not a one-off. Template folders per client or per project, created when a deal closes or a form is submitted, with a consistent naming convention and permissions applied automatically.
That last case is the one worth building properly, because it recurs. On CodeWords you describe what should happen in plain language and Cody, the automation builder, builds it, connects it to Drive and whatever triggers it, and deploys it. Automations connect to more than 3,000 integrations. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.
The methods that work walks through all four in detail. If your concern is specifically that subfolders and contents arrive intact, copying an entire folder covers the completeness problem. For recurring duplication across a team, see duplicating folders at scale.
Frequently asked questions
Is there any way to get a one-click folder copy?
Not within Drive itself. Browser extensions and third-party add-ons offer buttons that look like one, and each is running one of the methods above on your behalf with your Drive permissions. That is worth knowing before granting access to a folder tree that contains anything sensitive.
Does duplicating a folder use twice the storage?
In My Drive, yes: the copies are new files owned by you and counted against your quota. Within a single shared drive, the copies count against that drive's allowance rather than yours. This surprises people duplicating large media folders, where a routine copy can push an account over its limit.
Can I duplicate a folder someone shared with me?
Usually, provided the owner has not disabled copying and your organization's policy permits it. The duplicate becomes yours, in your Drive, counting against your storage, and shared with nobody. The original stays exactly as it was.
Will the copy stay in sync with the original?
No. The duplicate is an independent set of files from the moment it is created, and later changes to either side do not propagate. If you want two locations showing the same live content, a shortcut does that, and an automation that mirrors changes can do it across accounts or drives.
Why did my copy end up with everything in one folder?
That is the signature of copying by selecting files in the browser, which duplicates the files you selected without recreating the folders they sat in. Use the desktop client, a script, or an automation for anything with subfolders.
Do I lose comments when I duplicate?
Through the Drive interface you are offered a checkbox to carry comments and suggestions across on a Google file. Scripted and bulk copies usually do not include them. If review history matters, check the specific method rather than assuming.
Does the copy count as a backup?
Only in a limited sense. It protects against someone editing or deleting the original, since the duplicate is independent from the moment it is made. It does not protect against anything affecting the account or the drive itself, because both copies live in the same place under the same credentials. A genuine backup means a copy somewhere Google is not, which in practice means exporting through the desktop client and archiving it elsewhere.
Why does the copy show me as the author of everything?
Because you created those files. Drive records the account that made each copy as its owner and creator, and the original authorship stays with the originals. For folders being duplicated as a record of who produced what, this is a significant limitation and one of the stronger arguments for keeping the originals rather than working from copies.