@primoz.rome, if you add fit=max, like https://www.datocms-assets.com/53444/1712829472-accessing-device-view.gif?auto=format&dpr=4&fit=max, it should ensure the image is never upscaled past its native resolution (and in the process, help prevent DPR-related timeouts): Responsive Images with srcset | imgix Documentation (And sorry for not suggesting this earlier… I didn’t realize it was us adding the DPRs for you 
, my bad)
@mat_jack1 This almost seems like a bug on our part to me. I wonder if we should add that to our own image component/default Imgix queries too? DPR makes sense when an image is scaled down from its native size to fit a container, in which case DPR > 1 can improve clarity on retina devices. But when we accidentally use it to scale an image past beyond its native size, at best it will look bad (upscaled), at worst it will cause an Imgix timeout like here. It’s what Imgix suggests in their responsive images tutorial too. I think I’ve seen similar situations with other customers too, but at the time I didn’t realize we were the ones doing the DPR calculations for them. My mistake!