Papers › TotalSegmentator: robust segmentation of 104 anatomical structures in CT images

TotalSegmentator: robust segmentation of 104 anatomical structures in CT images

11 Aug 2022arXiv:2208.05868archive 2025-07-28

Jakob Wasserthal, Hanns-Christian Breit, Manfred T. Meyer, Maurice Pradella, Daniel Hinck, Alexander W. Sauter, Tobias Heye, Daniel Boll, Joshy Cyriac, Shan Yang, Michael Bach, Martin Segeroth

We present a deep learning segmentation model that can automatically and robustly segment all major anatomical structures in body CT images. In this retrospective study, 1204 CT examinations (from the years 2012, 2016, and 2020) were used to segment 104 anatomical structures (27 organs, 59 bones, 10 muscles, 8 vessels) relevant for use cases such as organ volumetry, disease characterization, and surgical or radiotherapy planning. The CT images were randomly sampled from routine clinical studies and thus represent a real-world dataset (different ages, pathologies, scanners, body parts, sequences, and sites). The authors trained an nnU-Net segmentation algorithm on this dataset and calculated Dice similarity coefficients (Dice) to evaluate the model's performance. The trained algorithm was applied to a second dataset of 4004 whole-body CT examinations to investigate age dependent volume and attenuation changes. The proposed model showed a high Dice score (0.943) on the test set, which included a wide range of clinical data with major pathologies. The model significantly outperformed another publicly available segmentation model on a separate dataset (Dice score, 0.932 versus 0.871, respectively). The aging study demonstrated significant correlations between age and volume and mean attenuation for a variety of organ groups (e.g., age and aortic volume; age and mean attenuation of the autochthonous dorsal musculature). The developed model enables robust and accurate segmentation of 104 anatomical structures. The annotated dataset (https://doi.org/10.5281/zenodo.6802613) and toolkit (https://www.github.com/wasserth/TotalSegmentator) are publicly available.

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 12 code samples harvested from 2 repositories linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 2 honoured, 0 violated, 9 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, 2 ran (2 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 10 samples from 1 repository, 9 ran (9 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-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

wasserth/totalsegmentator officialmentioned in papermentioned on GitHubpytorchSyntology: 2 samples, 2 ran (0 instrument-failed) · 0 unverified report
stanfordmimi/totalsegmentatorv2 mentioned on GitHubpytorchApache-2.0Syntology: 10 samples, 9 ran (0 instrument-failed) · 1 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

12 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 2 honoured, 0 violated, 9 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.

2ran · honoured contract
9ran
1unverified

Licence: 0 of the 12 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 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.

wasserth/totalsegmentator official repository 2 samples, 2 ran (0 instrument-failed) · 0 unverified
positive_float totalsegmentator/bin/TotalSegmentator.py ran · honoured contract Apache-2.0 (permissive) · a10d5a7ef3cf306b · report fixture: signature value:str/0/str · returned float · level recorded 2026-09-22
resampling_order totalsegmentator/bin/TotalSegmentator.py ran · honoured contract Apache-2.0 (permissive) · 40eb90ea5711b3d7 · report fixture: signature value:str/0/str · returned int · level recorded 2026-09-22
stanfordmimi/totalsegmentatorv2 community (archive-listed) 10 samples, 9 ran (0 instrument-failed) · 1 unverified
command_exists totalsegmentatorv2/dicom_io.py ran Apache-2.0 (permissive) · d1a4855959beb8d9 · report fixture: signature command:str/0/str · returned bool · level recorded 2026-09-25
crop_to_bbox totalsegmentatorv2/cropping.py ran Apache-2.0 (permissive) · 56b08e7a65ca7b6f · report fixture: signature image:ndarray/3/float, bbox:list/1/list · returned ndarray · level recorded 2026-09-25
get_bbox_from_mask in 5 papers totalsegmentatorv2/cropping.py ran Apache-2.0 (permissive) · 37ba223dc48dddd1 · report fixture: signature mask:ndarray/3/float, outside_value:int/0/int, addon:int/0/int · returned list · level recorded 2026-09-25
get_config_key totalsegmentatorv2/config.py ran fingerprinted Apache-2.0 (permissive) · 0eafd685e8045cc3 · report fixture: signature key_name:str/0/str · returned str · level recorded 2026-09-25
is_valid_license totalsegmentatorv2/config.py ran Apache-2.0 (permissive) · 226ac7dd432d8d40 · report fixture: signature license_number:str/0/str · returned bool · level recorded 2026-09-25
keep_largest_blob totalsegmentatorv2/postprocessing.py ran Apache-2.0 (permissive) · 0333f6eb1f790f7f · report fixture: signature data:ndarray/2/int, debug:bool/0/bool · returned ndarray · level recorded 2026-09-25
remove_small_blobs totalsegmentatorv2/postprocessing.py ran Apache-2.0 (permissive) · 5fa84fa04d5cb866 · report fixture: signature img:ndarray/2/int, interval:list/1/int, debug:bool/0/bool · returned ndarray · level recorded 2026-09-25
reorder_multilabel_like_v1 totalsegmentatorv2/libs.py ran Apache-2.0 (permissive) · 8eab68f75cf61e14 · report fixture: signature data:ndarray/2/int, label_map_v2:dict/0/?, label_map_v1:dict/0/? · returned ndarray · level recorded 2026-09-25
setup_totalseg totalsegmentatorv2/config.py ran Apache-2.0 (permissive) · cb6f2c57ee0d3459 · report fixture: signature totalseg_id:str/0/str · returned dict · level recorded 2026-09-25
undo_canonical totalsegmentatorv2/alignment.py unverified Apache-2.0 (permissive) · 49ba65e86a9016df · report

Tasks

Segmentation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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