Developer Mode does not delete your files, but it does wipe your device and reset it to factory settings

When you turn on Developer Mode on a Chromebook, the system automatically performs a powerwash — a complete factory reset that erases everything on the device. This includes all your files, photos, downloaded documents, browser history, saved passwords, and any accounts you have signed in with. After the powerwash completes, you get a blank Chromebook that boots into Developer Mode.

The reason for this automatic wipe is security. Developer Mode removes many of the protections that normally keep a Chromebook locked down. Google treats this as such a significant change to your device's security that it requires you to start fresh rather than let you keep files on a device running in an unprotected state.

If you have files you need to keep, you must back them up before you turn on Developer Mode. Files stored in Google Drive, Google Photos, or other cloud services remain safe because they live on Google's servers, not on your Chromebook itself. Files saved only to your Chromebook's local storage will be gone after the powerwash.

Key Takeaways

  • Turning on Developer Mode triggers an automatic powerwash that deletes all local files, accounts, and settings on your Chromebook.
  • Files stored in Google Drive, Google Photos, or other cloud services are not affected because they exist on servers, not on your device.
  • You must back up any files saved only to your Chromebook before enabling Developer Mode.
  • Developer Mode removes security protections and makes your Chromebook more vulnerable to malware and unauthorized access.
  • Turning off Developer Mode also powerwashes your device, so you cannot toggle it on and off without losing data each time.

What gets deleted during the powerwash

The powerwash erases everything stored directly on your Chromebook's hard drive. This includes downloaded files, photos you took with the built-in camera, documents you created offline, browser bookmarks, saved passwords, and any extensions you installed. Your Google account sign-in information is also removed, so you will need to sign back in after the reset completes.

The one exception is anything you stored in the cloud before the powerwash. If you downloaded a file from Google Drive to your Downloads folder, that local copy is deleted — but the original file in your Google Drive remains untouched. If you took a screenshot and it auto-saved to Google Photos, that photo is still there. The rule is straightforward: if it lives on your Chromebook, it goes. If it lives on a server, it stays.

How to back up your files before enabling Developer Mode

The safest approach is to move everything important to Google Drive before you turn on Developer Mode. Open the Files app on your Chromebook, select the files or folders you want to keep, and drag them into your Google Drive folder. Google Drive syncs automatically, so once the files appear in the Drive folder, they are backed up to Google's servers.

For files you want to keep offline, you can also read them to an external USB drive or SD card. Plug in the external storage, open the Files app, and copy your files to the drive. This gives you a physical backup that you can access from any computer after the powerwash.

Photos and videos are easiest to back up through Google Photos. Open Google Photos in your browser, click the menu, and turn on backup. Any photos already on your Chromebook will upload to Google Photos automatically. Once they are uploaded, they survive the powerwash.

Why Developer Mode requires a powerwash

Developer Mode removes the security features that normally protect a Chromebook from malware and unauthorized changes. In normal mode, the system verifies that the operating system has not been tampered with each time you boot up. In Developer Mode, those checks are disabled so you can modify system files and install custom software.

Because an attacker could use Developer Mode to install malware that persists across reboots, Google requires the powerwash to may support that no malicious code is already on the device before you enter this less-protected state. It is a forced reset to a known-clean state.

This also means that if you turn off Developer Mode later, your Chromebook powerwashes again. You cannot toggle Developer Mode on and off without losing your data each time. This design choice makes it clear that Developer Mode is not a casual setting to experiment with — it is a deliberate choice that has permanent consequences for your files.

What you can do after Developer Mode is enabled

Once Developer Mode is on and the powerwash is complete, you have access to the Linux terminal and can install custom software, modify system files, and run code that a normal Chromebook would block. You can also disable some security checks and install unsigned extensions.

However, your Chromebook is now more vulnerable to malware. If you read and run a malicious program, it can do more damage than it would on a locked-down Chromebook. You also lose the protection of verified boot, which means malware could potentially persist even after a restart.

For most people, Developer Mode is not necessary. It is intended for software developers, security researchers, and people who want to run Linux applications or modify their Chromebook's operating system. If you are not sure whether you need it, you probably do not.

How to turn off Developer Mode and return to normal

To turn off Developer Mode, restart your Chromebook and press Space when you see the "OS verification is OFF" screen. Your Chromebook will powerwash again and return to normal mode with all security protections re-enabled.

Like turning it on, turning off Developer Mode also erases all your local files. Any files you created or downloaded while in Developer Mode will be gone. This is why you should back up anything important before you disable Developer Mode as well.

After the powerwash completes and your Chromebook reboots, you will see the normal login screen. Sign in with your Google account, and your Chromebook will read your settings, extensions, and bookmarks from your Google account. Files in Google Drive will be accessible again, but anything that was only stored locally is permanently gone.

Frequently Asked Questions

Can I recover files after I turn on Developer Mode?

No. The powerwash is a complete factory reset that overwrites the storage where your files were kept. Once the powerwash finishes, recovery is not possible. This is why backing up to Google Drive or an external drive before enabling Developer Mode is essential.

Do my Google Drive files disappear if I enable Developer Mode?

No. Google Drive files are stored on Google's servers, not on your Chromebook. They remain accessible after the powerwash. Sign back into your Google account after Developer Mode is enabled, and your Drive files will be there.

What if I only want to use the terminal without losing my files?

You cannot access the terminal without enabling Developer Mode, and Developer Mode requires a powerwash. There is no way to use Developer Mode features while keeping your local files. If you need the terminal, you must accept the data loss or use a different device.

Will my extensions and bookmarks come back after I turn off Developer Mode?

Yes, if they were synced to your Google account before you enabled Developer Mode. When you sign back in after the powerwash, Chrome downloads your bookmarks, extensions, and settings from your account. Extensions you installed only in Developer Mode will not return because they were not synced.

Is there a way to enable Developer Mode without a powerwash?

No. The powerwash is automatic and mandatory. Google does not offer an option to skip it. If you need to keep files on your Chromebook, you must move them to cloud storage or external media before you enable Developer Mode.