Scenarios & devices

Mac Storage Tips for Students on a Budget Laptop (Free Up Space the Easy Way)

Running low on disk space is practically a rite of passage for college students. Between course PDFs, project files, design assets, and whatever your development environment has silently accumulated, the 256 GB SSD on a budget MacBook fills up faster than expected. These mac storage tips for students cover every major space hog — from the obvious Downloads folder to the hidden caches your coding tools leave behind — so you can reclaim meaningful gigabytes without spending a dollar or breaking anything.

Why Student Macs Run Out of Space So Quickly

Unlike a work machine managed by IT, a student laptop accumulates files from many directions at once: class recordings, code repositories, Node modules, Xcode simulators, virtual machine snapshots, and years of browser downloads. macOS also reserves space for system snapshots (used by Time Machine's local backup feature) and iCloud optimizations. The result is that 20–30 GB can vanish within a single semester with no single obvious culprit.

Where the Space Actually Goes: A Quick Breakdown

Before deleting anything, it helps to know what the biggest categories typically are on a student machine. The table below shows common folder locations and realistic size ranges for each.

Category Typical Location Typical Size Safe to Clear?
App caches ~/Library/Caches 2–15 GB Yes — apps rebuild them
Xcode DerivedData ~/Library/Developer/Xcode/DerivedData 5–40 GB Yes — Xcode rebuilds on next open
iOS/watchOS simulators ~/Library/Developer/CoreSimulator/Devices 5–30 GB Yes — delete unused runtimes only
Node modules node_modules/ inside each project 0.5–5 GB each Yes — run npm install to restore
Maven local repo ~/.m2/repository 1–10 GB Yes — Maven re-downloads as needed
Rust build artifacts ~/.cargo/registry and project target/ 3–20 GB Yes — cargo clean per project
Downloads folder ~/Downloads 1–30 GB Review manually
Trash (not emptied) System Trash Varies Yes — empty the Trash

Understanding what is taking up space on your Mac is always the right first move before deleting anything blindly.

How to Clear App Caches Without Uninstalling Anything

Application caches live in ~/Library/Caches. macOS hides the Library folder by default — hold Option and click the Go menu in Finder to reveal it. Inside you will see one folder per app. The sub-folders for browsers (Chrome, Firefox, Brave) are frequently the largest, followed by Slack, Zoom, and Spotify.

  1. Open Finder, press Shift-Command-G, and type ~/Library/Caches.
  2. Sort by Size (right-click the column header and enable the Size column).
  3. Quit the app whose cache you want to clear — do not delete caches for running apps.
  4. Move the folder for that app to the Trash, then empty the Trash.
  5. Reopen the app; it will regenerate a fresh, smaller cache over time.

A tool like Crumb can audit all of these at once and show what is safe before you delete, which saves time when you have a dozen apps to evaluate.

Tame Your Development Environment

If you are studying computer science, software engineering, or data science, your development tools are almost certainly the largest single space drain on your laptop.

Xcode and Simulators

Xcode stores build artifacts in ~/Library/Developer/Xcode/DerivedData. You can safely delete everything inside that folder — Xcode rebuilds it the next time you compile. Simulator runtimes are stored in ~/Library/Developer/CoreSimulator/Devices and can be managed directly in Xcode under Xcode > Settings > Platforms. Delete runtimes for iOS versions you do not actively test against — this alone can reclaim 10 GB or more on a machine used for iOS coursework.

Node.js Projects

Every JavaScript or TypeScript project clones its dependencies into a local node_modules/ directory. If you have ten projects from three different courses, you might have 10–50 GB of duplicated packages sitting in directories you have not opened in months. To find them all, run this in Terminal:

find ~ -name node_modules -type d -prune 2>/dev/null

Delete the node_modules folder from any project you are not actively working on. Run npm install (or yarn or pnpm install) to restore it in under a minute when you return to that project.

Maven and Java Projects

Maven stores every downloaded JAR in ~/.m2/repository. This directory grows silently across semesters. You can delete the entire folder; Maven will re-download only what your current projects actually need the next time you build. Similarly, Gradle caches live in ~/.gradle/caches and can be cleared the same way.

Rust Projects

Rust keeps a package registry at ~/.cargo/registry and compiled build output in the target/ directory of each project. Run cargo clean inside a project folder to remove its build artifacts. For the registry itself, the tool cargo cache -a (installable via cargo install cargo-cache) can remove stale entries automatically.

Clean Up Downloads, Screenshots, and Desktop Clutter

Students accumulate files in predictable places: lecture slides downloaded for a deadline, research papers saved during late-night study sessions, and installer packages that were opened once and never touched again.

  • Downloads folder (~/Downloads): Sort by Kind to group disk images (.dmg), ZIP archives, and PDFs. Installer images (.dmg, .pkg) are safe to delete once the app is installed.
  • Desktop (~/Desktop): Files on the Desktop are in RAM-backed memory regions on some workflows; clearing them is tidy and occasionally helps performance.
  • Screenshots: macOS saves screenshots to ~/Desktop by default (adjustable in the Screenshot app under Options). A semester of screenshots adds up — move the ones you need into a dedicated folder and delete the rest.

Manage iCloud and "Optimize Storage" Settings

If your Mac is enrolled in iCloud Drive, macOS may show items as "stored in iCloud" while keeping local copies that consume real disk space. Go to System Settings > Apple ID > iCloud > Manage Storage (on macOS Sequoia and later) to review what is synced. Enable Optimize Mac Storage under iCloud Drive settings — macOS will evict full-resolution files to iCloud and keep lightweight placeholders locally, freeing space automatically over time.

Also check System Settings > General > Storage. macOS offers built-in recommendations such as emptying the Trash automatically, removing watched Apple TV content, and reducing local Time Machine snapshots.

Remove Apps You No Longer Use

Dragging an app to the Trash removes the main binary but leaves behind preference files, caches, and support folders scattered across ~/Library. For a thorough removal, it is worth learning how to completely uninstall apps on Mac so the leftover files do not continue occupying space semester after semester.

A Sustainable Habit: Semester-End Cleanups

The most effective approach is to treat storage like you treat your physical desk at the end of term. At the end of each semester:

  • Archive finished course projects to an external drive or cloud storage, then remove them from your laptop.
  • Run cargo clean in any Rust projects you are parking.
  • Delete node_modules from inactive JavaScript projects.
  • Clear ~/Library/Developer/Xcode/DerivedData entirely.
  • Empty ~/Downloads after moving anything you actually want to keep.
  • Review ~/Library/Caches and clear the largest entries.

Doing this twice a year keeps a budget MacBook breathing comfortably without requiring an upgrade. The storage ceiling that felt tight in September usually looks roomy again after a focused 30-minute cleanup.

Reclaim your disk in one click

Crumb audits your whole Mac, tells you what's safe to delete, and frees the space in seconds — private, local, and Apple-notarized.

Download Crumb for macOS

Frequently asked questions

Is it safe to delete ~/Library/Caches on a Mac?
Yes, deleting the contents of ~/Library/Caches is generally safe. Apps store temporary data there to speed things up, but they rebuild the cache automatically the next time they run. Quit an app before clearing its cache folder to avoid any file-in-use errors.
Will deleting Xcode DerivedData remove my source code?
No. DerivedData contains only compiled build artifacts, indexes, and generated files — not your actual Swift, Objective-C, or other source files. Deleting ~/Library/Developer/Xcode/DerivedData just means Xcode will need to reindex and recompile your project the next time you open it.
How much space can I realistically recover on a student MacBook?
It depends on how long the machine has been in use and whether you do any coding. Students with development tools installed commonly recover 20–60 GB by clearing DerivedData, node_modules from old projects, app caches, and the Downloads folder. Even a non-developer can typically free 5–15 GB from caches and Downloads alone.
If I delete node_modules, will I lose my project code?
No. Your source code, package.json, and lock files remain untouched. The node_modules folder contains only installed dependencies that npm, yarn, or pnpm can restore in minutes by running the install command inside the project folder.
Does emptying the Trash actually free up disk space immediately?
Yes. macOS does not reclaim the space occupied by deleted files until the Trash is emptied. After emptying, the space is immediately available for new files. If the Trash appears empty but storage still seems low, check System Settings > General > Storage for local Time Machine snapshots, which macOS manages separately.