Workflow

Published Aug 24, 2026

Updated Sep 18, 2026Last verified Sep 18, 2026

8 min read

Uncensored AI Image Generation and Editing: A Production Guide

Connect text-to-image, references, localized edits, version records, and human review into a reproducible spicy image workflow.

Key takeawayGeneration explores; editing converges. Separating the two is usually less expensive and more reliable than rerolling the whole image.

Short answer

For reliable uncensored image editing, request one change at a time and explicitly preserve subject identity, composition, lighting, and text. Qwen Image Edit Spicy provides a dedicated edit contract, so the input asset and instruction remain auditable instead of being buried in chat history.

Start with the question behind the search

Many teams send every revision back through text-to-image, causing composition, identity, clothing, and background to change together. A more reliable approach uses generation to explore a small set of directions, approves one base image, and then assigns only the required region to an editing model. This reduces cost and leaves a clear version history.

How to evaluate beyond a polished demo

Score composition, style, and subject during generation; score requested change and preservation during editing.
State both what must change and what must remain in the editing prompt.
Handle one objective per edit and sequence multi-objective changes as versions.
Save source, mask, prompt, seed, model, and request ID so reviewers can reproduce the result.

ModelRush options for the job

Use Z-Image Spicy to explore multiple base compositions at low cost.
After approving a base, use Qwen Image Edit Spicy for targeted changes.
For conventional commercial visuals combining references and editing, also evaluate Wan 2.7 Image Pro.

A reproducible production workflow

In phase one, submit four distinct compositions and approve only one. In phase two, give every change an edit instruction, a preservation list, and a version number. The review queue shows the base, requested difference, model, cost, and rights information together. Only the final approved version enters public storage; intermediate versions follow the data retention policy.

Frequently asked questions

Must generation and editing use the same model?

No. A stable workflow depends on input/output contracts and version records, not on forcing one model through every stage.

How do I stop an edit from changing the whole image?

Narrow the edit scope, state preservation constraints, change one objective at a time, and compare each round against the approved base.

Can the workflow edit a real person?

Only with clear rights and subject consent. Minors, fraud, impersonation, and non-consensual intimate use are strictly prohibited.

Create separate generation and editing steps with the ModelRush image API, then optimize for approval rate rather than raw output count.

Minimum working request

/v1/images/edits

bash
curl -X POST https://api.modelrush.ai/v1/images/edits \
  -H "Authorization: Bearer $MODELRUSH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "modelrush/qwen-image-edit-spicy",
    "image": ["https://example.com/input.png"],
    "prompt": "Change only the background to a night city; preserve the subject"
  }'

What to verify before production

The model links, API schema, and live pricing table on this page are the source of truth. Recheck output quality, latency, moderation behavior, and cost with the same production-like input before committing traffic.

Current pricing for the models in this article

Rates come from the ModelRush Registry and use the same immutable price version as billing.

Model	Capability	Price variant	Customer price
Qwen Image Edit Spicy · modelrush/qwen-image-edit-spicy	Image editing	Standard	$0.040 / generation

Registry revision · 2026-10-14.apipod

Next steps

Move straight from this article to model details, current pricing, API documentation, and the Playground.

Qwen Image Edit Spicy model details Qwen Image Edit Spicy API pricing Image generation API documentation Run this model in the Playground

Bring the workflow into your project

Use a complete agent prompt to build, inspect, and verify the ModelRush integration.