
A Runway reference can be available in the current session without being saved for another session or shared with colleagues. Treat those as separate states: save the reference under a name, then explicitly share it with the workspace when collaboration requires it. Seeing an uploaded image beside a prompt does not establish either outcome.
Key Takeaways
- A temporary upload is different from a named, reusable reference.
- Saving a reference does not by itself establish workspace sharing.
- Verify the reference in the session and account context that will actually use it.
Check which kind of reference you have
In Runway's Gen-4 Image References workflow, inspect the image in the References panel. The official reference-management instructions distinguish temporary uploads, named references and workspace sharing. These controls belong to that workflow; another model or application may organize attachments differently.
Before changing anything, identify the exact image that was approved. Two visually similar revisions can have different clothing or product details. Use a meaningful revision name in your private project notes rather than assuming the most recent thumbnail is the approved source.
Save first, then decide who needs access
Hover over the reference, choose the tag/save control, enter its name and confirm it. For a shared project, open the saved reference's edit details and enable Share with Workspace where the account offers it.
Keep sharing scope tied to the project. A coworker who needs the approved source may not need every rejected exploration. Naming and sharing an image also do not grant permission to use someone else's likeness, logo or confidential product photograph.
For example, a fictional team might name a location reference courtyard-approved-r02. That name is an organizational choice, not a guarantee that later generations will reproduce the courtyard exactly.
Verify reuse rather than only the current thumbnail
Open a new session in the same intended workflow and locate the saved reference. Select it for use; where supported, the @ picker can help address the named asset. Check the picture itself before generating.
For a team handoff, ask the intended collaborator to confirm availability from the correct workspace. A screenshot from your own session only proves what you can currently see. Include the reference name, revision and intended visual role in the handoff record.
If the asset is absent, first distinguish the wrong workspace or account from an unsaved temporary image. Avoid deleting the original upload while investigating. If a reference is present but ignored by the model, that is a separate attachment-order and reference-association problem.
Keep an independent project record
A saved reference library helps reuse assets, but it is not a substitute for retaining authorized originals and approved outputs. Keep a source-to-reference record outside the generation session, particularly before removing old references.
When carrying an approved still into a film brief, preserve its identity and role in the brief. This procedure manages Runway assets; it does not imply that another film workspace automatically inherits Runway's library or sharing permissions.
Related tasks
- After Reordering References, Does “Image 1” Still Point to the Right File?
- How to Archive Imagild Assets Before the 90-Day Storage Window Ends
Sources and scope
- Runway Gen-4 Image References: reference asset persistence workspace sharing
- Runway reference media: reference asset persistence workspace sharing
Based on Runway's Gen-4 Image References help, retrieved October 23, 2026. Procedures and hypothetical review examples are documentation-based; no product account or media-processing test was performed.
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: 85 LENS (Ngô Hoàng Auth) / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.
Filled decision record: reference persistence
This is a constructed review exercise, not a reported generation, software test or audience study. Its purpose is to make the acceptance decision reproducible for the next reviewer.
| Review item | Hypothetical evidence or requirement | Decision and next action |
|---|---|---|
| Failure observed in the candidate | The approved image exists only in the current Runway session. | Hold the affected candidate; name this failure before changing anything else. |
| Protected result | Save the named reference and verify its intended workspace availability. | Compare against the approved source and intended sequence, not the attractiveness of an isolated frame. |
| Bounded next action | Check the actual receiving session rather than assuming sharing. | Make this change first, then inspect the same acceptance criterion again. |
Keep the actual source version and the rejected candidate distinguishable. A planning correction does not prove a later output follows it, and a successful individual frame does not approve the complete clip or sequence. Record which requirement is still unresolved rather than silently labeling the whole deliverable final.
For the next handoff, include the approved requirement, the evidence that supports it and this specific unresolved action. This record belongs to the editorial workflow; it is not a claim that Imagild enforces these constraints automatically.
Documentation and production boundary
Runway: Creating with Gen-4 Image References is a vendor-specific workflow reference. The decision record above is our original manual review method. Use Imagild's current film planning workspace for supported planning steps and inspect the current interface before choosing an input or generation mode. Do not infer an available control from another vendor's documentation.