How to Fix ‘NSPOSIXErrorDomain: 28’ No Space Left on Device in Safari

Browsing the web or downloading attachments in Safari on macOS only to have web pages crash with an alert reading “The operation couldn’t be completed. (NSPOSIXErrorDomain: 28 – No space left on device)” is a baffling error—especially when macOS Storage Settings shows tens or hundreds of gigabytes of available storage. In the Apple ecosystem, the NSPOSIXErrorDomain represents error codes originating from POSIX-compliant UNIX system calls, where error code 28 corresponds directly to ENOSPC (No space left on device). However, in modern versions of macOS utilizing the Apple File System (APFS), physical disk space is only one variable. Hidden APFS local Time Machine snapshots, exhausted filesystem inodes, corrupted WebKit offline blob stores, or swollen sandbox container scratch directories can prevent Safari from allocating memory-mapped cache space. This technical guide explains how APFS allocation boundaries affect Safari and provides step-by-step methods to resolve error 28.

Why Does Safari Report NSPOSIXErrorDomain: 28?

While the error text claims there is no space left, the root cause usually lies within disk allocation logic:

  • APFS Local Time Machine Snapshots: Time Machine automatically creates uncommitted local snapshots on your SSD. While macOS marks this space as “purgeable” in Finder, low-level UNIX system calls treat purgeable blocks as occupied until macOS purges them.
  • Corrupted WebKit Blob and IndexedDB Cache: Safari allocates scratch disk space for HTML5 video buffers and web applications inside its private sandboxed containers (~/Library/Containers/com.apple.Safari). Stale file descriptors block new allocations.
  • Exhausted Inodes on the System Volume: Having millions of tiny temporary files (such as Node.js modules, Git objects, or development caches) can exhaust filesystem file pointers (inodes) even with free gigabytes remaining.
  • Swollen System Virtual Memory (VM) Swap Files: Memory pressure forcing macOS to write multi-gigabyte swapfiles to /private/var/vm, exhausting dynamic disk scratch pools.
  • Restrictive Sandbox Container Quotas: Damaged permission bits in Safari’s sandboxed data folders preventing WebKit from creating temporary socket files.

Method 1: Thin and Delete Stale APFS Local Snapshots

Purging local Time Machine snapshots immediately reclaims uncommitted disk blocks, converting “purgeable” space into real available storage.

  1. Open Terminal via Spotlight (Command + Space) or Applications > Utilities.
  2. List all currently existing APFS local snapshots on your system disk:
    tmutil listlocalsnapshots /
  3. If you see a list of date-stamped snapshots (e.g. com.apple.TimeMachine.2026-11-14-...), thin them to reclaim blocks:
    tmutil thinlocalsnapshots / 10000000000 4
  4. To delete a specific stubborn snapshot directly:
    sudo tmutil deletelocalsnapshots 2026-11-14-123456
    (Replace the date string with the actual snapshot identifier listed in step 2).
  5. Verify that free physical space increases in Finder, then reload your webpage in Safari.

Method 2: Purge Safari’s Sandboxed WebKit Cache and Blobs

Deleting corrupted temporary web blobs stored in Safari’s sandboxed directory forces WebKit to rebuild clean storage queues.

  1. Quit Safari completely by pressing Command + Q.
  2. In Finder, click on Go in the top menu bar, hold down the Option key, and click Library.
  3. Navigate to ~/Library/Containers/com.apple.Safari/Data/Library/Caches.
  4. Select the folder named com.apple.Safari and move it to the Trash.
  5. Next, navigate to ~/Library/Safari and look for the folder named LocalStorage and Databases.
  6. Delete orphaned .db and .localstorage files.
  7. Empty the Trash and relaunch Safari.

Method 3: Check and Free Inodes on the APFS Container

Confirm that your filesystem hasn’t run out of file descriptors (inodes).

  1. Open Terminal.
  2. Check inode consumption across all mounted volumes:
    df -i /
  3. Look at the IUse% column. If the percentage is near 100%, your drive cannot create new files regardless of how many gigabytes appear free.
  4. Clear common temporary caches in user space:
    rm -rf ~/.Trash/*
    sudo rm -rf /private/var/log/asl/*

Method 4: Clear macOS Virtual Memory (Swapfile) Build-up

If heavy multitasking has created excessive swap partitions on disk, a clean reboot clears the VM directory.

  1. In Terminal, check the current size of your system swap files:
    ls -lh /private/var/vm
  2. If you see multiple swapfile entries totaling tens of gigabytes, your system has accumulated massive virtual memory overhead.
  3. Restart your Mac (Apple menu  > Restart).
  4. Upon reboot, macOS automatically purges expired swapfiles and resets the virtual memory paging pool.

Method 5: Reset Safari Website Data and Cache via Develop Menu

Purging WebKit memory caches clears runtime POSIX descriptor stalls.

  1. Open Safari.
  2. Click Safari in the menu bar > Settings > Advanced.
  3. Check Show features for web developers.
  4. Click on the new Develop menu at the top of your screen.
  5. Click Empty Caches.
  6. Go to Safari > Clear History, select all history, and click Clear History.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.