pipe2 assets upload

Upload a local file as an asset (image/video/audio)

Synopsis

Upload a local file and register it as an asset in your library.

The asset is stored in Pipe2.ai’s S3 bucket and gets a public URL you can pass to any pipeline (e.g. video-trim, transcription, captions) via either the asset’s id or its url field.

Files at or below 25 MiB use a single PUT. Larger files automatically use S3 multipart with parallel chunked PUTs (—parallel chunks at a time, each —part-size MiB). On Ctrl-C the in-progress upload is aborted cleanly.

Size limits: 10 MiB images, 5 GiB videos, 1 GiB audio.

Examples: pipe2 assets upload ./interview.mp4 pipe2 assets upload ./voiceover.wav —tags podcast,episode-42 pipe2 assets upload ./long-podcast.mp4 —parallel 8 —part-size 64 pipe2 assets upload ./photo —content-type image/jpeg

pipe2 assets upload <file> [flags]

Options

      --content-type string   explicit MIME type (default: detected from extension)
  -h, --help                  help for upload
      --parallel int          concurrent part uploads in multipart mode (default 4)
      --part-size int         multipart chunk size in MiB (default 32, min 5)
      --tags strings          comma-separated tags to attach to the asset

Options inherited from parent commands

      --api-url string   override API base URL (env: PIPE2_API_URL)
      --config string    path to config file (default: $XDG_CONFIG_HOME/pipe2/config.json)
      --json             emit JSON to stdout instead of human-readable text
      --token string     override personal access token (env: PIPE2_TOKEN)
  -v, --verbose          verbose human output on stderr

pipe2 assets upload