VS

Visual Studio Code Recorded Package Source

Direct package links and installation notes for Windows/macOS/Linux

Developer Tools · v1.135.0 · Free (Microsoft product license; source MIT)

Free, powerful code editor by Microsoft

Source record, not a product review. Automated checks can confirm URL availability but not package safety, installation behavior, or offline operation. Catalog maintained by .
License: Free (Microsoft product license; source MIT)
Size: 231.7 MB
Platforms: Windows macOS Linux

Download summary

Visual Studio Code is a developer tool for Windows/macOS/Linux, published by Microsoft. A direct package URL is recorded below. The host may be the publisher, a release repository, a CDN, or another distribution source documented by the publisher. Some packages still fetch optional components during setup. The recorded publisher site is code.visualstudio.com. We do not host or modify installer files.

Sources and identity

External references used to identify the product and publisher. These links do not prove that we installed the package.

Wikipedia article Source on GitHub SHA-256 listed in catalog

Publisher documentation

These references support the package and behavior notes. Documentation checks are separate from the recorded URL-check date and do not represent an installation test.

Choose a package

System setup, User setup or ZIP

The recorded Windows EXE is System setup for all users, which requires administrator permissions. Microsoft offers a separate User setup for an individual account.

The ZIP avoids setup and needs manual application updates. Select an update and policy strategy before deployment; this page’s pinned packages are 1.135.0, not a claim about the newest release.

Pinned macOS ZIP

The recorded 1.135.0 universal endpoint resolves to a ZIP. Extract this archive and inspect the included application before following the publisher’s instructions.

Current macOS documentation describes a DMG workflow too. Use instructions for the actual package you obtained, not a guessed format based only on the operating system.

Package guidance is based on the linked documentation, checked 11 September 2026. No installation test is claimed.

Publisher SHA-256 reference values

Compared each recorded value with the x-sha256 header on its Microsoft versioned redirect; exact destination filenames were recorded. No local binary hashing or signature test. Compared on 11 September 2026 with the publisher’s reference.

VSCodeSetup-x64-1.135.0.exe
91cc59509d5d0e2f0829525fb39197f26289e9a3c1079ea0ee5ca848de083e5f
VSCode-win32-x64-1.135.0.zip
0ee1557bab25c2b86d1dffc012fd367abef5e77ea62c2c3d7e32ec90281b2c6c
VSCode-darwin-universal.zip
c7bcee9c8256d19c3aafc0d411d36be89e07731d7e7b0c889557909ec36a78e7
code_1.135.0-1787669172_amd64.deb
e8101720f0a48f8e6ae5a4112d10ffea5f13d298e7d0a7012b4e36eebc53022c

Compare only with the exact named package. A matching hash alone does not establish publisher identity or package safety.

Download options

Recorded package links, store pages, and browser extensions where available.

Scroll the table sideways to compare packages and reach each download link.

Platform Build Architecture Package Action Notes
Windows

EXE

Visual Studio Code 1.135.0 Windows x64 System setup

64-bit EXE Download file System installer for all users; requires administrator permissions. Microsoft also offers a separate per-user setup.
Windows

ZIP

Visual Studio Code 1.135.0 Windows x64 archive

64-bit ZIP Download file Versioned no-installer archive; extensions, settings, and toolchains remain separate
macOS

Universal

Visual Studio Code 1.135.0 macOS universal ZIP

Universal ZIP Download file This pinned endpoint resolves to a ZIP archive; current publisher instructions may also discuss newer DMG packages.
Linux

DEB

Visual Studio Code 1.135.0 Linux DEB

64-bit DEB Download file Official Linux package endpoint

Verification scope

A direct package URL is recorded above. We have not independently installed every listed build or confirmed that setup remains fully offline.

We do not host software files. Links may resolve to a publisher domain, its release repository, app store, CDN, or a documented distribution host — confirm the final hostname, publisher signature, version, and architecture before deployment. Recorded URLs last checked 30 August 2026; content last updated 11 September 2026.

What Visual Studio Code does

Visual Studio Code is Microsoft's packaged desktop code editor for Windows, macOS, and Linux. The Microsoft binary distribution is free to use under Microsoft's product license and includes Microsoft branding, telemetry configuration, update services, and Marketplace integration; it is not itself distributed under the MIT license. The upstream vscode source repository, commonly called Code - OSS, is MIT-licensed, and third-party builds can differ in branding, services, extensions, and update behavior.

This record pins Stable 1.135.0 packages through Microsoft's versioned update service: Windows x64 setup and ZIP archive, macOS universal build, and Linux x64 DEB. Microsoft supplied SHA-256 response metadata for these artifacts. The service redirects to Microsoft-controlled CDN objects, so managed archives should retain the resolved filename and response metadata with the recorded digest. The ZIP avoids an installer but is not automatically policy-free or self-contained; settings, extensions, runtimes, terminals, compilers, and project dependencies live separately.

