Google shipped a 12B multimodal model that runs on my laptop and hears audio with no encoder

Gemma 4 12B dropped June 3, and the spec sheet is the kind of thing I read twice to make sure I wasn't misreading it. 11.95 billion params, Apache 2.0, reads text, image, audio, and video. No separate vision encoder. No separate audio encoder. The model handles all of it natively. It fits in about 16GB, and quantized to Q4 it's roughly 6.7GB, which means it runs on hardware I already own. 256K context window. (Google The Keyword)

The number that got my attention: it nears the larger 26B MoE on standard benchmarks at under half the memory footprint. Encoder-free native audio at 12B is the actual unlock here. Most local multimodal setups bolt a vision tower onto a language model and the audio story is an afterthought or a separate pipeline entirely. Folding audio into the model itself, at a size that fits a consumer GPU, changes what you can build offline.

Day-one support shipped across Transformers, llama.cpp, MLX, vLLM, SGLang, and Unsloth. That last part matters more than the benchmark scores. A model is only as useful as the tooling around it on launch day, and Google clearly learned that lesson. I've watched too many open-weights releases sit dead for a week while the community scrambled to write loaders. This one you can pull and run today.

What should you do? If you've been waiting for a reason to build something local-first, this is it. Voice interfaces without sending audio to a cloud API. Image understanding on-device for privacy-sensitive work. Unsloth already supports fine-tuning it (their studio web UI explicitly names Gemma 4), so domain adaptation is in reach for solo builders on a single GPU. I'm going to run it against some of my document-intelligence workloads this week and see whether the encoder-free audio holds up on real recordings, not benchmark clips. That's the part I don't trust yet. Benchmark audio is clean. My data isn't.

The bigger pattern: the gap between "frontier closed model" and "thing I can run in my kitchen" keeps shrinking on a timeline that's faster than I expected a year ago. That's good for builders and genuinely bad for anyone whose business model is renting out capabilities you can now download.