Configuration

This page shows where to find Direct Cloud Upload and how to enable it for each cloud service. For what the feature does and how it works, see the Introduction.

Before you start

• An active Pro license — this is the only requirement that unlocks Direct Cloud Upload. Without a valid license the switch stays locked.
• A cloud service connected and set as the form's active connection. Direct Cloud Upload works with every cloud service Cloud Storage Manager supports — Google Drive, Dropbox, Amazon S3, Cloudflare R2, and Microsoft OneDrive. Set one up from the Integrations guides.

Where to find it

Direct Cloud Upload is a per-form setting. You'll find it in each form's own Cloud Storage Manager settings:

Fluent Forms → your form → Settings → Cloud Storage Manager → Other Settings → Direct Cloud Upload

Enable Direct Cloud Upload

Open the form's settings

Edit the form in Fluent Forms, open Settings, and select Cloud Storage Manager.

Go to Other Settings

Open the Other Settings tab. Direct Cloud Upload is the first option at the top.

Turn it on

Switch Direct Cloud Upload to Enabled. The switch becomes available once you have an active Pro license and a connected cloud service. A consent window then opens explaining exactly what will happen for your connected service.

Conversational forms are the exception: Direct Cloud Upload isn't supported there, so the switch stays disabled and those forms always use the standard upload route.

Review and confirm

Read the consent window and confirm. Direct Cloud Upload is turned on and saved for this form right away — there's no separate Save step for it.

TIP

Direct Cloud Upload is set per form. Enable it on the forms that collect large files, and leave everyday forms on the standard route.

Enable for each cloud service

The flow is the same for every service: set the form's active connection to the service you want, switch Direct Cloud Upload on, then confirm in the consent window that appears.

The consent window's message depends on the service:

• Google Drive, Dropbox, and Microsoft OneDrive show a short confirmation — no setup on the cloud side is needed.
• Amazon S3 and Cloudflare R2 show the exact CORS rule that will be added to your bucket, because the browser needs the bucket's permission to upload to it directly.

Google Drive

The consent window confirms files will upload straight from the browser to Google Drive — no cloud-side setup is needed. It summarizes what changes:

• Upload sessions are authorized on your server — the browser never sees your login credentials.
• Large files land in the destination folder without being staged on your server first.

Confirm with Enable.

Dropbox

The consent window confirms files will upload straight from the browser to Dropbox — no cloud-side setup is needed. It summarizes what changes:

• Upload sessions are authorized on your server — the browser never sees your login credentials.
• Large files land in the destination folder without being staged on your server first.

Confirm with Enable.

Amazon S3

The consent window shows the CORS rule that will be added to your bucket so the browser can upload to it. It lists what happens when you confirm:

• Your bucket's current CORS configuration is read.
• The new rule is added — your existing rules are kept untouched.
• The merged configuration is written back to the bucket.

If your credentials can't write the rule, the plugin shows the permissions needed so you can add it manually in the AWS S3 console. Confirm with Enable & configure CORS.

Cloudflare R2

The consent window shows the CORS rule that will be added to your R2 bucket so the browser can upload to it. It lists what happens when you confirm:

• Your bucket's current CORS configuration is read.
• The new rule is added — your existing rules are kept untouched.
• The merged configuration is written back to the bucket.

If your token can't write the rule, the plugin shows the permissions needed so you can add it manually in the Cloudflare R2 dashboard. Confirm with Enable & configure CORS.

Microsoft OneDrive

The consent window confirms files will upload straight from the browser to OneDrive — no cloud-side setup is needed. It summarizes what changes:

• Upload sessions are authorized on your server — the browser never sees your login credentials.
• Large files land in the destination folder without being staged on your server first.

Confirm with Enable.

Good to know

• Email file attachments aren't available. Attaching an uploaded file to a notification email requires a copy of that file on your server. With Direct Cloud Upload the file goes straight to the cloud, so notification emails include a link to the file instead of the file itself. Use the standard upload route for forms that must email the uploaded file as an attachment.
• Your file settings still apply. File visibility (public or private), the file name convention, and folder placement all behave exactly as they do for standard uploads.
• Private files still work. Amazon S3 and Cloudflare R2 serve private files through temporary presigned URLs; Google Drive, Dropbox, and OneDrive require login — the same as the standard route.
• Large files are handled for you. Big uploads are split into chunks and sent one part at a time automatically.
• Works with every connection. Direct Cloud Upload is supported on all five cloud services, so you can use it whichever one a form is connected to.
• Turning it off is simple too. Switching Direct Cloud Upload off opens a short confirmation. For Amazon S3 and Cloudflare R2 you can optionally tick Also remove our CORS rule from the bucket to clean up — rules from other apps sharing the bucket are left untouched. Existing files and already-queued uploads are unaffected.

WARNING

If you turn off your Pro license or it expires, the switch locks and affected forms return to the standard upload route.