A 3840-pixel-wide exterior arrives in a studio folder. At fit-to-screen size it looks polished. At full size the mullions wander, leaves melt into railings, brick joints stop at the corner, and a door handle has become a strip of light. The workflow met the requested dimensions and missed the assignment.
Today's community sweep again surfaced requests for a ComfyUI process that can improve lighting, textures, reflections, vegetation, and overall detail while maintaining the architectural composition. Another request asks how to run image-to-image on architecture at 4K. Those are not node questions yet. They are delivery questions.
Before downloading a graph or choosing a model, write a one-page contract for the output. It should define the frame, protected facts, permitted edits, review scales, and files that prove what happened.
1. Name the frame, not only “4K”
Write the exact pixel dimensions and aspect ratio. “4K” may be used casually for more than one frame shape, while an architectural board, web hero, presentation slide, and video still can require different crops. State whether the source crop is fixed and whether the final can be trimmed after generation.
List the intended placement. A full-width image on a 4K display is judged differently from a quarter-page frame in a PDF. Note whether a reviewer will zoom into facade details or see the image from across a room. The delivery context decides which defects are visible and which processing steps are worth their cost.
Do not enlarge the source merely to satisfy a number. Record its native dimensions, compression, sharpening, and any prior upscale. A large file can still contain little trustworthy detail. The graph should know what evidence exists before it invents what is missing.
2. Draw three zones
Mark protected, editable, and expendable zones on a copy of the source. Protected zones contain project facts such as massing, openings, rails, circulation, signs, property edges, and specified materials. Editable zones contain the requested work. Expendable zones can change or be cropped without changing the design claim.
A sky may be expendable in one frame and part of an approved lighting study in another. Vegetation may be presentation atmosphere or a documented planting proposal. Glass reflections may be editable while the mullion grid behind them remains protected. Put each element in a zone instead of assuming the model knows its status.
| Zone | Typical contents | Acceptance rule |
|---|---|---|
| Protected | Silhouette, openings, access, rails, signs | No unapproved movement, deletion, or addition |
| Editable | Named light, finish, planting, cleanup task | Requested change appears inside its boundary |
| Expendable | Crop margin, generic sky, temporary entourage | Change may occur but must not contaminate protected zones |
Export authoritative masks from the source application when possible. If the team only has a flat image, say that the masks are editorial boundaries, not object data. That distinction prevents a guessed edge from being treated as model truth.
3. Give every requested improvement a noun
“More realistic” is not an edit. Name the defect or target: flat north facade, repeating grass texture, black glazing, noisy tree edge, plastic concrete, smeared chair, or empty planter. Then state what evidence can support the correction.
ComfyUI's official image-to-image tutorial explains that denoise controls how much the result departs from the input: lower values preserve more of the source, while higher values allow greater change. That is a behavior to test, not a universal setting to copy. The acceptable departure depends on the protected zones and the model in the installed graph.
Structural guidance also has a specific job. The official depth ControlNet example uses estimated depth to influence composition. For project work, label an estimated depth map as an interpretation of the image. A depth pass exported from the 3D scene carries different authority. Save whichever one the graph uses.
4. Set two review scales
Approve the image once at delivery size and once at a defined inspection zoom. The delivery-size review asks whether hierarchy, light, material separation, and composition work in context. The inspection review checks repeated elements, junctions, text, hands, rails, window rhythm, vegetation edges, and texture continuity.
Do not let unlimited zoom become an endless defect hunt. Pick an inspection scale before processing and tie it to the placement. A full-screen client display may justify a 100 percent pixel review. A small PDF image may need a lower practical threshold, plus targeted checks on legally or architecturally important details.
Use the same scales for source and output. Enhancement often exposes defects that were already present while introducing new ones elsewhere. A side-by-side at fixed zoom separates inherited flaws from generated changes.
5. Require a difference proof
Save an aligned source, final output, and difference image. The difference image is not a quality score. It is a map of where pixels moved. Large changes outside the editable zones demand inspection even when the final looks convincing.
Add crops for every protected junction: roof against sky, window against wall, rail against planting, door against paving, and sign against facade. Compare counts and spacing, not only texture. If the workflow processed tiles, check tile boundaries across long lines, gradients, glass, and repeated cladding.
When a change fails, rerun the smallest responsible region or stage. Do not send the entire accepted frame through another creative pass to repair one chair. The delivery contract should make local correction possible without reopening every approved decision.
6. Deliver the graph's memory
The final JPG or PNG is not the complete job. Package the source identifier, workflow JSON, model and custom-node versions, prompts, references, masks, structural maps, seeds when meaningful, intermediate approved frame, final output, and review sheet. Record any manual compositing or color correction after ComfyUI.
ComfyUI workflows can encode graph structure, but a graph alone may not preserve downloaded models, node behavior, or external files. List dependencies in readable text. Another operator should be able to see what is missing without opening a broken workflow and chasing red nodes.
Use filenames that connect every artifact to the same revision. Do not overwrite the source. If a later correction starts from the enhanced image rather than the original render, record that lineage. Repeated image-to-image passes accumulate changes that a final frame cannot explain.
A 4K file proves its dimensions. The contract proves what those pixels are allowed to say.
Our take: resolution is a container
The recurring request for a good ComfyUI architecture workflow is understandable. A downloadable graph feels concrete. Yet no graph can decide whether a tree is atmosphere or design, whether a reflection may hide a mullion, or whether a 4K frame will be printed, projected, cropped, or inspected.
Write the delivery contract first. Then choose nodes that serve its zones, evidence, and review scales. Keep the source authoritative, route named edits through the smallest necessary change, and package enough memory for another person to audit the result.
Four thousand pixels are not permission.
Editorial basis: the 3 October 2026 ArchiGen AI intel sweep, including recurring community requests for 4K image-to-image and architectural enhancement workflows. Denoise behavior was checked against the official ComfyUI image-to-image tutorial. The role of depth guidance was checked against the official ComfyUI depth ControlNet example. This is a workflow specification, not a claim of hands-on testing or universal parameter values.