A useful AI visual handoff lets a designer make the next named change without reconstructing the whole picture. Supply the chosen concept, original visual assets, approved copy, an editable working file and a short revision brief. Then verify that the file opens with the right dependencies and that the requested element can actually be changed.
Dreamina can help create the artwork and visual directions. The handoff needs an additional production decision: which parts should remain generated images, which should use supplied product artwork, and which must become independently editable objects. A polished preview answers what the design should look like. The working package must also answer how to change it.
This guide carries one fictional desk-lamp campaign through that process, including a specific price-and-layout revision. The example is a proposed workflow, not a completed Dreamina export or a tested designer handoff.
- Start with the next revision, then choose the file structure
- Separate four things that often arrive in one picture
- Know what the actual download contains
- Prepare artwork that will survive the handoff
- Build a working master with real controls
- Send a compact package with a clear entry point
- Package dependencies using the editor's actual behavior
- Write the change request so acceptance is observable
- Reopen, perform a small change and compare the result
- Fix the package problem instead of asking the designer to guess
Start with the next revision, then choose the file structure
“Please make this editable” is too vague to determine the package. Ask what the recipient must be able to change: the background, product color, price, language, crop, illustration, or all of them. Each change requires a different kind of control.
If the next task is to replace a price, native text is useful. If it is to show a real product from another angle, the designer needs approved artwork for that angle. If it is to make a square graphic taller, separate foreground and background components can help. A single flattened image may still be a useful reference, but it does not by itself supply those controls.
For the fictional example, assume the brief supplies an approved photograph of a cream desk lamp, an approved wordmark, exact launch copy and a licensed typeface available to the team. The selected visual direction places the lamp on a warm desk with quiet space for the headline. These are assumptions for the example, not facts about a real client or product.
The next request is deliberately concrete: change the displayed price from 49 to 45, replace “Light for your next idea” with “A little light. A fresh start.”, and produce a tall version while preserving the lamp's approved appearance. Both prices and headlines are invented teaching copy. No real pricing or performance claim is implied.
That request determines the structure: generated environment, approved lamp artwork, exact brand asset, editable headline and price, and two separately composed output layouts. The designer should not have to repaint the lamp or ask an image model to rediscover the correct price.
Separate four things that often arrive in one picture
Do not treat every visible element as equally authoritative. A generated lamp in a concept may communicate shape and mood, but it is not automatically the approved product photograph. A generated label may suggest placement without being accepted wording. Mark those differences before the preview reaches a production designer.
For an infographic, the separation also includes data and quantitative marks. Keep the actual source table and editable graph with the design; a flattened chart image cannot explain how its bars were calculated. The facts-to-infographic workflow develops that requirement. A handoff should carry the data relationship forward instead of reducing the graphic to decorative pixels.
Know what the actual download contains
Inspect the delivered artifact rather than inferring its structure from the model's name or its appearance. Can you select the headline as text? Is the product a separate object? Does the file contain transparency where expected? Does it open with meaningful layers, or only one image inside a layered-file container?
The model team's Seedream 5.0 Pro announcement describes layer separation into independent components with transparency and placement controls. That is relevant when those assets are available in the route you use. It does not establish that a particular Dreamina download contains live Photoshop typography, the team's fonts or a complete set of linked source files.
A separated text-shaped image and a native text object are different deliverables. You may be able to move the former while still being unable to replace its wording with the Type tool. Likewise, a separate product cutout can be repositioned without proving that its label or geometry matches the approved source.
Open the exact files you intend to send and classify what is present. Keep useful separated components. Rebuild only the controls the revision requires. Avoid promising a native editable layout until you have inspected that layout and the requested change can be performed.
Prepare artwork that will survive the handoff
For the lamp example, a background-only request is a practical option because the approved lamp photograph will be placed separately. Describe the viewpoint, surface, lighting and empty region that the product needs. Asking for a complete finished advertisement can bake together elements that the next revision needs to separate.
An untested background prompt could be:
Create a warm, quiet desk environment for a product campaign. Show a pale wooden desktop from a low three-quarter viewpoint, a softly lit cream wall and subtle morning light from the left. Leave an uncluttered placement area on the right for a separately supplied desk lamp and calm space on the left for typography. No lamp, other product, text, logo, price or decorative lettering. Keep the tabletop perspective clear and avoid a dramatic cast shadow where the lamp will be placed.
Dreamina's Seedream 5.0 Pro guide documents the AI Image route: enter text or upload an image, select Image 5.0 Pro, choose the available aspect ratio and resolution, generate, review and download. Use the settings available in your account. The prompt above has not been executed and does not guarantee a background that fits the supplied photograph.
Inspect candidates beside the product source. A high camera angle in the background and a low camera angle in the product can make the composite impossible to reconcile convincingly. Reject that mismatch early. Similarly, a strong light from the right may fight a product photograph lit from the left. Choose a compatible environment or obtain a better product source instead of stretching the product until it fits.
Preserve the selected original download. If the designer later needs a wider crop or less contrast, the original remains available. Include the exact chosen file in the package; a thumbnail in a chat and a prompt describing it are insufficient replacements.
Build a working master with real controls
The following Photoshop path is a documented external-editor workflow. It is not a claim that Dreamina produced the finished Photoshop file.
Create a working document for the agreed layout and place the chosen background. Keep the product and wordmark separate. Adobe's linked Smart Object instructions use File → Place Linked, followed by selecting the file and placing it. A linked object lets the document refer to the source artwork; that source must remain available with the handoff.
For the example, place the approved lamp photograph as its own linked object. Position and scale it proportionally. Keep the product's proportions, switch, cord and other visible features aligned with the approved reference. If the source includes a background, prepare a suitable mask while retaining the original file; putting a photograph into a Smart Object does not automatically cut it out.
Add the headline and price with the Type tool. Adobe's text instructions distinguish clicking for point text from dragging a box for paragraph text. Choose the form that suits the layout, enter the approved wording and confirm the actual text layer exists. For a two-line headline whose wrapping matters, a paragraph box can make the intended area explicit.
Name the layers by their jobs: background, lamp artwork, wordmark, headline, price and any separately constructed shadow. The names should help the recipient find the thing to change. A stack called “Layer 1 copy” through “Layer 1 copy 12” technically contains layers but leaves the editing decision unresolved.
Keep native text available in the working master. Adobe's type-layer guidance explains that rasterization turns type into pixels, ending direct text editing. If a special effect needs a rasterized copy, retain the editable original separately and make the relationship clear.
Save the master in a format that retains its required layers. Adobe's save workflow distinguishes preserving supported document features from creating a separate copy for output. A PSD extension alone is insufficient: inspect the actual layer structure after saving.
Make each output layout intentional
A square composition and a tall composition can use the same accepted artwork without sharing identical placement. In the square lamp layout, the headline may sit beside the lamp. In the tall version, it may need to move above the product so that the full shade and base remain visible.
Keep separate, clearly named layouts or documents for the agreed outputs. Copy the accepted wording accurately, then adjust its line breaks and spacing for the new composition. Do not stretch the square export to fill a tall canvas. That changes the lamp's proportions and may leave the next designer with a distorted starting point.
For a multi-card campaign, also identify which elements repeat and which are card-specific. The product-launch carousel guide covers that narrative structure. A handoff should state whether a headline change applies to one card or every card, rather than leaving the recipient to infer the campaign's information hierarchy.
Send a compact package with a clear entry point
The recipient should be able to identify the working master, approved reference and requested change without opening every file. Organize by use rather than by the order in which images were generated.
For the lamp example, a practical package contains:
Keep only the accepted selection in the main handoff. If alternatives are useful, put them in a clearly separate reference area and say why they are included. Ten almost-identical downloads without a selected version create a selection task the designer may not have been asked to perform.
The prompt and settings can help when new generation is needed. They should not be the only explanation of the artwork. Include the selected output and explain its role; the same prompt does not promise the same future image.
Package dependencies using the editor's actual behavior
In Photoshop, save the document before using File → Package, then choose the package destination. Adobe's packaging instructions describe collecting the document and linked sources. Review the resulting folder rather than assuming every resource used in the design has been collected.
Pay particular attention to fonts. A package of linked Smart Objects should not be described as an automatic font-delivery solution. Record the font family and style, how the recipient should obtain it, and whether the recipient already has access. If a substitute is necessary, agree on it and recheck wrapping before declaring the layout unchanged.
If the working file is Illustrator instead, File → Package has options for copying and relinking linked graphics and producing a report. Adobe's Illustrator packaging guide also describes collecting eligible fonts, with exclusions such as CJK fonts and the need to respect font permissions. Treat those as that editor's packaging behavior; do not transfer its options to Photoshop.
A package must be usable outside the sender's current folder arrangement. Opening the master on the same machine can succeed because the editor still finds an old source elsewhere. Check the linked-file locations and have the recipient open the delivered package in their environment when possible. If that check has not happened, say that recipient opening remains unverified.
Write the change request so acceptance is observable
Attach a short brief that names the current version, changes and fixed elements. For the fictional lamp, it could read:
In both supplied layouts, replace 49 with 45 and replace “Light for your next idea” with “A little light. A fresh start.” Use the supplied lamp photograph and wordmark unchanged. Retain the warm desk direction. In the tall version, reflow the headline above the lamp while keeping the complete shade and base visible. Return the revised editable masters, their required linked assets and one preview export for each layout. Flag a missing font or incompatible product source before substituting it.
This brief does not dictate every spacing adjustment. It protects the elements whose changes would alter the assignment while leaving the designer room to solve the composition. The approval question is specific: did the two layouts receive the correct wording and price, retain the correct product, and return in a form that supports another revision?
Include a visual reference for the intended product crop if that matters. “Keep the lamp visible” might mean only the shade to one person and the full object to another. Specify the meaningful boundary: in this example, complete shade and base. If the cord can be cropped, say so rather than introducing that choice after delivery.
Reopen, perform a small change and compare the result
Before handing over, open the packaged master and check for missing assets or substituted fonts. Compare it with the reference preview. Verify that the product source is the intended one and that the headline and price are actual editable type.
On a temporary revision of the working file, perform the kind of change the brief requests. Replace the price, confirm the headline can be edited, and inspect whether the text fits. This is a proposed acceptance check; no such test has been performed for the fictional example. Its value is that it tests the handoff's promise instead of only counting files.
Restore or clearly separate that temporary test version. A recipient should not accidentally receive an unapproved price because a packaging check left an edited master in the main folder.
Save the working design and make a separate preview or delivery copy. Reopen the exported image as well as the editable master. Check exact wording, crop, edges and appearance at the intended viewing size. The campaign-readiness guide explains how to decide whether a particular output is ready for its destination; a correct handoff package does not automatically approve every export for public use.
Fix the package problem instead of asking the designer to guess
The price cannot be edited. Inspect whether it is native type or part of the image. Rebuild it as text using the approved copy and a suitable clean background. Do not promise that moving a separated raster word also makes its wording editable.
The product link is missing. Locate the actual approved source, relink it and repack. Avoid selecting a visually similar rejected candidate merely because it opens successfully.
The typeface is unavailable. Provide its correct source or agree on a replacement. Recheck line breaks, spacing and the tall layout after substitution; matching the text string does not guarantee matching composition.
The tall version clips the product. Return to the editable composition and reposition its independent elements. A larger export of the clipped preview will not restore the missing shade or base.
The designer cannot tell which image is approved. Identify one selected source and one reference preview per layout. Keep alternatives outside the working set and state whether they remain options.
A successful handoff makes the next change smaller and clearer. Use Dreamina to develop suitable artwork, preserve the selected assets, build the controls the revision needs and send one intelligible package. The designer can then revise the work from a known starting point instead of reverse-engineering a finished-looking picture.