The release notes on your staging server need one fix before tomorrow's launch. Your developer sent over a hostname, a username, and a password, so you open Finder and look for a way in. There isn't one. Finder can't browse SFTP servers, and Terminal can, but only if you're comfortable typing commands. The easier way to access an SFTP server on a Mac without Terminal is a graphical client with two panes. Below, you'll gather your connection details, connect, open the right remote folder, update one file safely, and confirm the change landed.
What Can You Do with SFTP on a Mac?
SFTP lets you open the remote directory on a server from your Mac and work with its files over an encrypted connection. You can browse, download, upload, rename, and delete files, as long as your account has permission.
The name stands for SSH File Transfer Protocol. It runs over SSH, the same secure channel admins use to log in to servers remotely.
Don't confuse it with FTP or FTPS. Plain FTP sends files and passwords without encryption, and FTPS adds TLS encryption on top of FTP. SFTP is a separate protocol, so a server that offers one won't necessarily accept the others.
Keep in mind that SFTP needs a server on the other end, run by your host or admin. A desktop app only connects to it; it can't create one.
Can Finder Connect to an SFTP Server?
Finder's Connect to Server option works with SMB, NFS, WebDAV, and FTP shares, but SFTP isn't on Apple's list of supported servers.
Even Finder's FTP support is read-only. You can copy files from an FTP server, but Apple notes you may need another app to copy files back.
So when you need to connect to an SFTP server on a Mac, you have two real options. The first is the Terminal's built-in SFTP support, which works well if you're comfortable with the command line. The second is an app with SFTP support that shows remote folders in a window, much like Finder does. This guide takes the second route.
What Do You Need Before Connecting?
Before you open any app, get your SFTP connection settings from your host or server admin. You'll need five details, and you shouldn't guess any of them.
- Hostname or IP address. The server's address, such as
sftp.example.com. - Port. SFTP port 22 is the usual default, but some hosts use a different number.
- Username. The account name the server knows you by.
- Login method. Some servers use password authentication, while others require SSH key authentication. Ask which one your account uses.
- Starting folder and permissions. You need the remote path you'll work in, plus whether you can change files there.
The first time you connect, your app may show the server's host key fingerprint. Compare it with the one your admin sent, because a match confirms you've reached the right server. If you don't have one, ask before you accept it.
One last point: a folder on your Mac, like ~/Documents/, and a path on the server, like /staging/docs/, are two separate places. Mixing them up causes a lot of upload mistakes.
How to Connect to an SFTP Server with Commander One?
Any SFTP GUI for Mac can handle this job. This guide uses Commander One, a two-pane file manager for Mac that puts your local folders on one side and the server on the other. FTP and SFTP connections are part of its PRO features, and the developer's sftp client for mac page lists the protocols it supports.
Keep your five details handy, then follow these steps:
- Install Commander One and open it.
- Open Connections Manager. Click its toolbar icon, choose Window > Connections Manager, or press Command + F.
- Select FTP & SFTP, then pick SFTP as the connection method.
- Name the connection something you'll recognize later, such as "Staging docs."
- Enter the server address, port, username, and password. SFTP uses port 22 by default, so change it only if your host gave you another number.
- Add the remote path, such as
/staging/docs/, if you have one. Leave it blank to use the default folder your account logs into. - Click Connect, then open your local working folder in the other pane.
If you type your password in step 5, Commander One saves it to your Keychain. Leave it blank, and the app asks for it each time you connect. If your server only accepts SSH key authentication, check the app's current documentation for key support first.
Now pause before you touch anything. Read the full remote path in the server pane and scan the file names. This is the step most people skip, and it's the one that catches a wrong folder early.
How to Browse, Update, and Organize Remote Files Safely?
Once you can browse SFTP server files, safe changes come down to three habits: work on a copy, keep the original, and verify. Here's how that looks for the release notes file. Your folder names will differ, so treat these paths as examples.
- In the server pane, open
/staging/docs/and findrelease-notes.md. - Download the file into a local backup folder, such as
~/Documents/Release-Notes/backup/. Don't edit this copy; it's your way back. - Make a second copy in your working folder and edit that one. Commander One's Edit command (F4) opens text files in TextEdit by default, but any text editor works.
- Save your changes, then upload the edited file to the same remote folder. If the app asks whether to replace the existing file, confirm only after checking the destination path.
- Verify the change. Download the remote file again, or open it from the server pane, and look for your edit.
- If anything looks wrong, upload the backup copy to restore the original.
By the end, the file on the server has your new text, and the untouched original sits on your Mac for rollback.
Don't skip the check. A finished progress bar only tells you a transfer happened, not that it reached the right folder or replaced the right file.
Some apps let you edit files over SFTP without downloading them first. Behind the scenes, that often means a temporary local copy and an upload, so keep the backup habit anyway.
The same two-pane view helps you manage remote server files day to day. You can create folders, rename files, copy them between panes, or delete them, as long as your account has write permission. Seeing source and destination side by side makes a wrong-folder upload much easier to catch. On a production server, though, leave deletes and overwrites to whoever manages it.
Common SFTP Problems and What to Check
Most SFTP errors trace back to a wrong detail or a missing permission. Find your symptom below and start with the likely cause.
| Problem | Likely cause | What to check |
|---|---|---|
| Connection timed out or refused | Wrong host or port, network block, or server down | Hostname, port, network, and server status with your host |
| Authentication failed | Wrong login details or an unaccepted key | Your credentials and the login method your account uses |
| SFTP permission denied | Your account can't read or write in that folder | Folder permissions with your admin |
| You land in the wrong folder | Login folder differs from your target | Remote path field; full path in the pane |
| Upload finished, but the change isn't there | Wrong destination, failed transfer, or stale view | Transfer status, exact remote path, a freshly downloaded copy |
Whatever the error, don't turn off host key checks or loosen server permissions to make it go away. Those shortcuts hide the problem and open new security holes, so take the error to your admin instead.
GUI SFTP Client or Terminal: Which Is More Practical?
It depends on the job. A GUI client makes more sense when you want to see folders, make occasional edits, or compare local and remote files side by side. Terminal wins when you're scripting transfers or already work in the shell all day.
If you only need to know how to use SFTP on a Mac for the odd fix, the GUI route is quicker to learn. Commander One isn't the only option, either. Plenty of other SFTP clients exist for macOS, and the same backup-and-verify method works with any of them.
Keep the tool's role in perspective, though. A file client doesn't replace Git, automated deployments, proper backups, or server administration. It's for careful, hands-on changes to a few files.
A Repeatable Way to Manage SFTP Files on Mac
You don't need Terminal to manage SFTP files on a Mac. Get authorized access from your host, then connect with an SFTP client and open the right folder. Back up the original, change only the file you mean to change, and verify the result on the server. That last step takes a minute. It's also what lets you close the laptop knowing the fix is in place and the old version is safe.
