Downloading the Python Debugger (debugpy) extension as an offline VSIX package is a critical step when configuring an air-gapped Python development environment or working behind strict enterprise security proxies. In older versions of VS Code, debugging was baked directly into the monolithic Python extension. Microsoft has since extracted debugging into a dedicated, standalone extension: ms-python.debugpy.

Without this package, installing only the core Python extension will leave you unable to set breakpoints, inspect variables, or launch debugging sessions. In this guide, I have documented the direct platform-specific VSIX download links for the official Microsoft extension, step-by-step CLI and GUI installation instructions, dependency requirements, and troubleshooting fixes.

1. Direct Python Debugger (debugpy) VSIX Downloads

The official extension published by Microsoft is listed on the Visual Studio Marketplace as Python Debugger under the identifier ms-python.debugpy. Because debugpy relies on compiled native C-extension wheels (accelerators) to inspect running Python interpreter memory with minimal overhead, Microsoft publishes platform-specific VSIX packages tailored to each operating system and processor architecture.

Select the download button below matching your operating system architecture. The links point to verified stable releases and automatically look up newer stable builds when this page loads.

Download for Windows x64 (2026.7.13061010) Download for Windows ARM64 (2026.7.13061010) Download for macOS Apple Silicon (2026.7.13061003) Download for macOS Intel (2026.7.13061005) Download for Linux x64 (2026.7.13061008) Download for Linux ARM64 (2026.7.13061004)
Need another release or a different extension? Open my free VSIX Downloader – Python Debugger to inspect versions and download packages directly.

2. Why Platform-Specific VSIX Packages Are Required

A common stumbling block when downloading VS Code extensions offline is expecting a single universal .vsix archive. While pure JavaScript extensions are universal, debugpy is a native-accelerated debugger. Under the hood, it bundles precompiled Python binary components for frame evaluation and speedups that correspond to your specific OS kernel and CPU architecture.

To ensure smooth debugging without crashes, you must download the exact build for your machine:

– Windows x64 / ARM64: Choose win32-x64 for standard 64-bit Intel/AMD PCs, or win32-arm64 for Surface and Snapdragon devices.

– macOS Apple Silicon / Intel: Choose darwin-arm64 for M1, M2, M3, and M4 Macs. Choose darwin-x64 only for older Intel-based Macs.

– Linux x64 / ARM64: Choose linux-x64 for Ubuntu, Debian, RedHat, and standard cloud VMs. Choose linux-arm64 for ARM servers and developer boards.

Attempting to install an architecture mismatch will trigger an immediate VS Code engine error refusing to register the incompatible binary.

3. How to Download the VSIX via Terminal (cURL)

If you prefer downloading packages through a terminal or build script on an internet-connected workstation, you can query Microsoft’s Visual Studio Marketplace endpoint directly.

The official download URL pattern requires specifying the target platform query parameter:

https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/debugpy/VERSION/vspackage?targetPlatform=PLATFORM

Here is a complete cURL command to fetch the verified stable build for Windows x64:

curl --fail --location \
  "https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/debugpy/2026.7.13061010/vspackage?targetPlatform=win32-x64" \
  --output "ms-python.debugpy-win32-x64.vsix"

And here is the command for macOS Apple Silicon:

curl --fail --location \
  "https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/debugpy/2026.7.13061003/vspackage?targetPlatform=darwin-arm64" \
  --output "ms-python.debugpy-darwin-arm64.vsix"

On Windows PowerShell, always use curl.exe rather than the built-in PowerShell alias to ensure the binary stream and redirects are captured cleanly. Verify that the output file size is roughly 7 MB to 10 MB.

4. Step-by-Step Offline Installation Guide

Once you have transferred the .vsix package to your offline environment via an approved USB drive or internal share, install it using either method below.

Method A: Install via the VS Code Graphical Interface

1. Open Visual Studio Code.

2. Open the Extensions sidebar by clicking the Extensions icon on the Activity Bar or pressing Ctrl+Shift+X (Windows/Linux) or Cmd+Shift+X (macOS).

3. Click the Views and More Actions menu (the three horizontal dots ... in the top right corner of the Extensions panel).

