This is a guest post for the Computer Weekly Developer Network written by Dr Jon Sneyers, senior image researcher at Cloudinary.

Cloudinary is a SaaS technology company headquartered in Santa Clara, California, with an office in Israel. The company provides a cloud-based image and video management solution to enables users to upload, store, manage, manipulate and deliver images and video for websites and apps.

Sneyers writes… Last summer I had the opportunity to participate in my third JPEG meeting of the year, the 84th JPEG meeting in Brussels, Belgium, conveniently close to where I live. These are very exciting times for those of us involved in the world of standards and image formats — and especially for those of us directly involved in the development of what will soon be a major update – the first in about 20 years – to the widely adopted JPEG. A little history for those less familiar with image formats: JPEG stands for the Joint Photographic Experts Group, which created the standard in 1992. The main basis for JPEG is the Discrete Cosine Transform (DCT), a “lossy” image compression technique that was first proposed by Nasir Ahmed in 1972.

How did we get here? You might be wondering how we got here and why is a new image format necessary? Last spring, the JPEG Committee launched its Next-Generation Image Compression Call for Proposals, also referred to as JPEG XL. The goal was to: “Develop a standard for image compression that offers substantially better compression efficiency than existing image formats (e.g. >60% over JPEG-1), along with features desirable for web distribution and efficient compression of high-quality images.” My submission, which I dubbed FUIF or the Free Universal Image Format, was one of seven proposals selected to be presented at the 81st JPEG meeting, held in Vancouver, Canada. That was the first JPEG meeting I participated in, presenting and defending my proposal. Once all seven proposals were presented we spent the week discussing the pros and cons of each proposal, the subjective evaluation results, and how to get started on JPEG XL. At the 82nd JPEG meeting in Lisbon, Portugal, it was decided to combine two proposals: my FUIF and Google’s PIK, and make that the starting point for JPEG XL.

Use cases & requirements At that point, I was promoted to the role of co-chair of the JPEG XL Ad Hoc Group, together with Google’s Jan Wassenberg. The main discussions were on refining the use cases and requirements… and, on how to combine and unify the two proposals into a single image codec. At the next meeting, held in Geneva, Switzerland, we started writing the formal standard – it was still a very rough ‘working draft’, but it was a good start. Gradually we transitioned from a situation where the code was the ‘source of truth’ (and the spec draft was describing whatever the code did) to a situation where the spec became the source of truth and the code had to implement what the spec was saying.