Qwen omni model for text, vision, audio, and multimodal agent tasks

Key specifications

Capability
42.1
Context window
32.8K
Max output
2.0K
Input $/1M
$0.07
Output $/1M
$0.27
License
Proprietary

Inputs and outputs

Recorded modality support shows what this model can accept and produce. An undocumented modality is shown as unknown rather than assumed to be unsupported.

Accepts

  • Text input
  • Image input
  • Audio input
  • Video input

Produces

  • Text output
  • Audio output

Capabilities

Function callingVisionAudio

What is Qwen-Omni Turbo?

Editorial briefing: Qwen-Omni Turbo

Qwen omni model for text, vision, audio, and multimodal agent tasks This is a source-backed review draft for Qwen-Omni Turbo from Alibaba. It documents what the registry says and calls out what still needs a human editor to verify; it does not turn unverified fields into product claims.

What the source record says

The source record lists a release date of 2025-01-19 and a knowledge cutoff of 2024-04. It identifies the model family as qwen and describes open weights as not indicated as available. These fields are useful for narrowing a shortlist, but the linked primary source remains the reference for any current release or policy change.

Interface and modality fit

Qwen-Omni Turbo accepts text, image, audio, video and returns text, audio according to the registry. That makes the model a potential fit only where those interface assumptions match the product workflow. A team should test its own file types, tool schema, safety settings, and deployment constraints rather than assuming that a listed modality works identically in every provider surface.

Limits and operating assumptions

The listed context window is 32,768 tokens, with a listed maximum output of 2,048 tokens. The source declares tool calling, temperature control. Those flags describe an interface surface; they are not evidence of response quality, speed, tool reliability, or availability.

Recorded evaluation evidence

  • The registry record does not include a benchmark result for this model. That is an evidence gap, not a quality judgement.

A benchmark number is meaningful only alongside its task, harness, date, and source. It should not be treated as a universal ranking, and it should be refreshed before an editor uses it in a comparison or recommendation.

How to evaluate this model

Start with a small, representative test set: the prompts people actually send, the tools the product calls, the languages and files it receives, and the failure modes users care about. Compare output quality, structured-output reliability, latency, token use, safety behavior, and operational support under the same conditions for every candidate. Keep the source link, test date, region, and provider route next to any decision so the review can be repeated later.

Human review checklist

Before approval, an editor should verify the linked source, confirm whether a currently supported API or hosted route exists, add first-party pricing only when it is published, check benchmark provenance, and record any important limitations. If a fact cannot be verified, this page should say so plainly. That protects readers from stale model pages and gives search engines a materially useful, evidence-led resource rather than a generated catalogue entry.

How to evaluate Qwen-Omni Turbo

Use the recorded facts as a shortlist, then validate the model against representative inputs and production constraints.

Workload fit

Qwen-Omni Turbo is categorized for Any-to-any, Audio-text-to-text, Automatic speech recognition, Image-text-to-text, Image-to-text, Text generation, Text-to-speech, Text-to-text AI models, Video-text-to-text. Its current record accepts text, image, audio, video and produces text, audio. Confirm file formats, preprocessing, and provider-specific request schemas before implementation.

Capacity and cost

The directory records 32.8K context and 2.0K maximum output. Listed token prices are $0.07 input and $0.27 output per 1M tokens. Treat missing values as unknown and recheck current commercial terms.

Operational behavior

Recorded output speed is — and time to first token is —. Hosting route, region, prompt length, concurrency, and provider load can materially change both measurements.

Evidence boundary

This page separates sourced model facts from incomplete fields. Benchmark evidence is displayed only when its source is linked and verified. Before choosing Qwen-Omni Turbo, test task quality, tool reliability, safety behavior, data controls, rate limits, and total cost on the exact route you intend to use.

Strengths

  • + Registry-backed capabilities
  • + Provider: Alibaba

Limitations

  • Draft record — editorial review required
  • Verify pricing and independent evaluations before approval

Frequently asked questions

Qwen-Omni Turbo is a Alibaba model listed in the provider’s public registry. Qwen omni model for text, vision, audio, and multimodal agent tasks

Related approved models in Text-to-speech. Compare specifications and verify fit for your workload.

OpenAI

GPT-Realtime-2.1

Realtime speech-to-speech model with configurable reasoning, tool use, and robust voice-agent behavior

128K contextCompare

Google

Lyria 3 Clip Preview

Music generation model for short 30-second clips, loops, and previews from text or image prompts

131.1K contextCompare

Google

Lyria 3 Pro Preview

Music generation model for full-length songs from text or images with vocals and structure

131.1K contextCompare