OpenAI has quietly removed rate limits on text chats for its free and Go tiers. The Verge reports that casual users can now natter away with ChatGPT all day without hitting a wall. No more "you've reached your limit, come back in three hours" nonsense.
On the surface this looks like generosity. Forty years in software has taught me that generosity in a product roadmap is usually strategy wearing a friendly coat.
The Tell Is What They Didn't Unlock
Text chat is cheap. It's been cheap for a while — the marginal cost of another back-and-forth conversation is tiny compared to voice synthesis, image generation, or anything that spins up an agent to go and do real work across multiple tool calls. OpenAI didn't remove limits on those. They removed limits on the bit that costs them least and generates the most goodwill per pound spent.
That's not a criticism. It's just good business, and it's worth reading as a signal rather than a gift. When a company makes something unlimited, they're telling you where they don't see the value anymore. The value has moved on. It's moved to voice, to agents, to the API tier where you pay per token and OpenAI's margin is protected.
What This Does to User Expectations
Here's the bit that actually matters for anyone building on top of these models. Your users — the people signing up for whatever SaaS tool you've built — now have an unlimited free alternative sitting one browser tab away. If your product is essentially "a nice wrapper around ChatGPT with a few prompts baked in," that wrapper just got a lot less impressive.
I've said this for years to anyone who'll listen: raw access to a model is not a product. The prompt engineering, the workflow, the integration with other data sources, the bit where it publishes to WordPress or drops a video into your content calendar without you touching it — that's the product. If unlimited free chat makes your customers think "why am I paying for this when I could just ask ChatGPT myself," you've built on sand.
This is exactly the thinking behind how I've architected the Masher suite. RSSMasher, Article2Video, BookMasher — none of them are betting on the conversation itself being the valuable bit. The value is in stitching dozens of steps together into something that runs unattended and produces a finished asset. A free chat window doesn't do that no matter how unlimited it is.
Where Paid API Access Still Wins
For anyone running genuine automation at scale, the API tier hasn't got more generous — quite the opposite, arguably, since OpenAI needs that revenue line to subsidise the free generosity elsewhere. And that's fine, because the API was never about unlimited chit-chat. It's about:
Reliability at volume. You need predictable throughput when you're processing hundreds of articles or videos a day, not a rate limit that resets on OpenAI's schedule.
Structured output and function calling. The free tier's conversational UI is not built for machine-to-machine work. Your automation stack needs JSON back, not prose.
Model choice and version pinning. When you're running a production pipeline, you cannot have the underlying model quietly change behaviour overnight because OpenAI updated the free consumer app. The API lets you choose your poison and stick with it until you're ready to test the next one.
None of that changed this week. What changed is the psychological baseline of what "AI access" means to an ordinary user, and that baseline just dropped to zero cost for basic text chat.
The Practical Takeaway
If you're building or marketing anything on top of these models, don't panic about unlimited free ChatGPT — but do take it as a prompt to check your own value proposition. Ask yourself honestly: could a reasonably determined user replicate 80 percent of what my tool does by just chatting with the free version for twenty minutes? If the answer's yes, that's not OpenAI's problem to fix. It's yours.
The raw material — model access — keeps getting cheaper and more available. That was always going to happen. The alchemy, the actual transmutation of that raw material into something someone will pay for month after month, still has to come from the workflow you build around it. That part hasn't got any easier, and it's not going to.
Build there, not on the chat window.
— Wayne