CartVisualCreate account

Send a Whole Photoshop PSD or Selected Layers to Firefly Boards?

Send only the creative scope needed for ideation; the full PSD route and selected-layer route are distinct, and a returned Board image is a new Photoshop document rather than a live-linked master.

Published · By CartVisual editorial team

Choose what the Board should see

A merchant has a layered product poster with an approved bottle photograph, confidential draft pricing, background options and campaign typography. They want to explore a new scene in Firefly Boards. Sending the whole project is not equivalent to sending only the bottle and backdrop. Photoshop documents a PSD-to-Boards handoff and a separate command for selected layers. The latter lets the operator choose the creative layers intended for the handoff. It is not evidence that every other piece of document information or metadata is excluded from transfer.

Before either action, decide which layers are authorized for external cloud ideation. A draft price, internal note or unreleased SKU may not be necessary. Treat cloud upload as a separate data-handling decision and follow the organization’s approved permissions.

Understand the document boundary

Adobe describes sending a local PSD as a PSDC cloud document. For a narrower selection, the operator selects layers in Photoshop, right-clicks and uses Send layers to Firefly Boards. The exact account and current feature availability should be confirmed in Photoshop. These operations are not described as live bidirectional synchronization with the original local PSD.

The return direction is also bounded: selecting a Board image and choosing Open in Photoshop opens it as a new document. That image should not be mistaken for a reconstructed layer stack or an automatic replacement for the approved master. See the linked-file portability guide for a different problem involving missing external dependencies.

Check each handoff boundary

RouteDocumented behaviorUnproven assumption to avoid
Local PSDShare or Export offers Send to Firefly Boards; the file is uploaded as a cloud document, PSDC.That a local-only source remains local.
Selected layersSelect the layers and use the right-click Send layers to Firefly Boards command.That the help page promises a specific internal asset format, restored layer stack or exclusion of all other metadata.
Board image returnedOpen in Photoshop opens the selected image as a new document.That the original master has synchronized or regained all editable layers.

Adobe does not specify the selected-layer transfer's internal representation on this help page. Keep that unknown explicit. Inspect the actual received item and retain the source master rather than promising a structural property the instructions do not establish.

Fictional packaging poster review

Fictional source POSTER-BOTTLE-V7.psd contains PRODUCT-APPROVED, BACKDROP-OPTION, PRICE-DRAFT and LOGO-MASTER. The design lead wants ideas for a warmer shelf environment, not revisions to price or brand identity. The proposed route is a selected-layer handoff limited to product and scene references, subject to internal data permission. The resulting Board concept is reviewed as a new candidate image.

The candidate may be visually useful while still changing bottle lettering or scene geometry. The operator compares it with the approved bottle source and transfers only approved design ideas into the retained editable master. They do not assume that opening the Board image in Photoshop restores PRODUCT-APPROVED and PRICE-DRAFT as independent layers. No PSD was uploaded or Board generated for this example.

Handoff conditions

Record the source PSD revision, chosen layers or full-document scope, cloud destination, Board candidate identifier and returned image identity. If the returned image has useful atmosphere but altered product pixels, use it as a reference rather than replacing factual product evidence. If the merchant needs independently editable type and pricing, retain the original layered project.

The layered-versus-flattened poster guide explains another export boundary. Here the new issue is the scope of data sent into Boards and the absence of documented live sync. Approve only the intended ideation handoff, not a claim that the Board is the production master.

Sources

Scope and evidence

Prepared by CartVisual with AI assistance and checked against the listed sources. Cloud transfer and layer editability require separate review; no live sync or native layer preservation guarantee.

Related decisions

Explore the AI image remix workflow