How to Get Rid of a Broken File on a Chromebook
A broken file on a Chromebook can show up in a few different ways — a document that won't open, a download that sits greyed out in the Files app, a video that refuses to play, or an image that displays as a blank icon. Whatever the symptom, the underlying cause is usually the same: the file is corrupted, incomplete, or in a format ChromeOS can't read properly. Getting rid of it sounds simple, but it can be surprisingly stubborn depending on where the file lives and how it got there.
What Makes a File "Broken" on a Chromebook
Before deleting anything, it helps to understand what's actually wrong. A broken file typically falls into one of three categories:
- Corrupted file: The data inside the file got damaged — usually during a failed download, an interrupted transfer, or a storage error.
- Incomplete download: The file started downloading but never finished, leaving a partial file that can't be opened.
- Unsupported format: The file is technically intact but ChromeOS doesn't have a native app to read it, so it appears non-functional.
The fix for each is slightly different, but removal follows the same general path once you've identified the problem.
How to Delete a Broken File Using the Files App
The Files app is the primary way to manage local and cloud-based files on a Chromebook. Here's the standard removal process:
- Open the Files app from the launcher or shelf.
- Navigate to the folder where the broken file is stored — commonly Downloads, My Files, or a connected external drive.
- Right-click (or two-finger tap on the touchpad) on the broken file.
- Select Delete from the context menu.
- Confirm if prompted.
For most broken files stored locally, this is all you need. The file moves to the system trash and is cleared on the next empty or automatically after a set period.
When the File Won't Delete 🗑️
Sometimes a broken file resists deletion. This usually happens when:
- The file is actively in use by a background process or open tab
- The file sits on an external drive with permission issues
- A sync conflict has locked the file (common with Google Drive)
If the file won't delete normally, try closing all open apps and browser tabs first, then attempt deletion again. If it's on an external drive, safely eject and reconnect the drive before trying again.
Dealing with Broken Files in Google Drive
Google Drive files are handled differently from local files because they exist in the cloud, not on the Chromebook's internal storage. A file that appears broken in the Drive folder within the Files app may actually be fine on the cloud side — the issue could be a sync problem or a permissions conflict.
To remove a broken Drive file:
- Open the Files app and navigate to Google Drive.
- Right-click the file and select Remove (not Delete — Drive files are removed from sync, not permanently deleted immediately).
- To permanently delete, go to drive.google.com in the browser, find the file in Trash, and delete it from there.
If the file keeps reappearing after removal, it may be syncing back from another device. You'll need to delete it from the source device or through the web interface to stop it from returning.
Clearing Stuck or Partial Downloads
Incomplete downloads are a common source of broken files on Chromebooks. These partial files typically appear in the Downloads folder with their full filename but won't open correctly.
Two places to check:
- Files app → Downloads folder: Delete the partial file manually.
- Chrome browser → Downloads page (chrome://downloads): Find the failed download and click Remove to clear it from the download history. Note that removing it from the download history doesn't always delete the file from the Downloads folder — you may need to do both.
When the Problem Is Format, Not Corruption
If a file looks broken but is actually just in an unsupported format, deletion may not be necessary. ChromeOS handles common formats natively — JPEGs, PNGs, MP4s, PDFs, and Google Workspace files — but struggles with others like certain RAW image formats, less common video codecs, or proprietary document types.
In these cases, installing an Android app from the Google Play Store (available on most modern Chromebooks) can resolve the issue without touching the file at all. The distinction matters: a truly broken file should be deleted and re-obtained from its source; an unsupported file just needs the right app.
Variables That Affect How This Works
The right approach depends on a few factors that differ from one user to the next:
| Variable | How It Affects the Process |
|---|---|
| File location | Local, Drive, or external storage each has different deletion behavior |
| ChromeOS version | Older versions may have different Files app behavior or sync options |
| Google Drive sync settings | Offline sync can complicate Drive file removal |
| External drive format | FAT32, exFAT, NTFS drives have different write/delete permissions on ChromeOS |
| File type | Corrupted vs. unsupported vs. incomplete all require different approaches |
| Android app support | Not all Chromebooks support Play Store apps, limiting format workarounds |
🔍 A Note on Files That Keep Coming Back
If a deleted file reappears repeatedly, the issue is almost always a sync or backup system restoring it. This could be Google Drive, an Android app, or a connected cloud service. Identifying where the file is being synced from — not just where it appears — is the key step most users skip.
How straightforward the cleanup process turns out to be depends heavily on where the file lives, what created it, and which sync systems are active on your specific Chromebook setup.