Papers › Seedream 2.0: A Native Chinese-English Bilingual Image Generation Foundation Model

Seedream 2.0: A Native Chinese-English Bilingual Image Generation Foundation Model

10 Mar 2025arXiv:2503.07703archive 2025-07-28

Lixue Gong, Xiaoxia Hou, Fanshi Li, Liang Li, Xiaochen Lian, Fei Liu, Liyang Liu, Wei Liu, Wei Lu, Yichun Shi, Shiqi Sun, Yu Tian, Zhi Tian, Peng Wang, Xun Wang, Ye Wang, Guofeng Wu, Jie Wu, Xin Xia, Xuefeng Xiao, Linjie Yang, Zhonghua Zhai, Xinyu Zhang, Qi Zhang, Yuwei Zhang, Shijia Zhao, Jianchao Yang, Weilin Huang

Rapid advancement of diffusion models has catalyzed remarkable progress in the field of image generation. However, prevalent models such as Flux, SD3.5 and Midjourney, still grapple with issues like model bias, limited text rendering capabilities, and insufficient understanding of Chinese cultural nuances. To address these limitations, we present Seedream 2.0, a native Chinese-English bilingual image generation foundation model that excels across diverse dimensions, which adeptly manages text prompt in both Chinese and English, supporting bilingual image generation and text rendering. We develop a powerful data system that facilitates knowledge integration, and a caption system that balances the accuracy and richness for image description. Particularly, Seedream is integrated with a self-developed bilingual large language model as a text encoder, allowing it to learn native knowledge directly from massive data. This enable it to generate high-fidelity images with accurate cultural nuances and aesthetic expressions described in either Chinese or English. Beside, Glyph-Aligned ByT5 is applied for flexible character-level text rendering, while a Scaled ROPE generalizes well to untrained resolutions. Multi-phase post-training optimizations, including SFT and RLHF iterations, further improve the overall capability. Through extensive experimentation, we demonstrate that Seedream 2.0 achieves state-of-the-art performance across multiple aspects, including prompt-following, aesthetics, text rendering, and structural correctness. Furthermore, Seedream 2.0 has been optimized through multiple RLHF iterations to closely align its output with human preferences, as revealed by its outstanding ELO score. In addition, it can be readily adapted to an instruction-based image editing model, such as SeedEdit, with strong editing capability that balances instruction-following and image consistency.

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

By repository: community (archive-listed): 13 samples from 1 repository, 11 ran (8 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-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 11 samples that ran has no recorded date.

DYEvaLab/EvalMuse mentioned on GitHubpytorchApache-2.0Syntology: 13 samples, 11 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

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

3ran · our draft was wrong
8ran
2unverified

Licence: 2 of the 13 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 DYEvaLab/EvalMuse. “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.

DYEvaLab/EvalMuse community (archive-listed) 13 samples, 11 ran (3 instrument-failed) · 2 unverified
compute_metrics in 208 papers NTIRE2025/Track1_Alignment/evaluate.py ran fingerprinted Apache-2.0 (permissive) · c398976e864ca923 · report fixture: signature y_pred:ndarray/1/float, y:ndarray/1/float · returned tuple · level recorded 2026-09-24
find_connected_components NTIRE2025/Track2_Structure/evaluate.py ran Apache-2.0 (permissive) · 3ce6f2c660bdd4d5 · report fixture: signature mask:ndarray/2/int, area_threshold:int/0/int · returned list · level recorded 2026-09-24
get_plcc_srcc NTIRE2025/Track2_Structure/evaluate.py ran fingerprinted Apache-2.0 (permissive) · 157d2a06ef6e5db1 · report fixture: signature y_pred:ndarray/1/float, y:ndarray/1/float · returned tuple · level recorded 2026-09-24
interpolate_pos_embed in 59 papers lavis/models/vit.py ran · our draft was wrong Apache-2.0 (permissive) · c6ec173f19f5c34d · report fixture: signature pos_embed_checkpoint:Tensor/3/float, visual_encoder:callable/0/? · returned Tensor · level recorded, date not recorded
is_sublist process/element2mask.py ran Apache-2.0 (permissive) · 39c7582f0f751221 · report fixture: signature lst1:list/1/int, lst2:list/1/int · returned bool · level recorded 2026-09-24
load_csv_as_dict_list utils.py ran Apache-2.0 (permissive) · 7a749446072d47a6 · report fixture: signature file_path:str/0/str · returned list · level recorded 2026-09-25
load_data in 700 papers utils.py ran Apache-2.0 (permissive) · 43ad22367a932664 · report fixture: signature file_path:str/0/str, file_type:str/0/str · returned list · level recorded 2026-09-25
load_json_as_dict_list utils.py ran Apache-2.0 (permissive) · 7c83ce9ecb81c347 · report fixture: signature file_path:str/0/str · returned list · level recorded 2026-09-24
logistic_func NTIRE2025/Track1_Alignment/evaluate.py ran fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · eecc2b52c51e67dc · report fixture: signature X:ndarray/1/float, bayta1:float/0/float, bayta2:float/0/float, bayta3:float/0/float, bayta4:float/0/float · returned ndarray · level recorded 2026-09-24
node_to_dict in 40 papers lavis/common/config.py ran · our draft was wrong Apache-2.0 (permissive) · 791c72070c0b1cfb · report fixture: signature node:DictConfig/0/? · returned dict · level recorded 2026-09-24
tile in 109 papers
census: 5 implementations from 7 papers, 4 distinct outputs across 3 buckets, one shared input per bucket
lavis/models/base_model.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · cb33571427334815 · report fixture: signature x:Tensor/4/float, dim:int/0/int, n_tile:int/0/int · returned Tensor · level recorded 2026-09-24
all_gather_with_grad in 93 papers lavis/models/base_model.py unverified Apache-2.0 (permissive) · 0ec9fc2025c16f65 · report
calculate_score in 15 papers NTIRE2025/Track1_Alignment/evaluate.py unverified Apache-2.0 (permissive) · a33274f4811ba44b · report

Tasks

Image GenerationInstruction FollowingLarge Language Model

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

ALIGNDiffusionSFT

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