Skip to main content
Some multimodal models can process audio and/or video inputs directly, enabling video captioning, scene analysis, content understanding, and multimodal question answering. Availability depends on the model: GLM 5.3 Flash supports video input on Serverless, while Qwen3 Omni and Molmo2 use dedicated deployments.

Available models

GLM 5.3 Flash supports image, video, and text inputs. This page does not claim audio input support for GLM 5.3 Flash. Qwen3 Omni supports native video and audio inputs. Molmo2 models are video-only, so use the dedicated request structure below but omit audio_url; Molmo2 cannot understand audio from videos.

Choose a serving path

Serverless

GLM 5.3 Flash is available directly through Serverless. No deployment is required:

Dedicated deployment

Qwen3 Omni and Molmo2 require dedicated deployments. For Qwen3 Omni, create one using firectl:
Make sure to use the predefined qwen3-omni-30b-a3b-instruct-minimal deployment shape for your deployment to work correctly.

Chat Completions API

Serverless video by URL

GLM 5.3 Flash accepts a reachable video URL in a video_url content block.
The URL must return the media file directly and remain reachable while the request is processed. For private media, use a signed HTTPS URL that remains valid until inference finishes.

Dedicated video and audio with Base64

Qwen3 Omni accepts video_url, audio_url, and text content types. Provide the video and audio as Base64-encoded data URLs.

Working with videos

Video models perform best with inputs that balance quality and token efficiency. When you control the source media, use ffmpeg to optimize video and audio before sending requests. The settings below are starting points for the dedicated Base64 example, not universal hard limits.

Preprocessing video

Extract frames at 1 FPS and downscale to 360p for efficient processing:

Preprocessing audio

Extract audio as Opus in an Ogg container for optimal compression:

Complete preprocessing example

Preprocessing is highly recommended to reduce latency and ensure consistent performance.

Performance considerations

Tips for optimal throughput:
  • Preprocess all videos – 1 FPS at 360p provides good quality with minimal tokens
  • Extract audio separately – Opus/Ogg at 24kbps offers excellent compression
  • Limit video duration – Start with 60 seconds or less for consistent performance
  • Choose the appropriate serving path – Use GLM 5.3 Flash on Serverless, or scale replicas for models that require dedicated deployments

Known limitations

  1. Video duration: 60 seconds is a performance recommendation for the preprocessing example, not a universal API limit.
  2. Supported formats: The examples use .mp4 for video and .ogg (Opus) for audio.
  3. Base64 size: Keep the total encoded payload for the dedicated example under 10MB.
  4. Video URLs: The URL must be reachable by Fireworks and return the media file directly without custom authorization headers.
  5. Availability: GLM 5.3 Flash supports Serverless video input. Qwen3 Omni and Molmo2 require dedicated deployments.
  6. Audio support: Only use audio_url with models whose input support explicitly includes audio.

Chat with Video using Qwen3 Omni

Interactive notebook for video and audio analysis

Vision models

Query models with image inputs

Dedicated deployments

Deploy models on dedicated GPUs