{
  "id": 18433271,
  "title": "Why do du and Finder show different sizes for the same folder",
  "url": "https://urgent.news/2026/11/06/du-finder",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-06T03:50:44.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/bestaitools-hi/du-aur-finder-ek-hii-pholddr-kaa-alg-alg-saaij-kyon-dikhaate-hain-17gc"
  },
  "original_language": "hi",
  "account": "The article discusses the difference between the apparent size of files and the actual disk space they occupy. It explains that the `du` command and the Finder often show different sizes for the same folder, with `du` counting the actual disk space used and the Finder showing the apparent size. The article provides examples of how this difference can occur, including with small files, sparse files, and hard links. It also describes how the `osFoundry` desktop app's Disk screen calculates disk usage.",
  "summary": "Run du -sh on a folder and compare it to the size in Finder, and the two often come out different, sometimes by several gigabytes. Neither one is wrong. They answer different questions: how long are the files, and how much disk space do they take up. When the disk is full, only the second question matters, and to get it right, it's not enough to just add up st_size. The rules below are from the osFoundry desktop app…",
  "key_points": [
    "\"du\" calculates file size by counting 4 KB allocation blocks.",
    "Finder shows file size based on actual bytes of data.",
    "Small files appear differently: 2-byte file is 2 bytes in Finder, 4 KB in du."
  ],
  "editors_take": "Discrepancies between these tools highlight the gap between actual data content and the physical storage blocks required by the APFS file system to hold that information.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}