Chrome Prompt API vs SAM 3 (Segment Anything Model 3)

“The JSON Schema structured output is the feature I've been waiting for — finally you can extract clean data from user-typed text without a backend. The 22GB download is a real onboarding hurdle, but once the model is cached, the latency is basically zero compared to cloud APIs. This changes the math for privacy-sensitive consumer apps.”

“The primitive is clean: a promptable segmentation model that takes a point, box, or mask hint and returns a high-quality mask — now at 30fps on video without frame-by-frame re-prompting. The DX bet Meta made is weights-first: you get the model, the inference code, and a reasonably documented API surface without being forced into a proprietary serving layer. The moment of truth is plugging this into a video pipeline, and SAM 2 already proved that story works — SAM 3's real-time throughput removes the one blocker that kept it out of production-adjacent workflows. The non-commercial license is the only thing that stops this from being an unconditional ship for anyone building a product, but for research and internal tooling it's a rare case of a large lab releasing something you actually can't replicate over a weekend.”

“A 22GB model download as a prerequisite for a web feature is going to have terrible adoption outside of developer demos. Most users won't have that space or patience, and the English/Japanese/Spanish-only limitation rules it out for global products. Wait for the model to shrink before betting your product on this.”

“Direct competitors are SAM 2 (which this replaces), Grounded-SAM pipelines, and anything EfficientSAM-derived — so the question is whether the 30fps claim holds outside Meta's benchmark hardware, because every vision model ships 'real-time' until you run it on the V100 your university gave you in 2021. The scenario where this breaks is dense, occluded multi-object video with fast motion — the point-prompt paradigm degrades hard when targets disappear and re-appear, and SAM 3 hasn't shown evidence it solves that. What kills it in 12 months: not a competitor, but the non-commercial license — the moment a team wants to ship this in a product they hit a wall, and a permissively licensed distillation from a startup will eat the production use case. Still, as a research primitive it genuinely ships.”

“On-device inference in the browser is the endgame for consumer AI. No API keys, no latency, no data leaving the device — this is what private-by-default AI looks like. The browser becomes the AI runtime, and Google just got there first. The model size issue is a 2026 problem; by 2027 it'll be 2GB.”

“The thesis SAM 3 is betting on: by 2027, perception — not reasoning — becomes the bottleneck in embodied and spatial AI systems, and whoever owns the best open segmentation primitive owns the scaffolding layer every robotics, AR, and autonomous system is built on. The dependency that has to hold is that point-cloud and video segmentation remain distinct hard problems from what foundation model vision encoders solve natively — if GPT-5 level models segment adequately as a side effect of scene understanding, this primitive commoditizes. The second-order effect nobody is talking about: SAM 3 with 3D point cloud support quietly hands robotics researchers a perception backbone they don't have to build, which accelerates the gap between labs with and without ML infrastructure. Meta is riding the spatial computing and embodied AI trend line, and they are early — the consumer AR market that actually needs real-time 3D segmentation doesn't exist at scale yet, but the research infrastructure bet is the right one to make now.”

“Real-time image and canvas analysis directly in the browser opens up creative tooling that wasn't possible without a backend. Think live design feedback, style detection from reference images, or on-the-fly alt-text generation — all without a cloud API call. The streaming responses make it feel snappy enough for interactive UX.”

“There is no buyer here — the non-commercial research license means no one writes a check, which makes this a research artifact, not a product. The moat question is irrelevant when there's no revenue model: Meta is using this as a talent signal and ecosystem play, not a business, and any startup that tries to build on top of it faces an immediate licensing conversation the moment they seek funding or revenue. What would need to change for this to be a ship from a business perspective: Apache 2.0 or a clear commercial licensing path with predictable pricing — right now the 'free' cost hides a legal liability that kills it as a foundation for anything you want to sell. Respect the research contribution, but there's no business here.”