Papers › Point-BERT: Pre-training 3D Point Cloud Transformers with Masked Point Modeling

Point-BERT: Pre-training 3D Point Cloud Transformers with Masked Point Modeling

29 Nov 2021CVPR 2022 1arXiv:2111.14819archive 2025-07-28

Xumin Yu, Lulu Tang, Yongming Rao, Tiejun Huang, Jie zhou, Jiwen Lu

We present Point-BERT, a new paradigm for learning Transformers to generalize the concept of BERT to 3D point cloud. Inspired by BERT, we devise a Masked Point Modeling (MPM) task to pre-train point cloud Transformers. Specifically, we first divide a point cloud into several local point patches, and a point cloud Tokenizer with a discrete Variational AutoEncoder (dVAE) is designed to generate discrete point tokens containing meaningful local information. Then, we randomly mask out some patches of input point clouds and feed them into the backbone Transformers. The pre-training objective is to recover the original point tokens at the masked locations under the supervision of point tokens obtained by the Tokenizer. Extensive experiments demonstrate that the proposed BERT-style pre-training strategy significantly improves the performance of standard point cloud Transformers. Equipped with our pre-training strategy, we show that a pure Transformer architecture attains 93.8% accuracy on ModelNet40 and 83.1% accuracy on the hardest setting of ScanObjectNN, surpassing carefully designed point cloud models with much fewer hand-made designs. We also demonstrate that the representations learned by Point-BERT transfer well to new tasks and domains, where our models largely advance the state-of-the-art of few-shot point cloud classification task. The code and pre-trained models are available at https://github.com/lulutang0608/Point-BERT

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 6 code samples harvested from 2 repositories linked to this paper: 5 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; 4 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 3 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 5 samples from 1 repository, 4 ran (1 with no instrument failure; 3 where Syntology's instrument failed); community (archive-listed): 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 5 samples that ran has no recorded date.

lulutang0608/Point-BERT officialmentioned in papermentioned on GitHubpytorchMITSyntology: 5 samples, 4 ran (3 instrument-failed) · 1 unverified report
julie-tang00/point-bert mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
lmd0311/pointmamba mentioned on GitHubpytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to PointMamba: A Simple State Space Model for Point Cloud Analysis (arXiv:2402.10739; that paper's own run record: 8 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 0 violated, 1 with no contract checked; 6 where Syntology's instrument failed) · 3 unverified); nothing checks that they implement this paper's method. 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

6 samples harvested: 5 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; 4 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 last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
1ran · our draft was wrong
3ran; the contract check could not run
1unverified

Licence: 2 of the 6 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

lulutang0608/Point-BERT official repository 5 samples, 4 ran (3 instrument-failed) · 1 unverified
farthest_point_sample in 64 papers datasets/ModelNetDataset.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · f80066a00e7156a2 · report fixture: signature point:ndarray/2/float, npoint:int/0/int · returned ndarray · level recorded 2026-09-25
knn_point in 23 papers
census: 4 implementations from 5 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 3, kind float, dtype float32 · arg 2: rank 3, kind float, dtype float32
models/dvae.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) · 3fc6f6b239b211f9 · report fixture: signature nsample:int/0/int, xyz:Tensor/3/float, new_xyz:Tensor/3/float · returned Tensor · level recorded 2026-09-22
pc_normalize in 81 papers
census: 2 implementations from 6 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
datasets/ModelNetDataset.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only · 4783fbece52f500e · report fixture: signature pc:ndarray/2/float · returned ndarray · level recorded 2026-09-22
square_distance in 89 papers
census: 11 implementations from 18 papers, 4 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 3, kind float, dtype float32 · arg 2: rank 3, kind float, dtype float32
models/dvae.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · 3bfe172e686075cd · report fixture: signature src:Tensor/3/float, dst:Tensor/3/float · returned Tensor · level recorded, date not recorded
julie-tang00/point-bert community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
evaluate_svm tools/runner_BERT_pretrain.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · 0771dfb62d38a68e · report fixture: signature train_features:ndarray/2/float, train_labels:ndarray/1/int, test_features:ndarray/2/float, test_labels:ndarray/1/int · returned float64 · level recorded 2026-09-22

Tasks

3D Point Cloud Classification3D Point Cloud Linear ClassificationFew-Shot 3D Point Cloud ClassificationFew-Shot Point Cloud ClassificationPoint Cloud ClassificationPoint Cloud Segmentation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Point Cloud Classification ModelNet40 Point-BERT Overall Accuracy 93.8 #44 of 111 Archive leaderboard report
3D Point Cloud Classification ScanObjectNN Point-BERT OBJ-BG (OA) 87.43 #64 of 77 Archive leaderboard report
3D Point Cloud Classification ScanObjectNN Point-BERT OBJ-ONLY (OA) 88.12 #64 of 77 Archive leaderboard report
3D Point Cloud Classification ScanObjectNN Point-BERT Overall Accuracy 83.1 #64 of 77 Archive leaderboard report
Few-Shot 3D Point Cloud Classification ModelNet40 10-way (10-shot) Point-BERT Overall Accuracy 91.0 #18 of 31 Archive leaderboard report
Few-Shot 3D Point Cloud Classification ModelNet40 10-way (10-shot) Point-BERT Standard Deviation 5.4 #18 of 31 Archive leaderboard report
Few-Shot 3D Point Cloud Classification ModelNet40 10-way (20-shot) Point-BERT Overall Accuracy 92.7 #18 of 31 Archive leaderboard report
Few-Shot 3D Point Cloud Classification ModelNet40 10-way (20-shot) Point-BERT Standard Deviation 5.1 #18 of 31 Archive leaderboard report
Few-Shot 3D Point Cloud Classification ModelNet40 5-way (10-shot) Point-BERT Overall Accuracy 94.6 #17 of 30 Archive leaderboard report
Few-Shot 3D Point Cloud Classification ModelNet40 5-way (10-shot) Point-BERT Standard Deviation 3.1 #17 of 30 Archive leaderboard report
Few-Shot 3D Point Cloud Classification ModelNet40 5-way (20-shot) Point-BERT Overall Accuracy 96.3 #18 of 30 Archive leaderboard report
Few-Shot 3D Point Cloud Classification ModelNet40 5-way (20-shot) Point-BERT Standard Deviation 2.7 #18 of 30 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

Absolute Position EncodingsAdamAttentionAttention DropoutBERTBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerLinear Warmup With Linear DecayMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformerWeight DecayWordPiece

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