Use case 01
Use Inpaint when the team needs targeted image edits without losing the same campaign memory that powers the rest of the platform.
Image / Inpaint
Replace, repair, and direct specific image regions without rebuilding the whole composition.
Inpaint is the targeted edit route for teams who need to change one section of the frame while preserving the rest of the image.
Inpaint tied back to the active campaign
Region replacement visible enough to review clearly
Selective revisions packaged as part of the same release flow
Local realism kept inside the operating loop
Primary fit
Targeted image edits
Core control
Region replacement
Deliverables
Selective revisions
Use cases
What teams actually use this route for.
These pages are now filled as operating surfaces, not placeholders, so each route explains where it fits inside the wider Hadogen workflow.
Use case 02
Inpaint is strongest when region replacement needs to stay visible and repeatable across more than one launch or format.
Use case 03
The route makes the most sense when selective revisions should move directly into local realism and then into a broader Hadogen release package.
Route sequence
The route is structured around concrete operating moves.
This is the sequence teams typically follow when they use this route as part of a broader campaign system.
01
Start from the targeted image edits need
Use Inpaint when the team needs targeted image edits but still wants the route attached to the same campaign spine and decision history.
02
Use region replacement as the main lever
The route is structured around region replacement, which helps teams move from direction into selective revisions without dropping context.
03
Close the loop through local realism
The final step is not just generation. Inpaint stays valuable because local realism remains visible inside the same release cycle.
How it works
The route is broken into modules that map to real production decisions.
Each module explains what this lane controls, where it fits, and how it connects to the wider Hadogen system.
01
Where the route fits
Inpaint fits teams working on targeted image edits. The route becomes more valuable when that job stays tied to the same campaign context as the rest of Hadogen.
02
What the route actually controls
Inpaint is built around region replacement. That focus keeps the output narrower and more repeatable than a general-purpose generator surface.
03
How the route moves forward
Inpaint should end in selective revisions, then feed directly into local realism and the wider campaign system instead of stopping as a disconnected draft.
Related routes
Move deeper through the platform without leaving the same campaign logic.
FAQ
Questions teams usually ask before they use this route.
Who should use Inpaint?
Inpaint is built for teams focused on targeted image edits who still want that work attached to the same campaign operating layer as briefs, references, review, and delivery.
What does Inpaint control inside Hadogen?
The route is mainly about region replacement. That is the main lever it gives operators while still pushing toward selective revisions.
What should teams open after Inpaint?
Most teams move from Inpaint into Image Editor once selective revisions is ready for local realism or for the next step in the release cycle.