Papers › CLIPSelf: Vision Transformer Distills Itself for Open-Vocabulary Dense Prediction

CLIPSelf: Vision Transformer Distills Itself for Open-Vocabulary Dense Prediction

2 Oct 2023arXiv:2310.01403archive 2025-07-28

Size Wu, Wenwei Zhang, Lumin Xu, Sheng Jin, Xiangtai Li, Wentao Liu, Chen Change Loy

Open-vocabulary dense prediction tasks including object detection and image segmentation have been advanced by the success of Contrastive Language-Image Pre-training (CLIP). CLIP models, particularly those incorporating vision transformers (ViTs), have exhibited remarkable generalization ability in zero-shot image classification. However, when transferring the vision-language alignment of CLIP from global image representation to local region representation for the open-vocabulary dense prediction tasks, CLIP ViTs suffer from the domain shift from full images to local image regions. In this paper, we embark on an in-depth analysis of the region-language alignment in CLIP models, which is essential for downstream open-vocabulary dense prediction tasks. Subsequently, we propose an approach named CLIPSelf, which adapts the image-level recognition ability of CLIP ViT to local image regions without needing any region-text pairs. CLIPSelf empowers ViTs to distill itself by aligning a region representation extracted from its dense feature map with the image-level representation of the corresponding image crop. With the enhanced CLIP ViTs, we achieve new state-of-the-art performance on open-vocabulary object detection, semantic segmentation, and panoptic segmentation across various benchmarks. Models and code are released at https://github.com/wusize/CLIPSelf.

PaperPDFCodeCode Syntology ran

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):

Code

Syntology 6 code samples harvested from 1 repository linked to this paper: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 6 samples from 1 repository, 4 ran (4 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.

Levels written between 2026-09-24 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

wusize/clipself officialmentioned in papermentioned on GitHubpytorchNOASSERTIONSyntology: 6 samples, 4 ran (0 instrument-failed) · 2 unverified report

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.

Code Syntology ran Syntology

6 samples harvested: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 2 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.

4ran
2unverified

Licence: 6 of the 6 samples 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 wusize/clipself. “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.

wusize/clipself official repository 6 samples, 4 ran (0 instrument-failed) · 2 unverified
load_class_freq in 14 papers F-ViT/models/custom_losses.py ran licence not identified · pointer only · 42264faf65871374 · report fixture: signature path:str/0/str, freq_weight:float/0/float, min_count:int/0/int · returned Tensor · level recorded 2026-09-24
load_state_dict in 114 papers src/open_clip/factory.py ran no licence file found · pointer only · 4b3a4d17e1df3140 · report fixture: signature checkpoint_path:str/0/str, map_location:str/0/str · returned dict · level recorded 2026-09-24
prepare_inputs_for_generation in 58 papers src/open_clip/coca_model.py ran no licence file found · pointer only · fb651d0a97fd4d3f · report fixture: signature input_ids:Tensor/2/int, image_inputs:Tensor/3/float, past:NoneType/0/?, attention_mask:Tensor/2/int, position_ids:Tensor/2/int · returned dict · level recorded 2026-09-26
register_pooler in 46 papers src/open_clip/hf_model.py ran no licence file found · pointer only · 2a377da4a76a2d44 · report fixture: signature cls:callable/0/? · returned type · level recorded 2026-09-26
gather_features in 78 papers src/open_clip/loss.py unverified licence not identified · pointer only · fd6321f5fd69ea0a · report
get_model_config in 45 papers src/open_clip/factory.py unverified no licence file found · pointer only · 5c7cf820e99443ff · report

Tasks

Image ClassificationImage SegmentationObject DetectionOpen Vocabulary Object DetectionOpen Vocabulary Panoptic SegmentationOpen Vocabulary Semantic SegmentationOpen-vocabulary object detectionPanoptic SegmentationPredictionSegmentationSemantic SegmentationZero-Shot Image Classificationimage-classificationobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Open Vocabulary Object Detection LVIS v1.0 CLIPSelf AP novel-LVIS base training 34.9 #5 of 28 Archive leaderboard report
Open Vocabulary Object Detection MSCOCO CLIPSelf AP 0.5 44.3 #7 of 32 Archive leaderboard report
Open Vocabulary Panoptic Segmentation ADE20K CLIPSelf PQ 23.7 #6 of 10 Archive leaderboard report
Open Vocabulary Semantic Segmentation ADE20K-150 CLIPSelf mIoU 34.5 #10 of 23 Archive leaderboard report
Open Vocabulary Semantic Segmentation ADE20K-847 CLIPSelf mIoU 12.4 #14 of 19 Archive leaderboard report
Open Vocabulary Semantic Segmentation PASCAL Context-59 CLIPSelf mIoU 62.3 #5 of 24 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

CLIP

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