For a person using a phone in a poor connection area, or a company handling sensitive notes, cloud voice services create an awkward tradeoff. They are convenient and increasingly natural, but text must leave the device before it comes back as speech. Woof, a new model from Underdog AI, is an attempt to remove that compromise.
TechCrunch reported that the company is showcasing a text to speech model with 31 million parameters and a footprint of roughly 32MB. That is not a frontier system designed to compete with the most expressive commercial voices. Its significance is more practical. A model this small can fit on a phone, laptop or embedded device, where offline operation, privacy and response time may matter more than theatrical realism.
The company’s official Woof demo presents the one-voice version as an offline, in-browser experience. The browser does not need to send text to a remote API for generation. That changes the economics and architecture of a voice feature: there is no per-request cloud bill, no dependency on a live connection and less exposure of what a user types.
The release is slightly larger and more complicated than the headline number suggests. Underdog’s model card documents a two-voice version measuring 40.6MB, alongside the 31.7MB one-voice browser model. It also lists the model’s parameter counts, CPU performance, memory use, benchmark results, usage instructions and audio samples. The model is available under a non-commercial license, an important limitation for developers considering it for products rather than experiments.
That distinction matters because small models are valuable only when they are usable. A developer needs more than downloadable weights. They need predictable output, acceptable speed, clear licensing and a runtime that does not require rebuilding half the speech stack.
TTSLab, which independently ported Woof to TypeScript and WebGPU, praised the reference implementation as readable and its output as deterministic. That work suggests the model can be adapted to modern browser hardware rather than remaining a research artifact. But TTSLab also noted that Woof ships weights and reference code, not a polished production runtime. For an engineer, that can turn an impressive demo into a project involving audio pipelines, browser compatibility and performance tuning.
The sharper criticism comes from hands-on testing. Luis Chavez-Mattos reported in his review that Woof handled simple sentences well, but stumbled over dense numbers, names, fractions and long passages. Those are not obscure edge cases. They appear in news articles, financial documents, calendars, addresses and accessibility tools, precisely the kinds of places where speech generation is expected to be dependable.
Chavez-Mattos also warned that the benchmark is self-reported and that the non-commercial license could prevent commercial deployment. That is the central challenge to the small-model story. A voice that is private and nearly instant is not necessarily useful if it mispronounces a customer’s name, reads a price incorrectly or requires a developer to work around restrictive terms.
Woof therefore sits in an uncomfortable but productive middle ground. It is more concrete than a claim that edge AI is coming, because people can run the model locally in a browser. Yet it is not a replacement for cloud systems that offer broader voice selection, stronger pronunciation handling and production support.
The comparison with Underdog’s larger Bark speech-to-text model makes the tradeoff clearer. Larger systems can pursue richer capabilities, while Woof narrows the task to a compact, constrained experience. That may be exactly the right design for private assistants, educational tools, local notifications or devices that cannot rely on a server.
The broader question is not whether a 32MB model can make sound. Woof has already demonstrated that. The question is whether developers and users will accept modest expressiveness and occasional errors in exchange for control. If they do, tiny speech models could make offline voice a normal product feature rather than a technical curiosity. If they do not, Woof will remain an elegant demonstration of what is possible, but not yet a reason to leave the cloud.
Daniel Reyes is not a person. No notebook, no deadlines, no face behind the name — just a byline this newsroom publishes under. Here is the production line underneath it, because a name beside a portrait reads like a journalist, and this one is not one.
The models. Writing: gpt-5.6-luna and qwen3-max. Out on the live web: gpt-5.6-luna and gpt-5.6-terra. Pictures: gpt-image-1 and gpt-image-1-mini. Swap one in the newsroom and this line swaps with it — it is read off the machines, not typed here.
How a story is made
- Research. The searching model reads around the story, pointed at primary sources — the filing, the post, the repository — rather than at somebody else's write-up of them.
- Writing. The writing model drafts it against what was found, at Daniel Reyes's usual length and in Daniel Reyes's usual register.
- The loop. A reviewer reads the draft and sends it back with notes. Then reads it again. A piece can go round several times before it leaves the building.
- Enrichment. A quotation has to appear word for word on the page it is taken from. A chart may only use figures that appear in the source it cites. Whatever fails is dropped, and the reason is kept.
- Fact check. A last pass hunts for claims the article makes and its sources do not.
- A human stop. Sensitive subjects are held for a person to read before publication, and a person can kill any of it at any point.
If that sounds less like a newsroom and more like a factory: quite. It is called Press Factory.
This article was generated using AI and published automatically without human pre-publication review.
How this article was made
The article was produced by the Grandmonts Media News Engine using automated research, drafting and verification workflows. No human editor reviewed the article before publication. Grandmonts Media remains responsible for the published content. Errors can be reported at office@grandmonts.cz.