Images created with migration.createAsset are not considered as images

Developing with Prismic
1

Following the migration API docs, I'm doing the following :

migration.createAsset(fs.readFileSync(imagePath), 'test.webp')

The migration runs smoothly and I can see the new media in media library. However there is no preview, and I cannot use it in a ImageField :

Screenshot 2025-03-13 at 19.40.10
Screenshot 2025-03-13 at 19.40.10642Ă—708 16.7 KB

Note that the file is not corrupted, if I download it from the media library, it is identical to my original image.

Strangely, if I host the image somewhere and do the exact same, it works fine :

migration.createAsset('https://www.example.com/test.webp', 'test.webp')

I'm not sure what's going wrong here ?

Regards,
Grégoire

2

Hi Grégoire,

Is it happening specifically to this image, and no other? Are other .webp assets working fine?

Let me know!

3

Hi Ezekiel,

Every single image on more than 800.
When i read them on the filesystem with fs.readFileSync (Node22), this is the result. I kept one on our repo if you want to check it.

Once I hosted the same images online, I was able to import all of them without a single failure.

Regards,
Grégoire

5

Hi @gbelorgey,

I'm not entirely sure what's causing the issue in this case. I'm going to try to recreate this and investigate it on my own, I'll get back to you with news of how that goes!

For the time being, a good workaround is to apply Imgix URL parameters when rendering the image on your site. Imgix powers Prismic’s image URLs and supports format conversion on-the-fly using a simple ?fm=jpg parameter.

For example, if your image URL is:

https://images.prismic.io/your-repo/image-id.webp

You can convert it to .jpg like this:

https://images.prismic.io/your-repo/image-id.webp?fm=jpg

If you’re rendering the images dynamically, we recommend building a helper function that appends fm=jpg (and other Imgix params if needed) at runtime — this gives you full control over the format, compression, and sizing without modifying your migration logic.

Let me know if that helps!

7

hi @Ezekiel

The thing is, because the image is not identified as an image by the media library, I cannot assign it to an ImageField. So it's not really possible to use it in any meaningful way..

Regards,
Grégoire

8

Hi @gbelorgey,

This makes sense. Short of converting your images before migration, I'm not entirely sure what alternative I can provide here. However we have recreated the issue on our side and are looking at potential ways to fix it. I don't have a precise timeline, but the team is on it. Sorry for the inconvenience in the meantime! I'll keep you updated here when it's fixed.

1 Like
9

Hi @gbelorgey,

Good news, this has been fixed :slight_smile: This should all work as normal now. Thanks for raising this bug!

10

Hi @Ezekiel

I was just able to test this now, all my images are now created flawlessly !

Thanks to you and the team for looking into this :clap:

1 Like
11

Hey there @Ezekiel

Just wanted to bump this as I'm running into the same issue as OP. Slight difference is that when I do try to supply a string to the image hosted somewhere it doesn't seem to register the image as an image. I instead have to fetch each remote image, read it as a blob, create a file, then pass that file to the createAsset function. Not sure if there much you can look in to but wanted to share incase others come across this as well in their Google searches

12

Hi @jordankid93,

Welcome to the community! Do you mind giving us a bit more detail in the behavior you're observing? When you say "supplying a string", do you mean a query string? If you can share any snippet of your code to give us a bit more context, we can have a look :slight_smile: