Documentation

StackShift Assets overview

StackShift Assets is now a live media platform: storage, CDN delivery, image optimization, upload sessions, DAM, video, scanning, governance, AI metadata, and version history.

Try StackShiftRead the overview

Search Docs

Assets

StackShift Assets overview

Live

StackShift Assets is now a live media platform: storage, CDN delivery, image optimization, upload sessions, DAM, video, scanning, governance, AI metadata, and version history.

Goal

Understand the full Assets platform and which feature area to use for each workflow.

Current status

Live

This area is documented as current, user-reliable behavior.

Workflow

  1. 1Install an official StackShift SDK for your backend language.
  2. 2Upload originals with bucket, key, visibility, folder, tags, and metadata.
  3. 3Use public CDN URLs, private signed URLs, named image transforms, or signed dynamic transforms.
  4. 4Use resumable upload sessions for large browser files and DAM APIs for search, tags, bulk actions, collections, and saved searches.
  5. 5Let durable jobs scan assets, process videos, create AI annotations, and maintain derived outputs.
  6. 6Use version and branch URLs when you need pinned asset history instead of only the current head.

Live feature layers

  • Storage and CDN: upload, list, get, delete, replace, public delivery, and signed private delivery.
  • Image optimization: named transformations, signed dynamic transforms, WebP/AVIF/JPEG/PNG output, and derived cache reuse.
  • Upload UX and DAM: chunked sessions, progress, retry/resume, virtual folders, tags, search, duplicate hints, usage summaries, and bulk actions.
  • Video and governance: FFprobe metadata, poster and thumbnail outputs, normalized MP4/HLS delivery, ClamAV scan state, quarantine, policies, and audit events.
  • AI DAM and versions: OpenAI-backed tags/captions, moderation, transcripts, smart crop, background removal, collections, saved searches, and branching versions.

What users never manage directly

  • Storage node placement.
  • Replica node placement.
  • Local disk paths.
  • Derived asset paths for image, video, and AI outputs.
  • Cloudflare gateway and origin internals.

Expected result

You can treat Assets as the media layer for your product while StackShift owns storage placement, derived outputs, scanning, and delivery.