Last updated: Nov-09-2022
In this tutorial, you'll learn how to diagnose and resolve some of the most common errors you may encounter while delivering media using Cloudinary. You'll gain an overview of the most common client-side errors (400, 401, 404) and see how to inspect the error in the browser's developer tools or with the Cloudinary Media Inspector extension.
This video is brought to you by Cloudinary's video player - embed your own!
This tutorial presents the following topics. Click a timestamp to jump to that part of the video.
Introducing the x-cld-error header
|0:39||Whenever there is a client-side error, Cloudinary returns an HTTP header containing information about why the request failed. You can inspect this in any browser's developer tools - and find the
Introducing the Cloudinary Media Inspector extension
|1:06||Cloudinary offers a browser extension called Media Inspector, where you can see the status code and other helpful information in the
400: Bad Request
|1:34||A 400 - Bad Request error is returned when the delivery URL is invalid. You will receive a 400 error if you attempt to use a transformation key or value that doesn't exist or is not valid, or if you attempt to use transformation options that are syntactically correct, yet conflict with one another.|
|2:08||A 401 - Unauthorized error is returned when there is a restriction preventing the successful delivery of a requested asset. If you have Strict Transformations enabled and attempt to generate a derived on-the-fly transformation without a signature, attempt to use an add-on or feature that is set as restricted, attempt to access a private original asset, or apply a transformation to an authenticated asset without a valid signature, you will receive a 401 error.|
404: Not Found
|2:55||A 404 - Not Found error means that the user can communicate with the server, but the server is unable to locate the requested asset in the specified cloud. Another common case is if your delivery URL is not in the proper format, for example if your cloud name is added after the resource type, or transformations are added after the public ID. Order matters with Cloudinary URLs.|
- Learn more in our Error handling documentation.
- To understand more about an error you are encountering, check the
x-cld-errorHTTP response header, or download the Cloudinary Media Inspector extension for your browser.
- We also offer some documentation about understanding error reports.
- Not all combinations of cropping and gravity are valid. To learn more about which combinations go together and which don't, check out our Resize and crop interactive demo.
- Take courses in the Cloudinary Academy, such as our new self paced course, Introduction to Cloudinary for Node.js Developers or Fundamentals for Developers, where you can learn more about errors in Lesson 7: Handling Potential Errors.
- Get additional support and assistance with any delivery errors you encounter by submitting a Support Request form or check out our Knowledge Base.
If you like this, you might also like...
Create Upload PresetsStreamline media uploads using signed upload presets
Upload ProgrammaticallyUse a Cloudinary SDK to upload media assets
Get Started with the CLISet up the CLI and get familiar with some basic commands
Check out the Cloudinary Academy for free self-paced Cloudinary courses on a variety of developer or DAM topics, or register for formal instructor-led courses, either virtual or on-site.