Can You Password Protect a Google Drive Folder?

Google Drive's standard folder-sharing settings do not offer a standalone folder password. A LOCK.PUB password link can control the handoff of the folder URL, but it does not encrypt the folder or replace its Google access rules.

This guide is for ongoing folder collaboration. To encrypt a single document or prepare a password-protected download, see the individual Google Drive file guide.

Which controls protect a shared folder?

A shared project folder needs an access plan: who should see its contents, who may change them and when that access should end. Set those rules in Drive before adding an optional password link.

Think of the two controls separately: the LOCK.PUB password opens the handoff link; Google decides whether the recipient can enter the destination. Changing the first does not change the second.

Decide what belongs in the shared folder

Before inviting collaborators, separate the documents they need from private working material. For example, a client-delivery folder might contain approved drafts and final exports, while internal estimates and unrelated customer files belong elsewhere.

For the last case, a secure request link serves a different purpose from giving someone a shared folder to browse.

How do folder permissions affect the files inside?

Folder permissions normally carry into their contents. Review parent-folder access before relying on a setting on an individual file. Open Share, inspect the people and groups, and choose the appropriate role. Keep General access restricted when only invited people should enter. Google's sharing instructions cover these controls.

For content that needs a narrower audience, Google supports limited-access folders. Those can restrict inherited access, although a person may still see a grayed-out folder name in some situations. A folder name should therefore not contain confidential details. See Google's limited-access documentation for who can manage these settings and the exceptions.

How can I add a password to the folder handoff?

Once you have checked Drive access, copy the folder URL into the Google Drive password-link tool. Set a unique password and a non-sensitive label, then send the new LOCK.PUB link. Send its password separately.

Do not switch the folder to public link access merely to use LOCK.PUB. A recipient who lacks Drive permission will still need that permission after completing the password step.

Anyone who already has the original Drive URL can bypass LOCK.PUB and use it under Google's access rules. The password link is useful for keeping the raw destination out of the initial message, but an authorized recipient can learn and retain that destination.

How do I end a collaborator's access?

End access in Drive itself. Remove the relevant permission and review other access paths, such as a group or parent folder. Work and school accounts may offer Drive access expiration; Google's current instructions limit folder expiration to Viewer roles. Check the available sharing controls.

A Pro expiration or access limit on a LOCK.PUB link applies only to that link. It does not remove Drive access, and changing its password does not invalidate a Drive URL someone already saved.

For a project handoff, record who received access, which folder was shared and the planned review date. At completion, check the original destination as well as the protected link. Neither revocation nor expiration can recall previously downloaded copies.

What should I verify before sending the folder link?

Ask a designated collaborator to confirm they can open the intended folder and only the material meant for them. An owner account is not a reliable substitute for that check because it has broader access. Use a neutral sample file if you need to rehearse the workflow first.

If the task changes from collaboration to sending a final copy, follow the file protection guide. If the folder permissions are ready and you want a separate password step, create a protected Drive link.