Skip to main content

​
Reference Intake

Redbit’s reference intake surface is designed to keep source material close to the generation workflow. Users can bring in common working assets, preview them locally where browser APIs allow it, then decide whether the next step needs provider upload, Local Core processing, or only a local workspace reference.

​
Who Should Read This

Read this page when you need to explain how uploaded or dragged material becomes a reusable Reference, and where local preview ends before a provider or Local Core route begins.

​
Intake Behavior

Images, videos, audio, text snippets, and document-like files can enter the workspace through the intake surface or related pickers. The exact downstream use depends on the selected workflow and provider input requirements.
Browser file APIs and object URLs can preview local assets before a workflow decides whether the asset must be uploaded to a provider, sent through Local Core, or kept as local workspace context.

​
Where References Can Go

​
Security Boundary

Local preview does not mean the asset never leaves the device. The asset remains local only until a workflow sends it to a configured provider, relay, Local Core endpoint, or external integration. Check the selected route before using confidential media.

​
Next Step

Use Cards for card-level reference behavior, or Seedance Video Workflows for first-frame, last-frame, and multi-reference video rules.