Configuration Storage

You can clean up all configuration data stored on your machine.

To export/back up your configuration, go to Tools > Export/Backup configuration on Login dialog.

In older versions of WinSCP, use Export button on Preferences dialog.

To import/restore the complete configuration including all stored sites, go to Tools > Import/Restore configuration on Login dialog.

To import only selected sites, you can alternatively use Tools > Import Sites (and select INI file for import source). This feature is available only in the latest beta release.

See also How do I transfer my settings from a non-working computer?

To transfer your configuration to another computer/location, export the configuration to an INI file and then import the file on the another computer/location.

If you want to transfer just one specific stored site, you can generate a session URL from the site on the source location (make sure you include Advanced settings to the URL). Transfer the URL to the target location, paste it to the Login dialog and save it.

See Sharing WinSCP configuration between machines using cloud storage.

If you use registry as configuration storage, the configuration is stored under the following key:

[HKEY_CURRENT_USER\Software\Martin Prikryl\WinSCP 2] 

When loading configuration, WinSCP first looks for an INI file in the directory, where WinSCP executable is stored in. The INI file needs to have an .ini extension and the same name as the executable (i.e. WinSCP.ini). If INI file in not found there, WinSCP looks to application data directory of your user profile, i.e. to C:\Users\username\AppData\Roaming\WinSCP.ini.

When you opt to use INI file for the first time, WinSCP tries to write it to directory, where WinSCP executable is stored in. If the directory is not writable, INI file is stored to application data directory of your user profile.

You may also use an INI file in a different folder or with a different name using /ini switch or in preferences.

With /ini=nul command-line switch, WinSCP starts with the default configuration and does not save the configuration on exit. That is particularly useful for scripting, to make sure that the script always starts with all defaults. This is also the configuration mode used by WinSCP .NET assembly.

Particularly, when using a shared INI file or when pre-configuring WinSCP for a specific task, you may want to set the configuration or its parts read-only.

You can set individual configuration sections read-only. This way you can for example prevent a user from changing default transfer settings, while still allowing other kinds of customizations.

Setting a configuration section read-only makes WinSCP silently discard any changes to that section, when saving the configuration.

An access to individual sections is controlled using an optional Access key. If the key is not set, a section inherits the state of its parent section. By default, all sections are writable. To set a section read-only, set its Access key to readonly. To enable writing to a subsection of a read-only section, set the subsection Access key to full.

To change the default state of whole configuration, set root Access key. In Windows registry, it is a key in WinSCP root registry key. As INI files have no root section, WinSCP looks into a special section named [_] (a single underscore).

For example the following INI file sets all configuration read-only, with an exception of a host key cache and interface settings (but in turn with an exception of transfer settings, which are again read-only):

[_]
Access=read
 
[SshHostKeys]
Access=full
...
 
[Configuration\Interface]
Access=full
...
 
[Configuration\Interface\CopyParam]
Access=read
...

On startup, WinSCP first looks for an INI file in the directory, where WinSCP executable is stored in;1 and then in the user profile directory. If it does not find INI file in either location, it looks for presence of its key in registry, both in HKCU and HKLM. The HKLM key is created by the installer, so installed WinSCP uses the registry by default. If it does not find the registry key either, it creates an empty INI file in the directory, where WinSCP executable is stored in. If that directory is not writable, it creates an empty INI file in the user profile directory.

When troubleshooting problems, it is necessary to find whether WinSCP is actually using the configuration storage you intended. For that inspect a beginning of the session log:

-------------------------------------------------------------------------- 
WinSCP Version 5.15.3 (Build 9730) (OS 10.0.18362 - Windows 10 Enterprise)
Configuration: HKCU\Software\Martin Prikryl\WinSCP 2\
Log level: Normal
Local account: INTRANET\martin                                           

Tag Configuration shows either HKCU Windows registry key or a path to an INI file. When Windows registry configuration storage is in use, it is also important under what Windows account is WinSCP running, to know what account the HKCU refers to. For that refer to Local account tag.

Learn how to configure WinSCP for portable use.

Learn how to distribute pre-configured version of WinSCP.