How to Install VSCodium on Ubuntu 26.04, 24.04 and 22.04

VSCodium gives Ubuntu users the familiar VS Code editing workflow without Microsoft’s telemetry, branding, or default Marketplace wiring. You can install VSCodium on Ubuntu through the upstream APT repository, Snap, or Flatpak, depending on whether you want the fastest stable package updates, Snap refreshes, or a sandboxed Flathub build.

Install VSCodium on Ubuntu

APT behaves like a normal .deb app and updates through APT. Snap and Flatpak are self-contained app formats with their own update mechanisms.

Method	Channel	Version Behavior	Updates	Best For
APT Repository	VSCodium APT repository	Tracks the current stable release fastest	Via APT upgrades	Most users, native system integration
Snap	Snap Store, VSCodium publisher	Stable channel can lag behind APT	Automatic background refreshes	Users already using Snap packages
Flatpak	Verified Flathub app	Flathub stable can lag behind APT	Via flatpak update	Users preferring a sandboxed Flathub workflow

Recommended: use the APT repository for the most current stable package and the cleanest desktop integration. Use Flatpak if you prefer a sandboxed app with Flathub, or Snap if you already rely on Snap’s automatic refresh model and do not mind the stable channel moving more slowly.

Ubuntu does not include VSCodium in the default repositories, and VSCodium does not use a Launchpad PPA. The APT path adds the current VSCodium repository at repo.vscodium.dev/deb. The package name for both APT and Snap is codium, not vscodium.

The VSCodium GitHub releases page also publishes direct .deb files for several Debian-family architectures, an x86_64 AppImage, source archives, and checksum files. For routine Ubuntu installs, the repository path is easier to maintain because APT handles future updates; use direct downloads only when you intentionally need a one-off package or portable asset. If you choose the AppImage, Ubuntu 26.04 and 24.04 use libfuse2t64 from Universe, while Ubuntu 22.04 uses libfuse2; enable the Universe repository on Ubuntu first if APT cannot locate the required package.

VSCodium uses Open VSX for extensions by default, so a small number of Marketplace-only or license-restricted extensions may not appear. If you need Microsoft’s official build and the default Marketplace experience, follow our Visual Studio Code installation guide for Ubuntu.

The Ubuntu compatibility scope is 26.04 LTS, 24.04 LTS, and 22.04 LTS. VSCodium’s repository uses the same vscodium suite on each supported release, so the commands stay the same across these Ubuntu versions.

Method 1: Install VSCodium via APT Repository on Ubuntu

Update Ubuntu Package Lists Before Installing VSCodium

Refresh the APT package index:

sudo apt update

If you do not have sudo configured, see our guide on adding a user to sudoers on Ubuntu.

If you also want to apply pending system upgrades, run sudo apt upgrade separately before continuing.

Install VSCodium Repository Dependencies

Install curl and the minimal gpg package so Ubuntu can download and dearmor the VSCodium repository key. The -y flag auto-confirms the package prompt. If you want more curl examples, see our curl command guide:

sudo apt install curl gpg -y

Import the VSCodium APT Repository GPG Key

Download and store the GPG signing key so APT can verify that VSCodium packages are authentic and untampered:

curl -fsSL https://repo.vscodium.dev/vscodium.gpg | sudo gpg --dearmor --yes -o /usr/share/keyrings/vscodium.gpg

Add the VSCodium APT Repository

Add the VSCodium repository using the hosted DEB822 .sources file. The live source file lists amd64, arm64, and armhf; on normal 64-bit Intel or AMD Ubuntu systems, APT selects the amd64 package automatically.

sudo curl -fsSLo /etc/apt/sources.list.d/vscodium.sources https://repo.vscodium.dev/vscodium.sources

Review the source file before refreshing APT so you can catch an interrupted download or unexpected repository path:

cat /etc/apt/sources.list.d/vscodium.sources

Types: deb
URIs: https://repo.vscodium.dev/deb
Suites: vscodium
Components: main
Architectures: amd64 arm64 armhf
Signed-by: /usr/share/keyrings/vscodium.gpg

Refresh APT and Verify the VSCodium Repository

