Should You Delete Language Files on a Mac?

In short: Old cleanup guides love telling you to strip out "unused" localization files to reclaim disk space. In practice the payoff is tiny and the headaches can be real. Here's when it's worth it, when to skip it, and what actually frees up meaningful space.

If you've searched for how to delete language files on Mac, you've probably seen the pitch: apps ship with dozens of translations you'll never use, and removing them frees up gigabytes. It's a classic cleanup tip. It's also mostly outdated. This guide walks through what language files actually are, what you'd really save, and why the honest answer for most people is: skip it.

What language files actually are

Most Mac apps are localized, meaning they include the interface translated into many languages. Inside an app bundle, these live in folders named with a language code and an .lproj extension, such as en.lproj, fr.lproj, or de.lproj. Each one holds strings, and sometimes images or nib files, for that language.

You can look for yourself without changing anything. In Finder, go to your Applications folder, right-click an app, and choose Show Package Contents. Open Contents, then Resources, and you'll see the .lproj folders. Browsing is completely safe; nothing is removed just by looking.

What you'd really save (probably not much)

Here's the part the old guides gloss over. A single language folder is usually a few hundred kilobytes to a couple of megabytes. Across your whole Applications folder you might reclaim a few hundred megabytes if you're aggressive. On a modern Mac with a 256 GB or larger SSD, that's a rounding error next to your Photos library, downloads, mail attachments, or leftover app caches.

There's also a moving-target problem. Even if you strip translations out of an app today, the next update reinstalls the full bundle and puts them right back. So any "savings" evaporate the first time that app updates, which for actively maintained apps can be every few weeks.

The real risks of stripping localizations

Deleting files from inside an app bundle is more invasive than clearing a cache. A few things can go wrong:

• Code signing breaks. macOS signs apps so it can verify they haven't been tampered with. Removing files from a signed bundle can invalidate that signature, and Gatekeeper may refuse to open the app or warn you it's damaged.
• Updates get confused. Some updaters compare the installed app against what they expect and re-download the whole thing, or fail, when files are missing.
• You lose a language you needed. If you ever switch your Mac's language, or hand the machine to someone who reads another one, those translations are simply gone until you reinstall.

None of this is catastrophic, but it's a lot of fragility for a few hundred megabytes.

Never touch system localizations

One firm rule: leave the language resources that belong to macOS itself alone. Anything inside the /System folder is protected by System Integrity Protection for good reason, and you should not try to delete files there. The disk you'd save is trivial and the downside is a system that behaves unpredictably. This article is only ever talking about third-party apps in your Applications folder, and even there the recommendation is caution.

If you still want to do it, do it safely

Maybe you're on a tiny older SSD and every gigabyte counts. Fair enough. The safe way to approach any cleanup is the same three habits every time:

1. Preview before you remove. Know exactly which files you're targeting and roughly how much space they represent before anything leaves your disk.
2. Stick to user-level, low-risk targets first. App caches, old logs, and downloads reclaim far more space than language files and carry almost none of the code-signing risk.
3. Send removals to the Trash, never permanently delete. If something breaks, reversibility is your safety net.

The single most important habit: anything you clean should go to the Trash so it stays recoverable. If an app misbehaves after a cleanup, you can drag the files back out of the Trash and you're exactly where you started. Permanent deletion removes that safety net for no real benefit.

What to clean instead

If your goal is genuinely more free space, spend your effort where it pays off. Empty the Trash. Clear old caches under ~/Library/Caches. Review the Downloads folder. Use the built-in tools too: open the Apple menu, choose System Settings, go to General, then Storage to see what's actually using your disk and get recommendations. That single screen will point you at gigabytes, not the megabytes hiding in language folders.

A calmer way to handle cleanup

If you'd rather not poke around by hand, a good cleaner does the safe-by-default work for you: it previews everything first, touches only user-level junk unless you opt into more, and sends removals to the Trash so they stay reversible. And because a cleaner has no reason to send your file list anywhere, you can confirm it stays quiet with a firewall like Little Snitch and expect to see zero outbound traffic.

For most people the top free pick is CoreSweep. It's free forever, previews before it removes anything, sends everything to the Trash, and ships with zero telemetry, with an optional one-time Pro upgrade ($49, no subscription). The best-value runner-up is SkoonMac, which is also free with a one-time Pro at just $19. Either one will do far more for your free space than chasing localization files ever will.

The honest bottom line on deleting language files on a Mac: for almost everyone, it's not worth the risk or the effort. Clear caches, empty the Trash, and let the built-in Storage tools guide you. Keep it reversible, and you'll never regret a cleanup.

Frequently asked questions

Is it safe to delete language files on a Mac?

Just looking is completely safe: you can right-click an app, choose Show Package Contents, and browse the .lproj folders without changing anything. Actually deleting them is riskier, because removing files from a signed app bundle can invalidate its code signature and cause Gatekeeper to refuse to open the app or call it damaged. It can also confuse updaters and leave you without a language you later need, so for most people it's not worth it.

How much space do language files take up on a Mac?

Not much. A single language folder is usually a few hundred kilobytes to a couple of megabytes, and stripping them across your whole Applications folder might reclaim a few hundred megabytes at most. On a modern SSD that's a rounding error next to your Photos library, downloads, and app caches. The savings also disappear the next time an app updates, because the update reinstalls the full bundle.

What should I clean instead of language files to free up space?

Spend your effort where it actually pays off: empty the Trash, clear old caches under ~/Library/Caches, and review your Downloads folder. You can also open the Apple menu, go to System Settings, then General, then Storage to see what's really using your disk and get recommendations. Those targets reclaim gigabytes and carry almost none of the code-signing risk that comes with editing app bundles.

← All Mac cleaning guides · Back to the comparison