Papers › Three things everyone should know about Vision Transformers
Three things everyone should know about Vision Transformers
Hugo Touvron, Matthieu Cord, Alaaeldin El-Nouby, Jakob Verbeek, Hervé Jégou
After their initial success in natural language processing, transformer architectures have rapidly gained traction in computer vision, providing state-of-the-art results for tasks such as image classification, detection, segmentation, and video analysis. We offer three insights based on simple and easy to implement variants of vision transformers. (1) The residual layers of vision transformers, which are usually processed sequentially, can to some extent be processed efficiently in parallel without noticeably affecting the accuracy. (2) Fine-tuning the weights of the attention layers is sufficient to adapt vision transformers to a higher resolution and to other classification tasks. This saves compute, reduces the peak memory consumption at fine-tuning time, and allows sharing the majority of weights across tasks. (3) Adding MLP-based patch pre-processing layers improves Bert-like self-supervised training based on patch masking. We evaluate the impact of these design choices using the ImageNet-1k dataset, and confirm our findings on the ImageNet-v2 test set. Transfer performance is measured across six smaller datasets.
In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.
Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, on Syntology's MCP service (how to connect):
get_harvested_code_for_paper(arxiv_id="2203.09795")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2203.09795", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2203.09795")
Code
No sample from the archive's official repository (facebookresearch/deit) is linked to this paper; the 1 sample below comes from 1 community repository. Syntology harvested code from facebookresearch/deit for 2 other papers.
facebookresearch/deit: Syntology's graph links these samples to Augmenting Convolutional networks with attention-based aggregation (arXiv:2112.13692; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified) and Towards Understanding Why Label Smoothing Degrades Selective Classification and How to Fix It (arXiv:2403.14715; that paper's own run record: 9 ran (of which 2 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 0 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method.
Syntology 1 code sample harvested from 1 repository linked to this paper: 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.
By repository: community (archive-listed): 1 sample from 1 repository, 1 ran (1 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
No sample is linked to this paper from 4 of its repositories that Syntology harvested for other papers:
- facebookresearch/deit, official repository: harvested for 2 other papers, listed under the repository
- lucidrains/vit-pytorch, community (archive-listed): harvested for 5 other papers, listed under the repository
- rwightman/pytorch-image-models, community (archive-listed): harvested for another paper, listed under the repository
- yangyucheng000/University, community (archive-listed): harvested for another paper, listed under the repository
No date is recorded for the sample that ran: its level was written before Syntology's graph kept the date.
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.
Code Syntology ran Syntology
1 sample harvested: 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 0 of the 1 sample are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from conceptofmind/Parallel-ViT-flax. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.
Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.
6ba8cee9f5daea41 · report
fixture: signature t:int/0/int · returned tuple · level recorded, date not recorded Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Fine-Grained Image Classification | Stanford Cars | ViT-L (attn finetune) | Accuracy | 93.8% | #62 of 83 | Archive leaderboard | report |
| Image Classification | CIFAR-10 | ViT-B (attn fine-tune) | Percentage correct | 99.3 | #10 of 265 | Archive leaderboard | report |
| Image Classification | CIFAR-100 | ViT-L (attn fine-tune) | Percentage correct | 93.0 | #11 of 211 | Archive leaderboard | report |
| Image Classification | Flowers-102 | ViT-B (attn finetune) | Accuracy | 98.5 | #24 of 52 | Archive leaderboard | report |
| Image Classification | ImageNet | ViT-L@384 (attn finetune) | Top 1 Accuracy | 85.5% | #218 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | ViT-B@384 (attn finetune) | Top 1 Accuracy | 84.3% | #324 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | ViT-B-36x1 | Top 1 Accuracy | 84.1% | #347 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | ViT-B-18x2 | Top 1 Accuracy | 84.1% | #348 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | ViT-B (hMLP + BeiT) | Top 1 Accuracy | 83.4% | #425 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | ViT-S-24x2 | Top 1 Accuracy | 82.6% | #520 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | ViT-S-48x1 | Top 1 Accuracy | 82.3% | #549 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet V2 | ViT-B-36x1 | Top 1 Accuracy | 73.9 | #19 of 33 | Archive leaderboard | report |
| Image Classification | iNaturalist 2018 | ViT-L (attn finetune) | Top-1 Accuracy | 75.3% | #27 of 60 | Archive leaderboard | report |
Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.
Methods
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