Image resolution after import/export

Hey everybody,

I have this issue with images: when I export and import document resolution of image get "reseted" to origin resolution. It's a bit unexpected because I haven't made any changes to image object and I don't want to change it's resolution. Is there something I can do about it ?

How it looks in Prismic, when I open history:


I found out that this is limitation of import/export. But I also can't edit resolution for most of the images, because I have set the dimensions in my slice model. I found only one way to fix it - going through every image and re-adding the same image :pensive:


Any tips on this ?

Hi Modestas,

Welcome to the Prismic community,

As you have noticed, this is a known limitation in the Import/Export feature as mentioned in the documentation

  • You will lose image positioning and crop in the Import job. You need to re-apply these.

Unfortunately, there is currently no workaround for this except editing images one by one, but why do you say you need to reimport the images again? Can't you select the existing image and set the dimensions in the slice model? have you tried to unpublish and publish the imported document to see if the dimensions in the model will apply? Otherwise, I think it is an issue to create or document on our side.

Looking forward to your reply,

I don't need to re-import images to prismic (media), but I need to re-add (select) the same image to my document. In this way default dimensions of image are set automatically.
What I mean with default dimensions (it's from slicemachine):

So, yeah if I don't re-select the image I can't resize it (since it's restricted by slice model).

1 Like


Unfortunately, currently, there is no way to avoid reimporting the images in this case.

And certainly, this can be time consuming, and for that, I will create an issue in our tracker and will send it to our dev team

1 Like

Hello, @Fares,

Maybe do you have any updates on this issue ?

Hi @modestas.rimkus,

Unfortunately, there are still no updates for this issue. I'm waiting for a response from our production team to figure out if it will be considered a bug or a feature request/improvement as that can impact the resolution ETA of this.