👀 See Sanity in action: Watch product demo now →

Why are there Differences in Image File Sizes (Compared to the Browser) when Querying for an Image by ID?

4 replies
Last updated: Jan 19, 2021
Hey, trying to understand the difference in sizes when querying for an image by id. For example:• Sanity client says size = 933478
• browser request content-length = 1249489
• browser request size (network tab) = 1.3MB
So why is the size reported by the client so different from wha the browser reports?
Jan 14, 2021, 9:37 PM
Could you give some more information here? What do you mean by "Sanity client says"?
The last two I would
assume are just rounding differences - 1.24 vs 1.3 MB, though if you give me a URL I could look into it.
If the first is the size that the
sanity.imageAsset
record reports, it could be that the image gets re-encoded with a higher quality than the original (eg if you've uploaded a JPEG with quality 40, it might get re-encoded with quality 75). That's something we should look into improving.
Jan 15, 2021, 4:55 AM
My mistake for not being clear. I mean't that when I query for the image by ID using Sanity client the size in the response is a little lower than what the browser reports. Below is the response with most of the fields removed:
[
  {
    ...
    "size": 933478,
    "uploadId": "oFlMTxzgoNxbTsIJDJ1cV7hHAOmVH6u4",
    "url": "<https://cdn.sanity.io/images/oijolsw2/jc/66cbb2c06dbbffcf77c08d26074273752fefa632-828x780.png>"
  }
]

Jan 15, 2021, 6:48 PM
Gotcha. This is indeed caused by re-encoding of the image, unfortunately. We've got a fix for this lined up, but it might be a week or two before it's out.
Jan 16, 2021, 5:14 AM
Ah ok, good to know. Thanks!
Jan 19, 2021, 3:42 PM

Sanity.io – build remarkable experiences at scale

Sanity is a customizable solution that treats content as data to power your digital business. Free to get started, and pay-as-you-go on all plans.

Categorized in