CivArchive
    CyberRealistic Krea 2 - v2.0
    NSFW
    Preview 139904087
    Preview 139899844
    Preview 139899826
    Preview 139899836
    Preview 139972172
    Preview 139899819
    Preview 139899821
    Preview 139899833
    Preview 139900401
    Preview 139900547
    Preview 139901811
    Preview 139901463
    Preview 139902199
    Preview 139902520
    Preview 139902905
    Preview 139903281
    Preview 139903455
    Preview 139903653
    Preview 139903812
    Preview 139904698

    You can get this model through Civitai Early Access, or grab it along with many others by joining The Tinkerer on Whop. Membership gets you early releases, private tools and members-only pages. There are free pages too, no membership needed.

    👉 Join on Whop
    💬 Join the community for support, free tools and early news on Discord

    CyberRealistic Krea 2

    CyberRealistic Krea 2 is a full finetune of Krea 2 Turbo, Krea.ai's 12.9B diffusion transformer with a Qwen3-VL-4B text encoder and the Qwen Image VAE.

    Base Krea 2 is aesthetic first. It explores medium, texture and mood instead of settling on one look. Great for creative work, less useful when you want a photograph.

    This finetune moves the default toward photography. Natural skin, believable faces, available light, real materials and camera language, with less of the editorial gloss the base model drifts into.

    The creative side didn't go anywhere. The official style LoRAs still work, style reference still works, and the model will leave photography behind when you ask it to. What changed is where it starts.

    Base Krea 2 likes to interpret. CyberRealistic Krea 2 leans toward the camera.

    What changed

    • Photographic by default, no stack of realism keywords needed first

    • Less aesthetic drift on short or simple prompts

    • More natural skin texture, less plastic rendering

    • Better consistency in faces and hands

    • Stronger response to camera, lens, lighting and material descriptions

    • More predictable when you're trying to lock in a specific look

    • Still moves into illustration, print or anime when you prompt for it

    • Works with the official Krea 2 style LoRAs in my testing

    Seed variation is still there. I didn't try to remove it, since that's part of what makes Krea 2 interesting. CyberRealistic just makes it easier to stay inside one visual language.

    Which version should I download?

    CyberRealistic Krea 2 ships in five precision and quantization formats. All five contain the same finetune. What changes is file size, memory use, hardware requirements and, to a smaller extent, the image itself.

    If you're not sure: FP8.

    BF16 · reference version

    The original full-precision release and the version the other four are built from. Highest numerical precision and no quantization loss, but the largest files and the highest memory requirement.

    Best for:

    • Maximum quality

    • Merging, converting or further training

    • Systems with plenty of VRAM and RAM

    • Anyone who wants the master version

    For normal image generation you don't need BF16.

    FP8 roughly halves the size and memory footprint compared to BF16 while staying very close to it visually. It's the best all-round balance of quality, compatibility, memory use and speed.

    Best for:

    • Most ComfyUI users

    • GPUs with limited VRAM

    • Everyday generation

    • BF16-like results without BF16 requirements

    Start here if you don't want to think about it.

    INT8 ConvRot · efficient INT8

    INT8 quantization combined with ConvRot, a rotation applied before quantizing that flattens outliers and keeps more quality than a plain INT8 conversion. It needs far less memory than BF16 and runs well on hardware that likes INT8. Current ComfyUI builds support it natively on NVIDIA Turing and newer.

    Best for:

    • Low VRAM systems

    • GPUs with strong INT8 performance

    • A smaller model without giving up much quality

    INT8 isn't automatically faster than FP8. That depends on your GPU and backend, so FP8 stays the safer general-purpose pick.

    MXFP8 · Blackwell-optimized FP8

    MXFP8 is microscaling FP8. Instead of one large shared scaling range it scales small blocks of values, so the FP8 data keeps more accuracy. The real payoff comes from hardware with native MXFP8 acceleration, mainly NVIDIA Blackwell.

    Best for:

    • RTX 50-series / Blackwell

    • Setups with native MXFP8 support

    • Anyone who wants an efficient modern FP8 format

    On older cards MXFP8 gets emulated, so expect little or no gain over normal FP8.

    NVFP4 · smallest and most aggressive

    NVIDIA's 4-bit floating point format for Blackwell. By far the most compact of the five and the lowest memory footprint. It's also the most aggressive quantization here, so differences from BF16 and FP8 turn up more often depending on the prompt and settings.

    Best for:

    • Blackwell / RTX 50-series

    • Minimum VRAM use

    • Minimum model size

    • Efficiency over absolute precision

    Don't pick NVFP4 just because the file is small. On hardware that can't use it you lose most of the reason for it.

    Quick pick

    • Plenty of VRAM and want the original: BF16

    • Not sure what to download: FP8

    • Need to cut VRAM use further: INT8 ConvRot

    • RTX 50-series / Blackwell GPU: MXFP8

    • Blackwell and want the smallest file: NVFP4

    Differences between the quantized versions shift with your GPU, backend, workflow, resolution and prompt. No single format wins everywhere.

    These apply to Krea 2 Turbo and CyberRealistic Krea 2.

    • Sampler: Euler

    • Scheduler: Simple

    • Steps: 8

    • CFG (ComfyUI KSampler): 1.0

    • Guidance (official Krea code): 0.0

    • Mu / timestep shift: 1.15

    • Resolution: 1K to 2K

    About that CFG value

    Two conventions exist here and they cause a lot of confusion. Krea's own inference code uses guidance 0.0, which means CFG is off. The ComfyUI equivalent of "off" on the standard KSampler is CFG 1.0.

    Don't set the regular KSampler to 0.0. That breaks generation.

    Turbo runs without CFG, so traditional negative prompts do very little in the standard workflow. The official ComfyUI workflow simply zeroes the negative conditioning.

    Steps and resolution

    Turbo is an 8-step distilled model. More steps are not automatically better.

    Krea 2 Turbo is built for roughly 1K to 2K, so there's no need to generate everything at 1024 first if your hardware can handle more. Useful starting points:

    • 2048 × 2048

    • 1536 × 2048

    • 2048 × 1536

    • 1152 × 2048

    • 2048 × 1152

    • 1440 × 1920

    Lower resolutions are fine when you want speed or need the VRAM.

    Required models

    • CyberRealistic Krea 2 diffusion model

    • qwen3vl_4b text encoder

    • qwen_image_vae

    Prompting

    If you're coming from SDXL, Pony or Illustrious, read this part.

    Krea 2 has no CLIP text encoder. It uses Qwen3-VL-4B, so it reads your prompt much more like normal language. You don't have to forget everything you know, but most old Stable Diffusion habits stop paying off here.

    Describe, don't tag

    Natural language works very well. Comma-separated clauses are fine, and Krea's own examples use them, but each clause should describe something instead of being a loose tag.

    Instead of:

    woman, street, night, realistic, masterpiece, best quality, 8k, detailed skin

    try:

    A woman waiting alone on a quiet city street at night, photographed under the warm light of a shop window, with natural skin texture and wet pavement reflecting the streetlights.

    The second prompt tells the model what the image actually is.

    Quality tags do nothing special

    Words like masterpiece, best quality, ultra detailed, absurdres, score_9 and source_anime aren't quality switches here. Qwen reads them as ordinary language. They might nudge the result, but they're usually taking up space you could spend on something useful.

    Describe the detail you want instead.

    Skip numeric weighting

    ComfyUI can parse (rust:1.4) syntax, but I wouldn't build Krea 2 prompts around it. Stronger wording is more predictable:

    a heavily rusted iron gate, its hinges covered in rough orange corrosion

    If you're running a LoRA, LoRA strength is a much better numeric control.

    Put the subject first

    Prompt order still matters in practice. If the image is about a brass compass, start with the compass:

    A weathered brass compass resting on an old nautical chart...

    No need to obsess over exact word order. Just make the subject and the main composition clear early.

    Be specific

    • red dress becomes deep oxblood satin dress

    • orange light becomes warm sodium-vapor street lighting

    • old wall becomes sun-bleached plaster wall with hairline cracks and flaking paint

    Specific words carry more visual information than repeating "detailed" and "realistic."

    Describe the actual light

    This is the biggest single win for photographic prompts. Instead of cinematic lighting, say where the light comes from:

    soft daylight entering through a north-facing window

    a single tungsten bulb hanging above the table

    late-afternoon sunlight coming through venetian blinds

    cold fluorescent ceiling lights

    Keep actions simple

    Complex actions work, but if a pose starts breaking, simplify. One clear action per subject is a good rule. Get that working first, then add the secondary details.

    Quote your text

    If you want words in the image, put the exact text in quotation marks:

    a small neon sign reading "OPEN ALL NIGHT"

    Krea specifically recommends this.

    A structure that works

    subject → setting → composition/camera → lighting → mood/style → material and texture

    A middle-aged fisherman repairing a red net on a wooden dock, photographed from waist height with a 50mm lens, grey sea behind him, soft overcast morning light, muted natural colors, weathered hands, damp wool sweater and rough salt-stained wood.

    It doesn't have to read like literature. Dense descriptive clauses work fine. The point is that the words describe the image instead of listing magic tokens.

    How long?

    My practical ranges, not model limits:

    • 5 to 20 words: exploration, let the model decide

    • 30 to 80 words: good balance of control and freedom

    • 80 to 150 words: complex scenes, precise styling, detailed composition

    Longer prompts work. Length isn't the problem, contradiction is. Ask for soft window light, hard flash, dreamy pastels, deep black shadows and flat commercial lighting in one prompt and the model has to pick a winner. More words only help when they add information.

    Example prompts

    Available-light documentary

    A fishmonger in a yellow rubber apron arranging silver mackerel on crushed ice at a covered market stall in the early morning. Cold blue daylight enters from the open side of the market and mixes with warm tungsten bulbs above the counter. The concrete floor is wet and reflective, with slight motion blur on his hands and natural texture in the skin, rubber and fish scales.

    Natural-light portrait

    A woman laughing with her eyes closed against a pale blue sky, loose dark hair blowing across her face, wearing a sleeveless white lace top. Photographed from a slightly low angle in soft natural daylight with a minimal background, medium-format color photograph, shallow depth of field and natural skin texture.

    Low-light interior

    A nervous teenager standing alone in a convenience-store aisle at two in the morning, photographed handheld with a 35mm lens. Harsh fluorescent ceiling lights fall across the shelves and face, with slight motion blur, visible film grain, muted colors and realistic skin texture.

    Product photography

    A matte black perfume bottle standing on wet obsidian stone, photographed close-up in a dark studio. A single large softbox creates a narrow reflection along the left edge of the bottle while a subtle rim light separates it from the background. Shallow depth of field, crisp glass and stone texture, controlled specular highlights.

    A few last things

    Short prompts are great for exploring. Turbo is fast enough that generating five directions first and then adding camera, light and material detail to the one you like beats writing a perfect prompt blind.

    Text rendering is much better than older diffusion models, but it still isn't a typography engine. Quote the exact text and keep signs short.

    And the licensing. Krea 2 is not Apache 2.0. The weights and everything derived from them fall under the Krea 2 Community License, which covers commercial use, redistribution, attribution and derivative naming. Commercial use is free below the stated annual revenue threshold. Above it you need an Enterprise License from Krea. The license also requires derivative model names to start with "Krea", which is why this one is called CyberRealistic Krea 2 and not the other way around.

    If you're using or redistributing this model, read the current Krea 2 license instead of assuming the usual open-model terms.

    Description

    Grab this model and many more by joining The Tinkerer on Whop. Membership gets you early releases, private tools and members-only pages, plus a lot more.
    👉 Join on Whop

    CyberRealistic Krea2 V2 pushes the model further toward photographic realism while keeping the flexibility and strong prompt understanding of Krea 2.

    V2 builds on the first release with additional training and refinement across faces, skin, anatomy, lighting, textures and everyday photographic situations. The goal wasn't to completely change the model, but to make the look more consistent across a much wider range of prompts.

    Images should feel less polished-for-the-sake-of-being-polished and more like actual photography - natural skin texture, believable imperfections, better material detail and lighting that feels part of the scene rather than added on top of it.

    What's changed in V2

    • More consistent photographic realism, especially with simple prompts.

    • Improved skin and facial detail without pushing everything toward beauty photography.

    • Better anatomy and body consistency across a wider range of compositions.

    • More natural lighting, shadows and highlights.

    • Improved textures and small details in clothing, environments and objects.

    • Less unwanted editorial gloss and aesthetic drift.

    • Better handling of casual, imperfect and unposed photography.

    • Broader training coverage, including content on the less sanitized side of photography.

    CyberRealistic Krea2 is still primarily intended as a general-purpose photographic model. V2 isn't built around one specific genre or subject. Portraits, people, interiors, street photography, products, landscapes and more experimental or adult-oriented scenes should all live inside the same model rather than requiring separate versions.

    Model variants
    CyberRealistic Krea2 V2 is available in several formats:

    • BF16 - full-precision release and the reference version.

    • MXFP8 - reduced memory usage while staying close to BF16.

    • FP8 - a practical lower-VRAM alternative.

    • INT8 - further reduced memory requirements for compatible setups.

    • NVFP4 - the smallest variant for supported NVIDIA hardware and workflows.

    The quantized versions are provided to make the model usable on a wider range of GPUs. Small differences between formats are possible, so BF16 remains the reference if you want the model exactly as released.

    Prompting
    Krea 2 responds best to clear natural-language descriptions rather than traditional Stable Diffusion tag lists. Describe the subject, environment, composition and lighting as you would describe a photograph.

    V2 also responds well to short prompts. You don't need to bury the subject underneath quality tags to get detail - give it something interesting to photograph.

    FAQ

    Comments (32)

    SakrilegiousAug 19, 2026· 4 reactions
    CivitAI

    I had to do the following to get this model (both v1 and v2) to work as nvfp4 on Stable Diffusion:
    The NVFP4 metadata in cyberrealisticKrea2_v20.safetensors uses layer names that do not match the fully qualified tensor names.

    For example, the quantization metadata contains:

    blocks.0.attn.wq

    But the corresponding tensor is:

    model.diffusion_model.blocks.0.attn.wq.weight

    The fix was to prepend model.diffusion_model. to all 224 entries under:

    __metadata__ → _quantization_metadata → layers

    After the change, the entry becomes:

    model.diffusion_model.blocks.0.attn.wq

    This allows Forge Neo to associate the packed weights with their NVFP4 metadata correctly. Without the prefix, Forge detects/interprets the packed weights incorrectly and reports shape mismatches such as [6144, 3072] versus [6144, 6144].

    SaporyuAug 20, 2026· 1 reaction
    CivitAI

    Hi. Liked your ZiT models, but something is wrong with Krea 2 ones... I've tried Model v 1.0 fp8 and int8 versions. Both of them more than twice slower than Krea2 FP8 models from other authors - 5.4s/it other models and 12.4s/it these ones (the same settings, a dozen of generations and tests). And both fp8 and int8 gave me identical results (NOT similar, just identical pixel to pixel). And results seems like overcompressed screenshots (dirty, oversmoothed hair). I use RTX 5060 ti 16GB and ComfyUI. Is it a problem on my side? How can I fix it?

    vivalasorca917Aug 20, 2026

    Same for me with a 5080, the INT8 seems to be way slower than other INT8 models.

    Cyberdelia
    Author
    Aug 20, 2026

    @Saporyu @vivalasorca917 Mmm, need to check that! I think it's only for V1 but I will check this to be sure.

    supandifoolAug 20, 2026

    Thanks for sharing, great work on this model for v1.0, after a long wait.

    Yes, same here, v1.0 int8 taking a long time than other models.

    Also, there are some other models that have skin details far more detailed than ZIT. I was also fan of your ZIT esp v5,6. However, your Krea2 is not coming upto the mark of ZIT, wherein Krea2 itself is a big upgrade from ZIT. Can you also check that. Other model you can check is the Gonzo Krea2.

    Cyberdelia
    Author
    Aug 20, 2026

    @supandifool I'm already on V2 and the updates are on that department. If you check the +300 sample images you will see that this is better now.

    supandifoolAug 20, 2026· 1 reaction

    Yeah, will check it out when it becomes available for local usage, almost 14 days of waiting :-(

    schroeckAug 20, 2026· 1 reaction

    Hint regarding the slower speed - using Forge Neo for the v1 int8 (INFO from loader.py and k_model.py):
    Using MixedPrecision for Qwen3

    Using Detected Model Data Type: torch.float8_e4m3fn

    Diffusion Model: {storage: torch.float8_e4m3fn, computation: torch.float16}

    Usually for int8 Models it is:
    Using MixedPrecision for Qwen3

    Using MixedPrecision for Model

    Diffusion Model: {storage: torch.bfloat16, computation: Mixed}

    PohtaetoesAug 20, 2026

    I think the wrong file has been uploaded in the int8 slot. Probably a mix up while uploading the different versions.

    Dtypes

    dtype tensors bytes

    ------- ------- --------

    F32 15 1.19 GB

    F8_E4M3 415 11.64 GB


    Aside of that great finetune as always!

    wangf35979Aug 21, 2026· 1 reaction

    I encountered the same problem. But the model fine-tuning is indeed excellent; I've been following the author since Zit.

    jmblsmit129Aug 21, 2026· 2 reactions

    I made a python script sniffs out the model precision and the int8 version posted is indeed fp8. Anyone can confirm for themselves using the script here: https://pastebin.com/DN8F8c01

    I quantized the BF16 myself using convert_to_quant and the speed is as expected.

    schroeckAug 22, 2026

    @Cyberdelia would you be so kind to re-upload the int8 as true int8 (as it was discovered that the currently uploaded int8 is in fact fp8) - big thanks!

    Cyberdelia
    Author
    Aug 22, 2026· 1 reaction

    @schroeck @jmblsmit129 @wangf35979 @Pohtaetoes @supandifool @vivalasorca917 Sorry, I wasn’t able to sort this out earlier. Somehow the upload didn’t go through properly. V2 is fine, though. I’m working on fixing it now and will upload it again. Thanks everyone for the feedback - you were all right!

    UPDATE: New version is uploaded!

    Leeme161Aug 22, 2026

    @Cyberdelia I'm just getting noise with the new INT8 and it's taking too long. The FP8 generates fine. I'm kinda new to Krea 2 so it could be a mistake on my part, but other INT8 checkpoints seem to be fine. This is in Forge Neo.

    schroeckAug 22, 2026

    Newly uploaded int8convrot still not working for me in ForgeNeo =(

    Using MixedPrecision for Qwen3

    Using Override Model Data Type: torch.float16

    SingleStreamDiT Unexpected
    Diffusion Model: {storage: torch.float16, computation: torch.float16}

    Raw_FantasyAug 21, 2026· 5 reactions
    CivitAI

    Damn, this really is the best model among the Krea 2 series.

    scp890Aug 21, 2026
    CivitAI

    Pretty good and realistic results. one of my favorites now. can't wait for the v2 download link. thank you for the model

    ronaldmikhailp236Aug 22, 2026· 1 reaction
    CivitAI

    The chosen one has arrived in Krea2 to make it awesome.

    civit77899Aug 22, 2026
    CivitAI

    Similar to other Turbo variants, Cyberrealistic v1 suffers from severe sameface issue and lack of creativity. Are you planning releasing the Raw version so that we could have some variety?

    Cyberdelia
    Author
    Aug 22, 2026· 1 reaction

    I have released V2 that solve this - more variety in faces. Check the +300 sample images of V2

    unhappy_with_civitaiAug 22, 2026
    CivitAI

    Love the model (1.0), but cannot get a balls deep penetration rendered.

    K0n3zum1Aug 27, 2026

    Hmm... I haven't tested it myself, but maybe you could try this? 🤔
    https://civitai.red/models/2823421/krea2-penetration-control?modelVersionId=3200626

    unhappy_with_civitaiAug 27, 2026

    @K0n3zum1 well, they claim you should prompt with (Belly_bump:3) but the prompt parser does not understand this weighting syntax... does not look like they really know what they are doing. Also, they used very very little training images.

    K0n3zum1Aug 27, 2026

    @unhappy_with_civitai A lot of people still use that syntax even with Krea if you look closely. At worst, in a prompt, it'll just be ignored. But as a trigger, I don't know... I saw leetspeak used as triggers with no problem.
    Syntax-wise, if you browse galleries, you'll see people who've even managed to generate decent images with tags in Krea. 😆
    Now, looking at the comments on that LoRA, it seems some users still got the expected result with it, so maybe it's worth not judging it too quickly. 🤷🏻‍♀️

    Cyberdelia
    Author
    Aug 27, 2026· 1 reaction

    @unhappy_with_civitai @K0n3zum1 The reason it doesn’t work that well is that I had to remove some training because they caused conflicts with other poses. I may have fixed this in the next version; otherwise, I could also release a separate LoRA for it. That said, there are already plenty of LoRAs available that solve this issue.

    gershuAug 23, 2026· 1 reaction
    CivitAI

    From the controlled randomness of SDXL to Krea 2/Qwen is a wild ride, took me a few hours to understand the prompting dynamic but once you get the structure in place, refining the prompt for specific actions produces very high-quality results in seconds. So far, VERY impressed by 1.0, will keep testing and can't wait to test 2.0. Thank you!

    premoticrautre8277261Aug 23, 2026
    CivitAI

    The INT8 model seems to be broken on Forge Neo. This is all it will generate for me:
    https://civitai.com/posts/30577091
    Other INT8 checkpoints for Krea 2 are fine.

    premoticrautre8277261Aug 23, 2026

    Testing the FP8 version, and it works fine. GPU is Ampere architecture, which has native support for INT8, but lacks native support for FP8 so the speed is supposed to be slower.

    JFTCAug 24, 2026· 11 reactions
    CivitAI

    Thank you for not following the idiocy that is happening on this site and making it paid only without early access. I am glad at least one of my absolutely favorite creators will not get blocked. You are awesome and thanks for all the hard work.

    Cyberdelia
    Author
    Aug 24, 2026· 1 reaction

    Haha, I had to read the “and making it paid only” part twice - for a second I thought I was being accused of joining the dark side. 😄

    But seriously, thank you! I really appreciate the kind words!

    zworth552Aug 27, 2026
    CivitAI

    This author is consistently producing some of the best and a go to everytings. Thanks for sharing!

    arrssenneAug 28, 2026
    CivitAI

    hate dessayer ta version 2

    Checkpoint
    Krea 2
    by Cyberdelia
    Download (Beta) View on CivitAI
    realistic
    base model
    cinematic
    sf
    fantasy
    photorealistic

    Details

    Downloads
    49
    Platform
    CivitAI
    Platform Status
    Available
    Created
    8/19/2026
    Updated
    8/31/2026
    Deleted
    -

    Files

    cyberrealisticKrea2_v20_txt.safetensors

    Size:
    8.27 GB
    SHA256:
    36f3ff447ef59201722e8f9ce6020c9819fdcfba6aa2608c4e09b1c0ce114e34

    Mirrors

    HuggingFace (26 mirrors)
    CivitAI (4 mirrors)
    ModelScope (2 mirrors)
    ModelScope CN (1 mirrors)

    cyberrealisticKrea2_v20.safetensors

    Size:
    11.94 GB
    SHA256:
    b307877656a426d017311db6ad1a9e5e9e6af035655c6d6cfb3b6d23b27b8a71

    Mirrors

    CivitAI (1 mirrors)

    cyberrealisticKrea2_v20.safetensors

    Size:
    23.88 GB
    SHA256:
    dcfb76a260b169bb4e50215480e9b8a7630a7eeb3a2d78ae81200537e7e59759

    Mirrors

    CivitAI (1 mirrors)

    cyberrealisticKrea2_v20.safetensors

    Size:
    12.91 GB
    SHA256:
    8e1d446fa6f122888121ef4cddcdc4c7a6598f72b3a21bf39ce780a26e0e6b67

    Mirrors

    CivitAI (1 mirrors)

    cyberrealisticKrea2_v20_txt.safetensors

    Size:
    4.88 GB
    SHA256:
    54bd5144df0bbc25dd6ccadfcb826b521445a1b06ae5a42570bdd2974ca87094

    Mirrors

    HuggingFace (45 mirrors)
    CivitAI (10 mirrors)
    ModelScope (1 mirrors)

    cyberrealisticKrea2_v20.safetensors

    Size:
    12.57 GB
    SHA256:
    20a975e888763cd58d7211b2f3513c51b8d104118555363b3e3be2db036a9f5a

    Mirrors

    CivitAI (1 mirrors)

    qwen_image_vae.safetensors

    Size:
    242.05 MB
    SHA256:
    a70580f0213e67967ee9c95f05bb400e8fb08307e017a924bf3441223e023d1f

    Mirrors

    HuggingFace (255 mirrors)
    CivitAI (203 mirrors)
    TensorFiles (1 mirrors)
    ModelScope (3 mirrors)
    ModelScope CN (5 mirrors)

    cyberrealisticKrea2_v20.safetensors

    Size:
    7.61 GB
    SHA256:
    5d8127b2cbe3d7e5928b5cf10a651df7857c9fc70ea8bebe21d50d2292a983eb

    Mirrors

    CivitAI (1 mirrors)