Gravity Forms to Google Drive – GDrive Uploader
Seamlessly upload files to Google Drive from Gravity Forms submissions
Uploading files through a Gravity Forms form is convenient — and it quietly creates a second copy of every sensitive document your visitors hand over. That is why the question we hear most often about our Gravity Forms to Google Drive – GDrive Uploader plugin is not “how do I connect it?” but “how do I keep it secure?”
So, how do you secure Gravity Forms file uploads to Google Drive? The short answer: you control three things — what is stored on your web server, who can open the folder inside Drive, and what happens to the file after it has been delivered. Here is how to get all three right.
Table of Contents
Why Are Gravity Forms File Uploads a Security Risk?
By design, Gravity Forms writes every uploaded file to your WordPress host before anything else can happen to it. The plugin cannot bypass that step, because the upload is handled by Gravity Forms itself — our plugin takes over from the moment the file exists on disk. That first stop is where most of the risk lives: the file sits in your uploads directory (Gravity Forms keeps its own subfolder, typically wp-content/uploads/gravity_forms/), and it stays there until something deletes it.
Three problems follow from that. First, anything under wp-content/uploads/ is often reachable by direct URL, so a leaked or guessed filename can expose a document without any login. Second, the same folder is captured by every backup you take, which means client documents end up copied to storage you may not think of as sensitive. Third, retention rules such as GDPR or CCPA data minimization expect you to delete personal files when they are no longer needed — a folder nobody revisits is the opposite of that. The sections below show how to secure Gravity Forms file uploads at each of those points.

Where Do the Files Go, and Who Can Actually Open Them?
The GDrive Uploader sends each submission to a folder in the Google Drive account you connect when you set up the feed. Once a file has landed there, access is governed entirely by Google Drive sharing permissions — not by your WordPress user roles, and not by the fact that the file arrived through a form. A folder shared with “anyone with the link” is public to the internet, no matter how private your WordPress site is.
With a Pro or Developer license, you can send uploads to a custom parent folder instead of the default “Gravity Forms Uploaded Files” folder (see the plugin’s features), and you can change it later without touching the form. Decide the destination deliberately: a folder only you and your team can see, inside an account you control.
How Do You Lock Down the Google Drive Folder?

To secure Gravity Forms file uploads inside Drive, work through this list once per form, and revisit it when staff change:
- Set the folder to Restricted, then share it with named people or a Workspace group — never “anyone with the link”.
- Keep the Drive account behind two-factor authentication, and review its connected third-party apps periodically.
- If you are on Google Workspace, host uploads in a Shared Drive so files stay with the organization when an employee leaves.
- Use a dedicated account or Shared Drive for form uploads rather than an employee’s personal Drive.
- Check Drive activity for unexpected shares or downloads, and turn on alerts for external sharing if you have Workspace.
Should You Keep a Copy of the File on Your WordPress Server?
Usually not — deleting the local copy is one of the easiest ways to secure Gravity Forms file uploads. The plugin includes a “Do not store file in WordPress storage” setting, which deletes the local copy once the upload to Google Drive has succeeded. That gives you the best of both worlds: Gravity Forms still receives the upload the way it must, but your web server does not keep an archive of client documents.
Two caveats. The entry in Gravity Forms still records the file metadata — the name, type and size — so the submission history stays intact even after the bytes are gone. And if your host’s disk is the only fast, always-available copy you trust, confirm that your Drive folder is inside a backup or retention policy before you enable deletion. Test the feed with one submission, confirm the file appears in Drive, then check that the local file is gone.
How Do You Keep Submitters’ Files Separate From Each Other?

If you want to secure Gravity Forms file uploads from several clients, avoid a single shared folder: the moment you give a colleague or a client access to it, they can see everyone else’s documents too. With the Pro or Developer license you can map a form field — a client name, a company or an email address — to the folder name, so every submission is filed in its own folder automatically. The submitter never touches Drive permissions; the plugin creates the structure.
That separation also makes deletion manageable. When a project ends, you delete one folder and you have honored the retention promise for that client. If you want to go further, organizing Google Drive folders for Gravity Forms uploads covers naming rules and structure, and automating the upload itself covers the feed setup step by step.
What Else Should You Check to Secure Gravity Forms File Uploads?
- Restrict the allowed file extensions and maximum file size on the Gravity Forms File Upload field, so executables and scripts never arrive.
- Serve the form over HTTPS and keep WordPress, Gravity Forms and the uploader plugin updated.
- If you do keep local copies, block direct web access to the uploads folder at the server level and test a file URL to confirm it is denied.
- Do not attach sensitive uploads to email notifications; send a link or a note instead.
- Assume nothing is scanned for you — if the form is open to the public, add malware scanning on the receiving Drive storage.
- Write down the retention rule (for example, delete client documents 12 months after the project closes) and put a recurring reminder in the calendar.
The Bottom Line
You secure Gravity Forms file uploads to Google Drive by shrinking the time files spend on your web server, locking the destination folder down to named people, and giving each submitter a folder of their own. Gravity Forms to Google Drive – GDrive Uploader covers the middle of that workflow: connect your Google account, choose a parent folder or let a form field create one per submitter (both Pro and Developer features), and enable “Do not store file in WordPress storage” so your host stops holding copies it does not need.
You can review the full feature list and pricing on the GDrive Uploader product page, and browse our other WordPress automation tools at ristrettoapps.com.
Is it safe to upload files from Gravity Forms to Google Drive?
Yes, when the destination folder is set to Restricted and you remove the local copy. Files travel from your site to your own Google Drive account over HTTPS through Google’s API, so the main risk is not the transfer – it is who you have shared the folder with and how long copies sit on your web server.
Where are Gravity Forms file uploads stored before they reach Google Drive?
They are stored in your WordPress uploads folder first, in a Gravity Forms subfolder such as wp-content/uploads/gravity_forms/. The plugin cannot bypass that step because Gravity Forms handles the initial upload. Enable the Do not store file in WordPress storage setting and the local copy is deleted once the upload to Drive succeeds.
Can each person who submits the form get their own Google Drive folder?
Yes. With the Pro or Developer license you can map any form field – a name, company or client ID – to the destination folder name, so every submission is filed in its own folder instead of one shared folder that exposes everybody’s documents.
How do I stop uploaded files from being publicly accessible?
Keep the Google Drive folder Restricted or inside a Workspace Shared Drive with named members, run the site over HTTPS, limit the allowed file types and sizes on the upload field, and never share a file link publicly. If you keep local copies, block direct web access to the uploads directory at the server level and verify that a file URL is refused.
