Zhen Liu, Wenli Huang, Wei Song, Yuhan Liu, Zhiqin Yang, Jingwen Fu
7 min
Multimodal large language models encode images into hundreds or thousands of visual tokens, leading to high inference latency, memory consumption, and deployment costs. Visual-token pruning mitigates this by removing redundant tokens before language model processing. However, existing pruning methods rely heavily on handcrafted heuristics and costly trial-and-error by experts. As pruning objectives, budgets, and architectures diversify, manually navigating this design space becomes increasingly difficult. This paper asks whether large language models can automatically design effective visual-token reduction algorithms.
Directly asking an LLM to write complete pruning programs from scratch often fails because the search space is too vast and strict structural constraints must be met. To solve this, the authors propose AutoPrune, a training-free framework built around a Token Pruning Domain-Specific Language (TPDSL). TPDSL comprises 131 reusable atoms covering budget control, token scoring, selection constraints, and token reassembly. Crucially, TPDSL formulates each search state as a residual modification of a strong base policy rather than a standalone program. This constrains the search space, preserves reliable prior structures, and focuses the LLM on impactful components.
Evaluated across 14 multimodal benchmarks and three multimodal large language model backbones, AutoPrune demonstrates exceptional performance and efficiency. Under an aggressive 94.4% visual-token reduction ratio, AutoPrune preserves more than 99% of full-token performance on both LLaVA-1.5-7B and LLaVA-NeXT-7B, outperforming existing methods like CDPruner and PruMerge+. Furthermore, in efficiency settings retaining 320 tokens, AutoPrune reduces FLOPs by 9.9x and prefill latency by 6.4x.
AutoPrune bridges the gap between general-purpose LLM reasoning and specialized, constraint-heavy algorithmic design in computer vision. By replacing unconstrained code generation with a modular residual search space, it enables automated, training-free discovery of high-performing pruning policies that transfer effectively across budgets, tasks, and model backbones.
Visual-token pruning can substantially reduce the inference cost of multimodal large language models (MLLMs), yet existing methods largely rely on fixed, handcrafted heuristics and costly expert trial and error. As pruning objectives, budgets, and model architectures diversify, manually navigating the expanding design space becomes increasingly difficult. This paper aims to build an AI4AI framework for visual-token pruning by addressing a natural question: Can large language models automatically design effective visual-token reduction algorithms? Although LLMs possess broad algorithmic knowledge and strong reasoning capabilities, translating such general knowledge into effective solutions for a specialized task remains nontrivial. We argue that the key lies in designing an appropriate search-state representation that connects the internal knowledge of LLMs with the structural requirements and constraints of visual-token pruning. Based on this insight, we propose AutoPrune, a training-free framework for LLM-driven visual-token pruning policy design. At its core, AutoPrune introduces a Token Pruning Domain-Specific Language (TPDSL) comprising 131 reusable atoms for budget control, token scoring, selection constraints, and token reassembly. A key property of TPDSL is that it represents each search state as a residual modification of a strong base policy. This residual formulation narrows the search space and directs the LLM's attention toward the policy components that are most consequential for performance. Experiments on 14 multimodal benchmarks and three MLLM backbones demonstrate the effectiveness, efficiency, and transferability of AutoPrune. Even when removing 94.4% of visual tokens, AutoPrune preserves more than 99% of full-token performance while reducing FLOPs by 9.9x and prefill latency by 6.4x.
Sam: So the search space is already narrowed down to things that are at least structurally valid.
Alex: Exactly. And there's a second layer of safety on top of that. Before any proposed policy actually runs, it goes through an automated check — verifying that the budget is consistent, that the indices are valid, that the output shapes match what the model expects. If anything fails, the system discards that proposal and falls back to a safe default. Only policies that pass every check get evaluated on real tasks.
Sam: So you're filtering out bad ideas before they waste any compute.
Alex: Right. And the policies that do pass get scored based on how well they actually perform — which gives the system real feedback to learn from across search rounds.
Sam: How does the system avoid just rewriting everything from scratch each time? That sounds like it could get chaotic.
Alex: This is one of the more elegant parts of the design. Rather than generating a completely new policy each round, the system treats each candidate as a small modification to an already solid base policy. Think of it like a careful editor working on a well-written draft — instead of rewriting the whole thing, they swap out a few weak sentences while keeping the strong structure intact. The paper calls this a "residual formulation."
Sam: So the base policy provides a reliable floor, and the system only tinkers at the margins.
Alex: Precisely. And the tinkering is strictly limited. The system can only replace a small number of the base policy's selections — the ones it's least confident about — with higher-scoring alternatives. If you let it replace too many, performance drops, because you've eroded the reliable foundation. The sweet spot turns out to be replacing just a handful of tokens, which corrects the most uncertain decisions without destabilising the whole structure.
Sam: That's a surprisingly small margin of change to matter.
Alex: It matters because those uncertain patches are often the ones sitting on the boundary between "relevant" and "redundant." Getting those right has an outsized effect on what the model understands. The scoring system helps identify them by combining several signals — how relevant a patch is to the text prompt, how much the model's own attention focuses on it, where it sits spatially in the image, how similar it is to its neighbours, and how much local contrast it has. All of those get combined into a single quality score for each patch.
Sam: So it's not just asking "is this patch important in isolation" — it's asking "is this patch important given everything else around it?"
Alex: That's right. Redundancy matters. A patch might be visually interesting on its own, but if five identical patches surround it, keeping all six is wasteful. The scoring system accounts for that.
Sam: And does this whole approach actually hold up when you change the model, or the token budget, or the task?
Alex: The paper tests exactly those questions. When the researchers transferred policies found at one token budget to a different model size, performance remained high without needing to search again. When they compressed down to very tight token limits, the system still retained nearly all of its original accuracy. And when they ran the search multiple times with different random starting points, it consistently landed on the same high-performing configurations — which suggests it's not just getting lucky.
Sam: So the rules it's discovering are capturing something real about visual redundancy, not just memorising one specific setting.
Alex: That's what the stability results suggest. And the paper also tested whether the method depends on a particular base pruning strategy — they swapped in five different alternatives, and every one of them improved under AutoPrune's refinement. The framework appears to be a general-purpose layer that sits on top of existing approaches rather than replacing them.
Sam: Are there limits to what it can do?
Alex: Yes, and the paper is clear about them. The quality of the search is fundamentally bounded by two things: the expressiveness of the building-block vocabulary, and the reliability of the task feedback used to score policies. If the vocabulary doesn't include the right components to express a good solution, the system can't find one. And if the scoring signal is noisy or misleading, the search will chase the wrong target. The framework is only as good as the tools it's given.
Sam: So it's a significant step forward in automating something that used to require a lot of manual expertise — but it's not a complete solution to the underlying problem.
Alex: That's a fair summary. What it does offer is a structured, scalable way to remove the trial-and-error burden from researchers working on visual efficiency. Instead of hand-crafting pruning rules for every new model and every new deployment scenario, you can run AutoPrune and get a well-validated policy automatically. For the growing number of applications where these models need to run on devices with limited memory and processing power, that's a meaningful practical gain.
Sam: It's a good reminder that some of the most useful research isn't about building something new from scratch — it's about making what already exists work better, more reliably, and for more people.
Alex: Well put. Thanks for listening to ResearchPod.