Portable mode
Visual Studio Code supports Portable mode. This mode enables all data created and maintained by VS Code to live near itself, so it can be moved around across environments.
This mode also provides a way to set the installation folder location for VS Code extensions, useful for corporate environments that prevent extensions from being installed in the Windows AppData folder.
Portable mode is supported on the ZIP download for Windows, and the TAR.GZ download for Linux, as well as the regular Application download for macOS. See the Download page to find the correct .zip / .tar.gz file for your platform.
Do not attempt to configure portable mode on an installation from the Windows User or System installers. Portable mode is only supported on the Windows ZIP (.zip) archive. Note also that the Windows ZIP archive does not support auto update.
Enable Portable mode
Windows, Linux
After unzipping the VS Code download, create a data folder within VS Code's folder:
|- VSCode-win32-x64-1.84.2
|   |- Code.exe (or code executable)
|   |- data
|   |- bin
|   |  |- code
|   |  |- ...
|   |- ...
From then on, the data folder will be used to contain all VS Code data, including session state, preferences, extensions, etc.
The data folder will override the --user-data-dir and --extensions-dir command line options.
The data folder can be moved to other VS Code installations. This is useful for updating your portable VS Code version, in which case you can move the data folder to a newer extracted version of VS Code.
Linux
On Linux, in addition to creating the data folder, you also need to set the correct Electron sandbox permissions.
Chromium has a multi-layer sandboxing model on Linux. If Chromium cannot use the namespace sandbox for layer-1, it will try to use the setuid sandbox via the helper binary chrome-sandbox that is shipped alongside the application binary.
Run the following commands to set the correct permissions of the setuid helper:
sudo chown root <path-to-vscode>/chrome-sandbox
sudo chmod 4755 <path-to-vscode>/chrome-sandbox
macOS
On macOS, you need to place the data folder as a sibling of the application itself. Since the folder will be alongside the application, you need to name it specifically so that VS Code can find it. The default folder name is code-portable-data:
|- Visual Studio Code.app
|- code-portable-data
Portable Mode won't work if your application is in quarantine, which happens by default if you just downloaded VS Code. Make sure you remove the quarantine attribute, if Portable Mode doesn't seem to work:
xattr -dr com.apple.quarantine Visual\ Studio\ Code.app
On Insiders, the folder should be named code-insiders-portable-data.
Update Portable VS Code
On Windows and Linux, you can update VS Code by copying the data folder over to a more recent version of VS Code.
On macOS, automatic updates should work as always, no extra work needed.
Migrate to Portable mode
You can also migrate an existing installation to Portable mode.
Windows, Linux
- Download the VS Code (or VS Code Insiders) ZIP distribution for your platform.
 - Create the 
datafolder as above. - Copy the user data directory 
Codetodataand rename it touser-data:- Windows 
%APPDATA%\Code - Linux 
$HOME/.config/Code 
 - Windows 
 - Copy the extensions directory to 
data:- Windows 
%USERPROFILE%\.vscode\extensions - Linux 
~/.vscode/extensions 
 - Windows 
 
As an example, here's the desired outcome on Windows:
|- VSCode-win32-x64-1.84.2
|   |- Code.exe (or code executable)
|   |- data
|   |   |- user-data
|   |   |   |- ...
|   |   |- extensions
|   |   |   |- ...
|   |- ...
macOS
- Download VS Code (or VS Code Insiders) for macOS.
 - Create the 
code-portable-datafolder as above. - Copy the user data directory 
Codetocode-portable-dataand rename it touser-data:$HOME/Library/Application Support/Code
 - Copy the extensions directory to 
code-portable-data:~/.vscode/extensions
 
TMP directory
By default, the default TMP directory is still the system one even in Portable Mode, since no state is kept there. If you want to also have your TMP directory within your portable directory, you can create an empty tmp directory inside the data folder. As long as a tmp directory exists, it will be used for TMP data.