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

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?

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.

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:

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.

Ah ok, good to know. Thanks!