How to Install Linux on a Chromebook (Crostini or Full Ubuntu)

The safest way to install Linux on a Chromebook is Google’s built-in Linux development environment (Crostini): turn it on in Settings, wait for setup, then use a Debian terminal and apt—no USB wipe of ChromeOS and no Developer Mode. That is the right first path for coding, CLI tools, and many Linux apps beside ChromeOS.

Only go further if you need a full Ubuntu desktop that replaces ChromeOS on a supported Intel/AMD Chromebook. That route can require Developer Mode, firmware changes, and a data wipe. Success for most people means Terminal opens, sudo apt update works, and Linux apps appear in the launcher—while ChromeOS still boots normally.

If you already know your case: school/work managed device → check admin policy; want Linux apps without wiping → Crostini; want Ubuntu as the only OS → full install branch (destructive).

For the full PC install overview with Ubuntu, start with how to install Linux on a PC.

Pick Your Path Before You Touch Firmware

Goal	Method	Wipes ChromeOS data?	Best for
Linux apps + terminal beside ChromeOS	Official Linux (Crostini)	No	Most users
Full Ubuntu/Linux as primary OS (x86_64)	Firmware + Ubuntu USB (community)	Yes (plan a wipe)	Power users on supported Intel/AMD models
ARM Chromebook full Ubuntu	Model-specific / often limited	Often yes	Advanced only—verify board support first
Managed school/work Chromebook	May be blocked	—	Ask your admin

Ask Ubuntu’s current Intel/AMD Chromebook answers say the same thing up front: if you do not want to remove ChromeOS, use Set up Linux on Chromebook instead of a classic USB install.

Obsolete “ChrUbuntu / GalliumOS only” tutorials are not the default for modern devices.

Method 1 (Recommended): Turn On Linux on ChromeOS (Crostini)

This is Google’s supported feature. Official help: Set up Linux on your Chromebook.

Requirements

• A Chromebook that lists Linux support (check Google’s device list / Settings—if Linux development environment is missing, your model or policy may not support it)
• Free storage for the Linux disk image (you choose size during setup; you can expand later)
• Not blocked by school/work admin policy

Steps

1. Back up important ChromeOS files to Google Drive or external storage (always wise before system changes).
2. Sign in to ChromeOS (non-guest).
3. Bottom right → time → Settings.
4. Open About ChromeOS → Developers (labels can vary slightly by ChromeOS version).
5. Beside Linux development environment, select Set up / Turn on.
6. Choose a Linux username and disk size.
7. Select Install and wait (often 10+ minutes).
8. When finished, a Terminal window opens with a Debian environment.

Pin Terminal to the shelf for quick access.

First commands inside Linux

Update packages (Google’s troubleshooting path uses this family of commands):

sudo apt-get update && sudo apt-get dist-upgrade

Or the common modern form:

sudo apt update
sudo apt upgrade

Install tools with APT, for example:

sudo apt install git build-essential

Linux GUI apps you install typically appear in the ChromeOS launcher. Share folders with Linux from ChromeOS Files when you need project access (enable sharing for the folders you choose).

What Crostini is (and is not)

• Is: a Debian Linux environment in a VM/container on top of ChromeOS
• Is not: replacing ChromeOS, dual-booting a separate Ubuntu partition by default, or giving unrestricted hardware access
• Google notes limits such as cameras, many USB devices, Android emulators, and hardware GPU acceleration not being fully supported yet—verify current Help Center limits if you need those features

Turn Linux off later

Settings → About ChromeOS → Developers → Linux development environment → Remove. This deletes the Linux environment and its apps/files inside it—back up first.

Method 2: Full Ubuntu Install (Replace ChromeOS) — Advanced

Use this only if Crostini is not enough and you accept losing ChromeOS as the daily driver (or need a true bare-metal Linux desktop).

Critical warnings (read before Developer Mode)

1. Enabling Developer Mode wipes local user data on the Chromebook. Back up everything first.
2. Full ROM / replacing stock firmware can remove ChromeOS recovery paths and carries brick risk if flashing fails—follow current docs for your exact board.
3. Intel/AMD (x86_64) Chromebooks are the realistic target for mainstream Ubuntu USB installs. ARM Chromebooks need separate, board-specific guidance—do not follow an x86 guide on ARM.
4. Managed devices may block Developer Mode entirely.

Ask Ubuntu’s Intel/AMD Chromebook Ubuntu guide states clearly: installing Ubuntu this way removes ChromeOS; if you do not want that, use ChromeOS Linux setup instead.

High-level workflow (x86_64)

