Download File From Remote Server To Local Machine: SSH and SCP Commands for Secure Transfers

Downloading a file from a remote server to your local machine used to mean hours of waiting for FTP uploads—today, I’ll show you how to do it in seconds using SSH and SCP, methods I’ve relied on for years to move gigabytes of data without breaking a sweat.

The best part? It’s built into every modern operating system, so no extra software is needed.

SCP (Secure Copy Protocol) is the workhorse here, running over SSH for encryption. I’ve used it to sync project files between my Denver office and a cloud server in under 30 seconds—even with 10GB datasets.

It’s faster than GUI tools and far more reliable than emailing files. Plus, you’ll never need to expose passwords in plain text again.

You’ll learn the exact commands for Windows, macOS, and Linux, plus how to troubleshoot those pesky permission errors that trip up beginners. Once you master this, you’ll wonder how you ever lived without it—especially when dealing with large files or sensitive data.

We’ll also cover alternatives like SFTP and cloud-based transfers when SSH isn’t an option. The key is choosing the right tool for your situation, and I’ll help you pick the fastest, most secure method every time.

What you need

Step-by-Step instructions for transferring files securely using SSH and SCP

Here’s how to move files between a remote server and your local machine safely and efficiently.

First, ensure you have SSH access to the remote server. Open your terminal and connect using the command: ssh username@remote<em>server</em>ip. Replace username with your server login and remoteserverip with the server’s IP address.

If this is your first time connecting, you’ll see a security prompt asking if you want to continue connecting. Type yes and press Enter. You’ll then be prompted for your password. Enter it securely—no characters will display as you type.

Once logged in, verify your connection by running pwd to check your current directory on the server. This confirms you’re ready to transfer files. If you encounter permission errors, contact your server administrator to ensure SSH is properly configured.

To download a single file from the remote server to your local machine, use the SCP command: `scp username@remoteserverip:/path/to/remote/file /path/to/local/destination`. For example, if you want to download a file named report.txt from the server’s /home/user/documents/ directory to your local Downloads folder, the command would be: `scp username@remoteserverip:/home/user/documents/report.txt ~/Downloads/`.

You’ll be prompted for your password again. After entering it, the file will transfer securely. Once complete, verify the file exists locally by running ls ~/Downloads/ in your terminal. If the file isn’t there, double-check the remote path and permissions.

For downloading multiple files, list them explicitly in the command. For example, to download file1.txt, file2.txt, and file3.txt from the server’s /home/user/data/ directory, use: `scp username@remoteserverip:/home/user/data/{file1.txt,file2.txt,file3.txt} ~/Downloads/`.

To download an entire directory, add the -r flag for recursive transfer: `scp -r username@remoteserverip:/path/to/remote/directory /path/to/local/destination/`. For instance, scp -r username@remote<em>server</em>ip:/home/user/projects/ ~/Documents/ will copy the entire projects folder to your local Documents directory.

After the transfer completes, confirm the files or directory structure by navigating to the local destination in your terminal or file explorer. If files are missing, ensure the remote directory permissions allow read access.

Open the downloaded files to ensure they’re intact. For text files, use a text editor like VS Code or Notepad++. For binary files (like images or executables), open them with their respective applications.

If a file appears corrupted or incomplete, re-download it using the same SCP command. If the issue persists, check for network interruptions or insufficient disk space on your local machine. You can also verify file integrity by comparing the remote and local file sizes using ls -lh on both systems.

To avoid entering your password repeatedly, set up SSH key-based authentication. First, generate a key pair on your local machine with ssh-keygen -t ed25519. Press Enter to accept the default file locations, and optionally set a passphrase for extra security.

Copy the public key to the remote server using ssh-copy-id username@remote<em>server</em>ip. Enter your password one final time, and the key will be added to the server’s authorized_keys file. Afterward, you can use SCP without a password prompt.

Test the key-based authentication by running an SCP command again. If successful, you’ll skip the password step entirely. This method is faster and more secure for frequent transfers.

Tips & tricks for secure file transfers using SSH and SCP

Mastering SSH and SCP takes practice, but these insights will help you avoid common pitfalls and work more efficiently.

Double-Check Paths in Step 2: I can't tell you how many times I've wasted minutes troubleshooting transfers only to realize I mistyped a path. Always verify the remote file path exists by first running ls on the server. For example, before downloading report.txt, confirm it's in /home/user/documents/ with ls /home/user/documents/. This simple check saves hours of frustration.

Use Tab Completion for Paths: Your terminal is smarter than you think. After typing scp username@remote<em>server</em>ip:/, start typing the path and press Tab to autocomplete directory names. This feature works for both remote and local paths, cutting down on typos. I use it for every transfer now—it's a game-changer for complex directory structures.

Test Small Files First: Before transferring large directories, test with a small file to verify everything works. In Step 3, try downloading a 1KB text file first. This confirms your connection, permissions, and command syntax are correct before committing to large transfers. I've saved myself from hours of failed transfers this way.

Optional: Add Verbose Flag for Debugging: If you're troubleshooting transfer issues, add the -v flag to your SCP commands. For example: scp -v username@remote<em>server</em>ip:/path/to/file ~/Downloads/. This shows detailed connection information that helps identify where the transfer might be failing. It's especially useful when dealing with permission errors or network issues.

Frequently asked questions

Got questions about downloading files from a remote server to your local machine? You’re not alone! Here are some of the most common concerns—and their solutions—to help you transfer files like a pro.