Cut Image Into Strips

If the image dimension doesn’t divide evenly by the strip count, extra pixels are added to the first N strips. Example: 1000 px wide, 7 strips → base = 142, remainder = 6 → first 6 strips are 143 px, last is 142 px. Total = 6 × 143 + 1 × 142 = 1000. Visually you may notice the slightly-narrower last strip if you butt them next to each other; for most uses (sprite sheets, parallax, poster tiles) it’s invisible.

Vertical strips (default): image cut into vertical slices like a sliced cake from the top. Good for: sprite sheets (animation frames are typically vertical strips), tall banner ads, parallax background layers (each strip moves at a different speed).

The strips are already-compressed image formats (PNG, JPEG, WebP). Trying to compress already-compressed data with DEFLATE gains less than 0.5% in most cases – sometimes slightly increases the size due to compression metadata. STORE (method 0 in the ZIP spec) just packages the bytes verbatim. Saves ~30 KB of JS that a DEFLATE implementation would cost, with negligible size impact. The ZIP file still opens in every ZIP utility (7-Zip, macOS Archive, Windows Explorer) because STORE is universally supported.

Download ZIP: one file, opens in any archive tool, browser doesn’t prompt N times. Works reliably even when batch downloads are blocked. Recommended.

Soft cap for performance + sanity. Each strip is rendered to its own canvas and re-encoded – at 50 strips on a 4K image, that’s 50 canvas allocations + 50 toBlob calls ≈ 200-500 ms total. If you genuinely need 100+ strips, drop the cap in the HTML – the underlying logic handles any count up to the image’s pixel dimension in the chosen direction.

Not supported – this tool divides into equal strips only. For non-equal slicing (e.g., header at 80 px, body at 400 px, footer at 80 px), use the sibling tool Cut Image for precise pixel-coord cropping, run it multiple times, and download each separately. Or use a desktop editor like GIMP / Photoshop for visual region selection.

Depends on output format. PNG and WebP-lossless: pixel-identical (re-encoded but no quality loss). JPEG and WebP-lossy: re-encoded with the quality slider value, which means SOME quality loss even at 100. For JPEG sources, expect minor recompression artifacts. EXIF, ICC profiles, and JPEG quantization tables are NOT preserved (canvas re-encodes from scratch).

Canvas API can’t emit animated GIF. Only the first frame is read and emitted as a static PNG/JPEG/WebP (your choice via format selector). To slice animated GIFs while preserving animation, you’d need a GIF encoder library (~150 KB), which isn’t worth it for a tool this small. For animated GIFs, use ezgif.com’s split tool or a desktop editor.

Yes. The image is loaded via FileReader into a Canvas in your browser. The ZIP file is built in memory and offered for download – never uploaded. Object URLs are revoked when you change settings or reset (memory freed). Nothing is logged anywhere.