🍴 Forked & Modernized from Natizyskunk/vscode-sftp, originally based on the abandoned liximomo/vscode-sftp. Updated dependencies, new features, and full compatibility with the latest VS Code APIs.

🎉 What's New in v3.4.0 — Rename, Move & Safer Deletes

Manage remote files without switching to FileZilla or an SSH terminal.

✏️ Rename & Move on the Server

SFTP: Rename Remote renames or moves a file or folder on the server — a single request, no re-upload, however large the folder. Include a / in the new name to move it somewhere else.

🖱️ Drag to Move

Set "remoteExplorer": { "enableDragAndDrop": true } and drag items around the Remote Explorer to reorganize the server. Also a server-side rename, so nothing is transferred.

🔁 Local Renames Follow Along

"watcher": { "autoRename": true } turns a rename inside VS Code into a server-side rename instead of the old delete-and-re-upload, which used to leave the old folder orphaned.

🗑️ Deletes You Can Undo

"backup": { "onDelete": true } saves a copy of everything a delete removes, restorable from the Backups panel. Deleting a folder backs up its contents first, and the delete is aborted if any copy fails.

SFTP: Delete Remote also moved out of hiding — it's now in the local file explorer context menu and the Command Palette, retitled so it can't be mistaken for a local delete.

🔧 Fixes

• uploadOnSave and watcher.autoUpload no longer upload the same file twice on a Ctrl+S — safe to run both.
• Profiles can now override watcher, so auto-upload can be on for dev and off for prod. Switching profiles rebuilds the watcher immediately.
• SFTP: Upload Changed Files now actually applies Git renames (it silently failed before), and reports failures instead of swallowing them.

All new options default to off — nothing changes until you opt in. See the full option reference.

🎉 Previous Releases

📖 Full history in the CHANGELOG.

📑 Quick Links

✨ Features · ⚡ Quick Start · 🔧 Config Examples · 🔐 Security · 🔑 SSH Authentication · 🐛 Debug · ❓ FAQ

✨ Features

⚡ Quick Start

1. Install

Grab it from the VS Code Marketplace or install the .vsix from Releases.

2. Configure

Open the SFTP sidebar from the activity bar. If no config exists yet, click "Create SFTP Config" in the welcome view. You can also open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and run:

SFTP: Config

A sftp.json file is created under .vscode. Fill in your server details:

{
  "name": "My Server",
  "host": "example.com",
  "protocol": "sftp",
  "port": 22,
  "username": "root",
  "remotePath": "/var/www/html",
  "uploadOnSave": true,
  "backup": {
    "enabled": false,
    "location": "remote",
    "folder": ".vscode/sftp-backup",
    "versions": 5
  }
}

💡 No password? Leave "password" out (or set it to null) — you'll be prompted once and can save it securely to your OS keychain. See 🔐 Security.
🛡️ Backups are disabled by default. Set "backup.enabled": true to keep timestamped versions of remote files before every upload/sync. See 🛡️ File Backups.

3. Go!

Right-click any file or folder in the Explorer for quick upload / download / diff options.

🔧 Config Examples

🎭 Profiles

Switch between environments on the fly:

{
  "username": "deploy",
  "remotePath": "/app",
  "profiles": {
    "dev": { "host": "dev.example.com", "uploadOnSave": true },
    "prod": { "host": "prod.example.com", "uploadOnSave": false }
  },
  "defaultProfile": "dev"
}

Use SFTP: Set Profile to switch.

A profile can override any top-level option, including watcher — useful when something outside VS Code edits your files (an AI coding tool, a build step) and you want those changes uploaded automatically on dev but never on prod:

{
  "username": "deploy",
  "remotePath": "/app",
  "watcher": { "files": "**/*", "autoUpload": false },
  "profiles": {
    "dev":  { "host": "dev.example.com",  "watcher": { "files": "**/*", "autoUpload": true } },
    "prod": { "host": "prod.example.com", "watcher": { "files": "**/*", "autoUpload": false } }
  },
  "defaultProfile": "dev"
}

Object options are replaced wholesale rather than merged key-by-key, so repeat files in each profile. Switching profiles rebuilds the watcher immediately — no reload needed.

