Sublime SFTP


Sublime SFTP is tested on all three platforms supported by Sublime Text 2. If something isn't working right, send an email to If you believe you have found a bug, please consider generating a debug log to submit.

Also see the Sales FAQ, which includes information for individuals, businesses and resellers.

I am Still Getting License Prompts after Entering my License!

This is usually the result of one of a few things. In the following solutions, the SFTP.sublime-settings file can be opened by using the Preferences > Package Settings > SFTP > Settings - User menu entry.

If you are running macOS High Sierra (10.13) and Sublime Text 2, the menus will be greyed out because Apple removed Python 2.6 from the OS, however Sublime Text 2 requires it for packages to function properly. Apple has replaced Python 2.6 with 2.7, which has various incompatibilities. Unfortunately there isn't a way to support this breaking change in macOS High Sierra.

Additionally, Sublime Text 2 is no longer maintained by Sublime HQ. The SFTP package is fully supported on Sublime Text 3, which is still being actively developed by Sublime HQ. Users who purchased a license for Sublime Text in Feburary 2013 or after already have a Sublime Text 3 license. Users who purchased a license before then will need to purchase a license upgrade for $30 or $11 depending on the original purchase date. To see a list of all of the changes, visit

If you are not running Sublime Text 2 on macOS High Sierra, you may have run into a bug that occurs occasionally, related to plugin reloading.

To fix this, please perform the following:

  1. Open Preferences > Browse Packages…
  2. Navigate into the SFTP/ folder and open in Sublime.
  3. Without making any modifications, save the file. Sublime SFTP should now be fully functional again.

Generating a Debug Log

To turn on debugging and log commands to a file, perform the following steps:

  1. Open Preferences > Package Settings > SFTP > Settings – Default
  2. Copy the debug and debug_log_file settings to the Settings – User file.
  3. Set debug to 2 and choose where to save the debug_log_file
  4. Perform the operations that expose the bug
  5. Check the debug log to ensure no user credentials are contained within
  6. Send the debug log to with a description of the problem you are having