How Generation Works
When you click Generate (on the Creation Engine page or from Snap on Director Board), MediaSnap does not block the browser until the provider finishes. Generation runs as a background order so you can keep planning or editing.
What happens when you generate
- Order created — Your request is saved as a media generation order (model, prompt, settings, project context)
- Credits / billing — Applicable cost is checked at order time (wallet or plan rules)
- Worker processes the job — A server daemon calls the provider (Replicate, Fal, etc.)
- Result stored — Finished media is saved to your account (
user_media) - You are notified — Toast or notification when the job completes or fails
You can leave Director Board or Creation Engine and return later.
Where results appear
| Location | What you see |
|---|---|
| Creation Engine canvas | Latest results in your current GENERATE session |
| Snap chat | Cards and links when generate started from Director Board |
| Project asset library | All media linked to the project |
| Shot card | After you attach media to a shot |
| Notifications | Link or message when ready |
Unattached media still exists in your library — attach when you are ready to count it toward shot progress.
Attaching media
Generated media can connect to:
| Target | When |
|---|---|
| Shot | Canonical — ties media to production progress |
| Character | Reference or hero image for cast |
| Environment | Reference for a set |
Immediate attach — During or right after generation in the Creation Engine
Delayed attach — From the asset library or detail view later
Replacing existing links may ask for confirmation (force_replace).
Failed or slow jobs
- Failed — Notification with error hint; order may be retryable depending on cause
- Slow — Large video models can take minutes; status updates in the UI
- Tier limits — Some models or counts are limited by plan; the UI explains before you spend credits
See Troubleshooting if jobs repeatedly fail.
Why background generation matters
MediaSnap behaves like a studio, not a single blocking webpage:
- Queue several shots without waiting on each tab
- Continue planning in Director Studio while video renders
- Collect outputs in one project library