Update your package listings to include the newly added VSCodium repository:

sudo apt update

The update output should include the VSCodium repository line:

Get:3 https://repo.vscodium.dev/deb vscodium InRelease

After the update completes, verify that the repository is active and that VSCodium is available:

apt-cache policy codium

The expected output shows the package is available from the VSCodium repository:

codium:
  Installed: (none)
  Candidate: 1.116.02821
  Version table:
     1.116.02821 500
        500 https://repo.vscodium.dev/deb vscodium/main amd64 Packages

The candidate version changes as the VSCodium repository publishes new stable builds. The important checks are the Candidate line and the repo.vscodium.dev/deb vscodium/main repository source.

Install the VSCodium Package with APT

APT pulls the codium package from the VSCodium repository and registers it for future upgrades:

sudo apt install codium -y

Confirm the package installed from the VSCodium repository:

codium --version

1.116.02821
221e0a382c0be3a673a4e4cab0601344a0b3de3a
x64

The version and commit hash can change after VSCodium releases a new stable build. A successful check prints the application version, build hash, and architecture.

Method 2: Install VSCodium via Snap on Ubuntu

Snap is pre-installed on standard Ubuntu desktop installs and refreshes packages automatically in the background. On minimal installs, containers, or WSL environments, you may need to install Snap first.

If snap is unavailable, install it with sudo apt install snapd, then start a new login session before continuing.

Install VSCodium with the Snap Package

Snap handles refreshes automatically after installation, so you only need the install command:

sudo snap install codium --classic

The --classic flag disables strict confinement and gives the Snap full system access. VSCodium typically needs this for terminal integration and development tooling, but if you prefer a more sandboxed install, use the Flatpak method instead.

Verify the VSCodium Snap Installation

Confirm the Snap installed correctly and is tracking the stable channel:

snap list codium

Name    Version      Rev  Tracking       Publisher  Notes
codium  1.105.17075  495  latest/stable  vscodium   classic

The version and revision can change when the Snap stable channel updates. The important checks are the codium package name, latest/stable tracking channel, vscodium publisher, and classic confinement note.

Method 3: Install VSCodium via Flatpak on Ubuntu

Flatpak keeps VSCodium sandboxed and separate from system libraries, which some users prefer for desktop apps. This method requires the Flatpak package manager and Flathub repository setup.

Flatpak is not pre-installed on Ubuntu. If you have not set it up yet, install it with sudo apt install flatpak and restart your session before continuing. For detailed setup including the Flathub repository, follow our Flatpak installation guide for Ubuntu.

Enable the Flathub Repository for VSCodium

Add the Flathub repository so Flatpak can find the VSCodium package:

sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

The --if-not-exists flag skips the add operation if Flathub is already configured on your system.

Check that the Flathub remote is available at system scope before installing the app:

flatpak remotes

flathub	system

Install VSCodium with the Flatpak App ID

Use the VSCodium Flatpak app ID for a system-wide install so the app scope matches the system Flathub remote:

sudo flatpak install flathub com.vscodium.codium -y

Verify the VSCodium Flatpak Installation

Check the Flatpak app ID, version, and installation scope:

flatpak info com.vscodium.codium

VSCodium - Telemetry-less code editing

          ID: com.vscodium.codium
         Ref: app/com.vscodium.codium/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 1.112.01907
      Origin: flathub
Installation: system

The version can change as Flathub publishes new stable builds. The durable checks are the com.vscodium.codium app ID, stable branch, flathub origin, and the installation scope you intended to use.

Launch VSCodium on Ubuntu

Launch VSCodium from the Terminal on Ubuntu

For APT installation:

codium

For Snap installation:

snap run codium

For Flatpak installation:

flatpak run com.vscodium.codium

These terminal commands still start the graphical editor, so run them from an Ubuntu desktop session. Standard GNOME Wayland installs provide Xwayland compatibility through ubuntu-session; only add xwayland manually if a custom desktop stack removed it.

Launch VSCodium from the Ubuntu Applications Menu

• Click Activities in the top-left corner
• Click Show Applications (grid icon at the bottom of the dock)
• Find and click VSCodium

