Papers › Stylebreeder: Exploring and Democratizing Artistic Styles through Text-to-Image Models

Stylebreeder: Exploring and Democratizing Artistic Styles through Text-to-Image Models

20 Jun 2024arXiv:2406.14599archive 2025-07-28

Matthew Zheng, Enis Simsar, Hidir Yesiltepe, Federico Tombari, Joel Simon, Pinar Yanardag

Text-to-image models are becoming increasingly popular, revolutionizing the landscape of digital art creation by enabling highly detailed and creative visual content generation. These models have been widely employed across various domains, particularly in art generation, where they facilitate a broad spectrum of creative expression and democratize access to artistic creation. In this paper, we introduce STYLEBREEDER, a comprehensive dataset of 6.8M images and 1.8M prompts generated by 95K users on Artbreeder, a platform that has emerged as a significant hub for creative exploration with over 13M users. We introduce a series of tasks with this dataset aimed at identifying diverse artistic styles, generating personalized content, and recommending styles based on user interests. By documenting unique, user-generated styles that transcend conventional categories like 'cyberpunk' or 'Picasso,' we explore the potential for unique, crowd-sourced styles that could provide deep insights into the collective creative psyche of users worldwide. We also evaluate different personalization methods to enhance artistic expression and introduce a style atlas, making these models available in LoRA format for public use. Our research demonstrates the potential of text-to-image diffusion models to uncover and promote unique artistic expressions, further democratizing AI in art and fostering a more diverse and inclusive artistic community. The dataset, code and models are available at https://stylebreeder.github.io under a Public Domain (CC0) license.

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

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. 3 of the 10 samples that ran have no recorded date.

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

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 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.

stylebreeder/stylebreeder-code official repository 10 samples, 8 ran (5 instrument-failed) · 2 unverified
bool_flag in 47 papers utils.py ran · violated contract MIT (permissive) · 4d25be8ebf17fde1 · report fixture: signature s:str/0/str · returned bool · level recorded 2026-09-24
convert_embeddings predict_clusters.py ran · our draft was wrong MIT (permissive) · 0b00611ae9e8f91c · report fixture: signature file_paths:list/1/str · returned dict · level recorded 2026-09-24
drop_path in 325 papers
census: 27 implementations from 61 papers, 5 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 2 of 2, arg 1: rank 2, kind float, dtype float32
models/dino_vits.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) here; the stored copy is pointer only · 55120f2026b56aa2 · report fixture: signature x:Tensor/2/float, drop_prob:float/0/float, training:bool/0/bool · returned Tensor · level recorded, date not recorded
get_log_handlers search.py ran MIT (permissive) · 9cc52f98324d7fe7 · report fixture: returned tuple · level recorded 2026-09-22
is_corrupted sample_imgs_and_to_csv.py ran · violated contract MIT (permissive) · bcb186cff853eb55 · report fixture: signature filepath:str/0/str · returned bool · level recorded 2026-09-24
patchify in 32 papers
census: 6 implementations from 8 papers, 6 distinct outputs across 3 buckets, one shared input per bucket
utils.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) · 5db42d2262ce7bb3 · report fixture: signature x:Tensor/4/float, size:int/0/int · returned Tensor · level recorded 2026-09-24
process_path in 5 papers predict_clusters.py ran · our draft was wrong MIT (permissive) · 87b505a802d90228 · report fixture: signature folder_path:str/0/str · returned dict · level recorded 2026-09-24
trunc_normal_ in 154 papers
census: 37 implementations from 54 papers, 4 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
models/dino_vits.py ran; the contract check could not run (RAISES) MIT (permissive) here; the stored copy is pointer only · 056f371660385ea5 · report fixture: signature tensor:Tensor/2/float, mean:float/0/float, std:float/0/float, a:float/0/float, b:float/0/float · returned Tensor · level recorded 2026-09-22
multi_scale utils.py unverified MIT (permissive) · 4c82afb0fda4c03f · report
vit_tiny in 40 papers models/dino_vits.py unverified MIT (permissive) · 91b77e6ca5ded870 · report
cloneofsimo/lora community 3 samples, 2 ran (1 instrument-failed) · 1 unverified
inject_trainable_lora in 12 papers lora_diffusion/lora.py ran · our draft was wrong Apache-2.0 (permissive) · a1f6aab648f338b8 · report fixture: signature model:callable/0/?, target_replace_module:set/0/?, r:int/0/int, loras:NoneType/0/?, verbose:bool/0/bool, dropout_p:float/0/float, scale:float/0/float · returned tuple · level recorded, date not recorded
inject_trainable_lora_extended in 11 papers lora_diffusion/lora.py ran · honoured contract Apache-2.0 (permissive) · 5ed08f9762be44ee · report fixture: signature model:callable/0/?, target_replace_module:set/0/?, r:int/0/int, loras:NoneType/0/? · returned tuple · level recorded, date not recorded
extract_lora_ups_down in 9 papers lora_diffusion/lora.py unverified Apache-2.0 (permissive) · 33b1ae9f923ab3ec · report

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