How veImageX Cuts Image Bandwidth by 30% with AI‑Powered HEIF Compression

This article explains how the veImageX platform leverages a self‑developed HEIF codec and AI‑driven optimization to shrink image sizes by over 30%, reduce bandwidth costs, maintain visual quality, and provide flexible integration options for both native apps and web pages.

Volcano Engine Developer Services
Volcano Engine Developer Services
Volcano Engine Developer Services
How veImageX Cuts Image Bandwidth by 30% with AI‑Powered HEIF Compression

Introduction

Recently the fifth CLIC (Compression Learning Image Challenge) announced its results, and the Volcano Engine Video Cloud multimedia lab won first place in the video compression track. Image and video compression are critical for internet delivery; reducing file size while preserving perceived quality is a continuous research focus.

veImageX Overview

veImageX is Volcano Engine’s end‑to‑end image solution covering upload, storage, processing, distribution, display and quality monitoring.

An image’s lifecycle consumes bandwidth, storage and compute roughly in a 7:2:1 ratio, with bandwidth often being the dominant cost.

Architecture

The system consists of three core components: a CDN distribution layer, a storage layer, and a media‑processing layer. To lower bandwidth, veImageX adopts a self‑developed HEIF codec that compresses images without degrading user‑perceived quality.

veImageX architecture diagram
veImageX architecture diagram

Dual‑End Image Compression

On iOS (JPEG) and Android (WebP) devices, converting images to the custom HEIF format saves more than 30% of the original volume.

Image size comparison: original vs HEIF
Image size comparison: original vs HEIF

Quality Evaluation

While size reduction is the primary goal, preserving visual quality is essential. Objective metrics and a proprietary no‑reference VQScore algorithm were used to assess sharpness and aesthetics, showing negligible quality loss after compression.

VQScore impact on sharpness
VQScore impact on sharpness
VQScore impact on aesthetics
VQScore impact on aesthetics

Decoding Performance

To keep user‑side load time low, the custom decoder was tuned so that its added latency is smaller than the time saved by reduced file size. Benchmarks show the custom decoder’s latency comparable to WebP and better than many open‑source alternatives.

Decoding time comparison (ms)
Decoding time comparison (ms)

Experiment Design & Data

A controlled A/B test compared bandwidth usage between two domains (p‑xx‑a vs p‑xx‑b). The experiment showed a 32.4% reduction in bandwidth (2.53 PB vs 1.71 PB), confirming at least a 30% saving versus WebP.

Experimental traffic comparison
Experimental traffic comparison

General “Intelligent Slimming”

For H5 scenarios, a DNS‑only integration called “Intelligent Slimming” applies deep‑learning‑based compression to traditional formats (WebP, JPEG, PNG) without requiring a client SDK, delivering 15‑20% additional bandwidth savings.

Intelligent Slimming workflow
Intelligent Slimming workflow

Conclusion

Beyond the two main scenarios, veImageX’s AI‑driven compression reduces image size by over 30% compared with WebP, adaptive quality compression adds another 5‑10%, and “Intelligent Slimming” contributes 15‑20%, achieving up to 80% overall cost reduction while improving load speed and lowering user data consumption.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

frontendAIimage compressionHEIFbandwidth optimizationveImageX
Volcano Engine Developer Services
Written by

Volcano Engine Developer Services

The Volcano Engine Developer Community, Volcano Engine's TOD community, connects the platform with developers, offering cutting-edge tech content and diverse events, nurturing a vibrant developer culture, and co-building an open-source ecosystem.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.