Last updated: Aug-15-2023
After you or your users have uploaded image assets to Cloudinary, you can deliver them via dynamic URLs. You can include instructions in your dynamic URLs that tell Cloudinary to transform your assets using a set of transformation parameters. All transformations are performed automatically in the cloud and your transformed assets are automatically optimized before they are routed through a fast CDN to the end user for optimal user experience.
For example, you can resize and crop, add overlay images, blur or pixelate faces, apply a large variety of special effects and filters, and apply settings to optimize your images and to deliver them responsively.
Cloudinary's Rails library simplifies the generation of transformation URLs for easy embedding of assets in your Rails application.
See also: Rails video transformation
You can deliver your images using methods that generate image tags or via direct URL-building directives.
You can add images to your Rails view using Cloudinary's
cl_image_tag helper method, instead of the standard Rails 'image_tag' method. This method generates the full image resource URL based on the given transformation parameters and then internally uses 'image_tag' to add the image tag to your HTML code:
The code above generates the following HTML image tag:
You can also include transformation parameters in the request, for example, to deliver a JPEG image padded to a width of 400 pixels:
You can either add transformations directly to your
cl_image_tag method (all transformations will be in a single, flat component of the resulting URL source, as above), or you can define them with the
Additionally, you can add other, non-transformation parameters to the
cl_image_tag such as the asset version, configuration parameters and HTML5 image tag attributes.
versionparameter is added to the delivery URL as explained in Asset versions.
- Configuration parameters that you specify here override any that you have set globally.
HTML5 image tag attributes (e.g., alt or class) are added to the resulting
is compiled by Rails to:
In general, when using an SDK, you will probably take advantage of the SDK parameter names for improved readability and maintenance of your code. However, you can also optionally pass a raw transformation parameter, whose value is a literal URL transformation definition. Note that the string you pass as the raw transformation value will be appended as is (with no processing or validation) to the end of any other transformation parameters passed in the same component of the transformation chain.
Cloudinary supports powerful transformations. You can even combine multiple transformations together as part of a single transformation request, e.g. crop an image and add a border. In certain cases you may want to perform additional transformations on the result of the previous transformation request. To do that, you can use chained transformations.
To apply chained transformations in a transformation URL, you include multiple transformation components separated by '/'. Each transformation component is applied to the result of the previous one. In Ruby, applying multiple transformations is done by specifying the
transformation parameter as an array of transformation hashes. The following example first crops the original image to a specific set of custom coordinates and then transforms the result so it fills a 130x100 rectangle:
The following example applies 4 chained transformations: custom cropping to 300x200, fill to 130x100, rotate by 20 degrees and then scale to 50%:
For more information on image transformations, see Apply common image transformations.
cl_image_tag method described above generates an HTML image tag. In certain conditions, you might want to generate a transformation URL directly, without the containing image tag. To return only the URL, either use the
cloudinary_url view helper methods, or use the Ruby command:
Cloudinary::Utils.cloudinary_url. Here are few examples:
Most examples shown here are based on using Cloudinary's
cl_image_tag to embed and transform images. You can alternatively use the standard Rails 'image_tag' to get the same functionality by setting
true in your global configuration parameters.
After setting the configuration parameter, you can use the standard Rails
image_tag method to embed any uploaded images or transformed images, as long as you also include the
type parameter (generally set to 'upload', but for more details see the Access control documentation).
The same approach can be used to embed a remotely fetched and transformed image through Cloudinary:
While Cloudinary's service focuses on user-uploaded images, you can use Cloudinary to manage the static files you have in your web application as well, such as background images, buttons, icons, scripts, stylesheets. These too can be delivered through a CDN, offloading their delivery from your servers and improving your website's performance.
Cloudinary's Ruby gem simplifies and streamlines the process of uploading your static files to the cloud and delivering them through a CDN.
To upload all your Ruby-on-Rails applications' static files to Cloudinary, run the following Rake command:
This Rake task finds all the files in all common public folders and in Rails Asset Pipeline's image asset folders. Afterwards, it uploads all new and modified files to Cloudinary. Uploaded files and their versions are maintained using a local
.cloudinary.static file. Make sure you commit this file to your source control.
After uploading your static files to Cloudinary, edit your
cloudinary.yml file and set the following configuration parameters to 'true':
image_tag call in your views will now automatically check if the image was uploaded to the cloud (using
.cloudinary.static) and if so, will generate a remote Cloudinary CDN URL. For example:
Will now generate the following HTML code:
The Ruby gem automatically delivers background images defined in your CSS, SCSS or SASS files using the default
image-url directly or Cloudinary's
cloudinary-url custom directive.
This section provides an overview and examples of the following commonly used image transformation features, along with links to more detailed documentation on these features:
- Resizing and cropping
- Converting to another image format
- Applying image effects and filters
- Adding text and image overlays
- Image optimizations
- Responsive image settings
Keep in mind that this section is only intended to introduce you to the basics of using image transformations with Ruby and Rails.
For comprehensive explanations of how to implement a wide variety of transformations, see Image transformations. For a full list of all supported image transformations and their usage, see the Transformation URL API Reference.
There are a variety of different ways to resize and/or crop your images, and to control the area of the image that is preserved during a crop.
The following example uses the
fill cropping method to generate and deliver an image that completely fills the requested 250x250 size while retaining the original aspect ratio. It uses face detection gravity to ensure that all the faces in the image are retained and centered when the image is cropped:
You can also use automatic gravity to determine what to keep in the crop automatically.
For details on all resizing and cropping options, see resizing and cropping images.
You can deliver any image uploaded to Cloudinary in essentially any image format. There are three main ways to convert and deliver in another format:
- Specify the image's public ID with the desired extension.
- Explicitly set the desired format using the
- Use the
autofetch_format to instruct Cloudinary to deliver the image in the most optimized format for each browser that requests it.
- Deliver a .jpg file in .gif format:
- Let Cloudinary select the optimal format for each browser. For example, in Chrome, this image may deliver in .avif or .webp format (depending on your product environment setup):
The above code generates a URL with the
For more details, see:
- Delivering images in different formats
- Automatic format selection (f_auto)
- Tips and considerations for using f_auto
You can select from a large selection of image effects, enhancements, and filters to apply to your images. The available effects include a variety of color balance and level effects, tinting, blurring, pixelating, sharpening, automatic improvement effects, artistic filters, image and text overlays, distortion and shape changing effects, outlines, backgrounds, shadows, and more.
For example, the code below applies a cartoonify effect, rounding corners effect, and background color effect (and then scales the image down to a height of 300 pixels).
For more details on the available image effects and filters, see Visual image effects and enhancements.
You can add images and text as overlays on your main image. You can apply the same types of transformations on your overlay images as you can with any image and you can use gravity settings or x and y coordinates to control the location of the overlays. You can also apply a variety of transformations on text, such as color, font, size, rotation, and more.
For example, the code below overlays a couple's photo on a mug image. The overlay photo is cropped using face detection with adjusted color saturation and a vignette effect applied. The word love is added in a pink, fancy font and rotated to fit the design. A balloon graphic is also added. Additionally, the final image is cropped and the corners are rounded.
By default, Cloudinary automatically performs certain optimizations on all transformed images. There are also a number of additional features that enable you to further optimize the images you use in your application. These include optimizations to image quality, format, and size, among others.
For example, you can use the
auto value for the
quality attributes to automatically deliver the image in the format and quality that minimize file size while meeting the required quality level. Below, these two parameters are applied, resulting in a 351 KB AVIF file (in Chrome) instead of a 1.4 MB JPG with no visible change in quality.
For an in-depth review of the many ways you can optimize your images, see Image optimization.
Responsive web design is a method of designing websites to provide an optimal viewing experience to users, irrespective of the device, viewport size, orientation, or resolution used to view it. Ensuring that optimal experience means you should avoid sending high resolution images that get resized client side, with significant bandwidth waste for users of small displays. Instead, you should always deliver the right size image for each device and screen size.
For example, you can ensure that each user receives images at the size and device pixel ratio (dpr) that fit their device using the
auto value for the
width attributes. The
auto value is replaced with actual values on the client side based on the screen properties and viewport width:
Cloudinary offers several options for simplifying the complexity of delivering responsive images. For a detailed guide on how to implement these options, see Responsive images.
Check out our Introduction to Cloudinary for Ruby Developers course in the Cloudinary Academy. This self-paced resource provides video-based lessons, sample scripts and other learning material to get you going with Ruby and Cloudinary today.