4. Select Install from VSIX… from the dropdown menu.

5. Locate your downloaded .vsix file, select it, and confirm. VS Code will install the debugger extension quietly.

Method B: Install via the Terminal Command Line

For headless developer environments, remote servers, or rapid scripting, use the VS Code CLI tool:

code --install-extension "./ms-python.debugpy-win32-x64.vsix"

If reinstalling or overwriting an earlier broken installation, append the --force flag:

code --install-extension "./ms-python.debugpy-win32-x64.vsix" --force

To confirm that the extension has been successfully registered, run:

code --list-extensions --show-versions

You should see ms-python.debugpy present in the installed extensions list.

5. Critical Dependency: The Core Python Extension

A crucial detail discovered by inspecting the extension/package.json manifest is that ms-python.debugpy declares a hard dependency:

{
  "extensionDependencies": [
    "ms-python.python"
  ]
}

What this means for offline users: You CANNOT install debugpy alone on a clean VS Code installation without also having the core Python extension (ms-python.python) installed. If you attempt to install debugpy on a machine that lacks the core extension, VS Code will fail to activate debugging.

Always ensure you download and install the primary Python VSIX Extension before or alongside debugpy.

6. Verifying Offline Debugging with launch.json

After installing both extensions, verify that local debugging works without an internet connection. Create a basic test script (e.g. app.py) and add a standard launch configuration in .vscode/launch.json:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Python Debugger: Current File",
      "type": "debugpy",
      "request": "launch",
      "program": "${file}",
      "console": "integratedTerminal"
    }
  ]
}

Notice that the debugger configuration type is now explicitly "debugpy" (rather than the legacy "python" type). Set a breakpoint on a line of code and press F5. If the debugger stops at your breakpoint and populates local variables, your offline debugging environment is 100% operational.

7. Troubleshooting Common Offline Debugger Issues

Error: Cannot resolve debugger type ‘debugpy’

This occurs when the debugpy extension failed to activate or the core ms-python.python extension is missing. Run code --list-extensions and confirm that both ms-python.python and ms-python.debugpy are installed.

Error: Extension is incompatible with this version of VS Code

The current debugpy stable release requires VS Code ^1.92.0 or newer. Check your installed version under Help -> About. If running an older build, upgrade VS Code or download an older debugpy VSIX through the VSIX Downloader web tool.

Breakpoint is hit but variables do not appear or step over hangs

This typically indicates an architecture mismatch where an emulated binary is running incorrectly, or Python is executing inside a virtual environment whose interpreter path was not selected in VS Code. Press Ctrl+Shift+P, run Python: Select Interpreter, and ensure your project’s virtual environment is chosen.

Frequently Asked Questions

Why did Microsoft separate debugpy from the main Python extension?

Historically, the Python extension was a massive monolithic bundle that included the language server, linter, formatter, and debugger. To improve performance, startup time, and modularity, Microsoft split each responsibility into dedicated extensions (debugpy, Pylance, Ruff, Black, etc.).

Can I use debugpy for remote debugging across an air-gapped network?

Yes. You can install the debugpy Python package (pip install debugpy) on a remote server or container, attach VS Code via an approved internal TCP port using an "attach" launch configuration, and debug seamlessly without any external cloud access.

Will debugpy update automatically when installed from VSIX?

No. Automatic updates are disabled by default for VSIX sideloads. When you want to update, download the newer VSIX package and run code --install-extension <file> --force.

Related Reading

Explore more companion guides for locked-down and offline development setups:

– Download Python VSIX Extension (Offline Install Guide 2026)

– How to Build a Completely Air-Gapped Python Development Environment in VS Code

– Auto Rename Tag VSIX Download: Offline Install Guide for VS Code

– OpenAI ChatGPT (Codex) VSIX Download: Offline Install Guide for VS Code

– CMake VSIX Download: Offline Install Guide for VS Code

Conclusion

Having a dependable offline Python debugger is essential for air-gapped development. By downloading the correct platform-specific ms-python.debugpy VSIX alongside the core Python extension, you can step through code, inspect variables, and diagnose issues without relying on an internet connection.

Categorized in:

Azure

Tagged in:

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,