The core editor can work with local files offline, but many language features come from separately installed extensions or language servers. Marketplace browsing, extension installation and updates, Settings Sync, Remote Development bootstrap components, source-control remotes, and editor updates require connectivity and may require accounts. Extensions have separate publishers, licenses, permissions, telemetry, and executable-code risk. This audit did not install or code-signature-check the packages.

Try a practical task

Compare two configuration files before replacing one

Use an editor diff to spot a changed port and log level in two harmless sample files. This is useful before a configuration update because the change is visible in context.

Before you start

  • Create a scratch folder you control, separate from a real project.
  • No extension, account or remote workspace is required for this comparison.
  1. Create the baseline

    Save the following as before.json in the scratch folder.

    {
      "port": 8080,
      "logLevel": "info"
    }
  2. Create the proposed copy

    Save a second file as after.json, changing the port to 8081 and logLevel to debug. Keep the original unchanged.

  3. Open a diff

    In the Explorer, right-click before.json and choose Select for Compare. Right-click after.json and choose Compare with Selected.

  4. Read the differences

    Check which side is the baseline and inspect both changed values. Close the comparison without applying it to any real service.

Expected result

The comparison highlights the port and log-level changes. A visual diff does not prove the new configuration is valid for an application.

Our demonstration

VS Code comparing our before.json and after.json, showing port 8080 to 8081 and info to debug.
Our original sample: the left file keeps port 8080 and info; the proposed right file changes them to 8081 and debug. Captured 2026-10-11 using Visual Studio Code 1.136.0 on macOS 27.0.1 (arm64). Observed: opening both local files and reading the diff through Compare Active File With. The Explorer menu is an alternative documented route. This did not test installation of the catalogue’s pinned packages.

If the result is different

Nothing is highlighted
Save both files and check that you selected two different paths with different values.
Unexpected changes appear everywhere
Check line endings, encoding and formatting before treating every highlighted line as a semantic change.

This example compares text only. Test a real configuration with the application’s own validation and recovery procedure before deploying it.

Continue with the publisher’s instructions

Guide updated . Steps describe the linked documentation and our sample task. Only demonstrations with a stated environment record an observed run; this is not an installation test of every Visual Studio Code package listed above.

Product features

  • Core editing plus language-specific IntelliSense supplied by built-in support or extensions
  • Built-in Git source control with diff, staging, and merge tools
  • Integrated terminal and a full debugger with breakpoints and watch
  • Marketplace extensions have separate publishers, permissions, licenses, and network behavior
  • Remote and Sync features require separate components, connectivity, and sometimes accounts

Installation notes

Grouped by the package types recorded on this page — not a claim that every listed build was independently tested on every supported platform.

Windows Windows archive (ZIP/7Z)

  1. 1

    Extract the recorded file (VSCode-win32-x64-1.135.0.zip) into a separate folder and check the publisher's instructions for the executable or setup program inside. ZIP/7Z describes compression, not installation behavior.

  2. 2

    A no-installer build may still store settings, credentials, caches, or Registry entries outside that folder. Check Visual Studio Code's configuration and removal instructions before moving or deleting it.

Windows Windows installer (EXE)

  1. 1

    Download the recorded file (VSCodeSetup-x64-1.135.0.exe). If it has a digital signature, inspect the signer and validation result in Properties → Digital Signatures. If no signature is present, follow the publisher's documented verification method; a missing signature does not authenticate the file.

  2. 2

    Check any Windows warning before proceeding. A SmartScreen reputation warning is not signature verification; stop if the publisher is unexpected or the file is reported as malicious.

  3. 3

    Follow the publisher's setup prompts to finish; options vary by release, so review each screen rather than clicking through.

macOS macOS binary archive (ZIP/7Z)

  1. 1

    Extract the recorded file (VSCode-darwin-universal.zip); a ZIP or 7Z archive is not a macOS disk image and may contain an app bundle or command-line binaries rather than an installer.

  2. 2

    Follow the publisher's package-specific instructions, then verify any code signature before the first launch.

Linux Debian/Ubuntu package (DEB)

  1. 1

    Use the compatible distribution's package manager to install the local DEB and review its proposed changes. Missing dependencies require a reachable repository or a prepared local dependency set.

  2. 2

    For disconnected deployment, collect dependencies for the target release and architecture first. A local DEB file alone does not establish a complete offline installation.

More Developer Tools Source Guides

View all Developer Tools

Also Popular on OfflineInstallerSetup

Browse all software