
Import the content that must remain editable with Native Import, and rasterize selected complex elements whose appearance matters more than their internal editability. Express's Figma add-on allows both methods in the same design. Decide that boundary before importing an entire campaign frame as one image.
Specify the next correction
Ask what the receiving contributor must change. A weekly price label needs editable text; a complex decorative illustration may only need to remain visually faithful.
Consider a hypothetical ticket promotion containing editable dates and a masked gradient illustration. The marketing assistant needs to update the dates, while the illustrator retains responsibility for the artwork. A mixed import can reflect those responsibilities more clearly than promising that every Figma effect will remain editable.
Adobe's Figma import guide distinguishes Native Import from Rasterize and explicitly permits combining them. Some gradients, patterns and masked or combined shapes can arrive as images to preserve appearance.
Import selected content deliberately
Connect the Figma add-on using an authorized account with access to the source file. Paste the file URL and select the relevant page, frame or layer. Keep a record of which source frame the Express edition represents.
Use Native Import for supported content requiring later changes. Choose Rasterize for a selected complex element when preserving its appearance is the agreed priority. A rasterized element can be moved and scaled but not edited internally as separate objects.
The add-on has read-only access to Figma and does not modify the original file. Do not interpret edits in Express as a round-trip update to Figma. Name the receiving edition so the two sources are not confused.
Review fonts and complex boundaries
Read the import summary. Adobe matches fonts by name where available; unavailable fonts receive fallback and are identified as Font Not Available. Check representative text rather than assuming that editable letters use the approved font.
A missing Photoshop font before deliberate substitution raises a similar decision about visual fidelity, although Express uses its own import process.
Compare gradients, masks and transparent edges against the Figma reference. A merged visible proof versus a layered source also separates appearance from editability. Neither deliverable is inherently the correct one for every object.
Prove the actual handoff
For the ticket promotion, ask the assistant to change one date and export a proof. Confirm that the date remains editable, the illustration matches the reference and no fallback changes the layout unexpectedly.
If a required object becomes an image, revise it in Figma or rebuild only that object in a suitable way. Live effects changing across XCF and PSD likewise show why cross-application claims need object-level checks.
Acceptance concerns the agreed corrections and appearance, not a generic “native import completed” message. Keep the Figma source and the receiving proof independently.
Related tasks
- Copy the Visible Photoshop Composite Without Flattening Its Source
- Wait for a Missing Photoshop Font or Replace It Deliberately?
- Why Are GIMP Layer Effects Editable in XCF but Not After PSD Export?
Sources and scope
- Adobe: Import Figma designs into Adobe Express: Native and Rasterize can be mixed; font fallback summary; read-only source access.
Documentation-based guidance. Examples are hypothetical and acceptance checks are proposed; no installed-application test is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.