Unfortunately your browser will also not gzip an uploads. In fact it will likely be noticeably larger than the raw image. It takes a small amount of setup using the default Cloudinary config. Stringifying the image into a base-64 text format is all fine and well, but it will take a small amount of time and certainly does not compress it. Rather than creating a custom picture component we are going to use an existing library called ngx-picture. If you want to see an example have a look at the app-picture component in the sample Using ngx-picture

If you are using Angular-CLI (which I highly recommend), add the script relative path to your angular.json like below : 1. Once the library is installed, you need to add script in your application. Luckily the format of the element lends itself nicely to being encapsulated in a component with an ngfor for the image formats and another nested one for the media queries. For image compression, we will use image-compressor.js. There are 24 other projects in the npm registry using compress-images. Start using compress-images in your project by running npm i compress-images. Latest version: 2.0.5, last published: 2 years ago. So this just improved the app performance massively but it would be painful to do this manually for every image. Image compression with extension: jpg/jpeg, svg, png, gif. If it is an old browser that doesn't support the picture element (IE) then it will just render the img element. If the browser doesn't support webp (Safari for instance) it will fall back to the jpeg sources. For Chrome that will be webp, which has better compression than jpeg. The browser will use the first format it supports. I have successfully implement it to work but there is 1 problem, the compress function returns me with a base64 encoded image which is stored in a local scope. The order of the sources is important for the image formats.

Angular image compress