---
title: "How to Split a Storyboard Into Separate Images (Without a Grid Splitter)"
description: "Grid splitters cut straight through uneven storyboard panels. Here is how to split a storyboard, contact sheet or scanned photo page into separate image files using AI panel detection — free, no signup."
canonical: "https://www.razi.pro/blog/split-storyboard-into-separate-images"
date: "2026-09-07"
tags: ["Images", "Storyboard", "How-To", "AI", "Tools"]
source: "razi.pro"
---

# How to Split a Storyboard Into Separate Images (Without a Grid Splitter)

Before you read on, guess what happens when you feed a six-panel storyboard to a 3×2 grid splitter.

It does not give you six panels. It gives you six rectangles, and the lines between those rectangles fall wherever the arithmetic puts them — straight through a character's face, half an inch left of the gutter you actually wanted. You get six files, all of them wrong, each one containing a slice of two different shots.

That is the whole problem, and it is worth being precise about why it happens.

## Why grid splitters cut through your panels

Every free image splitter you will find does the same thing. You tell it rows and columns, and it divides:

    cellWidth  = imageWidth  / columns
    cellHeight = imageHeight / rows

That is it. The tool never looks at your image. It cannot, because nothing in that formula has any idea where a panel is. It works perfectly when the panels really are evenly spaced — and it fails completely the moment they are not.

There is a smaller cost hiding in the same line. That division is rounded down, so a 1000-pixel-wide image split into three columns uses 999 pixels and quietly discards the last one. Nobody notices a column of pixels. It is worth knowing it happens.

Storyboards are not evenly spaced. A wide establishing shot sits next to two narrow inserts. The gutters between rows are thicker than the gutters between columns because someone left room for dialogue notes. A scanned page is rotated a degree and a half because paper does not lie flat. None of that survives division.

## When a grid splitter is actually fine

Not every job needs anything cleverer. Be honest about which one you have:

| Your image | Grid splitter? |
|---|---|
| Instagram 3×3 puzzle feed | Yes — you *want* mathematically equal tiles |
| A panorama cut into carousel swipes | Yes — equal vertical strips is the correct answer |
| Midjourney's 2×2 output grid | Yes — the four quadrants are genuinely equal |
| A storyboard with mixed panel sizes | No — the cuts will miss |
| A contact sheet | No |
| Four photos on one flatbed scan | No |
| A phone photo of a comic page | No |