Exact key combos and firmware options depend on model year. Treat this as a map, then follow current documentation for your board name (for example from chrome://version / recovery label):

1. Backup all ChromeOS data.
2. Create ChromeOS Recovery media for your model (so you can restore ChromeOS later if needed).
3. Enable Developer Mode from Recovery (typically Ctrl+D flow)—expect a data wipe and a boot warning screen.
4. For many devices, community firmware helpers (commonly discussed as MrChromebox utilities) update RW_LEGACY (boot USB/Linux while keeping more stock behavior) or install UEFI Full ROM (device behaves more like a normal PC; ChromeOS usually will not boot afterward).
   • Run firmware tools from the environment those projects document (often a VT2 chronos shell—not from Crostini, which cannot flash firmware).
   • Full ROM typically requires disabling hardware write-protect—model-specific hardware step.
5. Write an official Ubuntu Desktop ISO to USB with a UEFI-capable tool (avoid known-broken writers called out by firmware docs).
6. Boot the USB (often Ctrl+L on Developer Mode screens for legacy/RW_LEGACY paths, or direct UEFI boot after Full ROM).
7. Install Ubuntu to internal storage. Expect keyboard, trackpad, audio, or firmware quirks—community sound/kernel notes are model-specific; verify for your board before assuming “it just works.”
8. Only after Ubuntu boots cleanly, remove recovery media and set firmware boot options carefully.

If anything fails mid-flash, stop and use your recovery plan—do not keep reflashing randomly.

Safer alternative if you only need “real Ubuntu” sometimes

• Keep ChromeOS + Crostini for daily work
• Or boot Ubuntu from USB without wiping (where your firmware path allows USB boot) for try-before-replace testing

School and Work Chromebooks

Google’s Help page warns: if the Chromebook is managed, Linux may be disabled. Contact your administrator. Do not try firmware/Developer Mode bypasses on devices you do not own—that can violate policy and brick enrollment.

Fix Common Problems

“Linux development environment” missing in Settings

Model unsupported, ChromeOS too old, or admin policy. Update ChromeOS first; if still missing, Crostini is not available—full Linux is a different, riskier project.

Terminal / penguin container fails to start

Restart the Chromebook. From Terminal’s shelf icon, try shutting down Linux, then reopen. Update packages when Terminal works again. If corruption persists, back up Linux files and remove/recreate the Linux environment.

apt errors after setup

Run Google’s update command pair, restart, retry. Check network permissions for Linux.

Need microphone in Linux apps

Enable Allow Linux to access your microphone under Linux settings (per Google Help).

Full Ubuntu: no USB boot / no keyboard

Default Chromebook firmware blocks normal USB installs—that is why firmware/Developer Mode paths exist. Keyboard/audio regressions after custom firmware are model-specific; keep Recovery media ready.

Want ChromeOS back after Full ROM

Restore stock firmware per the firmware project’s recovery docs, then use official ChromeOS Recovery—order matters; do not skip documented restore steps.

After Linux Works on Chromebook: Notes, Docs, and PDFs

After Crostini or a full Ubuntu install starts correctly, the next task is often school notes, lightweight office files, or PDFs that still have to move between ChromeOS, Linux, and Windows classrooms.

WPS Office for Linux gives that Linux side a familiar desktop suite for Writer, spreadsheets, slides, and PDFs.

What you need next	What WPS gives you
Turn Chromebook Linux work into Office-compatible files	Strong .docx / .xlsx / .pptx layout fidelity when files move between Linux, Windows, and macOS
One place for notes, sheets, slides, and PDFs	Free core suite: Writer, Spreadsheet, Presentation, plus PDF view/edit/convert tools
A familiar desktop UI for switchers	Ribbon-style apps with a lighter footprint than many heavy suites
A trusted install path	Official DEB (Ubuntu/Debian/Mint) and RPM packages from the vendor

Use the official WPS Office for Linux download page, then install the local package with sudo apt install ./wps-office_VERSION_amd64.deb on a full Ubuntu setup. Once Linux is ready, you can move plain notes into DOCX or export PDF for teachers, teammates, or classmates who are not using the same apps.

FAQ

What is the easiest way to install Linux on a Chromebook?
Turn on Linux development environment in ChromeOS Settings (Crostini). No Developer Mode required.

Does enabling Linux wipe my Chromebook?
Official Crostini setup does not wipe ChromeOS the way Developer Mode does. Developer Mode and full OS replacement do wipe or replace data—back up first.

Can I dual boot ChromeOS and Ubuntu?
Possible on some Intel/AMD devices with community firmware (for example RW_LEGACY + USB/internal Linux), but it is advanced. Most users should start with Crostini.

Is ChrUbuntu still the method I should follow?
Treat old ChrUbuntu guides as historical. Prefer Google’s Linux feature first; use current board-specific firmware + Ubuntu docs only if you need bare metal.

Will Linux apps see my GPU and camera?
Crostini still has official limitations (camera and hardware acceleration among them). Check Google’s current “what’s not supported” list.

ARM vs Intel Chromebook—does it matter?
Yes. Full Ubuntu USB installs are mainly practical on Intel/AMD. ARM needs board-specific images and expectations.