> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackshift.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

<Tip>
  **Live.** This area is documented as current, user-reliable behavior.
</Tip>

## Goal

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

## Prerequisites

* A StackShift API key

## Workflow

<Steps>
  <Step>
    Install an official StackShift SDK for your backend language.
  </Step>

  <Step>
    Upload originals with bucket, key, visibility, folder, tags, and metadata.
  </Step>

  <Step>
    Use public CDN URLs, private signed URLs, named image transforms, or signed dynamic transforms.
  </Step>

  <Step>
    Use resumable upload sessions for large browser files and DAM APIs for search, tags, bulk actions, collections, and saved searches.
  </Step>

  <Step>
    Let durable jobs scan assets, process videos, create AI annotations, and maintain derived outputs.
  </Step>

  <Step>
    Use version and branch URLs when you need pinned asset history instead of only the current head.
  </Step>
</Steps>

## 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

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

## Related guides

<CardGroup cols={2}>
  <Card title="Image optimization" href="/assets/image-optimization">
    Use named presets and signed dynamic transforms for strict, cached, responsive image delivery.
  </Card>

  <Card title="Upload UX and DAM" href="/assets/upload-ux-and-dam">
    Use resumable upload sessions, progress-aware browser uploads, tags, folders, search, bulk actions, and usage summaries.
  </Card>

  <Card title="Video, scanning, and governance" href="/assets/video-scanning-and-governance">
    Process video asynchronously, deliver HLS and posters, scan uploads, quarantine infected assets, and enforce account policies.
  </Card>

  <Card title="AI DAM and versioning" href="/assets/ai-dam-and-versioning">
    Use OpenAI-backed asset intelligence, moderation, transcripts, smart crops, background removal, collections, saved searches, and branching versions.
  </Card>
</CardGroup>