Yesterday a small, unglamorous build dropped in r/ChatGPTPromptGenius, and it’s the kind of thing that makes you go “wait, why didn’t I have this already.” No flashy demo, no launch video, no thread of screenshots showing off some flashy dashboard. Just a Chrome extension solving a problem anyone who’s fed a huge TXT file into ChatGPT knows way too well.
Here’s the setup: This Redditor (going by u/Aggressive_Swim_9361) works with long TXT files all the time. Notes, study material, documentation, prompt libraries, research dumps, whatever. Every time, the same annoying loop: copy a chunk, paste it, wait, scroll back to find where you left off, copy the next chunk, repeat until your patience is gone and you’ve lost track of which paragraph you already sent. Anyone who’s tried to feed a 40-page transcript into a chat window one section at a time knows exactly how much mental overhead that “where was I” moment adds. So this contributor built “ChatGPT Batch Sender” to kill that loop for good.
What it does is simple on paper. You pick a TXT file, set how many lines go into each batch, set a delay between sends, and the extension takes it from there. You can pause it, resume it, stop it, or reset it, and it always remembers exactly where it stopped. That last part matters more than it sounds. If your laptop sleeps mid run or you need to step away for a call, you’re not scrolling through a chat log trying to reconstruct your place. The extension just picks up where it left off.
Here’s the twist though: The file never leaves your browser. No upload to some server, no third party sitting between your notes and ChatGPT. Everything, including your progress, stays local. That’s a real distinction if you’re working with anything sensitive, like internal documentation, client notes, or a manuscript you haven’t shared with anyone yet. And it doesn’t try to trick ChatGPT’s limits either. It just automates the boring part of sending things in order, which honestly is the whole appeal. Nobody wants a rate-limit workaround that gets your account flagged. They want the tedious clicking gone, not a shortcut that risks the account they’ve built history on.
If you’ve got a giant transcript, a research dump, or a stack of meeting notes sitting in a TXT file right now, here’s the mini-workflow this thing sets up for you:
- 📄 Load your TXT file into the extension
- 🔢 Set your batch size (lines per send). The original poster left this open for feedback, since chapters, paragraphs, or custom separators might work better depending on the content
- ⏱️ Set a delay so ChatGPT has time to actually respond before the next chunk lands
- ▶️ Hit start, then let it run while you do literally anything else, grab coffee, answer a Slack message, whatever
- ⏸️ Pause or reset anytime without losing your place in the file
A couple pro tips if you’re going to try this. First, match your batch size to the density of the content. Dense technical documentation needs smaller batches than casual notes, or ChatGPT starts losing thread of what came before and you end up with summaries that miss half the nuance. A batch of 40 lines of API documentation is a very different ask than 40 lines of casual meeting notes, so test a small run before committing to a full file. Second, keep your delay generous if you’re feeding in something you actually need a coherent answer on each time. Speed isn’t the point here, consistency is. Third, if you’re running something long, like a book manuscript or a full course transcript, consider running it overnight with a longer delay between batches. You lose nothing in speed since you’re not watching it anyway, and you reduce the odds of hitting any response hiccups along the way.
Worth noting: One commenter asked whether this only works with TXT files, since their use case was 12 chapters of a community history project written by different authors in probably a dozen different formats. That’s a fair question, and if you’re dealing with mixed file types, this is where it gets interesting for feedback. The creator is actively asking the community whether splitting by lines is even the right call, or if paragraphs, characters, or custom separators would serve people better. That kind of open question is rare this early in a tool’s life, and it means the shape of “batch size” could look completely different a month from now depending on what people actually need.
That’s actually the best reason to go check this out today instead of just bookmarking it. The extension is free, it’s small, and the person behind it is genuinely asking what should change next. If you’ve been doing the manual copy-paste dance with long documents, install it, run a batch through, and drop your take in the replies. Early feedback like this is exactly what turns a decent tool into the one everyone recommends.
Frequently Asked Questions
Q: Can I use this with Google Docs, Word files, or other formats besides TXT?
The extension works with TXT files, but most document formats (Google Docs, Word, etc.) can be exported to TXT. Just download or convert your file to plaintext, then use the extension. This keeps everything clean without formatting complications.
Q: How should I set my batch size? Is lines-based splitting the best approach?
Lines-based splitting is straightforward and gives you predictable control over how much ChatGPT processes at once. For larger documents (like Dlmanon’s multi-chapter garden club project), you’d set a higher line count to preserve context. Character or paragraph-based splitting might work for specific use cases, but lines offer simplicity and flexibility for most workflows.
Q: What happens if my file is huge? What’s the actual limit?
The extension is designed for large files, you can batch a massive document into manageable pieces. The only real constraint is ChatGPT’s context window (how much it can digest in one conversation). The tool doesn’t bypass that limit, but it removes the tedious manual copy-pasting so you’re not spending hours on a repetitive task.
Q: Can I pause or stop the batch sending if I need to?
Yes. You can pause, resume, stop, or reset the sending at any time, and the extension tracks your progress. This is handy if ChatGPT needs time to respond or if you want to adjust something mid-process.
I built a Chrome extension for sending long TXT files to ChatGPT in controlled batches — looking for feedback
by u/Aggressive_Swim_9361 in ChatGPTPromptGenius