- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper proposes ConTra, a training-free visual token pruning method designed to preserve text-critical information in MLLMs. It applies a contrast transformation to the input image and selects tokens based on cross-view token consistency, assuming that text-bearing tokens remain more stable than background tokens. The method does not require attention matrices, making it compatible with FlashAttention. Experimental results show improved performance over existing pruning methods on text-rich benchmarks.
Critical strengths
- This paper introduces a novel query-agnostic token selection method based on cross-view consistency under contrast transformations.
- The proposed method does not require explicit attention matrices, making it compatible with FlashAttention.
Critical weaknesses
- (Major) Insufficient evidence for text-critical token preservation.
- Unclear qualitative evidence. In Figure 1, some text regions are removed even at 20%, 50%, and 70% pruning. These visualizations do not adequately support the paper's central claim that ConTra effectively preserves text-critical tokens.
- Potential competition between text and non-text structures. Since CCT preserves not only text but also object contours and geometric structures, it remains unclear whether ConTra remains effective when these features coexist in an image.
- Unclear text-background separation. It remains unclear whether consistency scores can reliably distinguish text from background tokens. Although Appendix C demonstrates score separability using GMM, the higher-mean component is designated as text without verifying its correspondence to actual text regions.
- Insufficient comparisons with relevant token pruning methods.
- Missing comparisons with text-rich pruning methods. The paper neither cites nor compares recent methods (e.g., [A], [B], [C]) designed for text-rich images.
- Insufficient comparison with query-aware methods. Although the paper claims to be competitive with query-aware methods, MMTok is the only such baseline evaluated. Additional comparisons with query-aware methods (e.g., [D], [E]) are needed.
+ Inconsistencies in presentation and reporting: Several inconsistencies throughout the paper should be carefully reviewed. For example:
- Section 4.3 refers to consistency-score maps in Appendix A, but these are not provided.
- Figure 3's caption does not match its content.
- CV-Bench is listed in Section 4.1 but omitted from Table 3.
References:
[A] Choi, Joonmyung, et al. "DocPrune: Efficient Document Question Answering via Background, Question, and Comprehension-aware Token Pruning." CVPR 2026.
[B] Kwon, Mincheol, et al. "Focus, Don't Prune: Identifying Instruction-Relevant Regions for Information-Rich Image Understanding." CVPR, 2026.
[C] Wan, Ben, et al. "RTPrune: Reading-Twice Inspired Token Pruning for Efficient DeepSeek-OCR Inference." ICML 2026.
[D] Yu, Hanxun, et al. “VisionTrim: Unified Vision Token Compression for Training-Free MLLM Acceleration”, ICLR 2026.
[E] Zhang, Qizhe, et al. "Beyond Attention or Similarity: Maximizing Conditional Diversity for Token Pruning in MLLMs." NeurIPS 2025.
Questions for authors
-
Q1. In Fig. 1, ConTra removes some text regions while retaining background regions, even at moderate pruning rates. If the consistency score favors text tokens, why are these background tokens ranked above the text tokens?
-
Q2. Appendix C designates the component with the higher mean as text. Does this component correspond to the annotated text regions, and what is the AUROC of the consistency score in classifying tokens inside and outside these regions on CC-OCR?
-
Q3. When text and objects appear simultaneously in an image, how are the retained tokens divided between text regions and object contours as the pruning rate increases? Do object structures replace text tokens when text occupies a small area?
-
Q4. How does ConTra differ from [A], [B], and [C], which also target text-rich images? Does it outperform them, as well as text-aware baselines such as [D] and [E], on the text-rich benchmarks?