Recently, many DeepSeek users have received a new prompt: due to insufficient computing power, long conversations that have been inactive for more than 7 days are no longer supported.
That's not the only one affected. Some users found that the maximum text input limit for a single input has been adjusted to about 40,000 words. If they used too much text that day, the page will prompt that the server is busy and the usage quota has reached the upper limit.
These three restrictions respectively block three types of people: those who use DeepSeek as a long-term project notebook and a conversation for several weeks; those who post an entire paper or an entire contract at once; and heavy users who browse intensively every day.
Several companies at home and abroad are doing this to tighten the free quota. However, DeepSeek has always given people the impression of "use it casually", so the gap is huge.
What to do with old conversations that are locked? Someone has already compiled a list of chat history migration tools. The basic idea is to export the conversation first, then organize it into a summary and feed it to the new conversation, or directly move it to other products to continue the conversation.
The 7-day line also revealed something: saving the context of a long conversation itself takes up resources, and the model has to re-read the first tens of thousands of words every time the conversation continues. For a company that keeps prices very low, cutting off dormant conversations is the most computationally efficient way to save active users.
If you have a long dialogue that you are using, it is recommended to export a copy now instead of waiting for it to sink 7 days away.