How to Install Linux on a Chromebook Without Wiping It

Updated

install linux on chromebook

On a Chromebook, open Settings → About ChromeOS → Developers, click Set up next to “Linux development environment”, and wait. Google says setup “can take 10 minutes or more”. You do not need Developer Mode and nothing is erased. When it finishes, a Terminal window opens with a Debian environment, and you can install software with apt. Google’s steps are on Set up Linux on your Chromebook.

Turn on Linux on a Chromebook

  1. At the bottom right, select the time, then Settings.
  2. Select About ChromeOS, then Developers.
  3. Next to “Linux development environment”, select Set up.
  4. Follow the on-screen instructions and wait for the Terminal window to open.

Google’s pages word the menu differently. The backup page says Settings → Advanced → Developers, and the ChromeOS.dev setup guide says to expand “Advanced” and go to “Developers”. If one path is missing, look for the other. The feature is not labelled “Beta” on Google’s setup page.

Open Terminal and install apps with apt

The Terminal app is your Debian shell. ChromeOS.dev suggests pinning it to the shelf (right-click its icon, then Pin), and updating the package index first:

sudo apt update
sudo apt install -y gnome-software gnome-packagekit

The second line adds GNOME Software and PackageKit, a graphical way to find and update apps (ChromeOS.dev). Install a command-line tool with sudo apt install <package>. For a program that ships as a .deb file, such as Visual Studio Code, download it and double-click it in the Files app: ChromeOS.dev says Linux on ChromeOS supports “double-click to install for .deb files”. To fix a misbehaving setup, Google suggests restarting the Chromebook and running sudo apt-get update && sudo apt-get dist-upgrade.

Share files and folders with Linux

To copy a file in, drag it onto “Linux files” in the Files app. To share a folder without copying it, right-click it in Files and choose Share with Linux. Inside Linux the shared folders are under /mnt/chromeos, so cd /mnt/chromeos lists them. Manage them later in Settings → Developers → Linux development environment → Manage shared folders. The ChromeOS.dev FAQ says USB access is enabled on a case-by-case basis under Settings → Developers → Linux → USB preferences. Google lists cameras and GPU hardware acceleration as not yet supported.

Back up and remove the Linux environment

To back up, go to Settings → Advanced → Developers → Linux → Back up and restore, select Back up, choose a place under “My files” and save. Google says the backup “should be a .tini file”, and restoring on another Chromebook needs the same architecture (x86 or ARM). Restoring deletes your current Linux apps and data first. To remove Linux, go to Settings → About ChromeOS → Developers → Linux development environment, and under “Remove Linux development environment” select Remove.

Why the Linux option is missing

Symptom Cause, as Google documents it
Work or school Chromebook, no Set up button Google: “If you use your Chromebook at work or school, you might not be able to use Linux.” Administrators can control access to containers and VMs, so ask yours.
Older model Chromium’s list says “all devices launched in 2019 and later support Linux on ChromeOS” unless otherwise specified; models from before 2019 are listed one by one on the supported-systems page.
Wanted a different distro ChromeOS.dev says other distros can run in the container, but only the default Debian container is tested, so things may break.

Which Linux can a Chromebook run

The built-in Debian container is the supported route. ChromeOS Flex is a different thing: it replaces the operating system on a Windows, Mac or Linux PC, and Google says it “completely erases all data” and that “Dual booting is not supported on ChromeOS Flex devices”. It is not a way to put Linux on a Chromebook.

When Developer Mode is the wrong tool

Developer Mode erases the device. The Chromium OS developer-mode guide says “transitioning to or from developer mode will trigger a Mode Transition Wipe which wipes the stateful partition of the device”, and Google’s recovery page warns that recovery “permanently erases everything on your Chromebook’s hard drive”. Google’s Auto Update policy says “ChromeOS devices receive 10 years of updates”. In its passage on ChromeOS Education Upgrade and ChromeOS Enterprise Upgrade, the same page says that after a device’s final automatic update, existing and future policies “may not work as intended, and technical support will not be provided”.

crouton and GalliumOS history

crouton, the older chroot tool that needed Developer Mode, is end-of-life: its repository is archived and its last commit says so. The GalliumOS release page last mentions version 3.1 from 2019-12-22, and the chrx dual-boot installer’s last commit is dated 2020-11-21, so neither is a safe choice for a machine you browse the web on. I put the crouton, GalliumOS and chrx checks, plus the Google wording quoted here, in a script you can run: /verify/install-linux-on-your-chromebook.sh makes read-only requests only. The crouton check, run on 15 October 2026:

$ curl -s https://api.github.com/repos/dnschneid/crouton | \
    python3 -c 'import json,sys; d=json.load(sys.stdin); print(d["description"], "| archived:", d["archived"], "| last push:", d["pushed_at"])'
Chromium OS Universal Chroot Environment (EOL) | archived: True | last push: 2025-03-30T01:56:01Z

$ curl -s "https://api.github.com/repos/dnschneid/crouton/commits?per_page=1" | \
    python3 -c 'import json,sys; c=json.load(sys.stdin)[0]; print(c["sha"][:8], c["commit"]["committer"]["date"], c["commit"]["message"].splitlines()[0])'
59e36db1 2025-03-30T01:53:48Z crouton is now EOL

What was tested here

No ChromeOS device was available, so no step on this page was performed on a Chromebook. Every step is taken from the Google and ChromeOS.dev pages linked above (read on 15 October 2026); only the crouton output above was run by me, on macOS.

Photo of author
Sudhir P. founded HeatWare.com in 1999 and has built and operated it full-stack ever since; it is now used by more than 88,000 people. He writes here about the PostgreSQL, MySQL, Linux and DevOps work that keeps it running. Articles are rewritten only after the commands in them have actually been run, and the verification scripts are published alongside them so anyone can check the claims. Reach him at blog@heatware.net.