Papers › TeCH: Text-guided Reconstruction of Lifelike Clothed Humans

TeCH: Text-guided Reconstruction of Lifelike Clothed Humans

16 Aug 2023arXiv:2308.08545archive 2025-07-28

Yangyi Huang, Hongwei Yi, Yuliang Xiu, Tingting Liao, Jiaxiang Tang, Deng Cai, Justus Thies

Despite recent research advancements in reconstructing clothed humans from a single image, accurately restoring the "unseen regions" with high-level details remains an unsolved challenge that lacks attention. Existing methods often generate overly smooth back-side surfaces with a blurry texture. But how to effectively capture all visual attributes of an individual from a single image, which are sufficient to reconstruct unseen areas (e.g., the back view)? Motivated by the power of foundation models, TeCH reconstructs the 3D human by leveraging 1) descriptive text prompts (e.g., garments, colors, hairstyles) which are automatically generated via a garment parsing model and Visual Question Answering (VQA), 2) a personalized fine-tuned Text-to-Image diffusion model (T2I) which learns the "indescribable" appearance. To represent high-resolution 3D clothed humans at an affordable cost, we propose a hybrid 3D representation based on DMTet, which consists of an explicit body shape grid and an implicit distance field. Guided by the descriptive prompts + personalized T2I diffusion model, the geometry and texture of the 3D humans are optimized through multi-view Score Distillation Sampling (SDS) and reconstruction losses based on the original observation. TeCH produces high-fidelity 3D clothed humans with consistent & delicate texture, and detailed full-body geometry. Quantitative and qualitative experiments demonstrate that TeCH outperforms the state-of-the-art methods in terms of reconstruction accuracy and rendering quality. The code will be publicly available for research purposes at https://huangyangyi.github.io/TeCH

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 14 code samples harvested from 1 repository linked to this paper: 12 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 14 samples from 1 repository, 12 ran (9 with no instrument failure; 3 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

huangyangyi/tech officialmentioned in papermentioned on GitHubpytorchMITSyntology: 14 samples, 12 ran (3 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

14 samples harvested: 12 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 3 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 last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · our draft was wrong
1ran; the contract check could not run
9ran
2unverified

Licence: 0 of the 14 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 huangyangyi/tech. “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.

huangyangyi/tech official repository 14 samples, 12 ran (3 instrument-failed) · 2 unverified
compact_tets core/lib/dmtet_network.py ran MIT (permissive) · 21f8db18059249bd · report fixture: signature pos_nx3:Tensor/2/float, sdf_n:Tensor/1/float, tet_fx4:Tensor/2/int · returned tuple · level recorded 2026-09-24
crop_by_mask core/lib/loss_utils.py ran MIT (permissive) · 720478a23c7f1394 · report fixture: signature rgb:Tensor/4/float, alpha:Tensor/4/float, base_size:int/0/int · returned tuple · level recorded 2026-09-24
get_edt core/lib/loss_utils.py ran MIT (permissive) · f74a827acce57b00 · report fixture: signature gt_mask:Tensor/4/float, loss_mask:Tensor/4/float, kernel_size:int/0/int, edt_power:float/0/float, l2_weight:float/0/float, edge_weight:float/0/float · returned Tensor · level recorded 2026-09-24
get_embedder in 88 papers core/lib/network_utils.py ran · our draft was wrong fingerprinted MIT (permissive) · d5b158881d454655 · report fixture: signature multires:int/0/int · returned tuple · level recorded 2026-09-22
get_encoder in 45 papers core/lib/encoding.py ran MIT (permissive) · f8e889919d6ffe62 · report fixture: signature encoding:str/0/str, input_dim:int/0/int, multires:int/0/int, degree:int/0/int, num_levels:int/0/int, level_dim:int/0/int, base_resolution:int/0/int, log2_hashmap_size:int/0/int, desired_resolution:int/0/int, align_corners:bool/0/bool, interpolation:str/0/str, input_bounds:NoneType/0/? · returned tuple · level recorded 2026-09-24
get_encoder in 45 papers core/lib/network_utils.py ran MIT (permissive) · cd89be610e2d21cd · report fixture: signature encoding:str/0/str, input_dim:int/0/int, multires:int/0/int, degree:int/0/int, num_levels:int/0/int, level_dim:int/0/int, base_resolution:int/0/int, log2_hashmap_size:int/0/int, desired_resolution:int/0/int, align_corners:bool/0/bool, interpolation:str/0/str · returned tuple · level recorded 2026-09-24
laplace_regularizer_const core/lib/dmtet_network.py ran MIT (permissive) · 39c9419cae242513 · report fixture: signature mesh_verts:Tensor/2/float, mesh_faces:Tensor/2/int · returned Tensor · level recorded 2026-09-24
nms in 65 papers core/lib/annotators.py ran; the contract check could not run (RAISES) MIT (permissive) · fa18e29c0ab322c6 · report fixture: signature x:ndarray/2/int, t:float/0/float, s:float/0/float · returned ndarray · level recorded 2026-09-24
rgb2srgb core/lib/color_utils.py ran fingerprinted MIT (permissive) · 29830e1e724bb23b · report fixture: signature imgs:Tensor/2/float · returned Tensor · level recorded 2026-09-24
rgb2xyz core/lib/color_utils.py ran MIT (permissive) · 3c6c1b5fa43f8aa8 · report fixture: signature var:Tensor/2/float, device:str/0/str · returned Tensor · level recorded 2026-09-24
rgb2ycrcb core/lib/color_utils.py ran fingerprinted MIT (permissive) · 99a27d0a0d932250 · report fixture: signature imgs:Tensor/4/float · returned Tensor · level recorded 2026-09-24
safe_normalize in 19 papers core/lib/camera_utils.py ran · our draft was wrong fingerprinted MIT (permissive) · 1c9cf033d080b2e0 · report fixture: signature x:Tensor/2/float, eps:float/0/float · returned Tensor · level recorded 2026-09-22
get_rays in 39 papers core/lib/camera_utils.py unverified MIT (permissive) · 33fea52680be893b · report
silhouette_loss core/lib/loss_utils.py unverified MIT (permissive) · 2396978f462745b3 · report

Tasks

DescriptiveQuestion AnsweringVisual Question AnsweringVisual Question Answering (VQA)

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Diffusion

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