Zero-Byte Files
Also known as: empty files, 0 byte file, zero byte files
Zero-byte files are files whose content length is 0 bytes. They hold no data but still occupy a directory entry and inode/metadata, and they typically appear from interrupted downloads, crashed writes, placeholder/lock files, or failed app operations.
- A zero-byte file has no content but still uses a directory entry and inode/metadata.
- Common causes: interrupted downloads, crashed writes, and placeholder or lock files.
- Most are safe to delete, but some (lock/sentinel files) are intentional and shouldn't be removed.
Why zero-byte files appear
A file becomes zero bytes when it is created but never written, or when a write is interrupted before any data is flushed. Common sources are interrupted or failed downloads, an app that crashed mid-save, placeholder or lock files apps create to reserve a path, and temporary outputs from operations that errored out.
Because the file has no content, it shows a size of 0 bytes, but it still consumes a directory entry and a small amount of filesystem metadata (an inode on ext4/APFS-style filesystems). On flash storage the practical space cost is negligible, but large quantities of them clutter folders and can confuse sync, backup, and media-indexing tools.
Are they safe to delete?
Stray zero-byte files left behind by failed downloads or crashes are generally safe to remove, since they contain nothing. The caution is that some zero-byte files are intentional: lock files, sentinel/marker files, and placeholders whose mere existence signals state to an app. Deleting those while the owning app expects them can cause errors.
On a phone you usually encounter them in Downloads, app cache directories, and media folders. A cleaner can flag empty files alongside other junk, but the safe approach is to target empty files in user-facing locations (downloads, temp, leftover export folders) rather than blindly purging every 0-byte file across the system.