Goal
Understand the full Assets platform and which feature area to use for each workflow.Prerequisites
- A StackShift API key
Workflow
Use resumable upload sessions for large browser files and DAM APIs for search, tags, bulk actions, collections, and saved searches.
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.
Related guides
Image optimization
Use named presets and signed dynamic transforms for strict, cached, responsive image delivery.
Upload UX and DAM
Use resumable upload sessions, progress-aware browser uploads, tags, folders, search, bulk actions, and usage summaries.
Video, scanning, and governance
Process video asynchronously, deliver HLS and posters, scan uploads, quarantine infected assets, and enforce account policies.
AI DAM and versioning
Use OpenAI-backed asset intelligence, moderation, transcripts, smart crops, background removal, collections, saved searches, and branching versions.