Qwen3.8-27B
by Qwen
Open-weight vision-language model for reading images and video frames as text
Qwen/Qwen3.8-27Bmixpeek://image_extractor@v1/qwen38_27b_v1Overview
Qwen3.8-27B is the vision-language generation in the Qwen3.x line, taking interleaved image and text input and producing text. It is the most-liked image-text-to-text model on the Hugging Face Hub at the time of writing, with roughly 1.0M downloads, and it ships under Apache 2.0, which makes it one of the few frontier-scale VLMs you can self-host without a negotiated licence.
On Mixpeek it is used as a captioning and visual-question-answering stage over extracted frames: scene-split a video, sample keyframes, and have the model describe what is in them so the text is searchable alongside the visual embedding.
Architecture
Decoder-only vision-language model, 27B parameters, qwen3_5 architecture in transformers. Conversational, accepts interleaved image and text input. Also published as an FP8 checkpoint for reduced memory footprint.
Mixpeek SDK Integration
import { Mixpeek } from "mixpeek";
const mixpeek = new Mixpeek({ apiKey: process.env.MIXPEEK_API_KEY });
// Caption sampled frames so the description is searchable next to the embedding.
await mixpeek.collections.create({
collection_name: "video_frames",
feature_extractors: [
{ extractor: "mixpeek://image_extractor@v1/qwen38_27b_v1" },
],
});Capabilities
- Image and video-frame captioning
- Visual question answering over documents and scenes
- Interleaved multi-image reasoning in one prompt
- On-screen text reading without a separate OCR stage
- Open weights under Apache 2.0, so it can be self-hosted
Use Cases on Mixpeek
Explore on Mixpeek
Compare alternatives in this category
Hand-picked tools & platforms compared
Deep-dive technical guide
See how Mixpeek runs models as extractors
Store & search embeddings at scale
Usage-based pricing for pipelines
Compare models, APIs & infrastructure
Specification
Research Paper
Qwen3.8-27B on Hugging Face
arxiv.orgBuild a pipeline with Qwen3.8-27B
Add this model to a processing pipeline alongside other extractors. Combine with retrieval stages for end-to-end search.
Run it on your own data, free