Storage CleanerIs 256 GB enough for programming on a Mac?
Short answer: for web and backend development, yes, if you clean up build folders and caches regularly. For iOS development it's tight: Xcode and one simulator runtime alone take about 14 GB. For running local AI models it's not enough without an external SSD, because a single 70B model is about 42.5 GB.
How much of 256 GB you actually get
A 256 GB Mac shows 245.1 GB of usable space (measured on a MacBook Air with a 256 GB SSD). macOS, its recovery system and System Data then take a share of that before you install anything, so plan on roughly 200 GB for your apps, projects and tools.
What developer tools really take
| Kind of development | What takes space | Typical total | 256 GB verdict |
|---|---|---|---|
| Web (JavaScript/TypeScript) | node_modules: a new Next.js app is 429 MB, Vite + React 70 MB; npm/pnpm caches; editors | 10–40 GB | Fine, with a periodic node_modules clean-up |
| Backend with Docker | Images: node, python, postgres, mysql, redis and ubuntu are 1.3 GB compressed together, larger once unpacked; Docker's disk image grows and doesn't shrink on its own | 20–60 GB | OK, if you prune images and cap Docker's disk size |
| iOS / macOS (Xcode) | Xcode 5.1 GB + 8.5 GB per simulator runtime, DerivedData, device support, archives | 30–100 GB | Tight: keep one or two runtimes and clear DerivedData often |
| React Native / Expo | Everything from web and iOS, plus a new Expo app's 283 MB of node_modules and Android tools if you target Android | 40–120 GB | Tight |
| Python / data science | One virtual environment with PyTorch starts at 127 MB for the wheel alone; datasets; notebooks | 10–50 GB | Fine for most, datasets permitting |
| Local AI models | An 8B model is 4.9 GB, a 32B 19.9 GB, a 70B 42.5 GB; the same model in two apps is stored twice | 20–150 GB | Not enough without an external SSD |
Sizes measured September 2026: Xcode 26.5 and its iOS runtime on disk, npm packages resolved for each starter, Docker Hub arm64 images, PyPI macOS wheels, Ollama registry. Full method in our Mac developer storage statistics.
MacBook Neo, MacBook Air and Mac mini with 256 GB
The same numbers apply to every 256 GB Mac. The MacBook Neo ($599) starts at 256 GB with 8 GB of memory, which also limits local AI models to small ones (roughly 8B and below), so its storage is less likely to fill with models than with Xcode and project folders. If you're choosing between models, 512 GB is the comfortable minimum for iOS development; for web development 256 GB is workable.
How to make 256 GB work
- Clear build output you don't need: node_modules in old projects, Xcode DerivedData, Rust
targetfolders. - Keep only the simulator runtimes you test on: delete old runtimes.
- Clear package caches every few months: npm, pip, Homebrew and others.
- Cap Docker: lower the disk image limit in Docker's settings and shrink Docker.raw.
- Put models and big datasets on an external SSD: move Ollama models to an external drive.
Keep a small SSD tidy automatically. Storage Cleaner finds node_modules, DerivedData, runtimes, caches and AI models in one scan, shows what you haven't used in months, and can clean safe items on a schedule. Scanning is free.
Try Storage Cleaner freeFrequently asked
Is 256 GB enough for a computer science student? Usually yes: coursework is mostly small projects. It gets tight only if you also do iOS development or run local AI models.
Is an external SSD fast enough for development? For AI models, archives, datasets and old projects, yes. Keep the project you're actively building and Xcode on the internal drive for the fastest builds.
Why is my 256 GB Mac full when my files are small? Developer tools store most of their data in hidden folders that macOS reports as System Data. See why System Data is so large.