How to Create and Use a Temporary Profile in VS Code

Create a Temporary Profile in VS Code to test extensions, try new settings, or reproduce a bug without touching your real setup. The profile is deleted when you close VS Code.

4 min read

A Temporary Profile is a VS Code profile that exists only for the current session. It starts as an Empty Profile with no custom settings, extensions, snippets, or keyboard shortcuts. You can modify it freely, and everything is discarded when you close VS Code.

This is the safest way to test a new extension, try a configuration change, or reproduce a bug report. You never risk breaking your normal setup. Unlike a permanent profile, which you create through the Profiles editor, a Temporary Profile is meant to be disposable. See /vscode/how-to-create-and-switch-between-profiles-in-vs-code if you need a profile that persists.

Create a Temporary Profile

Open the Command Palette with Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (macOS) and run the command:

Profiles: Create a Temporary Profile

VS Code immediately creates the profile with an auto-generated name such as Temp 1, Temp 2, and so on. The profile becomes active in the current window.

You can confirm it is active by checking the title bar. It shows the temporary profile name (for example, "Temp 1"). The Manage gear button at the bottom of the Activity Bar also shows a badge with the first two letters.

What the Temporary Profile starts with

A Temporary Profile begins completely empty:

  • Settings: Only VS Code defaults. No user or workspace settings carry over.
  • Extensions: No extensions are installed, not even ones you use in other profiles.
  • Keyboard shortcuts: Only built-in defaults.
  • Snippets: None.
  • User tasks: None.
  • UI layout: Default layout with all views visible.

This clean starting point makes it easy to isolate behavior. If an extension works in the Temporary Profile but not in your normal profile, you know another extension or setting is causing the conflict.

When to use a Temporary Profile

ScenarioWhy it helps
Test a new extensionInstall it in isolation. If it misbehaves, close VS Code and it is gone.
Try a risky settings changeChange any setting without worrying about undoing it later.
Reproduce a bug reportStart from a clean state to confirm whether the bug is in VS Code core or your configuration.
Quick demo or screen shareShow a clean VS Code interface without personal files, recent workspaces, or customizations visible.
Evaluate a Profile TemplateCreate a Temporary Profile, then apply template contents manually to preview without creating a permanent profile.

Work in a Temporary Profile

Once the Temporary Profile is active, you can use VS Code normally:

  • Install extensions from the Marketplace.
  • Change settings through the Settings editor or settings.json.
  • Open a project folder and work on it.
  • Adjust the UI layout.

The folder you open is not affected by the Temporary Profile. Your files are not temporary, only the profile is. When you close VS Code and reopen with your normal profile, the same folder opens with your usual setup.

What happens when you close VS Code

When you close the VS Code window, the Temporary Profile is deleted. This includes any extensions you installed, any settings you changed, any snippets or tasks you created, and any UI layout adjustments.

What is deletedWhat is kept
Extensions installed during the sessionFiles in your project folders
Settings changesYour Default Profile and saved profiles
Snippets and tasksFolder-to-profile associations
UI layout adjustmentsSettings Sync data

Save work from a Temporary Profile

If you built something useful in a Temporary Profile and want to keep it, export the profile before closing VS Code. While the Temporary Profile is active, open the Profiles editor, find the Temporary Profile, and select Export from its overflow menu. Save it as a GitHub gist or a .code-profile file. After VS Code restarts with your normal profile, import it as a permanent profile.

See /vscode/how-to-export-import-and-share-a-vs-code-profile for the full export and import steps.

Create multiple Temporary Profiles

You can create more than one Temporary Profile in a session. Each new one gets an incremented name: Temp 1, Temp 2, Temp 3. Switch between them with the Profiles: Switch Profile command.

This is useful when you want to compare two extensions side by side. Install one in Temp 1, switch to Temp 2, install the alternative, and compare behavior in two clean environments.

Rune AI

Rune AI

Key Insights

  • Create a Temporary Profile with the Profiles: Create a Temporary Profile command.
  • A Temporary Profile starts as an Empty Profile with an auto-generated name like Temp 1.
  • All changes made in a Temporary Profile are discarded when you close VS Code.
  • Use Temporary Profiles to test extensions, settings, or reproduce bugs without risk.
  • Export the profile before closing if you want to keep the setup permanently.
RunePowered by Rune AI

Frequently Asked Questions

What happens to my extensions and settings when I close a Temporary Profile?

The Temporary Profile and everything you changed inside it is deleted. Your Default Profile and any other saved profiles are untouched. When you reopen VS Code, your normal profile is active again.

Can I save a Temporary Profile as a permanent profile?

Yes, but only by exporting it before closing VS Code. Export the Temporary Profile as a GitHub gist or .code-profile file, then import it as a permanent profile after restarting. There is no one-click convert option.

How is a Temporary Profile different from an Empty Profile?

An Empty Profile is a permanent profile that starts with no customizations. You can switch to it, modify it, and come back to it later. A Temporary Profile also starts empty but is automatically deleted when you close VS Code.

Conclusion

Temporary Profiles are the safest way to experiment in VS Code. Use them to test a new extension, try a risky settings change, or reproduce a bug report. Everything resets when you close the window.