📂 Multiple Contexts

Sync different parts of your project to different places:

[
  {
    "name": "Frontend",
    "context": "client/dist",
    "host": "cdn.example.com",
    "remotePath": "/static"
  },
  {
    "name": "Backend",
    "context": "server",
    "host": "api.example.com",
    "remotePath": "/var/api"
  }
]

🔗 Connection Hopping

Reach a server through a bastion host:

{
  "name": "Target",
  "host": "bastion.example.com",
  "username": "jumpuser",
  "privateKeyPath": "~/.ssh/id_rsa",
  "hop": {
    "host": "target.internal",
    "username": "appuser",
    "privateKeyPath": "~/.ssh/id_rsa"
  }
}

📋 Every Option, With Defaults

You only need the handful of options your setup actually uses — the block below is a reference, not a starting point. Copy the lines you want, not the whole thing.

{
  "name": "My Server",
  "context": ".",
  "protocol": "sftp",

  "host": "example.com",
  "port": 22,
  "username": "user",
  "password": null,
  "remotePath": "/var/www/html",
  "connectTimeout": 10000,
  "keepalive": 30000,
  "concurrency": 4,

  "privateKeyPath": "~/.ssh/id_rsa",
  "passphrase": null,
  "agent": null,
  "interactiveAuth": false,
  "sshConfigPath": "~/.ssh/config",

  "uploadOnSave": false,
  "downloadOnOpen": false,
  "useTempFile": false,
  "openSsh": false,

  "ignore": [".vscode", ".git", ".DS_Store"],
  "ignoreFile": ".gitignore",

  "watcher": {
    "files": "**/*",
    "autoUpload": false,
    "autoDelete": false,
    "autoRename": false
  },

  "syncOption": {
    "delete": false,
    "skipCreate": false,
    "ignoreExisting": false,
    "update": false
  },

  "backup": {
    "enabled": false,
    "location": "remote",
    "folder": ".vscode/sftp-backup",
    "versions": 5,
    "onDelete": false
  },

  "remoteExplorer": {
    "filesExclude": [],
    "order": 0,
    "enableDragAndDrop": false
  },

  "remoteTimeOffsetInHours": 0,
  "limitOpenFilesOnRemote": false,

  "profiles": {
    "dev": { "host": "dev.example.com" },
    "prod": { "host": "prod.example.com" }
  },
  "defaultProfile": "dev"
}

🔐 Security

SFTP Neo stores passwords & passphrases in your OS credential store (macOS Keychain, Windows Credential Manager, Linux libsecret) via VS Code's Secret Storage API — so your sftp.json stays clean and commit-safe.

How to use it:

1. Set "password": null (or omit it) in sftp.json:

   {
     "host": "example.com",
     "username": "root",
     "password": null,
     "remotePath": "/var/www"
   }
   

2. Connect — you'll be prompted for the password.
3. Click "Save password to Secret Storage".
4. Future connections are automatic & encrypted.

The same works for private key passphrase.

🧹 Manage saved credentials anytime with SFTP: Delete Saved Password.

🔑 SSH Authentication

SFTP Neo supports three ways to authenticate SFTP connections. For both security and convenience, SSH keys or ssh-agent are recommended over plaintext passwords.

SSH private key (privateKeyPath)

1. Generate a key pair (skip if you already have one):

   ssh-keygen -t ed25519 -C "you@example.com"
   

   Press Enter to accept the default location (~/.ssh/id_ed25519). You can set a passphrase for extra security.

2. Copy the public key to your server:

   ssh-copy-id -i ~/.ssh/id_ed25519.pub user@example.com
   

3. Configure SFTP Neo:

   {
     "name": "My Server",
     "host": "example.com",
     "protocol": "sftp",
     "port": 22,
     "username": "user",
     "privateKeyPath": "~/.ssh/id_ed25519",
     "remotePath": "/var/www/html",
     "uploadOnSave": true
   }
   

💡 Encrypted key? Set "passphrase": true and SFTP Neo will prompt once, then offer to save it to Secret Storage. Or load the key into ssh-agent (see below) and omit passphrase.

SSH agent (agent)

