All-In-One video library & player for iOS/macOS/tvOS
...
Best local and net disk movie/tv player on Mac, creating a local personal media library.
Price reduced to Free Trial!
  • $29.99
  • 0
Macbook 系统数据超过200G,教你怎么清空
Macbook 系统数据超过200G,教你怎么清空
  • Windsor
  • 2026-02-06 19:31:20


Macbook 系统数据超过200G,教你怎么清空

——以 Keynote 重度使用与 Time Machine 为例

一、问题描述 部分 macOS 用户在长期使用后,会发现 存储空间中的「系统数据(System Data)」占用异常增大,常见情况包括: 系统数据占用 200GB 甚至更高 https://cdn.okaapps.com/resource/%E5%9B%BE2.webp Finder 中无法定位对应文件 删除缓存、日志文件无明显效果 使用第三方清理工具无效 卸载并重装应用(如 Keynote)无效 重装系统后,使用一段时间问题再次出现

该问题在 Keynote、Final Cut、设计类工具等重度生产力用户中尤为常见。

二、已尝试但无效的常见方法 用户通常会尝试以下方式,但大多无法从根本上解决问题: 1.手动删除 ~/Library/Caches、Logs 等目录 2.使用 CleanMyMac、柠檬清理等第三方工具 3.卸载并重新安装 Keynote 4.通过“重新安装 macOS”方式重装系统

这些方法之所以效果有限,是因为并未触及「系统数据」膨胀的真实来源。

三、什么是「系统数据」? 需要明确的是: 系统数据并不是一个真实存在的文件夹,而是 macOS 无法准确分类的一组数据集合。

系统数据可能包含但不限于: macOS 系统临时文件 应用及系统缓存 用户资料库(~/Library)中的部分内容 Spotlight 无法识别类型的文件 应用包(Package)内部的大型资源文件 云同步服务的本地缓存(如 iCloud、OneDrive) iPhone / iPad 备份文件 已删除但未彻底清理的用户账户数据 Time Machine 本地快照(Local Snapshots)

因此,系统数据的体积不能通过简单清缓存或 Finder 浏览来判断和处理。

四、关键原因一:Time Machine 本地快照占用空间

  1. 本地快照的工作机制 即使没有连接备份硬盘或 NAS,macOS 仍会: https://cdn.okaapps.com/resource/%E5%9B%BE3.webp 每小时创建一次 Time Machine 本地快照 默认保留最近 24 小时 当备份目标长期未连接时,保留最近一次完整备份对应的本地快照

这些快照: 基于 APFS 文件系统 不显示为普通文件 统一计入「系统数据」

在某些情况下,本地快照可能占用 几十 GB 甚至上百 GB。 https://cdn.okaapps.com/resource/%E5%9B%BE4.webp

  1. 无法删除的原因

当 Time Machine 的备份目标是 NAS(如网络存储设备)时,如果发生以下情况: NAS 曾断开连接 网络路径或 IP 发生变化 备份未被系统重新“认领(Claim)”

系统可能会认为这些快照仍隶属于一个失联的备份目标,从而导致: tmutil 删除失败 报错 Stale NFS file handle 快照无法正常回收,占用空间持续存在

五、关键原因二:Keynote 等应用放大系统数据问题 Keynote 本身并非异常,但其工作特性会显著放大系统数据的占用: Keynote 文件本质是 包含大量资源的 Package 内部可能包含: 高清图片 视频 字体 动画与过渡资源 Spotlight 有时无法准确识别这些内容类型,相关资源容易被归类为「系统数据」

对于长期、高频制作大型演示文稿的用户,系统数据随使用时间增长是可预期现象。

六、有效解决方案(按优先级) 方案一:检查并恢复 Time Machine 备份状态(推荐) 1.打开「磁盘工具」 2.菜单栏选择 显示 APFS 快照 3.选择系统的 Data 卷 4.查看是否存在大量 Time Machine 本地快照 5.若使用 NAS 作为备份目标: 重新连接 NAS 在 Time Machine 设置中选择原备份 按提示 认领(Claim)现有备份

在备份关系恢复正常后,系统可自动管理和回收本地快照空间。

方案二:使用“空间分析工具”定位真实大文件 建议使用 只分析、不自动清理 的工具来判断空间分布,例如: GrandPerspective EtreCheck

目标是识别: 实际占用空间最大的文件或目录 是否存在异常集中的数据区域 而非依赖“一键清理”。

方案三:检查历史用户账户残留数据 如设备曾: 创建过多个用户账户 删除账户时未选择“同时删除主文件夹” 则旧用户的 Home 目录可能仍存在,并计入系统数据。

方案四:彻底重建数据环境(最后手段) 当系统数据已严重失控,且无法定位具体来源时,唯一彻底方案为: 1.完整备份当前数据 2.抹掉磁盘并重新安装 macOS 3.初始化系统后:仅迁移用户账户,不迁移系统设置、应用和 Library 数据

该方式可彻底清除历史遗留数据结构问题。

七、长期预防建议(Keynote / 内容生产用户) 将历史 Keynote 项目归档至外置硬盘或 NAS 避免长期在本机堆积大量大体积演示文件 保持 Time Machine 备份目标长期可用 避免使用自动“系统级清理”的第三方工具 定期使用空间分析工具监测磁盘使用趋势

