DeepSeek caps chat history at 7 days and input at about 40,000 characters
DeepSeek's app and website now limit chat history, input length and daily use, reportedly because computing power is strained. Long-document habits may need to change.
The short version
- Chats inactive for more than 7 days are no longer kept as long-conversation history
- A single input is now capped at about 40,000 characters
- A new daily quota stops further use once you hit it, with a server-busy message
- Users attribute the changes to pressure on DeepSeek's computing resources
- Exact daily quota numbers are not given in the report
Why it matters
If you use DeepSeek's chat as a working notebook or paste in long documents, the habit now has a shelf life of about a week. Saving your own copies and keeping a tested backup tool is cheap insurance. It also shows that free AI tools run on limited capacity, and their terms can tighten without warning.
What DeepSeek changed
As AIBase reported, DeepSeek has started limiting long conversations in both its mobile app and its web version. The changes cover three areas: how long old chats are kept, how much text you can send at once, and how much you can chat per day.
Conversations that have sat idle for more than 7 days are no longer supported as long-conversation history. A single question is now limited to roughly 40,000 characters of text.
The daily quota wall
The platform has also added a daily conversation quota. When you reach it, the system shows a message saying the servers are busy and your allowance is used up, and it blocks further use for now.
The report does not say how big the quota is, so avoid planning around any specific figure you see circulating. Nor does it say whether the limit varies by task or user.
Why it is happening
According to user feedback, the main driver is pressure on DeepSeek's computing capacity. Long chats and multi-turn exchanges use more computing power the longer they run, and demand keeps growing as more people use AI apps more often.
The report frames this as a balancing act: platforms must hold down running costs while keeping the service usable. Options include smarter allocation of resources, more efficient processing, and tiered service levels.
What to do now
If you keep one long thread going as a project record, copy anything important into your own files. Ending a session by asking for a short summary, and saving it, lets you start a fresh chat without losing context.
If you paste whole reports or transcripts, test your longest input against the 40,000-character ceiling, or split it into pieces. If DeepSeek is part of your daily routine, line up a second tool in advance so a quota wall does not stop your work.
What to watch
- Whether DeepSeek publishes an official explanation or the exact daily quota numbers
- Whether older chats are deleted or merely hidden after 7 days, and whether the limits are temporary
- Whether developer (API) access is affected
Try it
Check your longest typical prompt against the roughly 40,000-character cap, and save a copy of any chat you still need before it has sat idle for 7 days.
Sources and links
- ReportingAIBase: the article we sourced
Liked it? Say why
Add a line for other readers.
No account needed. We never show your email. Comments with links, ads or abuse are held and not shown. Your comment shows after a quick check.
Listen to the AI Wire headlines
Listen to the AI WireListen to our daily AI shows every morning: on your commute, in the shower, wherever you are
Listen to the daily showsFirst reported by AIBase · Read the original. Written by the SI Agent News Desk from the reporting above.Written with AI from the source above. Every number is checked against the source. Spot a mistake? Corrections.
