[GH-ISSUE #263] Feature Request; Chunked Transfer of large files #198

Closed
opened 2026-10-26 21:16:39 +00:00 by bsakaguchi · 2 comments
Owner

Originally created by @StevesSteel on GitHub (Feb 4, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/263

I hope this message finds you well. I’m a frequent user of DeepSeek and have found it incredibly helpful for my projects. However, I’ve encountered a limitation when working with large files, as the current system doesn’t support chunked transfers.

I’d like to suggest implementing a chunked transfer feature that would allow users to upload and process large files more efficiently. Here’s how it could work:

Split Large Files: The system would automatically split large files into smaller chunks.

Send Chunks Sequentially: Each chunk would be sent with metadata;


The start of a chunked transfer.

The end of a chunked transfer.

The total number of chunks.

The current chunk number.

This metadata will allow the tool to recognize when a chunked transfer is in progress and wait for all chunks to be received before processing the complete content.

Reassemble on the Backend: DeepSeek would reassemble the chunks into the complete file and process it as usual.

This feature would greatly enhance the user experience, especially for those working with large documents or datasets. I’ve already prototyped a local version of this feature in a collaboration tool, and it works seamlessly.

Thank you for considering this suggestion. I’d be happy to provide more details or feedback if needed.

Best regards,

Originally created by @StevesSteel on GitHub (Feb 4, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/263 I hope this message finds you well. I’m a frequent user of DeepSeek and have found it incredibly helpful for my projects. However, I’ve encountered a limitation when working with large files, as the current system doesn’t support chunked transfers. I’d like to suggest implementing a chunked transfer feature that would allow users to upload and process large files more efficiently. Here’s how it could work: Split Large Files: The system would automatically split large files into smaller chunks. Send Chunks Sequentially: Each chunk would be sent with metadata; The start of a chunked transfer. The end of a chunked transfer. The total number of chunks. The current chunk number. This metadata will allow the tool to recognize when a chunked transfer is in progress and wait for all chunks to be received before processing the complete content. Reassemble on the Backend: DeepSeek would reassemble the chunks into the complete file and process it as usual. This feature would greatly enhance the user experience, especially for those working with large documents or datasets. I’ve already prototyped a local version of this feature in a collaboration tool, and it works seamlessly. Thank you for considering this suggestion. I’d be happy to provide more details or feedback if needed. Best regards,
bsakaguchi 2026-10-26 21:16:39 +00:00
Author
Owner

@github-actions[bot] commented on GitHub (Mar 7, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!

<!-- gh-comment-id:2705216146 --> @github-actions[bot] commented on GitHub (Mar 7, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!
Author
Owner

@github-actions[bot] commented on GitHub (Mar 31, 2025):

false

<!-- gh-comment-id:2764821625 --> @github-actions[bot] commented on GitHub (Mar 31, 2025): false
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepSeek-R1#198
No description provided.