Item logo image for Flow Batch — Bulk Prompt Queue

Flow Batch — Bulk Prompt Queue

ExtensionWorkflow & Planning
Item media 5 (screenshot) for Flow Batch — Bulk Prompt Queue
Item media 1 (screenshot) for Flow Batch — Bulk Prompt Queue
Item media 2 (screenshot) for Flow Batch — Bulk Prompt Queue
Item media 3 (screenshot) for Flow Batch — Bulk Prompt Queue
Item media 4 (screenshot) for Flow Batch — Bulk Prompt Queue
Item media 5 (screenshot) for Flow Batch — Bulk Prompt Queue
Item media 1 (screenshot) for Flow Batch — Bulk Prompt Queue
Item media 1 (screenshot) for Flow Batch — Bulk Prompt Queue
Item media 2 (screenshot) for Flow Batch — Bulk Prompt Queue
Item media 3 (screenshot) for Flow Batch — Bulk Prompt Queue
Item media 4 (screenshot) for Flow Batch — Bulk Prompt Queue
Item media 5 (screenshot) for Flow Batch — Bulk Prompt Queue

Overview

Queue many prompts into Google Flow, generate them one by one, and auto-save every image numbered by prompt.

Flow Batch turns a list of prompts into a folder of finished images. Paste your prompts, pick your open Google Flow tab, press Start. Flow Batch types each prompt into Flow, presses Generate, waits for the images, saves them to your Downloads folder named by prompt number, and moves on to the next one. A forty-prompt list becomes one action and a folder that matches your list. WHO IT'S FOR Anyone working from a shot list. Storyboard frames, scene references, thumbnail variations, character turnarounds, product shots, a style test across twenty variations. If you have ever sat through paste, generate, wait, download, rename — forty times in an evening — this is that evening back. WHAT A RUN LOOKS LIKE 1. Paste your prompts into the Prompts tab. One per block separated by blank lines, one per line, or split on a separator you choose. You can load a .txt file instead. 2. On the Setup tab, pick which open Flow tab to drive, then set the model, the aspect ratio and how many outputs you want per prompt. These read themselves from Flow, so the choices offered are whatever Flow is actually offering you. 3. Press Start and leave it. The side panel shows which prompt is running, how many images have landed, and anything that failed. WHAT YOU GET Files named by prompt number, so nothing needs matching up afterwards: 01.png, 02.png, 03.png ... 17-1.png, 17-2.png, 17-3.png (prompt 17 produced three images) The filename is a template you control, with tokens for the number, the variant, words from the prompt, the date and the time. You also choose the subfolder, the number to start at, and the zero padding. THE PARTS THAT MATTER WHEN A BATCH IS LONG A style block on every prompt. Whatever you put in the Prefix and Suffix boxes is added to every prompt in the batch, so a shared style lock stays identical across forty images instead of being pasted forty times. One reference image for the whole batch. Attach an image — uploaded, or picked from the ones already in your Flow library — and every prompt in the run uses it. It keeps going when you don't. The queue lives in the extension, not in the panel, so you can close the side panel, switch tabs and do something else. A run over an hour long survives. Failures don't end the run. Each prompt gets a number of retries you set. Anything that still fails is marked and skipped rather than stopping everything, and "Re-queue failed" puts just those back at the end. "Start from #" resumes a half-finished list without redoing the part that already worked. Pacing you control. Timeout per prompt, delay between prompts, retries per prompt. ABOUT THE "DEBUGGER" PERMISSION Chrome shows a prominent warning for this one, so here is the plain reason. Google Flow ignores clicks that software generates. Every scripted alternative was tested against the live page and produced no request at all. Chrome's debugging interface is the only remaining way to press Flow's own Generate button. It is used for exactly that — the keystrokes and the one button press you asked for — on the single tab you selected, only while a run you started is in progress, and it is disconnected the moment the run ends. It never reads the page's data, never inspects your network traffic, never runs code, and is never attached to any other tab. PRIVACY Flow Batch collects nothing. No accounts, no analytics, no telemetry. Your prompts and your images never leave your computer: they go from your browser to Flow on your own Google account, and the results download straight to your folder. The extension makes one network request. It fetches a small file describing where Flow's buttons are, because Flow's interface changes without notice and this lets a fix reach you the same day instead of waiting out a store review. That request carries no identifier, is the identical request for every user, and nothing is recorded against anyone who makes it. The extension works without it, using the description built into the version you installed. Full policy: https://flow-batch.ferianimahdi93.workers.dev/privacy REQUIREMENTS Google Chrome, and a Google Flow account you can already generate images with. Flow Batch drives the interface you already have. It does not provide image generation, and every generation uses your own Flow credits at the normal rate. Flow Batch is an independent tool. It is not affiliated with, endorsed by, or sponsored by Google. "Google" and "Google Flow" are trademarks of Google LLC.

Details

  • Version
    1.0.0
  • Updated
    November 4, 2026
  • Offered by
    ferianimahdi93@gmail.com
  • Size
    120KiB
  • Languages
    English
  • Developer
    Email
    mahdiferiani@proton.me
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization
The developer has disclosed that it will not collect or use your data. To learn more, see the developer’s privacy policy.

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, visit the developer's support site

Google apps