Drıftstack docs
Docs

Cookie jar too large for this session (413)

You might be here because: “This cookie jar is too large for this session” · “cookie import failed” · “That is too large to send. Choose something smaller” · “413 payload-too-large” · “That cookies file has too many cookies (max 2000)” · “why won’t my cookies import”

Short answer

The cookie file is bigger than the browser running this session can accept in one go, so nothing was imported. Trimming the file (only the sites you need) and importing again is the fix; retrying the same file will never work.

Check first

  • How big is the file, and how many cookies? The limit is about 3.9 MiB of JSON unless the session takes more, and at most 2000 cookies per import.
  • Is the session still running? Import needs a live session.

Likely causes and fixes

  1. Jar over the session’s size. The server refuses with HTTP 413: “This cookie jar is too large for this session (limit …).”. The desktop app repeats that sentence with the limit. Fix: export a smaller set of cookies (one site’s, or the current session cookies only) and import again.

  2. More than 2000 cookies. The app stops before sending: “That cookies file has too many cookies (max 2000).”. Split the file or remove sites you do not need.

  3. Whole request over 8 MiB (from code). Also a 413.

  4. Nothing to do with size? “Couldn’t read any cookies — …” means the file format was not understood — see Import or export cookies.

If it still fails

Press Talk to a person in this chat (or open Help) and include the file size, cookie count and the exact message. Support cannot raise the device’s limit.