Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

Use video outputs and security controls while keeping original asset URLs backward compatible.

​
Prerequisites

  • A video upload or replace operation
  • A configured account content policy when restrictions are needed

​
Workflow

1
Upload or replace a video asset.
2
StackShift scans the asset first and quarantines infected files.
3
Clean video assets enqueue processing for metadata, poster images, thumbnails, MP4 normalization, and HLS renditions.
4
Deliver HLS manifests, segments, posters, and thumbnails through public or signed private delivery routes.
5
Use policy controls for allowed MIME types, maximum file size by family, and scan requirements.

​
Video outputs

  • FFprobe metadata: duration, dimensions, codec, bitrate, frame rate, audio presence, and rotation.
  • Poster and thumbnail derived assets.
  • Normalized MP4 output for web playback.
  • HLS ladders for 240p, 360p, 480p, 720p, and 1080p when the source supports them.

​
Governance behavior

  • Scan states are pending, clean, infected, failed, and skipped.
  • Infected assets are quarantined and blocked from original, transform, and video delivery.
  • Policy checks run on direct uploads, upload-session creation, chunk completion, replace, and token uploads.
  • Audit logs cover uploads, replace, delete, scan results, quarantine, video processing, policy changes, tags, and visibility changes.

​
Expected result

Video assets show processing state, playback URLs, scan status, policy status, and audit history.

Private assets and signed URLs

Keep files private by default and generate short-lived URLs only when a user should download them.

AI DAM and versioning

Use OpenAI-backed asset intelligence, moderation, transcripts, smart crops, background removal, collections, saved searches, and branching versions.