Thanks for your suggestion. I'll consider it.

Some notes:

• You do not need to change global TEMP variable. You can change the temporary location in WinSCP preferences:
  https://winscp.net/eng/docs/ui_pref_storage
  
  
• The documentation says:

  You can also duplicate a remote file to different server using local temporary copy.

  
  

I really like that I can do Ctrl+C/Ctrl+V from one "remote" tab (say, FTPS) to another "remote" tab (say SFTP) in WinSCP 6.5. Thanks!

However, recently, I ran into an issue while trying to copy 1TB of files (4GB each) using this feature. It turns out that WinSCP downloads (to a local temp folder) all files from the source first and then moves them to the destination server. The thing is – I only had ~0.5TB free on my C:\ disk.

My workaround was to modify the %TEMP% (and the %TMP%, just-in-case) environment variable, for the WinSCP to use another disk (the one with few TB available).

So, I'd like to suggest the following:

1. it would be great if WinSCP would just copy files one-by-one (maybe few uploads + downloads in parallel, for better performance), not "download all" + "upload all"
   
   
2. it would be great if WinSCP would have warned me about a lack of space on my local disk before starting that operation
   
   
3. it would be great if this article would document that WinSCP would download all files to the %TEMP% folder instead of saying "without downloading them to local machine".