Libraries & Reusable Settings

Asset Library

The Asset Library is a personal media bank that follows you across productions. Anything you upload — and anything the AI generates — can live here permanently and be reused with one click in any future video.

Open it from the sidebar Media entry, or directly at /video_production/media-library.

What it stores

Asset typeExamples
LogoBrand logo PNG/SVG
Background MusicRoyalty-free or licensed tracks
Intro TemplatePre-made intro animations
OutroStandard sign-off footage
TransitionWipes, swipes, custom transitions
FontUploaded font files
ImagePhotos, illustrations, screenshots
VideoB-roll, demo recordings, stock clips
VoiceoverSaved narration audio
OtherAnything else (PDFs, JSON, CSV)

The Asset Library accepts a broader set of media types than the wizard's upload zone — including audio and video — because assets here are meant to be reused across many productions. Exact per-type size caps and total quota depend on your plan; see the storage panel at the top of the library page for your current usage and limit.

Note: the Create Wizard's Input Media drop zone is stricter than the library — it only accepts images (10 MB each) and documents (5 MB each), with a 200 MB total cap. To use audio in a production, save it to the Asset Library first, then pick it from the wizard's From Library button.

Browsing

The library page header shows a storage bar with usage / limit / percentage. Below it are three controls:

  • Search — by asset name (debounced — start typing, results filter live).
  • Filter by type — dropdown of the asset-type categories above.
  • Filter by sourceUploaded (you added it manually) · Generated (AI made it during a production) · Rendered (final video files) · Synced (mirrored from another source).
  • Group by — Asset Type · Source · Size Range · No Grouping.

Each asset appears as a card showing:

  • Thumbnail preview (or file-type icon if no preview is renderable)
  • Name
  • Type badge
  • File size
  • Source badge
  • Usage count (how many productions have used it)
  • A quick-delete button on hover

Click a card to open the detail / edit view.

Uploading

The upload form has:

  • A drag-and-drop zone (or click to browse).
  • Asset name — defaults from the filename.
  • Type — one of the type categories.
  • Media type — auto-detected, editable.
  • Scene hint (optional) — a hint about which scenes this asset is meant for.
  • Description — free text for your own reference.

Upload progress is shown inline; the asset appears in the grid as soon as the upload completes.

Asset detail view

Clicking an asset opens its full preview. You can:

  • Edit name, type, media type, description, and scene hint.
  • Toggle Must Include — when this asset is referenced in a production, the AI is required to use it (vs. treating it as optional).
  • Toggle AI Enhance — runs background removal, upscaling, or cleanup on the asset.
  • Add AI Enhancement Instructions — free text ("Remove white background, upscale 2×").
  • See metadata: filename, file size, MIME type, source, usage count, created date.
  • Trash the asset (or Restore it if it's already in trash).

Bulk operations

Toggle multi-select mode and you get a bulk-action bar with:

  • A selection counter
  • Bulk Trash — moves all selected assets to the trash

Bulk-edit-metadata is not currently exposed.

Sync from Productions

A Sync from Productions button at the top of the library page imports generated assets from your finished productions into the library in one click. Use this after a production completes to harvest reusable images, music, or voiceovers without manual download/re-upload.

The Trash

The library has a collapsible Trash section at the bottom showing:

  • Total item count
  • Total size of trashed items
  • Per-item days remaining countdown
  • Restore and Permanent Delete buttons per item

Heads up — Trash counts against your storage. A 500 MB asset in Trash still consumes 500 MB of your plan's storage allowance until it's permanently deleted. Auto-purge runs every 20 days (cron-based), but if you're tight on storage, empty Trash manually.

Real scenarios

Scenario A — One-time setup, lifetime payoff

A new user spends 10 minutes the first day:

  1. Uploads their logo (PNG with transparency), tagged as Logo type, Must Include on.
  2. Uploads three royalty-free background music tracks (one per mood they typically use).
  3. Uploads a standard outro — a 5-second clip with their channel branding.

Every production from then on auto-incorporates the logo, has music to choose from, and uses the same outro consistently. They don't touch the library for weeks.

Scenario B — Cleanup before a big batch

Before kicking off 10 multi-language variants, the user notices their storage bar is at 92%. They:

  1. Filter by source = Generated and group by Size Range.
  2. Bulk-select images from old, already-published productions.
  3. Move to Trash, then Empty Trash.
  4. Storage drops to 41%. Phase 1 storage check passes for the new batch.

Scenario C — Reusing a guest voiceover

A pre-recorded interview clip will appear in 4 different videos this month.

  1. Upload the MP3 once, type = Voiceover, with a clear name (SmithInterview_30s.mp3).
  2. In each new production, in the wizard's Media block, click Pick from Asset Library and select the file.
  3. Set scene hint per use ("Scene 3").

The clip is referenced by ID; uploading it once doesn't create four copies.

Tips & gotchas

  • Usage count is your "is this still useful" indicator. Anything with 0 uses for months is a deletion candidate.
  • Generated assets stay with their production by default. Use Sync from Productions to copy them into the library where they survive independently and can be reused.
  • AI Enhancement is irreversible without re-upload. Always keep your original file somewhere safe.
  • Logos with transparency render best. A logo on a white background will look like a white box on a coloured scene.
  • Search is by name only. It doesn't search descriptions, scene hints, or content. Name your assets descriptively.
  • Storage runs on dual backends. Your filestore handles small/recent files; an S3-compatible object store (Spaces / MinIO / AWS S3) handles bulk. As an end user you don't see this distinction — usage is reported as a single total.

See also