Using an ssh-agent is the most convenient option: your key is unlocked once per session, and both SFTP transfers and Open SSH in Terminal work without typing a password.

macOS / Linux

1. Start the agent and add your key:

   eval "$(ssh-agent -s)"
   ssh-add ~/.ssh/id_ed25519
   

2. Get the agent socket:

   echo $SSH_AUTH_SOCK
   # Example: /tmp/ssh-XXXXXX/agent.12345
   

3. Configure SFTP Neo:

   {
     "host": "example.com",
     "username": "user",
     "agent": "/tmp/ssh-XXXXXX/agent.12345",
     "remotePath": "/var/www/html"
   }
   

🍎 On macOS, if your key is stored in Keychain, use ssh-add --apple-use-keychain ~/.ssh/id_ed25519 so you are not prompted after every reboot.

Windows

• Pageant (PuTTY agent): set "agent": "pageant".
• Windows OpenSSH agent: make sure the OpenSSH Authentication Agent service is running, then set "agent": "\\\\.\\pipe\\openssh-ssh-agent" (the pipe name may differ on older Windows builds).

Platform-specific tips

A note on Open SSH in Terminal

The sidebar command builds a plain terminal command:

ssh -t user@host -p 22 -i "/path/to/key"

It can automatically use:

• your privateKeyPath (-i ...)
• your ssh-agent (no extra flags)

It cannot auto-type a password or passphrase into the terminal. If you want a fully password-less terminal experience, use an ssh-agent.

🖥️ Remote Explorer

Browse your remote server directly in the VS Code sidebar.

Open it via:

• Command Palette → View: Show SFTP
• Or click the SFTP icon in the Activity Bar

Select multiple files with Ctrl/Shift to download or upload in batches.

🛡️ File Backups

Before any remote file is overwritten by an upload or sync-to-remote operation, SFTP Neo automatically creates a timestamped backup copy. Choose to keep backups on the remote server or in your local workspace. Browse, restore, or delete backup versions without leaving VS Code.

🚀 How It Works

Remote backups ("location": "remote", default)

Before Upload                    After Upload
─────────────────                ─────────────────
remote/index.php                 remote/index.php  ← new content
                                 remote/.vsftp-backup/
                                   └─ index.php.20260612194215007.bak  ← old content

Local backups ("location": "local")

Before Upload                    After Upload
─────────────────                ─────────────────
remote/index.php                 remote/index.php  ← new content
                                 workspace/.vsftp-backup/
                                   └─ index.php.20260612194215007.bak  ← old content

The remote directory layout is preserved inside the backup folder so you can mirror the server structure locally.

⚙️ Configuration

Add the backup object to your .vscode/sftp.json:

{
  "name": "Production",
  "host": "example.com",
  "protocol": "sftp",
  "port": 22,
  "username": "root",
  "remotePath": "/var/www/html",
  "uploadOnSave": true,
  "backup": {
    "enabled": true,
    "location": "remote",
    "folder": ".vsftp-backup",
    "versions": 5
  }
}

💡 Tip: The backup folder is automatically excluded from sync operations and the Remote Explorer — you never have to worry about backups being uploaded or cluttering your file tree.

📂 Using the Backups Panel

1. Enable backups in your sftp.json (see configuration above).
2. Upload or sync a file — a backup is created automatically before the overwrite.
3. Click any file in the Remote Explorer panel.
4. The Backups panel (titled Remote Backups or Local Backups based on your setting) updates to show all backup versions for that file, sorted newest → oldest.

🔒 Safety Guarantees

• Upload never blocked: If a backup fails for any reason, the upload still proceeds. Your code always goes live.
• Auto-pruning: Old backups beyond your versions limit are cleaned up automatically after each upload.
• No sync loops: The backup folder is invisible to sync, so local backups are never auto-uploaded and remote backups are never downloaded.
• Context-aware: The panel only shows backups for the file you have selected in Remote Explorer.

🐛 Debug

Need to troubleshoot?

1. Open Settings (Ctrl+, / Cmd+,).
2. Search for sftp.debug and set it to true.
3. Reload VS Code.
4. View logs in Output → SFTP.

❓ FAQ

See FAQ.md for common questions and solutions.