Troubleshoot VSCodium on Ubuntu

Fix VSCodium credentials.cc Sandbox Crash on Ubuntu 26.04 and 24.04

If the VSCodium .deb package crashes at launch with a Chromium/Electron sandbox error mentioning credentials.cc and “Permission denied (13),” Ubuntu 26.04 and 24.04 usually block unprivileged user namespaces until an AppArmor profile explicitly allows userns.

FATAL:sandbox/linux/services/credentials.cc:131] Check failed: . : Permission denied (13)
Trace/breakpoint trap (core dumped)

This happens because Ubuntu 26.04 and 24.04 enable AppArmor’s unprivileged user namespace restriction by default, and the VSCodium .deb package currently does not ship or load an AppArmor profile for the codium binary. Ubuntu 22.04 typically reports kernel.apparmor_restrict_unprivileged_userns = 0 and is usually not affected. If you want more background on this Ubuntu behavior, see our AppArmor guide for Ubuntu.

Check whether the restriction is enabled on your system:

sysctl kernel.apparmor_restrict_unprivileged_userns

kernel.apparmor_restrict_unprivileged_userns = 1

Confirm the VSCodium APT package and the host AppArmor profile set do not already provide a loaded codium profile. The command filters the package file list with grep; for more output-filtering examples, see our grep command guide:

dpkg -L codium | grep -i apparmor || echo "No AppArmor files found in codium package"
dpkg -S /etc/apparmor.d/codium 2>/dev/null || echo "No distro-owned /etc/apparmor.d/codium profile"
sudo aa-status | grep -i codium || echo "No loaded codium profile"

No AppArmor files found in codium package
No distro-owned /etc/apparmor.d/codium profile
No loaded codium profile

If a future VSCodium package or Ubuntu update provides and loads its own codium profile, do not create a duplicate profile unless the same crash still occurs.

Create a minimal AppArmor profile for the VSCodium binary, then reload it:

sudo tee /etc/apparmor.d/codium > /dev/null << 'EOF'
abi <abi/4.0>,
include <tunables/global>

profile codium /usr/share/codium/codium flags=(unconfined) {
  userns,

  include if exists <local/codium>
}
EOF
sudo apparmor_parser -r /etc/apparmor.d/codium

This profile leaves VSCodium otherwise unconfined but adds the required userns, permission so the Chromium sandbox can start. Snap and Flatpak installs already use their own sandboxing and AppArmor integration, so this fix is specific to the APT .deb package path.

Verify the custom AppArmor profile is loaded:

sudo aa-status | grep codium

   codium

Launch VSCodium again with codium. If it now opens normally, the AppArmor namespace restriction was the cause.

Install VSCodium Extensions on Ubuntu

Open the Extensions view in VSCodium with Ctrl+Shift+X, then search and install what you need. VSCodium uses the Open VSX registry by default instead of Microsoft’s Visual Studio Marketplace, so most popular extensions (Python, GitLens, Prettier, Docker, ESLint) are available.

