Papers › StylizedNeRF: Consistent 3D Scene Stylization as Stylized NeRF via 2D-3D Mutual Learning

StylizedNeRF: Consistent 3D Scene Stylization as Stylized NeRF via 2D-3D Mutual Learning

24 May 2022CVPR 2022 1arXiv:2205.12183archive 2025-07-28

Yi-Hua Huang, Yue He, Yu-Jie Yuan, Yu-Kun Lai, Lin Gao

3D scene stylization aims at generating stylized images of the scene from arbitrary novel views following a given set of style examples, while ensuring consistency when rendered from different views. Directly applying methods for image or video stylization to 3D scenes cannot achieve such consistency. Thanks to recently proposed neural radiance fields (NeRF), we are able to represent a 3D scene in a consistent way. Consistent 3D scene stylization can be effectively achieved by stylizing the corresponding NeRF. However, there is a significant domain gap between style examples which are 2D images and NeRF which is an implicit volumetric representation. To address this problem, we propose a novel mutual learning framework for 3D scene stylization that combines a 2D image stylization network and NeRF to fuse the stylization ability of 2D stylization network with the 3D consistency of NeRF. We first pre-train a standard NeRF of the 3D scene to be stylized and replace its color prediction module with a style network to obtain a stylized NeRF. It is followed by distilling the prior knowledge of spatial consistency from NeRF to the 2D stylization network through an introduced consistency loss. We also introduce a mimic loss to supervise the mutual learning of the NeRF style module and fine-tune the 2D stylization decoder. In order to further make our model handle ambiguities of 2D stylization results, we introduce learnable latent codes that obey the probability distributions conditioned on the style. They are attached to training samples as conditional inputs to better learn the style module in our novel stylized NeRF. Experimental results demonstrate that our method is superior to existing approaches in both visual quality and long-range consistency.

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 15 code samples harvested from 1 repository linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 1 violated, 5 with no contract checked; 5 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 2 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: 15 samples from 1 repository, 11 ran (6 with no instrument failure; 5 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.

iglict/stylizednerf officialpytorchMITSyntology: 15 samples, 11 ran (5 instrument-failed) · 4 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

15 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 1 violated, 5 with no contract checked; 5 where Syntology's instrument failed) · 4 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 · violated contract
2ran · our draft was wrong
3ran; the contract check could not run
5ran
4unverified

Licence: 0 of the 15 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 iglict/stylizednerf. “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.

iglict/stylizednerf official repository 15 samples, 11 ran (5 instrument-failed) · 4 unverified
adaptive_instance_normalization in 37 papers
census: 5 implementations from 7 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 4, kind float, dtype float32 · arg 2: rank 4, kind float, dtype float32
Style_function.py ran · our draft was wrong fingerprinted MIT (permissive) · 16679a24b9881031 · report fixture: signature content_feat:Tensor/4/float, style_feat:Tensor/4/float · returned Tensor · level recorded 2026-09-22
calc_mean_std in 64 papers Style_function.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · 38eaf8511dc7bc9c · report fixture: signature feat:Tensor/4/float, eps:float/0/float · returned tuple · level recorded 2026-09-22
coral in 15 papers Style_function.py ran · our draft was wrong MIT (permissive) · 277f955e6caa9cfb · report fixture: signature source:Tensor/2/float, target:Tensor/2/float · returned Tensor · level recorded 2026-09-25
image_transform in 11 papers dataset.py ran MIT (permissive) · e991990b383b4401 · report fixture: signature size:int/0/int, crop:bool/0/bool · returned Compose · level recorded 2026-09-24
json_read_rgbd utils.py ran MIT (permissive) · 1c3b4acc6042ef47 · report fixture: signature DepthImg_path:str/0/str, RgbImg_path:str/0/str, factor:float/0/float · returned tuple · level recorded 2026-09-24
ndc2world train_style_modules.py ran MIT (permissive) · 9b7551cdc32913e0 · report fixture: signature coor_ndc:Tensor/3/float, h:int/0/int, w:int/0/int, focal:float/0/float · returned Tensor · level recorded 2026-09-24
normalize in 638 papers
census: 70 implementations from 82 papers, 51 distinct outputs across 11 buckets, one shared input per bucket this sample: bucket 3 of 11, arg 1: rank 1, kind float, dtype float64
load_llff.py ran · violated contract fingerprinted MIT (permissive) · 1d6f8390d799f055 · report fixture: signature x:ndarray/1/float · returned ndarray · level recorded 2026-09-22
ptstocam in 11 papers load_llff.py ran; the contract check could not run (RAISES) MIT (permissive) · 36f5de7a0aae4a9b · report fixture: signature pts:ndarray/2/float, c2w:ndarray/2/float · returned ndarray · level recorded 2026-09-25
read_ply in 16 papers utils.py ran MIT (permissive) · c6f78245da55a3f8 · report fixture: signature path:str/0/str · returned ndarray · level recorded 2026-09-24
read_rgbd utils.py ran MIT (permissive) · 0c53cb3537bd258a · report fixture: signature DepthImg_path:str/0/str, RgbImg_path:str/0/str · returned tuple · level recorded 2026-09-24
viewmatrix in 18 papers load_llff.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) · aa52acee18f54d38 · report fixture: signature z:ndarray/1/float, up:ndarray/1/float, pos:ndarray/1/float · returned ndarray · level recorded 2026-09-22
cal_geometry rendering.py unverified MIT (permissive) · 5e3dafa27d74cb58 · report
render in 19 papers rendering.py unverified MIT (permissive) · a1d7be7500efae44 · report
render_style rendering.py unverified MIT (permissive) · 821d0b44eff38d97 · report
view_synthesis dataset.py unverified MIT (permissive) · b9851df6a7434a2b · report

Tasks

Image StylizationNeRF

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