Microdeck.tools 100% In-Browser

Sprite Sheet Packer & Grid Tile Splitter

New

Essential asset workbench for indie game developers, frontend engineers, and social carousels. Pack individual PNG/SVG icons or game frames into a single transparent sprite sheet PNG with generated CSS classes, or upload a single image/tileset and export cleanly cropped `N × M` individual tile PNGs.

100% In-Browser No Server Storage Instant Results
Generated CSS Background Positions

Did this tool save you time? Help keep Microdeck free and maintained. Completely optional · From $3.

How It Works Under the Hood

Pack mode measures max frame bounds, computes padded shelf grid coordinates `(x, y)` per frame, composites sprites onto a transparent HTML5 Canvas, and emits ready CSS `.sprite-*` classes. Split mode divides source pixel dimensions evenly across `cols × rows` using integer floor boundaries (`Math.floor(i * dim / count)`) to drop exact lossless tile crops.

Step-by-Step Instructions

1

Pick **Pack Sprite Atlas + CSS** to combine sprites, or **Split Image into N×M Tiles** to slice one image.

2

In Pack mode: add sprite files, choose Columns and Padding px, copy generated CSS rules, and download `sprite-sheet.png`.

3

In Split mode: upload one image, configure Columns × Rows (`e.g. 3×3`), and click any generated tile card to download individual PNG slices.

Key Features & Performance

  • Dual utility: packs transparent sprite atlases AND splits tilesets/carousels without installing ImageMagick
  • Auto-generates CSS `background-position` classes matching every uploaded filename cleanly
  • Pixel-exact boundary splitting avoids missing 1px seams even when dimensions aren't evenly divisible
  • Preserves PNG alpha transparency across both packing and splitting pipelines
  • 100% browser-side: safe for commercial game assets and unreleased UI icon sets

Methodology, Formulas & Technical Standards

Atlas packing aligns cells to `(maxFrameW, maxFrameH)` shelf pitch separated by `padding` pixels (`x = pad + col * (cellW + pad)`), preventing adjacent sprite bleeding during subpixel GPU texture sampling.

Common Real-World Use Cases

  • Bundling small pixel-art game animation frames into a unified texture atlas locally
  • Generating CSS sprite sheets + `.sprite-*` coordinates for lightweight static web icons
  • Splitting 3×3 Instagram profile grid banners or RPG tilesets into individual tile PNGs
  • Inspecting exact pixel bounding offsets (`x, y, width, height`) before loading atlases in Canvas/Phaser/PixiJS

Worked Examples & Edge Cases

Pack 4 UI Icons (32×32) with 4px Margin

Input
4 icons | Cols: 4 | Pad: 4px
Output
Atlas: 148×40px PNG + `.sprite-icon { background-position: ... }` CSS

Zero-padding edges remain crisp when scaled smoothly on retina screens.

Slice 1200×1200 Art into 3×3 Grid

Input
Image: 1200×1200 | 3 cols × 3 rows
Output
9 tiles (`tile_r1_c1.png` ... `tile_r3_c3.png`), each 400×400 px

Download individual slices cleanly without quality loss.

Limitations, Scope & Accuracy Notes

  • • Atlas packing uses uniform cell pitch (`maxWidth × maxHeight`) rather than irregular bin-packing polygons — best suited for icons and consistent animation frames.
  • • In Split mode, very large grids (`10×10 = 100` tiles) trigger individual click downloads cleanly to avoid browser popup blockers.

Local Browser Processing & Privacy

Traditional web converters upload your documents, snippets, or media files to remote servers. Sprite Sheet Packer & Grid Tile Splitter runs inside your browser tab:

Processed in This Tab

Your input text and files are processed locally without uploading payloads to a processing server.

No Tool Payload Logging

Microdeck does not log or store the files or inputs you paste into tool workspaces (normal static hosting/CDN requests still load page assets).

Tab Memory Lifecycle

Working outputs stay in your browser tab and are released when you reset the tool or close the tab.

Frequently Asked Questions

Why does Pack mode add pixel padding between frames?

GPU texture sampling and browser CSS zooming can bleed adjacent pixels at non-integer DPR scales; 2–4px transparent padding eliminates edge artifacts.

Are alpha-transparent PNG backgrounds preserved?

Yes. Both atlas packing and tile splitting write directly onto cleared transparent `image/png` canvases.

Does splitting handle odd image dimensions like 1000×1000 ÷ 3?

Yes. Using progressive floor boundaries (`floor(i*w/N)`), adjacent tiles cover every pixel seamlessly from `0` to `1000` without gaps or overlaps.

Are game sprites or artwork sent to any backend?

No. Everything processes inside browser canvas memory.

Explore Related Micro-Tools

Support Microdeck

Completely optional · From $3 · No account required

Choose an amount (USD):Selected:$5

Minimum support amount is $3 USD.

Completely optional · From $3 · Checkout opens on Gumroad.