Image: Anthropic / support.claude.com Anthropic Extended Fable 5 Subscription Access to July 12
Anthropic reversed the July 7 cutoff for Claude Fable 5 just hours before it was set to take effect, extending included access on paid plans through July 12 at 11:59 PM PT.
Anthropic changed course on Fable 5 access again. The model was scheduled to leave standard paid subscriptions on July 7, but the company extended that date to July 12 just hours before the original cutoff hit.
The extension applies to Pro, Max, Team, and premium Enterprise subscribers. The usage rules stay the same: Fable 5 counts toward up to 50% of your weekly usage limit at no extra cost. After that 50%, you either switch to another Claude model or buy usage credits. No activation required.
The deadline is now July 12 at 11:59:59 PM PT.
The timeline so far
Fable 5 has had a complicated few months. It went into a paid usage-credit tier in June, got suspended for 18 days after US export control concerns, came back with an updated safety classifier on July 1, and then faced another removal from subscriptions.
The original July 7 cutoff was itself a revision of an earlier date. Anthropic initially signaled that access would end when subscriptions renewed after July 7, creating some confusion about exactly when individual accounts would lose access. The company then clarified the cutoff as July 8 at 12 AM PT, which is when most users read it as “July 7.” The extension adds five more days on top of that.
What happens on July 12
After July 12, Fable 5 moves fully behind usage credits. Access still exists, but it’s metered at $10 per million input tokens and $50 per million output tokens, the highest rate Anthropic has published for a generally available model.
Anthropic has said it wants to restore Fable 5 as a standard subscription benefit once capacity allows. No timeline has been given.
The extension comes after significant user backlash over removing a model that was actively part of the subscription value for Pro and Max subscribers. Anthropic did not explicitly cite that feedback as the reason for the delay, but the timing makes the connection obvious.
Source: Android Authority, Anthropic Support