八、结论

macOS「系统数据」占用异常增长,通常并非单一缓存问题,而是由 Time Machine 本地快照、应用包资源、历史数据继承结构 等多种因素共同导致。

只有明确系统数据的构成,并针对根本原因处理,才能真正、长期地解决空间占用问题。


Hottest Articles

Latest Articles

Mac System Data Exceeding 200GB? Here’s How to Actually Clear It — A Deep Dive with Heavy Keynote Usage and Time Machine as Examples I. Problem Overview After long-term use, some macOS users discover that “System Data” in Storage Settings grows abnormally large. Common symptoms include: System Data occupying 200GB or more https://cdn.okaapps.com/resource/图2.webp No corresponding files can be located in Finder Deleting caches or log files has little effect Third-party cleaning tools are ineffective Uninstalling and reinstalling apps (such as Keynote) does not help Even after reinstalling macOS, the issue reappears after some time This problem is especially common among heavy productivity users, such as those working extensively with Keynote, Final Cut Pro, or design tools. II. Commonly Tried but Ineffective Solutions Users typically attempt the following methods, most of which fail to solve the problem at its root: Manually deleting directories such as ~/Library/Caches and ~/Library/Logs Using third-party cleaning tools like CleanMyMac or similar utilities Uninstalling and reinstalling Keynote Reinstalling macOS via “Reinstall macOS” These approaches are limited because they do not address the real sources behind System Data inflation. III. What Exactly Is “System Data”? It is important to understand that: System Data is not a real folder, but rather a collection of data that macOS cannot accurately categorize. System Data may include, but is not limited to: macOS system temporary files Application and system caches Portions of the user Library (~/Library) Files Spotlight cannot classify Large resource files inside application packages Local caches from cloud services (such as iCloud or OneDrive) iPhone / iPad backup files Residual data from deleted user accounts Time Machine local snapshots As a result, System Data cannot be reliably inspected or reduced through simple cache deletion or Finder-based browsing. IV. Key Cause #1: Time Machine Local Snapshots Consuming Disk Space How Local Snapshots Work Even when no external drive or NAS is connected, macOS will: https://cdn.okaapps.com/resource/图3.webp Create a Time Machine local snapshot every hour Retain snapshots from the last 24 hours by default If the backup destination remains disconnected, keep local snapshots associated with the most recent full backup These snapshots: Are based on the APFS file system Do not appear as regular files Are entirely counted under System Data In some cases, local snapshots can consume tens or even hundreds of gigabytes. https://cdn.okaapps.com/resource/图4.webp Why They Sometimes Cannot Be Deleted When Time Machine uses a NAS or network storage device as its backup destination, the following situations may occur: The NAS was previously disconnected The network path or IP address changed The backup was not re-“claimed” by the system As a result, macOS may treat these snapshots as belonging to an unreachable backup destination, leading to: tmutil deletion failures Errors such as Stale NFS file handle Snapshots that cannot be reclaimed, causing persistent disk usage V. Key Cause #2: How Keynote and Similar Apps Amplify System Data Keynote itself is not malfunctioning, but its design inherently amplifies System Data usage: Keynote files are actually packages containing large numbers of resources These may include: High-resolution images Embedded videos Fonts Animation and transition assets Spotlight sometimes fails to correctly classify these resources, causing them to be grouped under System Data. For users who frequently create large, media-heavy presentations, steady growth in System Data over time is expected. VI. Effective Solutions (Prioritized) Solution 1: Verify and Restore Time Machine Backup Status (Recommended) Open Disk Utility From the menu bar, select Show APFS Snapshots Select the system Data volume Check whether a large number of Time Machine local snapshots exist If using a NAS as the backup destination: Reconnect the NAS Select the original backup in Time Machine settings Follow the prompts to claim the existing backup Once the backup relationship is properly restored, macOS can automatically manage and reclaim snapshot space. Solution 2: Use Disk Analysis Tools to Identify Real Space Usage It is recommended to use tools that analyze disk usage without automatically deleting files, such as: GrandPerspective EtreCheck The goal is to identify: Which files or directories consume the most space Whether disk usage is abnormally concentrated in specific areas Avoid relying on “one-click cleanup” tools. Solution 3: Check for Residual Data from Old User Accounts If the device previously: Had multiple user accounts Removed accounts without deleting their home folders Then old home directories may still exist and be counted as System Data. Solution 4: Rebuild the System Environment Completely (Last Resort) When System Data usage becomes severely unmanageable and no clear source can be identified, the only definitive solution is: Fully back up all current data Erase the disk and reinstall macOS During setup: Migrate only the user account Do not migrate system settings, applications, or Library data This approach completely removes legacy data structure issues. VII. Long-Term Prevention Tips (for Keynote and Content Creators) Archive older Keynote projects to an external drive or NAS Avoid storing large volumes of presentation files locally for long periods Keep the Time Machine backup destination consistently available Avoid third-party tools that perform automated “system-level cleaning” Periodically monitor disk usage with analysis tools VIII. Conclusion Abnormally large macOS System Data usage is rarely caused by a single cache or log issue. Instead, it is typically the result of Time Machine local snapshots, application package resources, and inherited historical data structures working together. Only by understanding what System Data actually contains—and addressing the root causes—can disk space issues be resolved effectively and long-term.