Rambler, the smart dictation feature Google added to Gboard as part of its Gemini Intelligence suite, has a usage limit. Google has now told Android Authority what happens when you reach it: Rambler drops to offline mode. What Google still has not said, anywhere, is where that limit sits.
What you lose when Gboard Rambler hits its limit
The good news is that the fallback is not a hard stop. A Google representative told Android Authority in an emailed statement:
When offline, Rambler does still remove filler words from dictation, in addition to adding punctuation and capitalization. Primarily what requires connectivity is more complex commands — like rewriting in a particular style or, for example, asking to make a block of text shorter.
So the everyday work survives the cap. Dictate a message with the usual “um”s and half-restarted sentences, and offline Rambler will still strip them out, punctuate the result and capitalise it. What goes away is the cloud-side layer: asking it to rewrite what you just said in a different register, or to compress a paragraph you have already dictated. In practice that means the feature degrades from an editor into a cleaner-upper.
Android Authority describes the fallback as effectively the offline voice typing that has shipped on Pixel phones for years. That is a fair characterisation, and offline voice typing was already good. But it is a downgrade, and it arrives without warning.
Google has not published a number, and that is the problem
This is the part worth being blunt about. There is no published figure for Rambler’s usage limit. Not a word count, not a minutes-per-day allowance, not a monthly quota, and no stated reset period. Google’s own support page for Rambler mentions that the feature is subject to usage limits and, per Android Authority, does not elaborate. The emailed statement clarifies the consequence of hitting the cap without disclosing the cap itself.
An undisclosed limit is not a neutral omission. A cap you can see is something you can plan around — you learn to save the good stuff for when it counts. A cap you cannot see is one you only discover by walking into it, usually mid-sentence, usually while composing something you cared enough about to dictate rather than type. No source describes a counter or a warning banner, and Google has not said whether either exists.
That matters most for the people leaning on this hardest. If voice input is how you get text into a phone because typing is difficult or painful, an invisible throttle on the quality of that input is a genuine accessibility issue, not a minor product quirk. Anyone in that position should know before they rely on Rambler that the polished behaviour is rationed and the ration is secret.
What to do about it
Practically, there is not much to do beyond knowing it exists. If your dictation suddenly stops handling rewrite commands, that is most likely the cap rather than a bug — though a connectivity drop triggers the same fallback, so check your signal before assuming you have hit the limit. Either way, the basic transcription keeps working. If you want more control over how Gboard behaves day to day, our walkthrough of Gboard’s less obvious settings covers the parts of the keyboard you can actually configure.
The thing genuinely worth asking Google for is the number. Metered AI features tend to end up with a published allowance sooner or later, because users push for one. Rambler should get one, ideally with an in-app indicator, before people build a workflow on top of a limit nobody has quantified.
Source: Android Authority
