--streaming-upload-cutoff versus --drive-upload-cutoff

What is the problem you are having with rclone?

No technical problem, just a lack of understanding the difference between these two flags:

  • --drive-upload-cutoff
  • --streaming-upload-cutoff

Do these serve the same purpose?

Run the command 'rclone version' and share the full output of the command.

rclone v1.67.0-beta.7957.625622bcb.fix-onedrive-metadata
- os/version: Microsoft Windows 11 Pro 23H2 (64 bit)
- os/kernel: 10.0.22631.3527 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.22.3
- go/linking: static
- go/tags: cmount

Which cloud storage system are you using? (eg Google Drive)

Google Drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

N/A

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

N/A

A log from the command that you were trying to run with the -vv flag

N/A

That's a specific flag for the Drive backend:

--drive-upload-cutoff
Cutoff for switching to chunked upload.

Properties:

Config: upload_cutoff
Env Var: RCLONE_DRIVE_UPLOAD_CUTOFF
Type: SizeSuffix
Default: 8Mi

So any file bigger than 8Mi by default changes from a single upload to uploading in chunks. The debug logs should the chunked uploads.

Streaming cutoff is for unknown files sizes and a global flag so it's somewhat dependent on the remote.

--streaming-upload-cutoff SizeSuffix          Cutoff for switching to chunked upload if file size is unknown, upload starts after reaching cutoff or when file ends (default 100Ki)

You'd see that also in the debug logs. I think some remotes that can't give a file size would use that but I can't think of any offhand as I only use a few remotes myself.