0% scroll to read · click to mark done
← all posts ◎ Quick Tips · #01

rsync vs scp — Which One and When

Mar 25, 2026· 3 min read· #rsync#scp#linux
PrerequisitesBasic Linux CLISSH access

Both copy files over SSH. They are not interchangeable, and reaching for the wrong one wastes time — or bandwidth — at exactly the wrong moment.

The one-line rule

scp for a quick one-shot copy of a file or two. rsync for anything large, repeated, resumable, or that might get interrupted.

Where scp wins

eknatha@prod ~
$ scp config.yaml user@host:/etc/app/

Clean, no flags to remember, installed everywhere. For "grab this one file," scp is less to type and less to think about.

Where rsync wins — and it's most places

eknatha@prod ~
$ rsync -avz --partial --progress src/ user@host:/dest/

That last point is the killer feature: sync a 5GB directory, change one file, re-run, and rsync moves kilobytes. scp would re-copy all 5GB.

The trap

scp on a flaky connection that dies at 90% leaves you with nothing — you start over. rsync --partial picks up where it stopped. On any transfer that matters, that resumability alone justifies rsync.

Quick and small: scp. Large, repeated, or unreliable: rsync. When unsure, rsync.
// written from production experience — by Eknatha