Reflective packaging is rarely documented in one perfect photograph. A front view may show the label clearly while hiding the side profile. A three-quarter photograph may explain the cap and shoulder but turn silver foil into a dark mirror. Another image may capture the material beautifully while showing an older label. Uploading every view without assigning responsibilities leaves Seedream 5.0 Pro to decide which evidence wins.
The current ClipDance image form accepts multiple reference images, but it does not present separate mask, layer, or bounding-box controls for each packaging feature. The practical method is to prepare a reference ledger, upload the images in a known order, state their jobs in the prompt, and verify whether the result followed that division. Reference assignment here is an instruction to test, not a guaranteed lock.
Give Each Reference One Authority
Before opening the generator, list what each photograph proves. A useful packet is smaller than a folder of near-duplicates. It covers the package’s distinct visual facts without asking two conflicting images to govern the same feature.
Reference | Its authority | Details to preserve | Details it must not decide |
Front view | Label face | Wording, line breaks, logo placement, label proportions | Side depth or rear edge |
Side or three-quarter view | Package geometry | Width, shoulder transition, wall angle, base profile | Front typography |
Closure close-up | Cap or seal | Height, diameter, ridges, join with neck | Overall body shape |
Material sample | Surface identity | Brushed metal, coated foil, glossy polymer, grain direction | Scene lighting or package proportions |
Lighting reference | Reflection behavior | Highlight width, softness, environment reflected in the surface | Brand copy or construction |
This ledger is for the human operator. Do not assume that a file name is visible to the model. Preserve the upload order and describe the same order in the prompt, such as “first reference for the front label” and “second reference for side geometry.” If the output swaps those roles, the assignment has failed and needs a simpler packet or clearer wording.
Choose an Anchor View for the Whole Object
One image should establish the package as a coherent object. Usually that is the cleanest three-quarter view because it reveals height, width, depth, closure, and the transition between planes. Call it the anchor and ask Seedream to retain its silhouette and camera angle.
The other references should repair missing facts rather than vote on the entire design. A straight-on label scan can clarify copy without flattening the body. A macro surface photograph can explain grain without changing the package into a sheet of metal. When no anchor is named, the generated object may become an average of several incompatible viewpoints.
Inspect the anchor itself for distortion. A phone photograph taken too close can exaggerate the near edge; a wide-angle view may make the top larger than the base. If that distortion is not part of the desired rendering, say that the reference supplies relative shape but not lens distortion. The result still requires a visual check because the instruction does not create a calibrated product drawing.
Treat the Label as Literal Copy
Packaging copy cannot be approved by resemblance. The front label reference may look right at a glance while a line contains a substituted letter, altered punctuation, or a compressed wordmark. Put the exact visible wording into the prompt and keep it separate from the descriptive prose.
Specify which lines are mandatory, their order, and their approximate placement. Ask for no invented badges, flavor names, legal lines, or decorative lettering. That can improve the chance of a faithful label, but it does not make generated text error-proof. Read every character in the exported image against the approved artwork.
Typography and geometry should also be reviewed independently. A correctly spelled line can still be too wide, causing a label panel to expand and changing the package proportions. Conversely, a convincing label shape can contain unusable text. Do not let success in one category excuse failure in the other.
Separate Material From Reflections
“Reflective” describes how a surface responds to its surroundings; it does not identify the surface. Polished aluminum, silver foil, chrome-coated plastic, and pearlescent film can all return bright highlights, yet their grain, edge behavior, and reflectance differ. Name the actual material shown by the material reference.
Then describe the intended reflection as a lighting condition. A broad vertical softbox creates a different highlight from a small hard source. A dark studio card can produce a controlled black band without implying that the package itself is black. If a reference contains a photographer, room, or window reflected in the object, say whether that environment should be ignored.
Avoid asking a single material close-up to govern the package’s shape. Macro views often lack scale and edges. Their job is to inform surface texture and highlight response after the anchor has established the body.
Write Conflict Rules Into the Prompt
A long inventory of references is not enough. The prompt needs an order of authority where the images disagree. A compact instruction can be more useful than elaborate advertising language:
Use the first reference as the anchor for silhouette and camera angle. Use the second only for the exact front-label content and proportions. Use the third for cap construction. Use the fourth only for brushed-metal grain and highlight behavior. Do not copy label text from the anchor, and do not copy object shape from the material close-up.
Follow that block with the desired background, view, and lighting. Keep optional styling after the non-negotiable product facts. If a generation repeatedly blends two labels or changes the closure, remove nonessential references and test the smallest packet that still covers the missing feature.
For programmatic image runs, reAPI provides access to multiple model endpoints without becoming part of the ClipDance interface. Whichever route is used, retain the prompt revision and reference order with the output; an image without that record is difficult to reproduce or diagnose.
Inspect the Render in Separate Passes
Trying to approve everything in one glance favors the shiny surface and hides structural errors. Review the same export several times, changing the question each time.
Read the label at full size
Compare wording, punctuation, line breaks, logo orientation, and the quiet space around the type. Magnify the file rather than relying on a page preview. If the copy is not literal, the render is not label-ready.
Trace the silhouette
Follow the outer contour from cap to base. Check shoulder slope, side-wall taper, symmetry where symmetry is intended, and the thickness suggested at exposed edges. Compare those points with the anchor view, not with the front-label image.
Follow each highlight
Ask whether a bright band describes the object’s curvature or falsely changes it. Look for broken reflections across seams, grain that rotates without a structural reason, and mirror details that belong to the source room. A beautiful highlight that contradicts the material reference is still a mismatch.
Sign Off the Reference Ledger With the Render
Attach the accepted output to the ledger and mark which upload governed label, geometry, closure, material, and lighting. Record any deliberate departure, such as simplifying a cap ridge that was hidden in the anchor. If this approved still later becomes a motion study in ClipDance using seedance 2.5, send its reference ledger along with it so animation does not quietly redefine the package.
Finish by opening the final file beside the front label artwork and anchor photograph. Read the label once, trace the outline once, and inspect the main reflection once. Approve the file only when all three checks point to the same product.