Transfers

The queue

Every copy (upload, download, server to server or within a server) becomes a job in the queue at the bottom of the window. Each job shows its progress, speed, and time remaining. Click the bar at the top of the queue to expand or collapse it.

When files already exist

If any of the items you’re copying already exist at the destination, BlazeSCP asks once for the whole transfer:

Choice	What happens
Replace	The destination file is overwritten
Skip	Existing files are left alone
Keep both	The new copy gets a free name, like photo 2.jpg
Resume	Partial files continue from where they stopped; complete ones are skipped
Replace if newer	Only when the source was modified more recently

Folders are always merged.

Pausing, resuming, cancelling

Use the buttons on each job. Paused jobs keep their progress; resuming continues mid-file where the protocol allows (SFTP, FTP, WebDAV and S3 downloads, local files). When some files fail, Retry copies just those again.

Dropped connections

If a connection drops mid-file, BlazeSCP retries automatically (twice, with a short wait) and continues from what already arrived. If the server is gone for longer, the job fails with the reason, and Retry picks it up again after you reconnect.

Quitting with transfers running

The queue is saved as it runs. If you quit (or BlazeSCP is updated) while transferring, the jobs come back paused and marked as interrupted the next time you open the app. Connect to the server and press resume: each file continues where it stopped, in the same destination file.

Server-side copies

When the source and destination are the same S3 account, WebDAV server or your own disk, BlazeSCP asks the server to copy the file itself. Nothing is downloaded and uploaded again, so it’s as fast as the server can manage.

Notifications

When a transfer finishes or fails while BlazeSCP isn’t the active window, you get a system notification. Turn this off in Settings → Notifications.