DeepSeek tightens free chat limits and Coding Plan code appears
Multiple users reported that the DeepSeek App and web version have begun limiting free chat services. Long conversations that have been inactive for more than 7 days are no longer supported for continuation, the per-input limit has been reduced to about 40,000 characters, and daily chat quotas have been set. After the quota is used up, users are prompted, “Because the server is busy, the usage quota has reached its limit.”
Two days ago, developers discovered that the DeepSeek web front end had added quota management code, which can synchronize the remaining quotas of each model every 5 minutes and display a reminder after the quota is exhausted. A package field named “Coding Plan” appeared in the code, prompting speculation about a personal paid subscription.
On November 13, DeepSeek opened application APIs for web search, file reading, voice, and other functions, and also open-sourced a demo client that supports importing historical conversations. Affected users can export their original chat records and continue conversations by importing them through this client. API calls are billed based on actual usage. DeepSeek has not yet announced specific daily usage quotas, nor has it confirmed the price or launch date of Coding Plan.
Original sources:
Title: DeepSeek users report chat limits as the service cites capacity constraints
Publisher: TechNode
Publication date: 2026-11-16
URL: technode.com/2026/11/16/deepseek-users-report-chat-limits-as-the-service-cites-capacity-constraints
Source nature: media report (user feedback)
Verification status: The full report was read this time, verification date 2026-11-16.
Supporting content: Supports the user-reported limit on long conversations inactive for 7 days, the per-input limit of about 40,000 characters, and the daily quota prompt after exhaustion; does not prove an official announcement or the exact quota figures.
ABAB AI Insight
DeepSeek is a Chinese AI company. Multiple users reported that its App and web free chat services have introduced new limits, including long conversations that have been inactive for more than 7 days no longer being able to continue, a per-input limit of about 40,000 characters, and a “server busy” prompt after the daily quota is exhausted. Users have linked these adjustments to computing capacity pressure.
On the capital and business path, the limits occurred alongside API opening. On November 13, DeepSeek opened APIs for web search, file reading, voice, and other functions, and provided an open-source client that can import historical conversations, with API usage billed according to actual usage. The “Coding Plan” field found in the front-end code is currently only a code-level discovery, and the company has not confirmed the price or launch date.
Compared with historical cases, it is not uncommon for large model companies to tighten free quotas after user growth, with common approaches being to gradually introduce paid tiers or guide users toward APIs. What is different this time is that the restrictions appeared alongside the open-source client and API feature expansion, and quota management code has already been observable by developers.
These changes alter market expectations for the sustainability of DeepSeek’s free services. When long conversations and daily quotas are restricted while an API path is explicitly provided, the focus shifts from model capability to the boundary between free and paid usage. Key observation points are whether the official side announces specific quotas or Coding Plan details, the scale of user migration to the API, and subsequent adjustments to similar restrictions.
ABAB News · Cognition Law
The restrictions on long conversations inactive for more than 7 days and the daily quota limit appeared at the same time.
The “Coding Plan” field in the front-end code is currently only an unconfirmed discovery.
API usage billing and free chat restrictions are being advanced in parallel.