{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiedql5enqnaexddu7mgl5uuh7metaaol4mvdzbsbqaceeg6xinh5m",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mk7bed35a6l2"
  },
  "path": "/t/how-big-is-the-issue-of-no-file-size-obfuscation-with-some-encryption-tools/37391#post_1",
  "publishedAt": "2026-04-23T22:31:53.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "github.com/cryptomator/cryptomator",
    "File size obfuscation",
    "pgassmann"
  ],
  "textContent": "I have researched that some encryption tools like Cryptomator, have no file size obfuscation.\n\nSource:\n\ngithub.com/cryptomator/cryptomator\n\n####  File size obfuscation\n\nopened 08:05AM - 18 Jul 17 UTC\n\nclosed 08:08AM - 18 Jul 17 UTC\n\n\n\n          pgassmann\n        \n\n## Basic Info This is a - bug report. (privacy) - feature request. (randomi…ze file size) ## Description From reading the documentation on the [security architecture](https://cryptomator.org/architecture/) it looks like the file size is not obfuscated. The file size is not exactly the original file size, but all the headers and metadata have fixed size. So it should be possible to calculate the exact original file size from only the encrypted file. Especially for bigger files this could be enough information to identify the file(s). E.g. a collection of a series/movies. A small randomly sized block could fix that. E.g add a block of 0% to 1% of filesize.\n\nMy question is: How big of a deal is this for privacy?\nCryptomator protects the file name and content, but if someone stores media files, determining the exact file size, could enable someone else to identify the content. Because of for example a song.mp3 the unencrypted version is publicly available.",
  "title": "How big is the issue of no file size obfuscation with some encryption tools?"
}