Get Started
Home
Topics
Search
Library
7 min read · Inference Optimization · Mechanistic Interpretability · Added Oct 2 · Paper published Sep 29, 2026

LoopVL: Recurrent Visual Intelligence

Source: research paper via Hugging Face Daily Papers
0:00 / 8:19
LoopVL tackles whether parameter-sharing recurrence, which worked for text-only models, transfers to vision-language: a 1B backbone reuses 32 layers across 128 calls via interleaved low/high stacks, beating a 4B dense model at matched FLOPs. Catch: the loop schedule is baked in — shrinking or extending it at inference collapses accuracy.
TL;DR
LoopVL applies Loop Transformer computation to vision-language modeling, repeatedly running two shared Transformer stacks (a “low-level” and “high-level” module) over a joint image-text state so a ~1B-parameter backbone executes 128 layer calls per forward pass and matches dense models several times larger.
Why It Matters
If you want a stronger vision-language model, the default move is to stack more unique Transformer layers or widen them. That costs parameters linearly, which costs memory, serving dollars, and training data to fill. Recent language-only work on Recurrent-depth models models has shown you can instead reuse the same layers many times per forward pass, trading extra compute for parameter efficiency. The open question this paper tackles: does that trick transfer to multimodal models, where visual tokens have spatial structure and the “right” region to attend to may change as the model thinks?
The concrete baseline is a standard 32-layer, 1.5k-hidden Transformer vision-language model (which they call Transformer-VL 1B) trained on the same data. LoopVL uses the same 32 unique layers but executes each one up to 4 times per pass. The practical question for an engineer: is the resulting model actually better per parameter, and does the recurrence do something interesting to visual attention, or is it just “deeper compute, same idea”?
How It Works
The backbone has two separate 16-layer Transformer stacks, called L (low-level) and H (high-level). Each stack shares its parameters across every time you invoke it. The default schedule, written H2L3, means: run L three times, then H once, then L three times again, then H once more. That’s 8 module invocations, each 16 layers deep, giving 128 Transformer-layer calls from only 32 unique layers of parameters.
Two kinds of looping stack on top of each other. Module-Loop repeats the L stack several times under the same high-level condition, letting the “fast” state refine itself. Model-Loop then does another full L-then-H cycle, letting the integrated high-level state feed back in. The architectural inspiration comes from Hierarchical Reasoning Model (HRM), a hierarchical recurrent language model whose open-source framework and data they used to pretrain the language backbone from scratch.
The multimodal piece: a frozen Penguin Vision Encoder produces patch features, a small projector maps them into the language embedding space, and those visual tokens then sit inside the sequence and get updated by every L and H invocation along with the text tokens. Crucially, at the start of each Model-Loop cycle, the model re-injects the original projected visual features into the visual slots (gated by a learned per-cycle scale), so later cycles have access to the raw image signal, not just the already-transformed version.
Training uses Selective backpropagation: all 8 invocations run forward, but gradients only flow through roughly the last 5. This keeps memory tractable without changing what the model computes at inference.
L_state = zeros() # low-level, carried across cycles H_state = scale * embed(tokens) # high-level, from inputs for cycle in range(2): # Model-Loop (H2) H_state = reinject_visual_anchor(H_state, visual_embed, cycle) for _ in range(3): # Module-Loop (L3) L_state = L_stack(L_state, cond=H_state) H_state = H_stack(H_state, cond=L_state) logits = lm_head(H_state)
What They Found
Recurrence beats width and depth at matched compute. At a 0.14T-token training budget, LoopVL (2.47 * 10^21 FLOPs) outperforms both a 78-layer deep Transformer-VL 4B (2.89 * 10^21 FLOPs) and a width-scaled 4B variant (2.99 * 10^21 FLOPs) across the five benchmarks reported. For example on MMStar, LoopVL hits 63.47 vs 55.33 for the 1B dense baseline and 61.33 for the 4B deep variant. On ChartQA it jumps from 51.12 (1B dense) to 74.52.
Schedule matters, not just depth. Independently training H1L3 and H2L1 (both execute 64 layer calls) gives different results: H2L1 wins on all five benchmarks they report. So how L and H updates are interleaved affects quality, not just the total number of layer calls.
You cannot cheaply shrink the loop at inference. Taking the H2L3-trained checkpoint and running it with fewer loops produces garbage. H1L1 and H1L3 readouts yield near-zero scores because the model never learned to produce a usable distribution at early cycle endpoints. Running more loops than training (H3L3, H4L3) also degrades performance, for example MMStar drops from 63.47 to 58.20 then 24.00. Inference-time compute scaling is not free for this checkpoint.
Visual Aha Moments. Measuring where attention lands on the image at each layer, they find a sharp jump in concentration at the Model-Loop boundary: mean Gini coefficient (over attention) rises from 0.405 to 0.858 between layer 63 and layer 64. The same shared H layer, applied at the end of cycle 1 vs end of cycle 2, allocates attention to different image regions, with some patches that were in the bottom half of attention ranking during cycle 1 jumping into the top quartile in cycle 2. They verify this isn’t an artifact of selective backprop or the anchor-reinjection mechanism by retraining ablations with those removed. They are explicit that spatial reallocation is a diagnostic, not proof of a causal mechanism for better answers.
Logit lens says the final H call does most of the integration. Measuring KL divergence from each intermediate layer’s output distribution to the final one, the trajectory stays high through most of the forward pass and drops sharply inside the last H invocation. The late H stage is where the prediction actually crystallizes.
What’s Useful
If you’re deciding between scaling width/depth vs trying parameter-sharing recurrence for a small VL model: this paper is positive evidence that the recurrence route can match a 3-4x-larger dense model at roughly matched training FLOPs. The caveat is you have to train from scratch with the recurrence schedule in place; you can’t bolt it onto an existing checkpoint.
If you’re hoping to use loop count as an inference-time compute knob (think Chain-of-Thought-style “think longer”): this paper is a cautionary data point. The H2L3 checkpoint collapses when run with any other schedule. Adaptive-depth recurrence (the authors cite Mixture-of-Recursions as a complementary direction) is left as future work. Treat the loop schedule as a fixed architectural choice, not a runtime dial.
If you work on interpretability for multimodal models: the shared-parameter setup gives you a clean experimental handle. You can hold the physical layer fixed and compare its attention and state across cycles, which is harder in a standard Transformer where each layer has its own weights. The authors release code at LoopVL and a 1B checkpoint on HuggingFace.
Worth testing but not demonstrated: whether these Visual Aha Moments show up in larger-scale or non-hierarchical recurrent VL models, and whether they correlate with answer correctness on specific samples (the paper measures aggregate attention statistics, not per-sample causal attribution).
Caveats
•
Comparisons to larger dense baselines are all at 0.14T tokens of training. The paper doesn’t claim this ordering holds at modern frontier-scale training budgets.
•
The 1B comparison table (Table 2) stacks LoopVL at 0.14T tokens against models trained on 3T-36T tokens. LoopVL wins on some benchmarks (MathVision, several MMK12 subjects) and loses on others (ChartQA, VMCBench, AI2D). The paper is honest that this is a mixed picture, not uniform dominance.
•
Reinforcement-learning post-training uses only 0.006B tokens from a single source (Vision-R1-RL), and the authors note extended reasoning can get stuck in repetition. The reasoning claims are preliminary.
•
The language backbone is pretrained from scratch using HRM-Text’s framework and data recipe. If you want to replicate, you’re inheriting a specific hierarchical recurrent prior; results may not transfer to a flat recurrent backbone, which they didn’t train as a control.
•
“Visual Aha Moment” is a descriptive label for an attention statistic shifting at the cycle boundary. The paper explicitly does not claim this shift causes correct answers, and attention-weight interpretability has well-known limits.
Topics
Inference Optimization
Mechanistic Interpretability
Multimodal
Computer Vision
Inference Optimization
Mechanistic Interpretability
Multimodal
Computer Vision
Up next in Inference Optimization
Speculative Forcing for Efficient Autoregressive Video Generation
SCOPE: Semantic Bounded Credit Optimization for Prompt Engineering in Text-to-image Generation
Don't miss new content
Log in to follow topics and personalize your feed.
Related topics you might like
Multimodal153 episodes
Mechanistic Interpretability34 episodes
Inference Optimization159 episodes