Chromebooks ship with small drives — often 32GB or 64GB — because the design assumption is that your files live in the cloud. That assumption works well until Android apps, Linux containers, and downloaded media start consuming space that was never there to begin with.
Here's what actually fills a Chromebook, and how to work within the constraint.
Understanding the layout
The Files app shows several distinct locations, and knowing which is which is most of the battle.
My files / Downloads — actual local storage on the device. This is the constrained resource. Everything the browser downloads lands here by default.
Google Drive — your cloud storage, shown as a location. Files here don't consume local space unless you mark them offline.
Play files — where Android apps store their data, if Android apps are enabled.
Linux files — a separate container, if Linux is enabled. This is a whole virtual machine and it consumes real space.
Removable devices — USB drives and SD cards.
The critical distinction: My files is local and small; Google Drive is cloud and large. Files saved to My files consume your limited storage. Files saved to Drive don't.
What actually fills a Chromebook
In descending order of frequency:
1. Downloads. Everything downloads here by default and stays. PDFs, images, installers, files opened once. This is almost always the biggest single find.
2. Android apps and their data. Games in particular. Android apps install locally and some are large. Their cached media accumulates.
3. The Linux container, if enabled. This is a full virtual environment — the container itself takes gigabytes before you install anything in it, and it doesn't shrink automatically when you delete things inside it.
4. Offline files from Drive. Files marked available offline are downloaded and held locally. Marking a large folder offline consumes exactly as much space as the folder.
5. Offline media — downloaded films, series, and music from streaming apps.
6. Browser cache and site data, which can grow substantial.
7. Multiple user accounts. Each user on the device has their own local storage, and a family Chromebook with four accounts has four sets of downloads.
The clean-up, in order
Check what's using space first: Settings → Device → Storage management. It breaks usage down by category.
1. Empty Downloads. Sort by size, delete the large items, then sort by date and delete anything over a few months old. Move anything worth keeping to Drive rather than deleting.
2. Empty the trash. The Files app has a trash that holds deleted items.
3. Review offline files. In the Files app, check what's marked available offline in Drive and unmark anything you don't currently need. This is often a large recovery.
4. Uninstall Android apps you don't use, and clear the cache and data of ones you keep. Android app storage is managed in Settings → Apps.
5. Clear browser data. Cached images and files, and site data for sites you don't use.
6. Shrink or remove the Linux container. If you're not using Linux, turning it off recovers several gigabytes immediately. If you are using it, the container can be resized in settings — and note that deleting files inside Linux doesn't shrink the container until you explicitly do so.
7. Remove unused user accounts from the device.
8. Check for offline media in streaming apps and remove what you've watched.
Working with Drive properly
Set Drive as your default save location where applications allow it, so files don't accumulate in Downloads by default.
Change the browser download location to a Drive folder. Settings → Downloads → Location. This one change prevents the most common cause of a full Chromebook.
Note the trade-off: downloads then require a connection to complete and to open. For most people on a Chromebook, that's already true of everything else.
Use the same folder structure you use elsewhere:
00 Inbox
01 Personal
02 Finance
03 Projects
04 Reference
05 ArchiveUnderstand that Drive files don't take local space unless marked offline. This is the whole design and it works well once you trust it.
Working offline
Chromebooks are usable offline, with preparation.
Mark files available offline before you need them — right-click in the Files app. Then confirm the download completed.
Enable offline mode for Google's document apps. This has to be turned on explicitly, per-browser, in advance. It downloads recent documents in the background so they can be opened and edited without a connection. Turn it on now rather than discovering it isn't on when you're on a plane.
Check which apps work offline. Many Android apps do; many web apps don't. Test in airplane mode at home before relying on it.
Changes sync when you reconnect. Watch for conflicts if the same document was edited elsewhere.
Using external storage
An SD card or USB drive is the cheapest way to extend a Chromebook, and it's genuinely useful.
A permanently-inserted SD card works well for media libraries, archives, and anything you don't need synced. Many Chromebooks have a card slot, and a card can sit in it indefinitely.
Format considerations: exFAT works well and handles large files. FAT32 is universally readable and limited to 4GB per file.
External drives work through the Files app like any other location.
One caution: external storage on a Chromebook isn't backed up by anything. Treat it as convenience storage, not as a home for the only copy of something.
Backup on a Chromebook
The Chromebook model means most of your data is already in the cloud, and that's not a complete answer.
What's protected: anything in Drive, and browser settings and extensions tied to your account.
What isn't:
- Anything in My files or Downloads that hasn't been moved to Drive
- Android app data, unless the app syncs to its own service
- Anything in the Linux container
- Files on an SD card or USB drive
The gap that matters: Drive is sync, not backup. Deletions propagate, and the trash retention window is limited. If your Chromebook is your only computer and Drive is your only storage, you have one copy in one account.
The fix: an occasional export of Drive to an external drive, or a second copy of your irreplaceable material somewhere independent. Once or twice a year is enough.
For Linux users: back up the container, or at minimum the files inside it, separately. It isn't covered by anything else.
Powerwash and what it takes
Powerwash — the Chromebook factory reset — is the standard fix for persistent problems, and it's genuinely effective because so little is stored locally.
It removes: everything in local storage, all local accounts, Android apps and their data, and the Linux container entirely.
It keeps: nothing local. Drive files are untouched because they're not on the device.
Before powerwashing: move anything in My files or Downloads to Drive, export anything from Android apps, and back up the Linux container.
Recovery after a powerwash is fast — sign in and your settings, extensions, and Drive access return within minutes. That speed is the Chromebook's genuine advantage.
Choosing a Chromebook, storage-wise
If you're buying:
32GB is workable if you genuinely live in the browser and use Drive properly.
64GB or more if you'll use Android apps, want offline files, or plan to enable Linux.
128GB+ if Linux is central to your use.
A card slot is worth having — it's cheap capacity for media and archives.
The general point: local storage on a Chromebook is a working buffer, not a library. Sizing it means asking how much you need available at once, not how much you own.
The setup checklist
- Browser download location set to a Drive folder
- Same folder structure in Drive as on your other devices
- Offline mode enabled for document apps
- Offline files reviewed and minimal
- Android apps pruned, caches cleared
- Linux container removed if unused
- Downloads emptied
- A copy of important Drive material exists outside the account
- SD card in the slot, if you have one and need capacity
Chrome OS storage management and feature names change with updates. Check current documentation for specifics.
Next in this series: File Paths, Drives, and Where Your Stuff Actually Lives