If your row is in the top half of that table, use [Image Splitter](https://www.razi.pro/tools/split-image) in one of its grid modes and stop reading — **Instagram 3×3 Grid**, **Instagram 3×1 Carousel Swipe** and **2×1 Split** are presets, and **Custom Grid** lets you set rows and columns yourself. It will take about fifteen seconds.

The rest of this post is for the bottom half.

## Splitting a storyboard with AI panel detection

The alternative to dividing is *detecting*. Instead of computing where the cuts should go, look at the image and find the panels that are actually in it.

That is what the **AI Auto-Detect (Storyboards & Panels)** mode does. The image goes to Google's Gemini vision model, which returns a bounding box in absolute pixels for every panel it can find, and each of those boxes is then cropped out individually.

The consequence worth understanding: **the boxes do not have to be the same size as each other.** A wide panel and a narrow panel come back with different widths, because they were measured rather than calculated. That is the difference between the two approaches, and it is the entire reason this works on storyboards.

Step by step:

1. Open [Image Splitter](https://www.razi.pro/tools/split-image).
2. Drop in your storyboard page. One image at a time — more on that below.
3. Under **Splitting Mode**, choose **AI Auto-Detect (Storyboards & Panels)**. Leave the grid inputs alone; picking a grid mode means the detector never runs.
4. Pick your **Output Format** — PNG, JPEG or WebP.
5. Click **Split Image**, wait for the model, and download the ZIP.

The status line tells you how many panels came back. If that number matches the number of panels you can see on the page, the detection worked.

## What comes back in the ZIP

Always a ZIP, even for a single panel. Inside it:

- Files are named **panel_1**, **panel_2**, and so on in reading order, in whichever format you chose.
- Where the model produced a caption for a panel, that caption becomes the filename instead, stripped down to letters, numbers, dashes and underscores.
- Quality is fixed at 90. There is no slider, which is one fewer decision but also one you cannot revisit.

One detail that will bite you if you are scripting against the output: the numbers are not zero-padded. **panel_10** sorts before **panel_2** in any alphabetical listing. Rename with padding before you feed the folder to anything that cares about order.

## Scanned photos and comic pages

The same mechanism handles a different input entirely. Four photographs on one flatbed scan are, to a panel detector, just four rectangles with space between them — it does not know or care that they are photographs rather than storyboard frames. Same for a photographed comic page.

One real limit here: detected boxes are **axis-aligned rectangles**. If a photo went onto the scanner glass at an angle, you get an upright crop around the tilted photo, not a deskewed one. Straighten the scan before splitting, or straighten the crops after. The tool will not rotate anything for you.

## What this tool does not do

Worth knowing before you plan a workflow around it:

- **One image per run.** There is no batch upload and no multi-page mode. A twelve-page storyboard book is twelve separate runs. If you are working at that volume, this is the honest sticking point.
- **No preview of the detected boxes.** You get a panel count, then a ZIP. You cannot see where the model put the boundaries until you open the files, and you cannot nudge a box that landed badly. If a detection is wrong, your options are to re-run it or to switch to a manual grid.
- **Nothing is processed in your browser.** The image is uploaded to the server to be cropped, and in AI mode it is also sent to Google for detection. Files over about 4.5 MB take a further hop through blob storage on the way. If the page is confidential, that matters — use a desktop tool instead.
- **Twenty splits per hour**, per IP address. No account needed, but the ceiling is real.
- When detection fails outright you get an error, not a silent fallback. **"No panels detected in the image"** means the model found nothing it was confident about — usually a very low-contrast scan or panels with no visible gutters at all.

## When to use Photoshop or Toon Boom instead

If you already own the software, and especially if you are already inside it, use it.

Photoshop has two answers here. **File → Automate → Crop and Straighten Photos** is purpose-built for exactly the flatbed-scan case: it breaks a scan of several prints into separate documents and deskews them as it goes. If you have a scanner full of photo pages every week, that is the better tool and it is not close. Be aware of its one real weakness, which Adobe's own community documents at length — it predates machine learning entirely, and it wants a clean white background. Handwriting, stains or album residue between the photos will confuse it.

For panels you mark out yourself, Photoshop's other answer is slices: cut the image up with the Slice tool, then use **File → Save for Web**, which writes every slice out as its own file. That is manual by definition, but it is exact, which is the trade.

Toon Boom Storyboard Pro exports panels as individual images natively — **File → Export → Bitmap** writes a separate file per panel — because the panels are real objects in the project rather than pixels in a flat image. Much of what ranks for storyboard-splitting searches is Toon Boom documentation, and it is worth knowing that those pages are answering a genuinely different question: how to export from a project you authored, not how to recover panels from a flat JPEG somebody sent you.

This tool is for the flat JPEG somebody sent you, when you do not have the project file and do not want to install anything.

## Where the split panels go next

Splitting is rarely the last step.

- Forty freshly cropped PNGs are a lot of megabytes. [Image Compressor](https://www.razi.pro/tools/image-compress) converts them to WebP in a batch and will typically take most of that weight back out.
- If you split a page apart to work on the panels and now need to hand back something reviewable, [Images to PDF](https://www.razi.pro/tools/images-to-pdf) reassembles them into a single document in the order you choose.
- If the storyboard was headed for animation, the panels are the input to the next stage — [everything that broke making an AI animated film](https://www.razi.pro/blog/making-an-ai-animated-film-with-veo-and-flow) covers what happens after the boards are done.

---

*Grid splitters are not bad tools. They are the right tool for a job that most people do not have. Once you know which job you have, the choice takes a second.*