Image splitter for exact grids, tiles, and sprite frames

01

How the image splitter turns one source into exact tiles

image splitter — Preview every cut before generating individual files

image splitter — Choose rows and columns when the finished grid matters most. The image splitter divides the usable source area as evenly as possible and assigns any remainder pixels deterministically, so neighboring tiles cover the full source without hidden gaps. Presets handle halves, quarters, and a 3 by 3 grid, while custom values support up to 20 rows and 20 columns.

Choose exact tile size when a runtime, print workflow, or sprite sheet already specifies frame dimensions. The image splitter starts after the outer margin, advances by tile width plus gutter, and keeps a smaller final edge tile when the source does not divide evenly. Margin and gutter remain at zero for ordinary photos but make regular sprite sheets and icon atlases practical.

image splitter — The numbered preview maps every rectangle to its output filename before export. Standard order starts at the top-left and moves across each row; reverse order assigns file 01 to the bottom-right, which can help with publishing sequences. Download one tile for inspection or encode the complete set into a browser-created ZIP only after the plan looks correct.

• image splitter — Use a 2 by 1 grid for left and right halves.
• image splitter — Use a 1 by 2 grid for top and bottom halves.
• image splitter — Use 3 by 3 for nine equal social or print panels.
• image splitter — Use exact tile size with margin and gutter for sprite frames.

02

image splitter — Choose rows, columns, or an exact tile size

image splitter — Every cut maps to a source-pixel rectangle

The image splitter calculates rectangles from the intrinsic pixel width and height reported after decoding. In grid mode it subtracts the selected outer margin and gutters, then distributes the remaining width and height across the requested columns and rows. In exact-size mode it advances by the requested tile dimensions and includes a smaller last rectangle only when pixels remain. The preview uses the same plan as the file encoder, so its labels, row and column positions, dimensions, and output names are not a separate approximation.

03

image splitter — Keep the source file private

image splitter — Local File and Canvas APIs avoid a processing upload

The image splitter accepts one locally selected File and decodes it with createImageBitmap(). Canvas drawImage() receives a source rectangle for each tile and copies only that rectangle into a temporary export canvas. The implementation does not contain an upload request, account project, or remote processing endpoint. Clearing the workspace closes the decoded bitmap and revokes its local object URL; the source file on the device is never overwritten.

04

image splitter — Export one tile or a complete ZIP

image splitter — Format, quality, and filenames stay explicit

The image splitter can save PNG, JPEG, or WebP according to current browser support. PNG is a dependable choice for text, hard edges, and transparency; JPEG trades transparency for compact photographic output; WebP is useful when the destination supports it. A single-tile action encodes only the chosen rectangle. ZIP export encodes the full ordered plan, applies a zero-padded filename, stores each Blob in one archive, and reports progress while the browser works.

05

How this image splitter is verified

image splitter — Official sources and reproducible geometry checks

The image splitter verification uses controlled color fixtures whose dimensions make the expected crop boundaries unambiguous. Checks load one file, exercise grid and exact-size modes, include nonzero margin and gutter values, compare tile coordinates with the preview, reopen exported dimensions, and inspect a ZIP directory. Source inspection separately rejects fetch, XMLHttpRequest, WebSocket, EventSource, and sendBeacon primitives so the stated browser-local boundary remains testable rather than implied by marketing copy.