A source image and a reference image may look similar in the upload tray, but they have different responsibilities.
The source defines the room or design being changed. A reference provides selected visual direction. Keeping those roles separate produces clearer instructions, cleaner revisions, and a more reliable project history.
The source defines the space
The source is the base image for the render. It might be:
- a design-software export
- a photograph of an existing room
- an approved concept render
- the latest version you want to revise
It establishes the composition the model should work from: room geometry, camera position, openings, major objects, and the visible relationship between elements.
Choose a source that supports the decision you want to make. If the question is about island color, the island needs to be clearly visible. If the question is about the relationship between cabinetry and flooring, the crop should show enough of both materials to judge them together.
A technically sharp image is helpful, but clarity of purpose matters more. A cluttered photo with three competing focal points can be less useful than a clean, moderately sized export that shows the exact design condition under review.
References guide selected decisions
A reference is not the room you are redesigning. It is evidence for a material, product, finish, mood, or visual behavior you want to apply.
Useful references include:
- a close photograph of a cabinet finish
- a stone slab or tile sample
- a fixture or appliance product image
- a lighting or atmosphere example
- a previous approved render with the right design language
The image alone is not enough. Assign it a category and explain what to use from it.
For example:
Use this reference for the cabinet species, warm-neutral tone, and low-sheen finish. Do not copy its door style, hardware, or room layout.
That sentence tells the model what is relevant and what is noise.
Give each reference one job
References become unreliable when one image is asked to control too many unrelated decisions.
A photograph of an inspiration kitchen may contain attractive cabinets, counters, floors, hardware, lighting, windows, styling, and proportions. If the instruction says only make it look like this, every visible feature becomes a possible interpretation target.
Use a narrower assignment:
| Reference category | Useful instruction |
|---|---|
| Cabinetry | Match the wood tone and grain restraint only |
| Countertops | Use the warm base color and sparse vein movement |
| Flooring | Follow the plank width, finish, and neutral undertone |
| Lighting | Use the soft directional quality, not the fixture design |
| Style | Apply the calm, edited atmosphere without copying layout |
If two references conflict, decide which one is more important for the current render. Project RNDR lets each use carry its own category, instruction, and importance so the same canonical asset can support different project decisions without changing its identity.
The image is reusable. Its role belongs to the current render.
That distinction is especially useful when a material sample appears in several projects. Upload it once, then describe how it should influence each new concept.
Protect approved details
A strong source-reference workflow includes an explicit preservation list.
If the layout is approved, protect it. If the appliance package is selected, protect appliance locations. If the client is evaluating only finishes, preserve windows, doors, ceiling conditions, camera position, and major dimensions visible in the source.
This does not guarantee pixel-perfect continuity—generative systems can still introduce errors—but it gives the render a disciplined brief and makes misses easier to identify.
When a selected reference belongs to a category that later becomes protected, detach it from the current render rather than leaving it visually selected but silently inactive. The interface should tell the same story as the generation request.
For a revision, use the latest approved image as the source and carry forward only the references still relevant to the next decision. Old references remain part of the project history; they do not need to control every future version.
A simple preflight check
Before rendering, ask five questions:
- Is the source the exact room or version I want to change?
- Can I describe one clear decision this render should support?
- Does every selected reference have one category and one specific job?
- Have I named the details that must remain unchanged?
- Would someone else understand the brief without seeing my private mood board?
If the answer to the last question is no, tighten the instructions before spending a generation.
A useful mental model is simple:
- Source: where the work happens
- Reference: visual evidence for a selected decision
- Instruction: how that evidence applies now
- Preserve: what the exploration must respect
- Version: the durable result of that specific brief
Once those parts have distinct roles, rendering becomes less like asking for a surprise and more like directing a focused visual study.