Whether a video is optimized or transformed, a new video(s) is generated and saved internally by ImageKit. This process could take a few seconds, depending on the video duration, output format, and transformation parameters. Therefore, you should eagerly generate the transformation before using the video URL in a live environment to ensure it works as expected. It guarantees that all necessary transformations are prepared and ready to be served. This avoids unnecessary data transfer costs on your origin. In the beta version, you will have to manually or programmatically get the resource to see if the
200 status code is received. That means transformation is ready. On the other hand, if a
302 is received, it means transformation is not prepared. In that case, you should wait. In the future, we will support webhook, which you can implement to get updates on asset transformations.