Papers › ULIP: Learning a Unified Representation of Language, Images, and Point Clouds for 3D...

ULIP: Learning a Unified Representation of Language, Images, and Point Clouds for 3D Understanding

10 Dec 2022CVPR 2023 1arXiv:2212.05171archive 2025-07-28

Le Xue, Mingfei Gao, Chen Xing, Roberto Martín-Martín, Jiajun Wu, Caiming Xiong, ran Xu, Juan Carlos Niebles, Silvio Savarese

The recognition capabilities of current state-of-the-art 3D models are limited by datasets with a small number of annotated data and a pre-defined set of categories. In its 2D counterpart, recent advances have shown that similar problems can be significantly alleviated by employing knowledge from other modalities, such as language. Inspired by this, leveraging multimodal information for 3D modality could be promising to improve 3D understanding under the restricted data regime, but this line of research is not well studied. Therefore, we introduce ULIP to learn a unified representation of images, texts, and 3D point clouds by pre-training with object triplets from the three modalities. To overcome the shortage of training triplets, ULIP leverages a pre-trained vision-language model that has already learned a common visual and textual space by training with massive image-text pairs. Then, ULIP learns a 3D representation space aligned with the common image-text space, using a small number of automatically synthesized triplets. ULIP is agnostic to 3D backbone networks and can easily be integrated into any 3D architecture. Experiments show that ULIP effectively improves the performance of multiple recent 3D backbones by simply pre-training them on ShapeNet55 using our framework, achieving state-of-the-art performance in both standard 3D classification and zero-shot 3D classification on ModelNet40 and ScanObjectNN. ULIP also improves the performance of PointMLP by around 3% in 3D classification on ScanObjectNN, and outperforms PointCLIP by 28.8% on top-1 accuracy for zero-shot 3D classification on ModelNet40. Our code and pre-trained models are released at https://github.com/salesforce/ULIP.

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 1 code sample harvested from 1 repository linked to this paper: 1 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; 1 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: official repository: 1 sample from 1 repository, 1 ran (0 with no instrument failure; 1 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

salesforce/ulip officialmentioned in papermentioned on GitHubpytorchBSD-3-ClauseSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 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

1 sample harvested: 1 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; 1 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure 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 · our draft was wrong

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 salesforce/ulip. “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.

salesforce/ulip official repository 1 sample, 1 ran (1 instrument-failed) · 0 unverified
get_metric_names in 11 papers models/ULIP_models.py ran · our draft was wrong BSD-3-Clause (permissive) · 01955600041e2b19 · report fixture: signature model:callable/0/? · returned list · level recorded 2026-09-22

Tasks

3D Architecture3D Classification3D Point Cloud ClassificationClassificationLanguage ModellingTraining-free 3D Point Cloud ClassificationZero-Shot Transfer 3D Point Cloud ClassificationZero-shot 3D Point Cloud ClassificationZero-shot 3D classification

Datasets

Introduced by this paper, per the archive.

ModelNet40 (Pretrained on ShapeNet)

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Point Cloud Classification ModelNet40 ULIP + PointMLP Mean Accuracy 92.4 #6 of 111 Archive leaderboard report
3D Point Cloud Classification ModelNet40 ULIP + PointMLP Overall Accuracy 94.7 #6 of 111 Archive leaderboard report
3D Point Cloud Classification ModelNet40 ULIP + PointBERT Overall Accuracy 94.1 #23 of 111 Archive leaderboard report
3D Point Cloud Classification ModelNet40 ULIP + PointNet++(ssg) Mean Accuracy 91.2 #61 of 111 Archive leaderboard report
3D Point Cloud Classification ModelNet40 ULIP + PointNet++(ssg) Overall Accuracy 93.4 #61 of 111 Archive leaderboard report
3D Point Cloud Classification ScanObjectNN ULIP + PointNeXt Mean Accuracy 88.6 #22 of 77 Archive leaderboard report
3D Point Cloud Classification ScanObjectNN ULIP + PointNeXt Number of params 1.4M #22 of 77 Archive leaderboard report
3D Point Cloud Classification ScanObjectNN ULIP + PointNeXt Overall Accuracy 89.7 #22 of 77 Archive leaderboard report
3D Point Cloud Classification ScanObjectNN ULIP + PointMLP Mean Accuracy 88.5 #26 of 77 Archive leaderboard report
3D Point Cloud Classification ScanObjectNN ULIP + PointMLP Overall Accuracy 89.4 #26 of 77 Archive leaderboard report
3D Point Cloud Classification ScanObjectNN ULIP + PointBERT Overall Accuracy 86.4 #50 of 77 Archive leaderboard report
Training-free 3D Point Cloud Classification ModelNet40 ULIP Accuracy (%) 60.4 #4 of 7 Archive leaderboard report
Training-free 3D Point Cloud Classification ModelNet40 ULIP Need 3D Data? Yes #4 of 7 Archive leaderboard report
Zero-Shot Transfer 3D Point Cloud Classification ModelNet40 ULIP + PointMLP Accuracy (%) 61.5 #13 of 16 Archive leaderboard report
Zero-Shot Transfer 3D Point Cloud Classification ModelNet40 ULIP + PointBERT Accuracy (%) 60.4 #14 of 16 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