Embodied Image Compression

Chunyi Li, Rui Qing, Jianbo Zhang, Yuan Tian, Xiangyang Zhu +4 more
12/12/2025
cs.CVeess.IV

No official code found. Best implementation: Jianbo-maker/EmbodiedComp (3 stars, last commit 2026-01-22).

Abstract

Image Compression for Machines (ICM) has emerged as a pivotal research direction in the field of visual data compression. However, with the rapid evolution of machine intelligence, the target of compression has shifted from task-specific virtual models to Embodied agents operating in real-world environments. To address the communication constraints of Embodied AI in multi-agent systems and ensure real-time task execution, this paper introduces, for the first time, the scientific problem of Embodied Image Compression. We establish a standardized benchmark, EmbodiedComp, to facilitate systematic evaluation under ultra-low bitrate conditions in a closed-loop setting. Through extensive empirical studies in both simulated and real-world settings, we demonstrate that existing Vision-Language-Action models (VLAs) fail to reliably perform even simple manipulation tasks when compressed below the Embodied bitrate threshold. We anticipate that EmbodiedComp will catalyze the development of domain-specific compression tailored for Embodied agents , thereby accelerating the Embodied AI deployment in the Real-world.

View on arXivView PDF

Code Implementations(1)

Embodied Image Compression

32CMake, ShellJan 11, 20269 months ago

Similar Papers

Cite this paper

@article{li2025embodied,
  title  = {Embodied Image Compression},
  author = {Chunyi Li and Rui Qing and Jianbo Zhang and Yuan Tian and Xiangyang Zhu and Zicheng Zhang and Xiaohong Liu and Weisi Lin and Guangtao Zhai},
  year   = {2025},
  eprint = {2512.11612},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2512.11612v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2512.11612.svg)](https://codeofpaper.com/paper/2512.11612)

Discussion