Some Marketplace-only or license-restricted extensions (such as Microsoft’s official C# extension or Remote SSH) may not appear in Open VSX. If you rely on one of these, refer to the VSCodium documentation on extensions and marketplaces for workarounds. Extension updates are handled inside the editor, while application updates come from APT, Snap, or Flatpak depending on how you installed VSCodium.

VSCodium Compatibility with Ubuntu Derivatives

The Ubuntu scope is 26.04, 24.04, and 22.04. Ubuntu-based distributions often share enough APT tooling for the repository to work, but Snap policy, Flatpak defaults, package sources, and AppArmor behavior can differ. If you are not actually using Ubuntu, use the matching LinuxCapable guide to install VSCodium on Linux Mint, install VSCodium on Debian, or install VSCodium on Fedora. EndeavourOS is Arch-based, so do not use these Ubuntu APT commands there; use the Arch or AUR workflow documented by that distribution instead.

Manage VSCodium on Ubuntu

Update VSCodium on Ubuntu

Update VSCodium with the same package manager you used to install it:

For APT installations:

sudo apt update && sudo apt install --only-upgrade codium -y

For Snap installations:

sudo snap refresh codium

For Flatpak installations:

sudo flatpak update com.vscodium.codium -y

Remove VSCodium from Ubuntu

Each installation method leaves different packages and data behind, so remove VSCodium with the same package manager you used to install it. If you used more than one method while testing, repeat the matching removal block for each one.

For APT removal:

sudo apt purge codium -y

Remove the repository configuration and GPG key created by the APT method:

sudo rm -f /etc/apt/sources.list.d/vscodium.sources /etc/apt/sources.list.d/vscodium.list
sudo rm -f /usr/share/keyrings/vscodium.gpg /usr/share/keyrings/vscodium-archive-keyring.gpg

If you created the manual AppArmor profile from the troubleshooting section, unload and remove that article-created profile too:

if [ -f /etc/apparmor.d/codium ]; then
  sudo apparmor_parser -R /etc/apparmor.d/codium 2>/dev/null || true
  sudo rm -f /etc/apparmor.d/codium
fi

Refresh the package cache and verify that the package is no longer installed:

sudo apt update
dpkg -l codium 2>/dev/null | grep '^ii' || echo "codium is not installed"

The expected output should confirm that no installed codium package remains:

codium is not installed

Review orphaned packages before removing them. On systems with older package history, apt autoremove can include unrelated packages, so inspect the dry run first:

sudo apt autoremove --dry-run

If the preview only lists packages you no longer need, run the real cleanup:

sudo apt autoremove

Confirm the repository files are gone:

if [ ! -e /etc/apt/sources.list.d/vscodium.sources ] && \
   [ ! -e /etc/apt/sources.list.d/vscodium.list ] && \
   [ ! -e /usr/share/keyrings/vscodium.gpg ] && \
   [ ! -e /usr/share/keyrings/vscodium-archive-keyring.gpg ]; then
  echo "VSCodium repository files removed"
else
  echo "Review remaining VSCodium repository files"
fi

VSCodium repository files removed

Snap removal:

sudo snap remove --purge codium
snap list codium 2>/dev/null || echo "codium snap is not installed"

Flatpak removal:

sudo flatpak remove com.vscodium.codium -y
flatpak info com.vscodium.codium 2>/dev/null || echo "VSCodium Flatpak is not installed"

Remove VSCodium User Configuration Files

The following commands permanently delete your VSCodium settings, extensions, and cached data. The -rf flags remove directories recursively without a confirmation prompt, so export any important configurations or snippets before proceeding.

VSCodium stores user data in your home directory across several locations. To complete the uninstall for APT or direct package installs, remove these directories:

rm -rf ~/.config/VSCodium
rm -rf ~/.cache/VSCodium
rm -rf ~/.vscode-oss

For Snap and Flatpak installations, remove their sandboxed data directories if they still exist:

rm -rf ~/snap/codium
rm -rf ~/.var/app/com.vscodium.codium

To confirm the shell no longer finds codium, clear Bash’s command cache and check your PATH:

hash -r
command -v codium || echo "codium command not found"

The expected output should show that no host-side codium command remains:

codium command not found

Official VSCodium Documentation and Resources

For additional configuration options, troubleshooting, and community resources:

• VSCodium Official Website – Download links, project overview, and keyboard shortcuts
• VSCodium APT and RPM Repository – Current repository setup files and package architecture list
• VSCodium GitHub Repository – Source code, issue tracker, and release notes
• VSCodium GitHub Releases – Direct .deb packages, AppImage builds, source archives, checksums, tags, and release notes
• VSCodium Extensions and Marketplace Notes – Open VSX defaults, marketplace behavior, and extension source configuration

Conclusion

VSCodium is running on Ubuntu through APT, Snap, or Flatpak, with the APT repository giving most users the freshest stable package and native desktop integration. Updates and removal stay tied to the package manager you chose, extensions come from Open VSX by default, and newer Ubuntu releases can use the AppArmor profile fix if the .deb package hits the user namespace sandbox crash. If you need Microsoft’s Marketplace defaults, use our guide to install Visual Studio Code on Ubuntu.