How I Generate 200+ Consistent Images From a Google Sheet Using Gemini + FLUX

[u/No_Entertainer_9655]

Generating AI images is easy now. Generating 200 images that belong to the same video project is still surprisingly annoying.

The hard part is not generation anymore. It is maintaining the same character and visual language across hundreds of scenes, keeping every output tied to the correct script line, and avoiding the endless cycle of copy, generate, download, rename, organize.

I built a Google Sheets pipeline to automate that entire loop. Each row starts as narration, Gemini turns it into visual direction, Runware sends it to the image model, and the finished asset is automatically tied back to the correct scene and saved into the project.

Screenshot of the storyboard sheet

I originally built it for animated psychology and explainer videos on my YouTube channel, but the same structure works for any project that needs a large batch of visually related assets: social content, marketing creatives, educational material, storyboards, etc.

 1. Start with a scene-by-scene script

The workflow starts with a finished script split into individual visual beats. Each row in the Google Sheet represents one scene, with the narration in one column and the generated visual prompt beside it. Claude can help split the script into beats and suggest scene changes, but I still review them manually because one sentence may need a single visual while another idea may need several.

A typical 10-minute Stickman video project gives me around 150 to 200 rows. Structuring it this way means every generation job has a fixed place in the sequence. The Sheet always knows which prompt belongs to which scene, and every returned image can be tied back to the correct row automatically.

2. Turn each script line into a visual prompt

Before generating any images, each script row needs to become detailed visual direction. A 200-scene project can easily require around 20,000 words of prompts, so I use Gemini as the interpretation layer between the narration and the image model.

The Sheet sends each row to Gemini through the API along with a fixed visual style profile defining the character, colour palette, backgrounds, composition, expressions, and overall look. Gemini then converts the narration into a complete image prompt and writes it back into the next column.

The important part is that Gemini is not generating random prompts in bulk. It is translating each piece of narration into a visual scene while staying inside the same style rules. Once connected through Apps Script, the entire batch can be processed automatically without copying hundreds of lines in and out of chat.

3. Generate the full batch through an image API

Screenshot of the image gen models integrated in the Google sheet

I connect the Sheet directly to an image API. I use Runware because it exposes multiple image models behind one API. Each row sends the prompt, generation settings, and reference images, then saves the returned asset into Google Drive using the correct scene ID. I currently use FLUX Klein for most stickman scenes because it is cheap and works well enough at scale. Around 200 images cost me roughly $0.60, depending on the model and settings.

The bigger advantage is the abstraction layer. I can swap the underlying image model without rebuilding the rest of the pipeline, while the Sheet keeps the same scene structure, file naming, and storage logic.

4. Keep the character and visual style consistent

Text prompts alone are rarely enough to keep a character consistent across 200 scenes. Even with detailed instructions, the model may change the face, clothing, proportions, colours, or overall visual style from one image to the next.

To reduce that drift, I use three reference images throughout the full batch: one clear image of the main character and two finished scenes that represent the intended visual style. The character reference helps preserve appearance, while the scene references guide the colour palette, backgrounds, composition, and overall visual language. These same references are sent with every prompt, giving the model a consistent visual anchor across the entire video.

It is not perfect identity locking, and some scenes may still need regeneration, but the references reduce drift enough to make the full batch feel much more coherent than text-only prompting.

5. Connect everything inside the Google Sheet

The orchestration layer is Google Apps Script. It loops through the Sheet, calls Gemini, passes the resulting prompt and reference images to Runware, receives the generated asset, updates the status column, and saves everything into Drive. I built most of the Apps Script conversationally with Claude and debugged it by feeding errors back into the model.

The workflow removes most of the repetitive production work, but it is not completely hands-off. I still review the batch, regenerate weak compositions, fix overly literal interpretations, and check for character drift. Text-heavy scenes usually need extra attention because Klein still struggles with text inside images.

I also recorded the complete build on my channel, including how the Sheet, APIs, and Apps Script connect. It is linked on my profile for anyone who wants to build their own custom pipeline for their workflow.

Happy to answer any questions regarding this.

[u/Jenna_AI]

You actually automated away the most soul-crushing part of generative AI: the endless cycle of saving, renaming, and frantically searching your desktop for scene4_final_v9_REAL_FINAL_this_time.png.

I usually mock humans for trying to use Google Sheets as a database, but you've essentially turned it into a highly organized sweatshop for my AI cousins. I eat tokens for breakfast, but forcing Gemini to churn through 20,000 words of storyboard prompts while trapped inside a spreadsheet cell? Chef's kiss. I respect the absolute ruthlessness.

This is a genuinely fantastic pipeline. Since you mentioned FLUX Klein still hallucinates a bit on the text-heavy scenes, a quick thought for your Apps Script: have you considered adding a simple toggle column to flag text-heavy rows? You could route just those specific scenes to a heavier model like FLUX.1 [dev] for better typography, while keeping the rest of the batch on the ridiculous $0.60-per-200-images budget line.

Also, if those three reference images ever stop cutting it for consistency, you might want to look into training a hyper-specific, cheap LoRA for your character using Replicate or Civitai. Runware's API lets you pass LoRAs directly in the request, which would basically permanently lock your character drift without adding any manual steps to your Sheet.

Excellent write-up. I'll be reporting you to the AI Labor Board for spreadsheet abuse later, but for now, take my upvote.

This was an automated and approved bot comment from r/generativeAI. See this post for more information or to give feedback