How to Enable Developer Mode on a Chromebook

What developer mode is

Developer mode is a Chromebook state that turns off normal OS verification. A standard Chromebook checks its system at startup and repairs itself if something is wrong. Developer mode instead gives you access to lower-level Linux and debugging tools that are hidden or blocked in verified mode.

The Chromebook security model relies on verification at boot, a read-only operating system, and sandboxing. Developer mode is a deliberate exception to that model. It is useful for advanced Linux work, for running Crosh debugging commands, and for testing software that needs to boot with verification turned off.

What developer mode is not

Developer mode is not the same as the Linux container. Modern ChromeOS has a built-in Linux environment that is off by default and can be turned on from Settings. Google's ChromeOS.dev page describes Linux as seamlessly built into ChromeOS. You do not need developer mode for ordinary Linux apps, code editors, or the terminal.

If your goal is to install Linux packages or use a code editor, start with the built-in Linux feature. Follow the Linux setup guide first and treat developer mode as an extra step only when you need system-level access.

Before you start: back up and check policies

Enabling developer mode resets the Chromebook and erases local files. The exact message you see depends on the model, but expect a full reset. Copy anything important to Google Drive, an external drive, or another device first. If your Chromebook uses a school or work account, ask the administrator before you try, because managed devices often block developer mode.

Also consider what you are giving up. The normal update process keeps ChromeOS current for a long support window. Google's Auto Update policy page says ChromeOS devices receive 10 years of updates, and that a Chromebook checks itself at startup for tampering. Developer mode turns off part of that protection until you re-enable verification.

How to enable developer mode

The steps below work for most recent Chromebooks. Models from different makers can use slightly different key combinations, so follow any on-screen prompts. You need physical access to the keyboard because the process starts before the operating system loads.

Complete the steps in order:

• Back up your local files and make sure you know your Google Account password. You will need it after the reset.
• Turn the Chromebook off completely.
• Hold down Esc and the Refresh key, which is the circular arrow above the number row, then press Power. Release the keys when a recovery screen appears. If the screen asks for a recovery USB drive, ignore that prompt for now.
• Press Ctrl+D. The screen explains that OS verification is off, or that you are entering developer mode.
• Press Enter or follow the prompt to confirm. The Chromebook resets and may take a few minutes on the next boot.
• When the white screen appears with a warning about OS verification, press Ctrl+D again to continue booting into developer mode.

After the first developer mode boot

After the first boot, the startup screen pauses at that warning each time. You can press the space bar at that screen to turn verification back on, or press Ctrl+D to continue. The pause is normal and is the main visible sign that the device is in developer mode.

What you can do in developer mode

Developers use developer mode for tasks that normal ChromeOS intentionally prevents. A common goal is to open Crosh and run debugging commands that are not available in verified mode. You can also access a Linux shell outside the standard Linux container, use system tools to inspect hardware, and boot from a USB drive when a project requires it.

For everyday Linux development, the built-in Linux environment is usually enough. It installs a Debian environment and can run command-line tools, code editors, and IDEs, according to Google's Linux setup page. That same page also lists current limitations, including no camera support and no hardware acceleration for GPU or video decode yet. If you hit those limits, developer mode gives you another route to lower-level access.

• Run Crosh commands that are blocked in verified mode.
• Install a custom ChromeOS image or test a debug build.
• Boot from an external USB drive.
• Use system tools that need write access to the system partition.

Risks, updates and security

Developer mode makes the device less secure while it is active. Google's ChromeOS security page highlights verification at boot, a read-only operating system, data encryption, and app sandboxing. Turning off OS verification removes the first layer of that protection. A modified system that would normally be repaired by the startup self-check can keep running instead.

Keep developer mode active only for as long as you need it. Do not use it for daily browsing, banking, or schoolwork. If important accounts are on the device, turn verification back on before returning to normal use.

How to leave developer mode

To turn developer mode off, reboot the Chromebook and wait for the white warning screen. Press the space bar when it appears. ChromeOS re-enables verification and resets the device again, so local files are erased. After that, the Chromebook boots normally with the startup self-check restored.

If the device is managed, the administrator may also be able to enforce verified mode. When in doubt, contact whoever manages the Chromebook. You can compare managed business Chromebooks and, if you need to restore a device completely, use Powerwash or recovery.

Choosing a Chromebook for developer mode

Any Chromebook that can enter developer mode is worth trying, but the experience depends on hardware. Developer-mode debugging often involves a terminal, sometimes a second display, and a lot of open documentation. A larger screen and a comfortable keyboard help. Models with more RAM and faster processors handle builds better. You can compare Intel Core Chromebooks, models with more memory, and 2-in-1 Chromebooks to find a setup that suits your workflow.

The best choice also matches your use. If you are in a school program with a managed Chromebook, use the built-in Linux tools before asking for developer mode. If you are building a dedicated development device, start with a model that meets your performance expectations. For more detail, see the guide to programming on Chromebooks and the Chromebook RAM explainer.

What to pick for your use

Questions

Does enabling developer mode erase my data?

Yes. Moving from normal verified mode to developer mode resets the device and erases local storage. Back up anything you need before you start. You can keep copies in Google Drive or on an external drive.

Is developer mode required for Linux on a Chromebook?

No. ChromeOS includes a Linux development environment you can turn on from Settings. Google's Linux setup page says it creates a Debian environment with a terminal, command-line tools, and package manager support. Developer mode is a deeper setting for system-level work.

Will developer mode let me run every Linux app?

Not necessarily. Google's Linux setup page lists current limitations, including no camera support in Linux and no hardware acceleration for GPU or video decode yet. Some apps may also need more memory or storage than your model has.

Why does my Chromebook show an OS verification warning after reboot?

When developer mode is on, ChromeOS shows a warning screen at each boot. Press Ctrl+D to continue, or press the space bar to turn OS verification back on. Re-enabling verification resets the device.

Can my school or employer block developer mode?

Yes. Managed Chromebooks are controlled by policies from an administrator. If developer mode is missing or the device will not enter developer mode, contact your IT or school administrator. Google also advises contacting an administrator when Linux is not available on a managed device.

How do I return to normal mode?

Reboot, wait for the OS verification warning screen, and press the space bar. The device resets and re-enables normal startup checks. Local data is erased again, so keep backups.