Frequently Asked Questions

For a specific image to be optimized, the API uses a unique hash value that is based on the image file content. The reason for using a hash value is to be able to uniquely identify the image - even if, for example, the file name changes. To create a value for image_file_hash you can for example use https://emn178.github.io/online-tools/sha1_checksum.html.

The image optimization comes in two packages. Each of the packages are available both as an API and as an add-on service that can be contracted in our content distribution network, which we can put in front of your websites to cache and accelerate them.

  • Light package - no configuration needed For those that only need serving their images in new image formats, we offer the so called light tier, which can be plugged directly in front of an existing e-commerce and requires no configuration. It takes care of converting JPEG files to WebP for those browsers that can accept WEBP. It can also convert to JPEG2000.
  • Lux package - complete image handling Serving images at the right size requires starting from high quality images. Sometimes, the high quality image is not even available for the e-commerce manager, or the e-commerce platform serving the website has a bolted asset pipeline which is really difficult to customize. Then there is the need of serving the image not only in different formats, but also at different sizes and quality levels, depending on the browser and the viewing device. Lux has been built in for those that require that extra-bit of functionality.

To encode image file to base64 to be used in parameter file https://base64.guru/converter/encode/file.

Provide the first two characters of the previously used image_file_hash as the hash_prefix and the job_name as the previously used image_file_hash.