Methods › Computer Vision › Image Models › MLP-Mixer

MLP-Mixer

96 papers tagged archive 2025-07-28

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

The MLP-Mixer architecture (or “Mixer” for short) is an image architecture that doesn't use convolutions or self-attention. Instead, Mixer’s architecture is based entirely on multi-layer perceptrons (MLPs) that are repeatedly applied across either spatial locations or feature channels. Mixer relies only on basic matrix multiplication routines, changes to data layout (reshapes and transpositions), and scalar nonlinearities.

It accepts a sequence of linearly projected image patches (also referred to as tokens) shaped as a “patches × channels” table as an input, and maintains this dimensionality. Mixer makes use of two types of MLP layers: channel-mixing MLPs and token-mixing MLPs. The channel-mixing MLPs allow communication between different channels; they operate on each token independently and take individual rows of the table as inputs. The token-mixing MLPs allow communication between different spatial locations (tokens); they operate on each channel independently and take individual columns of the table as inputs. These two types of layers are interleaved to enable interaction of both input dimensions.

Source: MLP-Mixer: An all-MLP Architecture for Vision

In Syntology repository known, no verified implementation (declared_code; repositories: 5 listed of 49 in the graph, strongest link: official). The archive credits no paper with an arXiv id for this method, so whether this answer (about arXiv:2105.01601) is about this method is not checked.

Code Syntology holds under other names, as the lookup lists them (code_nearby); not a complete list, and none of them is this method.

Origin paper of this answer, arXiv:2105.01601 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 114 ran (of which 77 constructed an object rather than computing a result; 104 with no instrument failure: 2 honoured, 1 violated, 101 with no contract checked; 10 where Syntology's instrument failed) · 20 unverified (of 134 harvested samples) · 40 pointer-only (licence). The instrument figure counts failures of Syntology's instrument, not of the code. Ran means executed on a synthesized input, not that the code is correct.

Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.

What each level means, quoted from Syntology's server card: V0 “imports”; V1 “executes against a synthesized fixture and returns a value of the recorded type”; V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” The card adds: “No rung on this ladder compares the served code against the authors' implementation, so treat every level as evidence about runnability and internal agreement, not about matching the paper's results.” A level quoted in two parts is one definition the card writes as two clauses joined by a double hyphen, each clause quoted on its own (how these levels are quoted).

Papers archive 2025-07-28

archive papers tagged: 96 · with a code link: 67 · where Syntology ran a sample: 23 (20 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (23 of 96 tagged: 20 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument)

Page 1 of 1: papers 1 to 96 of 96, newest first by the archive's date (ties by slug), in archive order.

Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.

Tasks archive 2025-07-28

20 shown of 138 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Image Classification23
image-classification16
Inductive Bias9
Object Detection7
Semantic Segmentation7
Time Series6
object-detection6
Classification5
Medical Image Analysis4
Transfer Learning4
All3
Benchmarking3
Computational Efficiency3
Data Augmentation3
GPU3
Image-to-Image Translation3
Knowledge Distillation3
Language Modeling3
Language Modelling3
Time Series Forecasting3

Usage over time archive 2025-07-28

Papers per year tagged with MLP-Mixer: 2021 to 2025, peak 26 26 0 2021: 26 papers 2021 2022: 21 papers 2022 2023: 17 papers 2023 2024: 24 papers 2024 2025: 8 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (96 dated). Bars are counts, not a trend claim.

Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).

Categories archive 2025-07-28

Image Models

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections