AssemblyAI vs Qwen3-ASR: picking speech-to-text for production

Qwen's audio models are some of the most interesting work coming out of open research. Qwen3-ASR is capable, multilingual, and if your team already builds on the Qwen ecosystem, reaching for it is a natural move. Strong model, real momentum — worth taking seriously.

And then worth pressure-testing against what production actually demands. Because a capable open checkpoint and a production speech platform solve overlapping but different problems, and the gap shows up fastest on the two things Qwen wasn't primarily built to own: everything around the transcript, and everything around running it.

Quick comparison

Multilingual is the right battleground — so let's use it

Qwen's appeal is heavily multilingual, so that's the fair place to test it. And multilingual transcription has a specific hard mode: code-switching, where a speaker changes language mid-sentence — Hinglish, Spanglish, and the like. It's one of the harshest tests in speech-to-text, and the spread between models is enormous.

Universal-3.5 Pro handles native code-switching across 18 languages with no configuration and no separate pass — the model transcribes each word in the language it was actually spoken. On our published code-switching benchmark it posts 7.69% average normalized WER, well ahead of other models on the same audio. That's the capability to beat, and building it out of a raw checkpoint is not a config flag.

The transcript is the start, not the finish

Qwen3-ASR gives you words. A production feature needs the layers around them.

Diarization that survives interruptions and overlap — produced jointly with the transcript, not stitched on from a second system. Entity accuracy on the tokens that break products when they're wrong: account numbers, emails, addresses, names. Streaming for anything live — Universal-3.5 Pro Realtime ships the chunking, partials, and endpointing you'd otherwise build from scratch, since most open checkpoints are async-first. Redaction and formatting on top of that.

You can assemble all of it around Qwen. The question is whether that assembly is your product or a distraction from it.

And it still has to run

Free weights come with a GPU bill you pay whether audio is flowing or not, autoscaling against spiky traffic, and an on-call rotation. A managed API bills per second and runs hundreds of millions of inference calls a month with unlimited concurrency — the full economics are in the anchor post, "the real cost of self-hosting open-source speech-to-text."

When Qwen3-ASR is the right choice

If you're already deep in the Qwen ecosystem, doing research or offline batch where you control the audio and can keep GPUs busy, or you have a platform team that wants to own and fine-tune the model, Qwen3-ASR is a solid, flexible choice. Those are legitimate reasons to self-host.

Verdict

Qwen3-ASR is a strong open model, especially for multilingual and research-flavored work. A production voice product needs code-switching that just works, diarization that holds up, reliable entities, streaming, and an SLA — and Universal-3.5 Pro delivers those without a GPU fleet or a stack to maintain. If you're shipping a product rather than studying a model, that's usually the trade worth making.

Settle it on your own audio: grab a free API key and run Universal-3.5 Pro against your hardest multilingual recordings next to Qwen3-ASR.

Frequently asked questions

What is Qwen3-ASR?

Qwen3-ASR is a family of open-source automatic speech recognition models from Alibaba's Qwen team, released in early 2026. It includes two all-in-one models (Qwen3-ASR-1.7B and Qwen3-ASR-0.6B) built on the Qwen3-Omni foundation, with language identification and transcription across 52 languages and dialects. The weights are freely available on Hugging Face, and Alibaba also offers a hosted version (Qwen3-ASR-Flash) through its API.

Is Qwen3-ASR free, and what does it cost to run in production?

The Qwen3-ASR weights are free to download, but running them in production is not. Self-hosting means paying for GPU time — billed whether or not audio is flowing — plus the engineering to add streaming, diarization, and formatting and the on-call time to keep it up. A managed API like AssemblyAI instead charges $0.21 per hour of audio, billed per second with no minimums, so you only pay for what you process. Alibaba's hosted Qwen3-ASR-Flash API is a third option, priced separately from the open weights.

How does Qwen3-ASR compare to AssemblyAI for production speech-to-text?

Qwen3-ASR is a capable open checkpoint, while AssemblyAI is a managed speech platform — they solve overlapping but different problems. Qwen3-ASR gives you the transcript and the freedom to host and fine-tune it yourself; AssemblyAI's Universal-3.5 Pro adds the production layers around the transcript (native code-switching, joint speaker diarization, entity accuracy, streaming, and redaction) plus an SLA, SOC 2, a BAA, and per-second pricing. If you're shipping a product rather than studying a model, the managed path usually removes more work. Benchmark both on your own audio before deciding.

Does Qwen3-ASR support real-time streaming and speaker diarization?

Qwen3-ASR is primarily an offline, async-first model, so real-time streaming and production diarization aren't turnkey — you'd build the chunking, partial results, endpointing, and speaker separation yourself. AssemblyAI ships these natively: Universal-3.5 Pro Realtime streams partial transcripts with roughly 300 ms end-of-turn detection, and diarization is produced jointly with the transcript and optimized for cpWER. For live or conversational audio, that difference is usually where self-hosting gets expensive.

How good is Qwen3-ASR at multilingual and code-switched audio?

Qwen3-ASR covers 52 languages and dialects with built-in language identification, which makes it attractive for multilingual work, though code-switching behavior depends on configuration. Code-switching — where a speaker changes language mid-sentence, like Hinglish or Spanglish — is one of the hardest tests in speech-to-text. AssemblyAI's Universal-3.5 Pro handles native code-switching across 18 languages with no configuration and posts 7.69% average normalized word error rate on its published code-switching benchmark. Test both on your own multilingual recordings, since results vary widely by audio.

When should you use Qwen3-ASR instead of a managed speech-to-text API?

Qwen3-ASR is the right choice when you're already invested in the Qwen ecosystem, doing research or offline batch work where you control the audio and can keep GPUs busy, or you have a platform team that wants to own and fine-tune the model. Those are legitimate reasons to self-host. For real-time or customer-facing products that need reliable code-switching, diarization, entities, streaming, and an SLA without maintaining a GPU fleet, a managed API like AssemblyAI is usually the lower-cost, faster path to production.

‍