Skip to main content

vc_auto not working for every video in library



  • Michal Kuperman

    Hi Matthew,

    In general, in order to help debug Cloudinary URLs, the response for failed requests includes a header called `X-Cld-Error` which provides more information on why the request was not successful. If you inspect the X-Cld-Error response to this example URL you'll see the following: "X-Cld-Error: Video is too large to process synchronously, please use an eager transformation with eager_async=true to resolve"

    Cloudinary sets an 'online' video transformation limit of 40MB for Free plans and 100 MB for paid plans. This is not a limit on the size of videos you can upload into your account but is the maximum size of a video which can be transformed synchronously/on-the-fly.

    For videos larger than this limit you must request that the derived versions are created before they're requested, which we call 'eagerly', and that the processing takes place in the background ('asynchronously'). When using asynchronous eager transformations you can manipulate videos as large as your account's maximum video file size limit.

    Part of the reason that this limit exists is that transforming/transcoding large videos can take significantly longer than smaller videos and there can be a long delay before the first request for the video receives a response, and requests may time out before it finishes processing. if your application needs to know when the derived video is ready, you can use the 'eager_notification_url' parameter and we'll send a request to your server when the requested transformations have completed, and you can use this to update your system state and start using the newly transformed/derived video.

    Eager transformations can be requested for new videos in the upload API call or configured in an upload preset, including an upload preset that is used when you upload to Media Library.

    You can read more about eager transformations here:

    For existing videos, you can request eager transformations via the explicit API method:

    Once the video is transformed eagerly/asynchronously it will be available via the URL as normal.

    Please let us know if this works for you.



  • Matthew McGillivray

    Thanks for the detailed response!

  • Michal Kuperman

    You are welcome. Let us know if you have any further questions.

  • Matthew McGillivray

    Hey, I have a related question now. I want to add an overlay image to all uploaded videos, and I also want to use the eager transformation as discussed previously. However, since adding the overlay transformation, I now get this message:

    Here are the transformations I have listed in my upload preset. To my understanding, it should apply the overlay transformation before storing the media, and then it should eagerly create the auto video codec transformations afterwards? I have successfuly added the watermark image by just inserting the transformation into the url using '.../video/upload/l_watermark,w_300,g_north_east/...' so I'm pretty sure the overlay parameters are correct.

  • Shirly Manor


    In order to set the incoming transformation to be async, you will need to set the Async to True on the upload control. Here is a screenshot:

    Hope that helps,


Post is closed for comments.