Papers › Image Segmentation Using Text and Image Prompts

Image Segmentation Using Text and Image Prompts

18 Dec 2021CVPR 2022 1arXiv:2112.10003archive 2025-07-28

Timo Lüddecke, Alexander S. Ecker

Image segmentation is usually addressed by training a model for a fixed set of object classes. Incorporating additional classes or more complex queries later is expensive as it requires re-training the model on a dataset that encompasses these expressions. Here we propose a system that can generate image segmentations based on arbitrary prompts at test time. A prompt can be either a text or an image. This approach enables us to create a unified model (trained once) for three common segmentation tasks, which come with distinct challenges: referring expression segmentation, zero-shot segmentation and one-shot segmentation. We build upon the CLIP model as a backbone which we extend with a transformer-based decoder that enables dense prediction. After training on an extended version of the PhraseCut dataset, our system generates a binary segmentation map for an image based on a free-text prompt or on an additional image expressing the query. We analyze different variants of the latter image-based prompts in detail. This novel hybrid input allows for dynamic adaptation not only to the three segmentation tasks mentioned above, but to any binary segmentation task where a text or image query can be formulated. Finally, we find our system to adapt well to generalized queries involving affordances or properties. Code is available at https://eckerlab.org/code/clipseg.

PaperPDFConference PDFCodeCode 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 2 code samples 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: 1 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 2 samples 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 2 of its repositories that Syntology harvested for other papers:

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

timojl/clipseg officialmentioned on GitHubpytorchSyntology: 2 samples, 1 ran (0 instrument-failed) · 1 unverified report
casia-iva-lab/fastsam mentioned on GitHubpytorchAGPL-3.0Syntology: not harvested report
huggingface/transformers mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Attention Is All You Need (arXiv:1706.03762; that paper's own run record: 610 ran (of which 293 constructed an object rather than computing a result; 529 with no instrument failure: 45 honoured, 15 violated, 469 with no contract checked; 81 where Syntology's instrument failed) · 336 unverified), HuggingFace's Transformers: State-of-the-art Natural Language Processing (arXiv:1910.03771; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified), DeBERTa: Decoding-enhanced BERT with Disentangled Attention (arXiv:2006.03654; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 2 honoured, 1 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 9 unverified) and 1 more (every one in this page's JSON twin); nothing checks that they implement this paper's method. report
openrobotlab/ov_parts mentioned on GitHubjaxSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to OV-PARTS: Towards Open-Vocabulary Part Segmentation (arXiv:2310.05107; that paper's own run record: 10 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 0 violated, 3 with no contract checked; 6 where Syntology's instrument failed) · 4 unverified); nothing checks that they implement this paper's method. report
2024-MindSpore-1/Code2 mindsporeSyntology: not harvested report
MindSpore-scientific/code-7 Syntology: not harvested 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.

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

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

1ran · honoured contract
1unverified

Licence: 2 of the 2 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 timojl/clipseg. “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.

timojl/clipseg official repository 2 samples, 1 ran (0 instrument-failed) · 1 unverified
cosine_warmup_lr training.py ran · honoured contract fingerprinted licence not identified · pointer only · 057d183d358d1e9a · report fixture: signature i:int/0/int, warmup:int/0/int, max_iter:int/0/int · returned float · level recorded 2026-09-22
get_cached_pascal_pfe score.py unverified licence not identified · pointer only · c78a6fe00b0a118f · report

Tasks

DecoderImage SegmentationMulti-modal image segmentationOne-Shot SegmentationReferring ExpressionReferring Expression SegmentationReferring Image Matting (Expression-based)Referring Image Matting (Keyword-based)Referring Image Matting (RefMatte-RW100)SegmentationSemantic SegmentationZero Shot Segmentation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Referring Image Matting (Expression-based) RefMatte CLIPSeg (ViT-B/16) MAD 0.0394 #3 of 4 Archive leaderboard report
Referring Image Matting (Expression-based) RefMatte CLIPSeg (ViT-B/16) MAD(E) 0.0419 #3 of 4 Archive leaderboard report
Referring Image Matting (Expression-based) RefMatte CLIPSeg (ViT-B/16) MSE 0.0358 #3 of 4 Archive leaderboard report
Referring Image Matting (Expression-based) RefMatte CLIPSeg (ViT-B/16) MSE(E) 0.0381 #3 of 4 Archive leaderboard report
Referring Image Matting (Expression-based) RefMatte CLIPSeg (ViT-B/16) SAD 69.13 #3 of 4 Archive leaderboard report
Referring Image Matting (Expression-based) RefMatte CLIPSeg (ViT-B/16) SAD(E) 73.53 #3 of 4 Archive leaderboard report
Referring Image Matting (Keyword-based) RefMatte CLIPSeg (ViT-B/16) MAD 0.0101 #3 of 4 Archive leaderboard report
Referring Image Matting (Keyword-based) RefMatte CLIPSeg (ViT-B/16) MAD(E) 0.0106 #3 of 4 Archive leaderboard report
Referring Image Matting (Keyword-based) RefMatte CLIPSeg (ViT-B/16) MSE 0.0064 #3 of 4 Archive leaderboard report
Referring Image Matting (Keyword-based) RefMatte CLIPSeg (ViT-B/16) MSE(E) 0.0067 #3 of 4 Archive leaderboard report
Referring Image Matting (Keyword-based) RefMatte CLIPSeg (ViT-B/16) SAD 17.75 #3 of 4 Archive leaderboard report
Referring Image Matting (Keyword-based) RefMatte CLIPSeg (ViT-B/16) SAD(E) 18.69 #3 of 4 Archive leaderboard report
Referring Image Matting (RefMatte-RW100) RefMatte CLIPSeg (ViT-B/16) MAD 0.1222 #4 of 4 Archive leaderboard report
Referring Image Matting (RefMatte-RW100) RefMatte CLIPSeg (ViT-B/16) MAD(E) 0.1282 #4 of 4 Archive leaderboard report
Referring Image Matting (RefMatte-RW100) RefMatte CLIPSeg (ViT-B/16) MSE 0.1178 #4 of 4 Archive leaderboard report
Referring Image Matting (RefMatte-RW100) RefMatte CLIPSeg (ViT-B/16) MSE(E) 0.1236 #4 of 4 Archive leaderboard report
Referring Image Matting (RefMatte-RW100) RefMatte CLIPSeg (ViT-B/16) SAD 211.86 #4 of 4 Archive leaderboard report
Referring Image Matting (RefMatte-RW100) RefMatte CLIPSeg (ViT-B/16) SAD(E) 222.37 #4 of 4 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.

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